From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Chris Morgan <macromorgan@hotmail.com>
Cc: Chris Morgan <macroalpha82@gmail.com>,
linux-rockchip@lists.infradead.org,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
sebastian.reichel@collabora.com, daniel@ffwll.ch,
airlied@gmail.com, sam@ravnborg.org, neil.armstrong@linaro.org,
heiko@sntech.de, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org
Subject: Re: [PATCH V2 4/4] arm64: dts: rockchip: add Powkiddy RK2023
Date: Fri, 10 Nov 2023 16:02:06 +0100 [thread overview]
Message-ID: <de9ef958-158d-4f56-8e76-9bfe62dfd6fe@linaro.org> (raw)
In-Reply-To: <SN6PR06MB5342CA386D24487297783A17A5AEA@SN6PR06MB5342.namprd06.prod.outlook.com>
On 10/11/2023 15:30, Chris Morgan wrote:
> On Fri, Nov 10, 2023 at 02:14:23PM +0100, Krzysztof Kozlowski wrote:
>>> +
>>> +/delete-node/ &adc_keys;
>>> +
>>> +&chosen {
>>> + /delete-property/ stdout-path;
>>> +};
>>
>> If you have to delete so many nodes and properties, this means your
>> common DTSI is not that common.
>>
>> Common DTSI means there is shared hardware. If you take shared hardware
>> and put it into another board, pieces of the shared hardware do not
>> disappear.
>>
>>
>> Best regards,
>> Krzysztof
>>
>
> I can redo this with a different top-level dtsi so I won't have to
> delete so much if that helps. I'll redo both the RGB30 and RK2023
> so that they use a common dtsi and no longer rely on the Anberic
> one. I'll do that and submit a V3.
I am not sure whether you need another top-level DTSI, but maybe rather
move things from common DTSI to each boards. Or you are using wrong
common DTSI. You are supposed to reference common DTSI if the hardware
parts are common. Don't use some DTSI just because DTS looks similar.
I did not investigate your hardware to give recommendation how DTS
should look like. But judging from node removals, something is not done
obvious way.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-11-10 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 21:50 [PATCH V2 0/4] rockchip: Add Powkiddy RK2023 Chris Morgan
2023-11-09 21:50 ` [PATCH V2 1/4] dt-bindings: display: panel: Update NewVision NV3051D compatibles Chris Morgan
2023-11-10 13:11 ` Krzysztof Kozlowski
2023-11-10 14:28 ` Chris Morgan
2023-11-10 14:52 ` Krzysztof Kozlowski
2023-11-09 21:50 ` [PATCH V2 2/4] nv3051d: Add Powkiddy RK2023 Panel Support Chris Morgan
2023-11-15 22:37 ` Jessica Zhang
2023-11-09 21:50 ` [PATCH V2 3/4] dt-bindings: arm: rockchip: Add Powkiddy RK2023 Chris Morgan
2023-11-10 13:12 ` Krzysztof Kozlowski
2023-11-09 21:50 ` [PATCH V2 4/4] arm64: dts: rockchip: add " Chris Morgan
2023-11-10 13:14 ` Krzysztof Kozlowski
2023-11-10 14:30 ` Chris Morgan
2023-11-10 15:02 ` Krzysztof Kozlowski [this message]
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=de9ef958-158d-4f56-8e76-9bfe62dfd6fe@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sebastian.reichel@collabora.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).