From: "Andrew F. Davis" <afd@ti.com>
To: Suman Anna <s-anna@ti.com>, Tero Kristo <t-kristo@ti.com>,
Nishanth Menon <nm@ti.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] Add MCU SRAM nodes for TI K3 SoCs
Date: Thu, 6 Jun 2019 09:51:41 -0400 [thread overview]
Message-ID: <706a01f7-6953-73ec-d72a-62b4aac5dafa@ti.com> (raw)
In-Reply-To: <37a5bf73-2f93-8474-bca1-2e9fae4d6668@ti.com>
On 6/5/19 1:01 PM, Suman Anna wrote:
> On 6/5/19 11:53 AM, Andrew F. Davis wrote:
>> On 6/5/19 12:34 PM, Suman Anna wrote:
>>> Hi Tero,
>>>
>>> The following series adds the DT nodes for the MCU SRAM present within
>>> the MCU domain for both AM65x and J721E SoCs. The first 2 patches enable
>>> the MCU SRAM node to be probed properly on AM65x SoCs, and the third
>>> patch the equivalent for J721E SoCs. The third patch depends on the
>>> base J721E support patch series from Nishanth [1].
>>>
>>> The last patch is not related to MCU SRAM, but adds the ranges for the
>>> R5F cluster that is also present in the MCU domain in preparation for
>>> the R5F nodes.
>>>
>>
>> Why not have this last patch as part of the series adding the R5F nodes?
>
> The patch can be applied independently as is, no reason to wait until I
> post those.
>
No reason not to wait either.. plus it would keep related changes in the
same series.
Anyway, I don't have any problem with this, was just asking as I was not
sure if I was missing some hidden dependency between the nodes.
Andrew
> regards
> Suman
>
>>
>> Andrew
>>
>>> regards
>>> Suman
>>>
>>> [1]
>>> https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=121189
>>>
>>> Suman Anna (4):
>>> arm64: dts: ti: k3-am65: Add MCU SRAM ranges in interconnect nodes
>>> arm64: dts: ti: k3-am65-mcu: Add the MCU RAM node
>>> arm64: dts: ti: k3-j721e: Add the MCU SRAM node
>>> arm64: dts: ti: k3-am65: Add R5F ranges in interconnect nodes
>>>
>>> arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 8 ++++++++
>>> arch/arm64/boot/dts/ti/k3-am65.dtsi | 6 ++++++
>>> arch/arm64/boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 8 ++++++++
>>> 3 files changed, 22 insertions(+)
>>>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-06 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 16:34 [PATCH 0/4] Add MCU SRAM nodes for TI K3 SoCs Suman Anna
2019-06-05 16:34 ` [PATCH 1/4] arm64: dts: ti: k3-am65: Add MCU SRAM ranges in interconnect nodes Suman Anna
2019-06-05 16:34 ` [PATCH 2/4] arm64: dts: ti: k3-am65-mcu: Add the MCU RAM node Suman Anna
2019-06-05 16:34 ` [PATCH 3/4] arm64: dts: ti: k3-j721e: Add the MCU SRAM node Suman Anna
2019-06-18 14:43 ` Tero Kristo
2019-06-05 16:34 ` [PATCH 4/4] arm64: dts: ti: k3-am65: Add R5F ranges in interconnect nodes Suman Anna
2019-06-05 16:53 ` [PATCH 0/4] Add MCU SRAM nodes for TI K3 SoCs Andrew F. Davis
2019-06-05 17:01 ` Suman Anna
2019-06-06 13:51 ` Andrew F. Davis [this message]
2019-06-17 14:49 ` Tero Kristo
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=706a01f7-6953-73ec-d72a-62b4aac5dafa@ti.com \
--to=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nm@ti.com \
--cc=s-anna@ti.com \
--cc=t-kristo@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).