[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174133309362.1072814.1438889304366712802.b4-ty@ti.com>
Date: Fri, 7 Mar 2025 16:06:36 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
<conor+dt@...nel.org>, Wadim Egorov <w.egorov@...tec.de>
CC: Vignesh Raghavendra <vigneshr@...com>,
<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <upstream@...ts.phytec.de>
Subject: Re: [PATCH v2 1/5] arm64: dts: ti: k3-am62x-phyboard-lyra: Add boot phase tags
Hi Wadim Egorov,
On Wed, 05 Mar 2025 09:55:33 +0100, Wadim Egorov wrote:
> The bootph-all and bootph-pre-ram tags were introduced in dt-schema
> (dtschema/schemas/bootph.yaml) to define node usage across different
> boot phases.
>
> Add boot phase tags to all required nodes to ensure boot support from
> all sources, including UART, USB (DFU), Ethernet, uSD card, eMMC, and
> OSPI NOR Flash.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/5] arm64: dts: ti: k3-am62x-phyboard-lyra: Add boot phase tags
commit: c2d18ec0ea4ce9d6d8be5a1a9b266f57a40b5e24
[2/5] arm64: dts: ti: k3-am62a-phycore-som: Add boot phase tags
commit: a5965ee0107a37ca4c73f05f06f55dad759572d2
[3/5] arm64: dts: ti: k3-am642-phyboard-electra: Add boot phase tags
commit: a9c8485cd13cdffee5bdcda6b625f678900994c4
[4/5] arm64: dts: ti: k3-am642-phyboard-electra: Reorder properties per DTS coding style
commit: 61a12b5a9923e4beec5595fed3b9c3d5c0c25c32
[5/5] arm64: dts: ti: k3-am62a-phycore-som: Reorder properties per DTS coding style
commit: a89d3f47b09c793d0454350739ee8695ff30fb5c
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
--
Vignesh
Powered by blists - more mailing lists