From: Dave Gerlach <d-gerlach@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Suman Anna <s-anna@ti.com>, Rob Herring <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, Tony Lindgren <tony@atomide.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
Kishon Vijay Abraham <kishon@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
Aswath Govindraju <a-govindraju@ti.com>
Subject: Re: [PATCH 2/3] arm64: dts: ti: Add Support for AM642 SoC
Date: Tue, 5 Jan 2021 09:53:06 -0600 [thread overview]
Message-ID: <8a3c7296-f372-5392-2e6e-2cc6e0510adf@ti.com> (raw)
In-Reply-To: <20210105151220.vy42nw7uwv5ax3z6@library>
On 1/5/21 9:12 AM, Nishanth Menon wrote:
> On 22:02-20210104, Dave Gerlach wrote:
>>>> This is atleast missing the ranges for On-Chip SRAM and the R5FSS, but those can
>>>> always be added incrementally as well.
>>
>> Yes, I think they should be added incrementally once a user is present.
>>
>
>
> Most of the driver dependencies are resolved in v5.11-rc1. So, you
> should be able to add a lot of devices (aka users) instead of making
> this a barebones dts as the first introduction - I see no benefit of
> things coming in piece meal - other than creating all kind of dependency
> mayhem that I don't want to deal with.
>
> Please make sure that all nodes for all peripherals that can be
> introduced in v5.11-rc1 is part of this introduction of device.
>
Yeah that's no issue, I will add those that Suman referenced for v2 and
then that covers every entry I am currently aware of.
Regards,
Dave
next prev parent reply other threads:[~2021-01-05 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 5:20 [PATCH 0/3] arm64: Initial support for Texas Instruments AM642 Platform Dave Gerlach
2020-11-25 5:20 ` [PATCH 1/3] dt-bindings: arm: ti: Add bindings for AM642 SoC Dave Gerlach
2020-12-08 16:03 ` Rob Herring
2020-11-25 5:20 ` [PATCH 2/3] arm64: dts: ti: Add Support " Dave Gerlach
2020-12-03 21:56 ` Suman Anna
2020-12-03 22:00 ` Suman Anna
2021-01-05 4:02 ` Dave Gerlach
2021-01-05 15:12 ` Nishanth Menon
2021-01-05 15:53 ` Dave Gerlach [this message]
2021-01-05 16:14 ` Nishanth Menon
2020-12-04 13:17 ` Grygorii Strashko
2021-01-05 3:52 ` Dave Gerlach
2021-01-05 7:19 ` Vignesh Raghavendra
2020-11-25 5:20 ` [PATCH 3/3] arm64: dts: ti: Add support for AM642 EVM Dave Gerlach
2020-11-27 12:40 ` [PATCH 0/3] arm64: Initial support for Texas Instruments AM642 Platform Peter Ujfalusi
2020-11-27 14:25 ` Nishanth Menon
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=8a3c7296-f372-5392-2e6e-2cc6e0510adf@ti.com \
--to=d-gerlach@ti.com \
--cc=a-govindraju@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=tony@atomide.com \
--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).