From: Krzysztof Kozlowski <krzk@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>, Conor Dooley <conor@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <jesszhan0024@gmail.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>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: display: panel: Add Novatek NT37705
Date: Tue, 5 May 2026 09:25:54 +0200 [thread overview]
Message-ID: <dd7ebb25-014c-4983-ae31-6a6cbd24e628@kernel.org> (raw)
In-Reply-To: <DIAJCURQ37FA.1CNEKX6QM6ZO8@fairphone.com>
On 05/05/2026 08:40, Luca Weiss wrote:
>>>>> + compatible:
>>>>> + contains:
>>>>> + const: boe,bj631jhm-t71-d900
>>>>
>>>> Compatible doesn't match the filename, nor does the commit message match
>>>> what you've got here. Sounds like you're missing a fallback to
>>>> $filename.
>>>
>>> The last times I was upstreaming panel drivers (Feb 2024 and June 2025),
>>> this was the requested way of doing things.
>>
>> So this was requested that time and is requested now. What is here
>> uncertain?
>>
>>>
>>> Compatible being the company and model number making the actual panel
>>> assembly (driver IC + touchscreen + glass etc), while the rest being
>>> named after the driver IC manufacturer & number.
>>
>> So exactly what was asked for...
>
> I don't quite understand what is asked for now, that's my issue.
>
> 1. Change the filename to boe,bj631jhm-t71-d900.yaml and leave the rest
> as-is.
>
> 2. Add a fallback compatible for novatek,nt37705. IIRC last time it was
> argued that a "generic" nt37705 driver will never be correct for a
> specific panel since it's missing a bunch of panel-specific init. So
> that's why there should not be a fallback to nt37705.
To my limited knowledge the (2) with fallback describing the specific IC
is preferred, because that compatible although not currently usable is
still specific and describes actual IC used. I imagine that such
fallback still could be useful to some SW implementation to determine
the IC and act based on that.
If you have sources of other preference, please share, but I just gave
same review to Neil for his ayaneo,wt0600-2k panels.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-05 7:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 13:52 [PATCH 0/4] Add Novatek NT37705 panel driver for Fairphone (Gen. 6) Luca Weiss
2026-05-01 13:52 ` [PATCH 1/4] dt-bindings: display: panel: Add Novatek NT37705 Luca Weiss
2026-05-01 15:51 ` Conor Dooley
2026-05-04 13:36 ` Luca Weiss
2026-05-04 20:45 ` Krzysztof Kozlowski
2026-05-04 20:47 ` Krzysztof Kozlowski
2026-05-05 6:40 ` Luca Weiss
2026-05-05 7:25 ` Krzysztof Kozlowski [this message]
2026-05-01 13:52 ` [PATCH 2/4] drm/panel: Add driver for Novatek NT37705 panel Luca Weiss
2026-05-01 18:17 ` David Heidelberg
2026-05-01 13:52 ` [PATCH 3/4] arm64: defconfig: Enable " Luca Weiss
2026-05-04 22:41 ` Dmitry Baryshkov
2026-05-01 13:52 ` [PATCH 4/4] arm64: dts: qcom: milos-fairphone-fp6: Enable display Luca Weiss
2026-05-04 22:40 ` 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=dd7ebb25-014c-4983-ae31-6a6cbd24e628@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=maarten.lankhorst@linux.intel.com \
--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=~postmarketos/upstreaming@lists.sr.ht \
/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