From: Javier Martinez Canillas <javierm@redhat.com>
To: Douglas Anderson <dianders@chromium.org>,
dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
robert.foss@linaro.org, linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
jjsu@chromium.org, lschyi@chromium.org,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] drm/panel-edp: Allow querying the detected panel via sysfs
Date: Tue, 25 Jan 2022 23:55:35 +0100 [thread overview]
Message-ID: <e89dbc7b-b3ae-c334-b704-f5633725c29f@redhat.com> (raw)
In-Reply-To: <20220125135406.1.I62322abf81dbc1a1b72392a093be0c767da9bf51@changeid>
Hello Doug,
On 1/25/22 22:54, 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 sysfs 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 <dianders@chromium.org>
> ---
Patch looks good to me.
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Should this new sysfs entry be documented in Documentation/ABI/ ?
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2022-01-25 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 21:54 Douglas Anderson
2022-01-25 22:55 ` Javier Martinez Canillas [this message]
2022-01-25 23:25 ` Doug Anderson
2022-01-26 8:25 ` Javier Martinez Canillas
2022-02-01 16:41 ` Doug Anderson
2022-02-01 17:02 ` Daniel Vetter
2022-02-01 17:22 ` Doug Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e89dbc7b-b3ae-c334-b704-f5633725c29f@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jjsu@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lschyi@chromium.org \
--cc=robert.foss@linaro.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®