From: Nishanth Menon <nm@ti.com>
To: Hari Nagalla <hnagalla@ti.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vigneshr@ti.com>, <robh+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am64: Add ESM0 to device memory map
Date: Tue, 8 Feb 2022 18:35:19 -0600 [thread overview]
Message-ID: <20220209003519.clokfvln7m2deewi@buddhism> (raw)
In-Reply-To: <20220208182119.24707-1-hnagalla@ti.com>
Please loop in LAKML as stated in MAINTAINERS file.
On 12:21-20220208, Hari Nagalla wrote:
> AM64x SoCs have two ESM modules, with one in MAIN voltage domain and the
> other in MCU voltage domain. The error output from Main ESM module can
> be routed to the MCU ESM module. The error output of MCU ESM can be
> configured to reset the device.
So what happens to the window for MCU ESM - Is that already open?
>
> For ESM details please refer technical reference manual at
> https://www.ti.com/lit/pdf/spruim2
>
> Signed-off-by: Hari Nagalla <hnagalla@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am64.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am64.dtsi b/arch/arm64/boot/dts/ti/k3-am64.dtsi
> index 120974726be8..0622a93ec136 100644
> --- a/arch/arm64/boot/dts/ti/k3-am64.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am64.dtsi
> @@ -66,6 +66,7 @@
> #address-cells = <2>;
> #size-cells = <2>;
> ranges = <0x00 0x000f4000 0x00 0x000f4000 0x00 0x000002d0>, /* PINCTRL */
> + <0x00 0x00420000 0x00 0x00420000 0x00 0x00001000>, /* ESM0 */
> <0x00 0x00600000 0x00 0x00600000 0x00 0x00001100>, /* GPIO */
> <0x00 0x00a40000 0x00 0x00a40000 0x00 0x00000800>, /* Timesync router */
> <0x00 0x01000000 0x00 0x01000000 0x00 0x02330400>, /* First peripheral window */
> --
> 2.17.1
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2022-02-09 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 18:21 Hari Nagalla
2022-02-09 0:35 ` Nishanth Menon [this message]
2022-02-09 1:18 ` Hari Nagalla
2022-02-09 13:24 ` 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=20220209003519.clokfvln7m2deewi@buddhism \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=linux-kernel@vger.kernel.org \
--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®