From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Abel Vesa <abel.vesa@linaro.org>, Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 1/5] dt-bindings: display: panel: samsung,atna33xc20: Document ATNA45AF01
Date: Wed, 10 Jul 2024 21:03:06 +0200 [thread overview]
Message-ID: <Zo7a6qso7RZ2pkmb@linaro.org> (raw)
In-Reply-To: <CAD=FV=XJuV12mStW3eUm5MHG8BA9W_fn0skN=BrtmqC+fnCZig@mail.gmail.com>
On Wed, Jul 10, 2024 at 10:35:28AM -0700, Doug Anderson wrote:
> On Wed, Jul 10, 2024 at 10:05 AM Stephan Gerhold
> <stephan.gerhold@linaro.org> wrote:
> >
> > The Samsung ATNA45AF01 panel is an AMOLED eDP panel that has backlight
> > control over the DP AUX channel. While it works almost correctly with the
> > generic "edp-panel" compatible, the backlight needs special handling to
> > work correctly. It is similar to the existing ATNA33XC20 panel, just with
> > a larger resolution and size.
> >
> > Add a new "samsung,atna45af01" compatible to describe this panel in the DT.
> >
> > Signed-off-by: Stephan Gerhold <stephan.gerhold@linaro.org>
> > ---
> > .../devicetree/bindings/display/panel/samsung,atna33xc20.yaml | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml b/Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml
> > index 765ca155c83a..d668e8d0d296 100644
> > --- a/Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml
> > +++ b/Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml
> > @@ -14,7 +14,11 @@ allOf:
> >
> > properties:
> > compatible:
> > - const: samsung,atna33xc20
> > + enum:
> > + # Samsung 13.3" FHD (1920x1080 pixels) eDP AMOLED panel
> > + - samsung,atna33xc20
> > + # Samsung 14.5" WQXGA+ (2880x1800 pixels) eDP AMOLED panel
> > + - samsung,atna45af01
>
> Seems OK, but a few thoughts:
>
> 1. Is it worth renaming this file? Something like
> "samsung,atna-oled-panel.yaml"? I'd be interested in DT maintainer
> folks' opinions here.
>
I think examples for both approaches exist in the kernel tree, so I am
also interested in the opinion of the DT maintainers here. :-)
> 2. In theory you could make your compatible look like this:
>
> compatible = "samsung,atna45af01", "samsung,atna33xc20"
>
> ...which would say "I have a 45af01 but if the OS doesn't have
> anything special to do that it would be fine to use the 33xc20
> driver". That would allow device trees to work without the kernel
> changes and would allow you to land the DT changes in parallel with
> the driver changes and things would keep working.
>
> ...and, in fact, that would mean you _didn't_ need to add the new
> compatible string to the driver, which is nice.
>
Yeah, I considered this. I mentioned the reason why I decided against
this in patch 2:
> While ATNA45AF01 would also work with "samsung,atna33xc20" as a fallback
> compatible, the original submission of the compatible in commit
> 4bfe6c8f7c23 ("drm/panel-simple: Add Samsung ATNA33XC20") had the timings
> and resolution hardcoded. These would not work for ATNA45AF01.
Basically, it works with the current driver. But if you would run the
kernel at the state of the original submission then it would behave
incorrectly. This is why I considered the resolution and timings to be
part of the "samsung,atna33xc20" "ABI". The new panel would not be
compatible with that.
I don't mind changing it, if there is consensus that we should ignore
this and use the fallback compatible instead.
Thanks,
Stephan
next prev parent reply other threads:[~2024-07-10 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 17:04 [PATCH 0/5] drm/panel: atna33xc20: Fix the Samsung ATNA45AF01 panel Stephan Gerhold
2024-07-10 17:04 ` [PATCH 1/5] dt-bindings: display: panel: samsung,atna33xc20: Document ATNA45AF01 Stephan Gerhold
2024-07-10 17:35 ` Doug Anderson
2024-07-10 19:03 ` Stephan Gerhold [this message]
2024-07-10 19:16 ` Doug Anderson
2024-07-12 10:11 ` Stephan Gerhold
2024-07-11 6:27 ` Krzysztof Kozlowski
2024-07-11 6:25 ` Krzysztof Kozlowski
2024-07-10 17:04 ` [PATCH 2/5] drm/panel: samsung-atna33xc20: Add compatible for ATNA45AF01 Stephan Gerhold
2024-07-10 17:35 ` Doug Anderson
2024-07-10 17:04 ` [PATCH 3/5] Revert "drm/panel-edp: Add SDC ATNA45AF01" Stephan Gerhold
2024-07-10 17:35 ` Doug Anderson
2024-07-10 17:05 ` [PATCH 4/5] arm64: dts: qcom: x1e80100-crd: Fix backlight Stephan Gerhold
2024-07-10 22:07 ` Konrad Dybcio
2024-07-10 17:05 ` [PATCH 5/5] arm64: defconfig: Add CONFIG_DRM_PANEL_SAMSUNG_ATNA33XC20 Stephan Gerhold
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=Zo7a6qso7RZ2pkmb@linaro.org \
--to=stephan.gerhold@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=johan@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@kernel.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