On 2/5/22 01:13, Douglas Anderson wrote: > Recently we added generic "edp-panel"s probed by EDID. To support > panels in this way we look at the panel ID in the EDID and look up the > panel in a table that has power sequence timings. If we find a panel > that's not in the table we will still attempt to use it but we'll use > conservative timings. While it's likely that these conservative > timings will work for most nearly all panels, the performance of > turning the panel off and on suffers. > > We'd like to be able to reliably detect the case that we're using the > hardcoded timings without relying on parsing dmesg. This allows us to > implement tests that ensure that no devices get shipped that are > relying on the conservative timings. > > Let's add a new debugfs entry to panel devices. It will have one of: > * UNKNOWN - We tried to detect a panel but it wasn't in our table. > * HARDCODED - We're not using generic "edp-panel" probed by EDID. > * A panel name - This is the name of the panel from our table. > > Signed-off-by: Douglas Anderson <diand...@chromium.org> > ---
Reviewed-by: Javier Martinez Canillas <javi...@redhat.com> Best regards, -- Javier Martinez Canillas Linux Engineering Red Hat
