From: Clayton Craft <clayton@craftyguy.net>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/panel-edp: Add entry for BOE NV133WUM-N63 panel
Date: Tue, 9 Jul 2024 10:36:30 -0700 [thread overview]
Message-ID: <20240709103630.GC13955@craftyguy.net> (raw)
In-Reply-To: <20240520221836.16031-1-clayton@craftyguy.net>
On Mon, 20 May 2024 15:18:36 -0700 Clayton Craft <clayton@craftyguy.net> wrote:
> This panel is found on some laptops e.g., variants of the Thinkpad X13s.
>
> Signed-off-by: Clayton Craft <clayton@craftyguy.net>
> ---
> drivers/gpu/drm/panel/panel-edp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/panel/panel-edp.c b/drivers/gpu/drm/panel/panel-edp.c
> index 6db277efcbb7..f75db9917667 100644
> --- a/drivers/gpu/drm/panel/panel-edp.c
> +++ b/drivers/gpu/drm/panel/panel-edp.c
> @@ -2047,6 +2047,7 @@ static const struct edp_panel_entry edp_panels[] = {
> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0a5d, &delay_200_500_e50, "NV116WHM-N45"),
> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0ac5, &delay_200_500_e50, "NV116WHM-N4C"),
> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0b34, &delay_200_500_e80, "NV122WUM-N41"),
> + EDP_PANEL_ENTRY('B', 'O', 'E', 0x0a1b, &delay_200_500_e50, "NV133WUM-N63"),
> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0b43, &delay_200_500_e200, "NV140FHM-T09"),
> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0b56, &delay_200_500_e80, "NT140FHM-N47"),
> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0c20, &delay_200_500_e80, "NT140FHM-N47"),
> --
> 2.45.1
>
Any chance this can get picked up soon? Is there something else wrong with it?
Thanks! Clayton
next prev parent reply other threads:[~2024-07-09 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 22:18 [PATCH v3] drm/panel-edp: Add entry for BOE NV133WUM-N63 panel Clayton Craft
2024-07-09 17:36 ` Clayton Craft [this message]
2024-07-16 19:53 ` Dmitry Baryshkov
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=20240709103630.GC13955@craftyguy.net \
--to=clayton@craftyguy.net \
--cc=dri-devel@lists.freedesktop.org \
/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