From: Judith Mendez <jm@ti.com>
To: Markus Schneider-Pargmann <msp@baylibre.com>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Tero Kristo <kristo@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH 0/3] arm64: dts: ti: k3-am62a/p: Add r5fss nodes
Date: Wed, 26 Feb 2025 08:58:28 -0600 [thread overview]
Message-ID: <8cf95899-bebb-46a2-843e-debdfb5079ff@ti.com> (raw)
In-Reply-To: <qlqxmqluqrw36bkjaa7efcsk6cinyr2rxvznfhz6dopeu67dsf@w4lkuq65uwno>
Hi Markus,
On 2/25/25 4:28 AM, Markus Schneider-Pargmann wrote:
> Hi Judith,
>
> On Mon, Feb 24, 2025 at 09:06:56AM -0600, Judith Mendez wrote:
>> Hi Markus,
>>
>> On 1/22/25 3:54 AM, Markus Schneider-Pargmann wrote:
>>> Hi,
>>>
>>> am62p-wakeup already has the r5fss node defined, but it is currently
>>> missing from the am62a-wakeup domain in the devicetree. This is added as
>>> part of the series.
>>>
>>> For am62a and am62p starter kit boards the r5fss memory region is added
>>> and referenced for the r5fss core 0 node.
>>
>>
>> This has already been sent here:
>> https://lore.kernel.org/linux-devicetree/20250210221530.1234009-1-jm@ti.com/
>
> yes, I saw that recently. Could you please cc me on the next version?
>
Sure no problem. (:
> Thanks!
>
> Best
> Markus
prev parent reply other threads:[~2025-02-26 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 9:54 Markus Schneider-Pargmann
2025-01-22 9:54 ` [PATCH 1/3] arm64: dts: ti: k3-am62a-wakeup: Add r5fss Markus Schneider-Pargmann
2025-01-22 9:54 ` [PATCH 2/3] arm64: dts: ti: k3-am62a7-sk: Add r5fss memory region Markus Schneider-Pargmann
2025-01-22 9:54 ` [PATCH 3/3] arm64: dts: ti: k3-am62p5-sk: " Markus Schneider-Pargmann
2025-02-24 15:06 ` [PATCH 0/3] arm64: dts: ti: k3-am62a/p: Add r5fss nodes Judith Mendez
2025-02-25 10:28 ` Markus Schneider-Pargmann
2025-02-26 14:58 ` Judith Mendez [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=8cf95899-bebb-46a2-843e-debdfb5079ff@ti.com \
--to=jm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msp@baylibre.com \
--cc=nm@ti.com \
--cc=robh@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
all inboxes | Powered by JetHome®