From: Hari Nagalla <hnagalla@ti.com>
To: Vignesh Raghavendra <vigneshr@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <nm@ti.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 4/4] arm64: dts: ti: k3-am62a7-sk: Enable ipc with remote proc nodes
Date: Mon, 10 Jun 2024 10:56:10 -0500 [thread overview]
Message-ID: <4405d53a-bb9b-24bc-9bbc-b5dbecefdba4@ti.com> (raw)
In-Reply-To: <1b03ae72-b1c4-4165-b3cc-df85255b9dbf@ti.com>
On 6/10/24 02:02, Vignesh Raghavendra wrote:
>> Reserve memory for remote rpoc IPC and bind the mailbox assignments
>> for each remote proc. Two memory regions are reserved for each
>> remote processor. The first region of 1Mb of memory is used for Vring
> s/1Mb/1MB?
>
Yes, will correct it to 1MB.
>> + reg = <0x00 0x99900000 0x00 0x01efffff>;
> 0x01efffff -> are you sure this is correct? Just missing a byte to a
> nice round number size. looks like typo of using range vs size?
>
You are right. Will round it to 0x01f00000.
next prev parent reply other threads:[~2024-06-10 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 12:48 [PATCH v3 0/4] Add R5F and C7x DSP nodes for AM62a SoC Hari Nagalla
2024-06-05 12:48 ` [PATCH v3 1/4] arm64: dts: k3-am62a-main: Add C7xv device node Hari Nagalla
2024-06-05 12:48 ` [PATCH v3 2/4] arm64: dts: k3-am62a-mcu: Add R5F remote proc node Hari Nagalla
2024-06-05 12:48 ` [PATCH v3 3/4] arm64: dts: k3-am62a-wakeup: Add R5F device node Hari Nagalla
2024-06-05 12:48 ` [PATCH v3 4/4] arm64: dts: ti: k3-am62a7-sk: Enable ipc with remote proc nodes Hari Nagalla
2024-06-06 17:16 ` Bryan Brattlof
2024-06-10 15:52 ` Hari Nagalla
2024-06-10 19:30 ` Bryan Brattlof
2024-06-10 7:02 ` Vignesh Raghavendra
2024-06-10 15:56 ` Hari Nagalla [this message]
2024-06-06 15:56 ` [PATCH v3 0/4] Add R5F and C7x DSP nodes for AM62a SoC Rob Herring (Arm)
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=4405d53a-bb9b-24bc-9bbc-b5dbecefdba4@ti.com \
--to=hnagalla@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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
all inboxes | Powered by JetHome®