public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Judith Mendez <jm@ti.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Add and fix ESM nodes
Date: Wed, 14 Aug 2024 06:04:56 +0200	[thread overview]
Message-ID: <4295a15a-6285-4005-bc40-328e52addc2b@siemens.com> (raw)
In-Reply-To: <20240813230312.3289428-1-jm@ti.com>

On 14.08.24 01:03, Judith Mendez wrote:
> The following patch adds ESM nodes and fixes ESM source
> interrupts for Sitara K3 platforms. Currently watchdog cannot
> reset the CPU because of misconfiguration or missing ESM node
> in DT.
> 
> ESM node was added for am62ax and am65x. For am62px ESM source
> interrupts are fixed. Comments were also added for clarity on what
> source interrupts are routed to ESM based on device TRM.
> 
> ESM nodes like MCU ESM for am65x are added for device completion,
> currently, some ESM0 events are not routed to MCU ESM, so watchdog
> cannot reset the CPU using the current implementation.

Yes, that's why there is https://github.com/siemens/k3-rti-wdt and
probably similar bits in other R5 firmware. I was always told that is
the only way to reset the /system/ (CPU alone would not help). That
information is still correct?

Jan

> 
> Changes since v1:
> - Remove watchdog patch
> - Add am64x patch 5/6
> - Add am65x patch 6/6
> - Add missing bootph flag
> 
> Judith Mendez (5):
>   arm64: dts: ti: k3-am62a: Add ESM nodes
>   arm64: dts: ti: k3-am62p: Fix ESM interrupt sources
>   arm64: dts: ti: k3-am62: Add comments to ESM nodes
>   arm64: dts: ti: k3-am64: Add more ESM interrupt sources
>   arm64: dts: ti: k3-am65: Add ESM nodes
> 
> Santhosh Kumar K (1):
>   arm64: dts: ti: k3-am62p: Remove 'reserved' status for ESM
> 
>  arch/arm64/boot/dts/ti/k3-am62-main.dtsi               | 1 +
>  arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi                | 1 +
>  arch/arm64/boot/dts/ti/k3-am62a-main.dtsi              | 8 ++++++++
>  arch/arm64/boot/dts/ti/k3-am62a-mcu.dtsi               | 8 ++++++++
>  arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi | 3 ++-
>  arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi  | 4 ++--
>  arch/arm64/boot/dts/ti/k3-am64-main.dtsi               | 3 ++-
>  arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi                | 3 ++-
>  arch/arm64/boot/dts/ti/k3-am65-main.dtsi               | 8 ++++++++
>  arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi                | 8 ++++++++
>  10 files changed, 42 insertions(+), 5 deletions(-)
> 
> 
> base-commit: e3cce1229c34b5c28f103361c4d6b3ef17302d5d

-- 
Siemens AG, Technology
Linux Expert Center


  parent reply	other threads:[~2024-08-14  4:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13 23:03 [PATCH v2 0/6] Add and fix ESM nodes Judith Mendez
2024-08-13 23:03 ` [PATCH v2 1/6] arm64: dts: ti: k3-am62a: Add " Judith Mendez
2024-08-13 23:03 ` [PATCH v2 2/6] arm64: dts: ti: k3-am62p: Fix ESM interrupt sources Judith Mendez
2024-08-13 23:03 ` [PATCH v2 3/6] arm64: dts: ti: k3-am62p: Remove 'reserved' status for ESM Judith Mendez
2024-08-13 23:03 ` [PATCH v2 4/6] arm64: dts: ti: k3-am62: Add comments to ESM nodes Judith Mendez
2024-08-13 23:03 ` [PATCH v2 5/6] arm64: dts: ti: k3-am64: Add more ESM interrupt sources Judith Mendez
2024-08-13 23:03 ` [PATCH v2 6/6] arm64: dts: ti: k3-am65: Add ESM nodes Judith Mendez
2024-08-14 14:05   ` Judith Mendez
2024-08-15 12:32     ` Nishanth Menon
2024-08-15 14:20       ` Jan Kiszka
2024-08-14  4:04 ` Jan Kiszka [this message]
2024-08-14 13:59   ` [PATCH v2 0/6] Add and fix " Judith Mendez
2024-08-15 12:29     ` Nishanth Menon
2024-08-15 14:19       ` Jan Kiszka
2024-08-15 14:27       ` Judith Mendez

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=4295a15a-6285-4005-bc40-328e52addc2b@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jm@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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