[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <172522225751.998566.15548857625813492043.b4-ty@ti.com>
Date: Sun, 1 Sep 2024 15:26:55 -0500
From: Nishanth Menon <nm@...com>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Judith Mendez <jm@...com>
CC: Nishanth Menon <nm@...com>, Vignesh Raghavendra <vigneshr@...com>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Jan Kiszka
<jan.kiszka@...mens.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 0/6] Add and fix ESM nodes
Hi Judith Mendez,
On Thu, 15 Aug 2024 15:48:27 -0500, 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.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/6] arm64: dts: ti: k3-am62a: Add ESM nodes
commit: 54ed32742a2b722a9eeeca601b5d9b715423381b
[2/6] arm64: dts: ti: k3-am62p: Fix ESM interrupt sources
commit: c94da2159dfdcc44b78a8b1f3ebe4909d4efc9ec
[3/6] arm64: dts: ti: k3-am62p: Remove 'reserved' status for ESM
commit: d4847546b6209876bbbbc00f5b8583387e80b731
[4/6] arm64: dts: ti: k3-am62: Add comments to ESM nodes
commit: cc3a295ebb659a56534a2baea9040dc0dec1980d
[5/6] arm64: dts: ti: k3-am64: Add more ESM interrupt sources
commit: 633bcfa502591103b5d5c4429d90bf10ac9bfd52
[6/6] arm64: dts: ti: k3-am65: Add ESM nodes
commit: 50f368a0c166ebac9301b834aed729b2bb901e6a
NOTE: There were minor reodering fixups I did (e.g.: removes should
probably precede fixes which precede additions in a patch series
unless there is a specific reason not to; trm urls should be the
canonical urls; Follow the dt coding style in ordering properties) -
please cross check and let me know if you disagree and I can drop the
series from my branch.
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists