From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Robinson <pbrobinson@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Peter Geis <pgwipeout@gmail.com>
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: add overlay for RockPro64 screen
Date: Tue, 10 Jun 2025 12:48:50 +0200 [thread overview]
Message-ID: <78773d27-d815-4fac-a131-275bde51788d@kernel.org> (raw)
In-Reply-To: <62276efe-13ca-448c-ad1d-ec0a8657737f@kernel.org>
On 10/06/2025 12:44, Krzysztof Kozlowski wrote:
> On 18/05/2025 23:59, Peter Robinson wrote:
>> The Pine64 touch panel is a panel consisting of the Feiyang fy07024di26a30d
>> panel with a Goodix gt911 touch screen. Add a device tree overlay to
>> allow the display to be easily used on the device.
>>
>> This was previously included in the main device tree but left disabled
>> by default which still required rebuilding the DT to use the device, now
>> overlays can go upstream the overlay is the best way to handle the
>> add on devices.
>>
>> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
>> ---
>> arch/arm64/boot/dts/rockchip/Makefile | 9 ++
>> .../dts/rockchip/rk3399-rockpro64-screen.dtso | 89 +++++++++++++++++++
>> 2 files changed, 98 insertions(+)
>> create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-rockpro64-screen.dtso
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/Makefile b/arch/arm64/boot/dts/rockchip/Makefile
>> index 3e8771ef69ba1..c7b13bff3ac20 100644
>> --- a/arch/arm64/boot/dts/rockchip/Makefile
>> +++ b/arch/arm64/boot/dts/rockchip/Makefile
>> @@ -77,6 +77,7 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-rock-pi-4c.dtb
>> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-rock960.dtb
>> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-rockpro64-v2.dtb
>> dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-rockpro64.dtb
>> +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3399-rockpro64-screen.dtso
>
>
> This was absolutely never built as reported by Naresh. You should never
> sent patches which are at least built tested... although they should be
> actually tested as well, but if code does not build actual testing is
> impossible.
Huh, I was wrong - this actually builds, just cannot execute install target.
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-06-10 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 21:59 [PATCH 1/2] arm64: dts: rockchip: drop touch panel display from rockpro64 Peter Robinson
2025-05-18 21:59 ` [PATCH 2/2] arm64: dts: rockchip: add overlay for RockPro64 screen Peter Robinson
2025-06-10 10:44 ` Krzysztof Kozlowski
2025-06-10 10:48 ` Krzysztof Kozlowski [this message]
2025-06-10 11:15 ` Heiko Stübner
2025-06-10 11:33 ` Diederik de Haas
2025-06-10 12:20 ` Diederik de Haas
2025-06-09 10:23 ` [PATCH 1/2] arm64: dts: rockchip: drop touch panel display from rockpro64 Heiko Stuebner
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=78773d27-d815-4fac-a131-275bde51788d@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pbrobinson@gmail.com \
--cc=pgwipeout@gmail.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