From: Krzysztof Kozlowski <krzk@kernel.org>
To: Logan Bristol <l-bristol@ti.com>, Bryan Brattlof <bb@ti.com>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] arm64: dts: ti: introduce a minimal am642 device tree
Date: Wed, 10 Jul 2024 08:52:29 +0200 [thread overview]
Message-ID: <e5ded1c1-be7e-4e16-b175-f4bd4a121d3a@kernel.org> (raw)
In-Reply-To: <766dceb1-222a-401b-95e3-69b7fb331411@ti.com>
On 09/07/2024 18:20, Logan Bristol wrote:
>
> Hi all,
>
> On 3/22/22 13:14, Krzysztof Kozlowski wrote:
>> On 21/03/2022 16:54, Bryan Brattlof wrote:
>>> Texas Instrument's am642 is one of many k3 based, low cost, low power,
>>> chips designed to work in a wide range of applications spanning an even
>>> wider range of industries that TI is actively developing
>>>
>>> With its pin-mux and peripheral rich designs, these chips will likely
>>> have a multitude of custom device trees that range wildly from one
>>> another and (hopefully) guarantee an influx of variants into the kernel
>>> in the coming years
>>>
>>> With overlays no longer a thing, I wanted to ask for opinions on how
>>> we can best help integrate these dt files as they begin to be developed
>>>
>>> I also wanted to introduce a skeletonized (nothing but uart) device tree
>>> to give others a good starting point while developing their projects.
>>
>> Real hardware as DTS please. There is no need to add some skeleton for
>> specific SoC. What if every SoC goes that way?
>>
>> Feel free to create re-usable components in DTSI ways, still reflecting
>> some hardware parts.
>>
>
> I am working on a project for the AM62 and came across this email thread.
>
> Following Krzysztof's direction, I am wanting to submit a DTSI to serve
> as a minimal configuration for the existing boards based on the AM62
> SoC, which are currently defined by bloated DTS files.
>
> This DTSI file can be consumed by other board DTS files to reduce the
> configuration. Krzysztof, could this be merged upstream?
Aren't you writing something contradictory to what I wrote above? I do
not see your description matching my earlier guideline.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-10 6:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 15:54 [RFC] arm64: dts: ti: introduce a minimal am642 device tree Bryan Brattlof
2022-03-22 18:14 ` Krzysztof Kozlowski
2024-07-09 16:20 ` Logan Bristol
2024-07-10 6:52 ` Krzysztof Kozlowski [this message]
2024-07-15 14:12 ` Logan Bristol
2024-07-10 7:38 ` Francesco Dolcini
2024-07-15 14:02 ` Logan Bristol
2024-07-15 14:55 ` Francesco Dolcini
2022-03-30 13:55 ` Wadim Egorov
2022-03-31 6:58 ` Vignesh Raghavendra
2022-03-31 7:19 ` Wadim Egorov
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=e5ded1c1-be7e-4e16-b175-f4bd4a121d3a@kernel.org \
--to=krzk@kernel.org \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=l-bristol@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).