From: "Nagalla, Hari" <hnagalla@ti.com>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
"Menon, Nishanth" <nm@ti.com>
Subject: RE: [PATCH 0/5] Add ESM driver support for AM64x R5
Date: Fri, 25 Feb 2022 22:00:16 +0000 [thread overview]
Message-ID: <e1d3e319cd60493496abc3c8eda1bfbd@ti.com> (raw)
In-Reply-To: <CAH9NwWfkmp4eu5O+7HZDGy8R12avWaBQwetrkWp5tcsy=4DTKA@mail.gmail.com>
Hi Christian,
I have a v2 series.. Will send out by Saturday.
Thanks
Hari
-----Original Message-----
From: Christian Gmeiner <christian.gmeiner@gmail.com>
Sent: Wednesday, February 23, 2022 1:53 AM
To: Nagalla, Hari <hnagalla@ti.com>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>; Menon, Nishanth <nm@ti.com>
Subject: Re: [PATCH 0/5] Add ESM driver support for AM64x R5
Hi Hari
Am Mi., 2. Feb. 2022 um 18:50 Uhr schrieb Hari Nagalla <hnagalla@ti.com>:
>
> AM64x devices have a main ESM and a MCU ESM. The ESM driver enables
> routing of the error events from various sources to different
> processors or to reset hardware logic. Only the MCU ESM's high output
> can trigger reset logic. The main RTI0 WWDT output can be routed to
> the MCU highoutput to trigger reset through the main ESM. For this
> reset to occur CTRLMMR_MCU_RST_CTRL:MCU_ESM_ERROR_RESET_EN_Z is set to '0'.
>
> AM64x Technical Reference Manual - https://www.ti.com/lit/pdf/spruim2
Are there any plans to send out a V2 of this patch series? If not I can jump in (as I really want to see in U-Boot sooner than later).
--
greets
--
Christian Gmeiner, MSc
https://christian-gmeiner.info/privacypolicy
prev parent reply other threads:[~2022-02-25 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 17:10 [PATCH 0/5] Add ESM driver support for AM64x R5 Hari Nagalla
2022-02-02 18:15 ` Nagalla, Hari
2022-02-23 7:53 ` Christian Gmeiner
2022-02-25 22:00 ` Nagalla, Hari [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=e1d3e319cd60493496abc3c8eda1bfbd@ti.com \
--to=hnagalla@ti.com \
--cc=christian.gmeiner@gmail.com \
--cc=nm@ti.com \
--cc=u-boot@lists.denx.de \
/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