The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Val Packett <val@packett.cool>
To: Douglas Anderson <dianders@chromium.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Jessica Zhang <quic_jesszhan@quicinc.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: Val Packett <val@packett.cool>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 4/4] drm/panel-edp: Add BOE NE14QDM panel for Dell Latitude 7455
Date: Sun, 25 May 2025 06:53:36 -0300	[thread overview]
Message-ID: <20250525095341.12462-6-val@packett.cool> (raw)
In-Reply-To: <20250525095341.12462-2-val@packett.cool>

Cannot confirm which variant exactly it is, as the EDID alphanumeric data
contains '0RGNR' <0x80> 'NE14QDM' and ends there; but it's 60 Hz and with
touch.

I do not have access to datasheets for these panels, so the timing is
a guess that was tested to work fine on this laptop.

Signed-off-by: Val Packett <val@packett.cool>
---
 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 90e8c154a978..ec7c1e21f2d2 100644
--- a/drivers/gpu/drm/panel/panel-edp.c
+++ b/drivers/gpu/drm/panel/panel-edp.c
@@ -1937,6 +1937,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', 0x0b09, &delay_200_500_e50_po2e200, "NV140FHM-NZ"),
+	EDP_PANEL_ENTRY('B', 'O', 'E', 0x0b1e, &delay_200_500_e80, "NE140QDM-N6A"),
 	EDP_PANEL_ENTRY('B', 'O', 'E', 0x0b34, &delay_200_500_e80, "NV122WUM-N41"),
 	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"),
-- 
2.49.0


  parent reply	other threads:[~2025-05-25  9:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25  9:53 [PATCH 0/4] Add support for Dell Latitude 7455 (X1E-80-100) Val Packett
2025-05-25  9:53 ` [PATCH 1/4] dt-bindings: arm: qcom: Add Dell Latitude 7455 Val Packett
2025-05-29  9:29   ` Krzysztof Kozlowski
2025-05-25  9:53 ` [PATCH 2/4] arm64: dts: qcom: Add support for X1E80100 " Val Packett
2025-05-25 13:25   ` Dmitry Baryshkov
2025-05-27 12:24     ` Manivannan Sadhasivam
2025-05-27 15:12       ` Stephan Gerhold
2025-05-27 11:25   ` Konrad Dybcio
2025-05-25  9:53 ` [PATCH 3/4] firmware: qcom: scm: Allow QSEECOM on " Val Packett
2025-05-25 13:12   ` Dmitry Baryshkov
2025-05-25  9:53 ` Val Packett [this message]
2025-05-25 13:11   ` [PATCH 4/4] drm/panel-edp: Add BOE NE14QDM panel for " Dmitry Baryshkov
2025-08-11 18:41 ` (subset) [PATCH 0/4] Add support for Dell Latitude 7455 (X1E-80-100) Bjorn Andersson

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=20250525095341.12462-6-val@packett.cool \
    --to=val@packett.cool \
    --cc=airlied@gmail.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=simona@ffwll.ch \
    --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