[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <173524500637.82584.659172810910949750.b4-ty@ti.com>
Date: Thu, 26 Dec 2024 14:30:34 -0600
From: Nishanth Menon <nm@...com>
To: Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Enric Balletbo i Serra
<eballetb@...hat.com>
CC: Nishanth Menon <nm@...com>, <linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Andrew Halaney
<ajhalaney@...il.com>,
Andrew Halaney <ahalaney@...hat.com>, Udit Kumar
<u-kumar1@...com>,
Beleswar Padhi <b-padhi@...com>
Subject: Re: [PATCH v4 0/2] arm64: dts: ti: k3-j784s4: Mark tps659413
Hi Enric Balletbo i Serra,
On Wed, 13 Nov 2024 10:15:15 +0100, Enric Balletbo i Serra wrote:
> This series marks tps659413's regulators as bootph-all in order for
> the nodes (and parent nodes) to be accessible during MCU's u-boot SPL.
>
> This in turn is desired since the tps659413 needs its MCU ESM
> state machine setup in order for the watchdog to reset the board.
>
> This took me a little while to track down, as enabling the ESM, TPS6594,
> etc in u-boot would result in the below boot failure:
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] arm64: dts: ti: k3-j784s4-evm: Mark tps659413 regulators as bootph-all
commit: 0cd578054e7107cab921ff0c24f4ac6d14d3661b
[2/2] arm64: dts: ti: k3-am69-sk: Mark tps659413 regulators as bootph-all
commit: 0a41157c5a988520debb656325722f401163eca3
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