linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Gmeiner <christian.gmeiner@gmail.com>
To: Hari Nagalla <hnagalla@ti.com>
Cc: devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-arm-kernel@lists.infradead.org, Nishanth Menon <nm@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Rob Herring <robh+dt@kernel.org>, Tero Kristo <kristo@kernel.org>
Subject: Re: [PATCH v1] arm64: dts: ti: k3-am64: Add ESM0 to device memory map
Date: Fri, 11 Feb 2022 08:19:23 +0100	[thread overview]
Message-ID: <CAH9NwWes070Z+VmpfvkUfx+vGn_41H_Ps2960uaktJkyXPrWuQ@mail.gmail.com> (raw)
In-Reply-To: <20220210172246.27871-1-hnagalla@ti.com>

Hi

Am Do., 10. Feb. 2022 um 18:30 Uhr schrieb Hari Nagalla <hnagalla@ti.com>:
>
> 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. The MCU ESM configuration address space
> is already opened and this patch opens the MAIN ESM configuration
> address space.
>
> For ESM details please refer technical reference manual at
> https://www.ti.com/lit/pdf/spruim2
>
> Signed-off-by: Hari Nagalla <hnagalla@ti.com>

Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.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
>


-- 
greets
--
Christian Gmeiner, MSc

https://christian-gmeiner.info/privacypolicy

  reply	other threads:[~2022-02-11  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 17:22 [PATCH v1] arm64: dts: ti: k3-am64: Add ESM0 to device memory map Hari Nagalla
2022-02-11  7:19 ` Christian Gmeiner [this message]
2022-02-16 16:40 ` 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=CAH9NwWes070Z+VmpfvkUfx+vGn_41H_Ps2960uaktJkyXPrWuQ@mail.gmail.com \
    --to=christian.gmeiner@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=kristo@kernel.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;
as well as URLs for NNTP newsgroup(s).