From: "Adil Hüsrev Tepe" <tadilhusrev@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Neil Armstrong" <neil.armstrong@linaro.org>,
"Jessica Zhang" <jesszhan0024@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"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>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Michael McAllister" <me@michaelmcallister.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: display: panel: add Novatek NT36525
Date: Sun, 22 Nov 2026 10:52:35 +0300 [thread overview]
Message-ID: <20261122075235.2915534-1-tadilhusrev@gmail.com> (raw)
In-Reply-To: <20261121-brave-adamant-caribou-b01daa@quoll>
On Sat, Nov 21, 2026 at 12:09:21PM +0100, Krzysztof Kozlowski wrote:
> Still incorrectly threaded.
>
> I asked to use b4 for a reason. If you insist on not to, then at least
> follow standard process and standard guides of upstreaming work.
Understood, and sorry. I was sending each new version with
--in-reply-to pointing at v1, which is exactly what buried it. The next
version will be prepared and sent with b4, as a new thread.
> > + - enum:
> > + - novatek,nt36525-xcover5
>
> I don't get it, what is xcover5? This claims it is Novatek device. Why
> isn't this actual panel manufacturer?
You're right, Novatek only makes the controller. Samsung's vendor
kernel names the panel vendor as CSOT ("CSO" in its panel table), but
it doesn't give a part number, and I haven't found one in any public
source. I'll try to read it off the panel itself. If that fails, what
name would you accept for a CSOT panel whose part number isn't known?
> I don't understand why this cannot be part of other bindings... looks
> exactly like nt36536 or nt36672a
Agreed, it's the same shape as novatek,nt36536.yaml (three supplies,
reset, backlight), which already carries a CSOT panel. Would you prefer
the NT36525 panel added to that file, as a second compatible item with
a novatek,nt36525 fallback, or a separate file modelled on it?
Michael McAllister (Cc'd) has a DJN NT36525B panel on the Moto G10 that
would use the same driver, so I'd like to get the structure right
before his panel is added too.
> > + - port
>
> Drop port
Will do.
Thanks,
Adil
next prev parent reply other threads:[~2026-11-22 7:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 7:02 [PATCH v1 0/2] drm/panel: add Novatek NT36525 (Samsung Galaxy XCover5) Adil Hüsrev Tepe
2026-11-16 7:02 ` [PATCH v1 1/2] dt-bindings: display: panel: add Novatek NT36525 Adil Hüsrev Tepe
2026-11-16 7:14 ` sashiko-bot
2026-11-16 7:02 ` [PATCH v1 2/2] drm/panel: add Novatek NT36525 panel driver Adil Hüsrev Tepe
2026-11-16 7:22 ` sashiko-bot
2026-11-17 10:43 ` [PATCH v2 1/2] dt-bindings: display: panel: novatek,nt36525: fix v1 review issues Adil Hüsrev Tepe
2026-11-17 10:43 ` [PATCH v2 2/2] drm/panel: novatek-nt36525: " Adil Hüsrev Tepe
2026-11-17 10:47 ` Krzysztof Kozlowski
2026-11-17 17:33 ` Adil Hüsrev Tepe
2026-11-17 17:33 ` [PATCH v3 0/2] drm/panel: add Novatek NT36525 (Samsung Galaxy XCover5) Adil Hüsrev Tepe
2026-11-17 17:33 ` [PATCH v3 1/2] dt-bindings: display: panel: add Novatek NT36525 Adil Hüsrev Tepe
2026-11-17 17:33 ` [PATCH v3 2/2] drm/panel: add Novatek NT36525 panel driver Adil Hüsrev Tepe
2026-11-18 7:48 ` Uwe Kleine-König
2026-11-18 15:53 ` [PATCH v3 0/2] drm/panel: add Novatek NT36525 (Samsung Galaxy XCover5) Michael McAllister
2026-11-22 7:52 ` Adil Hüsrev Tepe
2026-11-20 11:40 ` [PATCH v4 " Adil Hüsrev Tepe
2026-11-20 11:40 ` [PATCH v4 1/2] dt-bindings: display: panel: add Novatek NT36525 Adil Hüsrev Tepe
2026-11-21 11:09 ` Krzysztof Kozlowski
2026-11-22 7:52 ` Adil Hüsrev Tepe [this message]
2026-11-20 11:41 ` [PATCH v4 2/2] drm/panel: add Novatek NT36525 panel driver Adil Hüsrev Tepe
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=20261122075235.2915534-1-tadilhusrev@gmail.com \
--to=tadilhusrev@gmail.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=me@michaelmcallister.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@baylibre.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