From: "Andy Yan" <andyshrk@163.com>
To: dianders@chromium.org
Cc: quic_jesszhan@quicinc.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, neil.armstrong@linaro.org,
tzimmermann@suse.de, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re:Re:[PATCH] drm/panel-edp: Add BOE NV140FHM-N4Z panel entry
Date: Tue, 14 Jan 2025 17:04:56 +0800 (CST) [thread overview]
Message-ID: <341c653.7fa6.194640f0f37.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <34a1058f.9829.1945f2b448c.Coremail.andyshrk@163.com>
Hi All,
At 2025-01-13 18:17:38, "Andy Yan" <andyshrk@163.com> wrote:
>
>Sorry, please don't merge this patch. after further testing,
>I found that there are still some changce, it can't read edid.
It turns out that we need set hpd-reliable-delay-ms = 120 in dts to ensure
the right time to access edid.
So the patch is ok, it is ready for review.
>
>At 2025-01-13 16:59:54, "Andy Yan" <andyshrk@163.com> wrote:
>>Add an eDP panel entry for BOE NV140FHM-N4Z.
>>
>>No datasheet found for this panel.
>>
>>edid:
>>00 ff ff ff ff ff ff 00 09 e5 09 0b 00 00 00 00
>>01 20 01 04 a5 1f 11 78 03 9b 75 99 5b 5d 8f 2a
>>23 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
>>01 01 01 01 01 01 c8 37 80 cc 70 38 28 40 6c 30
>>aa 00 35 ae 10 00 00 1a 00 00 00 fd 00 30 3c 43
>>43 8f 01 0a 20 20 20 20 20 20 00 00 00 fe 00 42
>>4f 45 20 48 46 0a 20 20 20 20 20 20 00 00 00 fe
>>00 4e 56 31 34 30 46 48 4d 2d 4e 34 5a 0a 00 35
>>
>>Signed-off-by: Andy Yan <andyshrk@163.com>
>>---
>>
>> 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 94a46241dece..a3402b76aa3e 100644
>>--- a/drivers/gpu/drm/panel/panel-edp.c
>>+++ b/drivers/gpu/drm/panel/panel-edp.c
>>@@ -1909,6 +1909,7 @@ static const struct edp_panel_entry edp_panels[] = {
>> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0ac5, &delay_200_500_e50, "NV116WHM-N4C"),
>> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0ae8, &delay_200_500_e50_p2e80, "NV140WUM-N41"),
>> EDP_PANEL_ENTRY('B', 'O', 'E', 0x0b34, &delay_200_500_e80, "NV122WUM-N41"),
>>+ EDP_PANEL_ENTRY('B', 'O', 'E', 0x0b09, &delay_200_500_e50_p2e200, "NV140FHM-NZ"),
>> 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', 0x0b66, &delay_200_500_e80, "NE140WUM-N6G"),
>>--
>>2.43.0
next prev parent reply other threads:[~2025-01-14 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 8:59 [PATCH] " Andy Yan
2025-01-13 10:17 ` Andy Yan
2025-01-14 9:04 ` Andy Yan [this message]
2025-01-14 9:11 ` [PATCH] " Thomas Zimmermann
2025-01-14 16:44 ` Doug Anderson
2025-01-15 9:45 ` Andy Yan
2025-01-15 17:40 ` Doug Anderson
2025-01-15 9:55 ` [PATCH] " Thomas Zimmermann
2025-01-15 17:41 ` Doug Anderson
2025-01-15 10:15 ` Re:Re: " Andy Yan
2025-01-15 17:51 ` Doug Anderson
2025-01-16 1:04 ` Andy Yan
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=341c653.7fa6.194640f0f37.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=tzimmermann@suse.de \
/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®