From: Olivier Benjamin <olivier.benjamin@bootlin.com>
To: Diederik de Haas <didi.debian@cknow.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] arm64: dts: rockchip: Fix the panel compatible for the PinePhone Pro
Date: Wed, 18 Jun 2025 16:11:49 +0200 [thread overview]
Message-ID: <865fc263-b3c6-470a-9fb8-3d6df51a2b74@bootlin.com> (raw)
In-Reply-To: <DAPPKP3OWLMU.C6HXTY24NZ4H@cknow.org>
On 6/18/25 15:54, Diederik de Haas wrote:
> On Wed Jun 18, 2025 at 12:32 AM CEST, Olivier Benjamin wrote:
>> As documented in its bindings, the compatible for the Himax HX8394
>> MIPI-DSI LCD panel controller is in 2 parts.
>> The PinePhone Pro DTS currently only specifies the first part of the
>> compatible, generating a warning.
>>
>> Signed-off-by: Olivier Benjamin <olivier.benjamin@bootlin.com>
>> ---
>> arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts b/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>> index 04ba4c4565d0a205e2e46d7535c6a3190993621d..5ebc380a24df86ba7172b0950b89cac56b61c507 100644
>> --- a/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>> +++ b/arch/arm64/boot/dts/rockchip/rk3399-pinephone-pro.dts
>> @@ -479,7 +479,7 @@ mipi_out_panel: endpoint {
>> };
>>
>> panel@0 {
>> - compatible = "hannstar,hsd060bhw4";
>> + compatible = "hannstar,hsd060bhw4", "himax,hx8394";
>> reg = <0>;
>> backlight = <&backlight>;
>> reset-gpios = <&gpio4 RK_PD1 GPIO_ACTIVE_LOW>;
>
> Reviewed-by: Diederik de Haas <didi.debian@cknow.org>
>
Thanks for the review.
> But I'd actually suggest to combine it with patch 3 and use that
> opportunity to also fix the property sorting, so you'd get 1 patch which
> fixes all of the panel issues.
>
Makes sense, I'll integrate your suggestions from the other 2 patches,
fix the property sorting, and squash the fixes into 1 commit/patch in v2.
> Cheers,
> Diederik
--
Olivier Benjamin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-06-18 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 22:31 [PATCH 0/3] Fix the Rockchip PinePhone Pro DTS warnings Olivier Benjamin
2025-06-17 22:32 ` [PATCH 1/3] arm64: dts: rockchip: Fix the panel compatible for the PinePhone Pro Olivier Benjamin
2025-06-18 13:54 ` Diederik de Haas
2025-06-18 14:11 ` Olivier Benjamin [this message]
2025-06-17 22:32 ` [PATCH 2/3] arm64: dts: rockchip: Fix the mipi port definition for RK3399 Olivier Benjamin
2025-06-18 13:50 ` Diederik de Haas
2025-06-18 14:14 ` Olivier Benjamin
2025-06-17 22:32 ` [PATCH 3/3] arm64: dts: rockchip: Remove unused property in PinePhone Pro MIPI panel Olivier Benjamin
2025-06-18 12:12 ` Diederik de Haas
2025-06-18 13:39 ` Olivier Benjamin
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=865fc263-b3c6-470a-9fb8-3d6df51a2b74@bootlin.com \
--to=olivier.benjamin@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).