| Message ID | 20230602214937.2349545-1-nm@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | arm64: dts: ti: k3-j784s4/am69: Add uart, i2c, eeprom, misc | expand |
On 16:49-20230602, Nishanth Menon wrote: > Hi, > > This series picks up from where [1] left off. After fixing the mux > regions, introduce the basic i2c, uarts, ethernet, and a few alias > fixups sprinkled along with it. > > This series also takes over [2] and rebased on top of [1] and my series. > > Test log: Apologies on that, I seem to have forgotten to provide the link to the test log. Anyways, here we go: https://gist.github.com/nmenon/dca0ea1203c4e06d77f77b5c4a4a3e3f > > Dasnavis Sabiya (1): > arm64: dts: ti: k3-am69-sk: Add pinmux for RPi Header > > Nishanth Menon (7): > arm64: dts: ti: k3-j784s4-evm: Fix main_i2c0 alias > arm64: dts: ti: k3-j784s4-evm: Add mcu and wakeup uarts > arm64: dts: ti: k3-j784s4-evm: Enable wakeup_i2c0 and eeprom > arm64: dts: ti: k3-am69-sk: Fix main_i2c0 alias > arm64: dts: ti: k3-am69-sk: Enable mcu network port > arm64: dts: ti: k3-am69-sk: Add mcu and wakeup uarts > arm64: dts: ti: k3-am69-sk: Enable wakeup_i2c0 and eeprom > > arch/arm64/boot/dts/ti/k3-am69-sk.dts | 165 ++++++++++++++++++++++- > arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 56 +++++++- > 2 files changed, 219 insertions(+), 2 deletions(-) > > [1] https://lore.kernel.org/linux-arm-kernel/20230503083143.32369-1-t-konduru@ti.com/ > [2] https://lore.kernel.org/linux-arm-kernel/20230316104743.482972-3-sabiya.d@ti.com/ > -- > 2.40.0 >
Thanks Nishanth On 6/3/2023 3:19 AM, Nishanth Menon wrote: > Hi, > > This series picks up from where [1] left off. After fixing the mux > regions, introduce the basic i2c, uarts, ethernet, and a few alias > fixups sprinkled along with it. > > This series also takes over [2] and rebased on top of [1] and my series. > > Test log: > > Dasnavis Sabiya (1): > arm64: dts: ti: k3-am69-sk: Add pinmux for RPi Header > > Nishanth Menon (7): > arm64: dts: ti: k3-j784s4-evm: Fix main_i2c0 alias > arm64: dts: ti: k3-j784s4-evm: Add mcu and wakeup uarts > arm64: dts: ti: k3-j784s4-evm: Enable wakeup_i2c0 and eeprom > arm64: dts: ti: k3-am69-sk: Fix main_i2c0 alias > arm64: dts: ti: k3-am69-sk: Enable mcu network port > arm64: dts: ti: k3-am69-sk: Add mcu and wakeup uarts > arm64: dts: ti: k3-am69-sk: Enable wakeup_i2c0 and eeprom > > arch/arm64/boot/dts/ti/k3-am69-sk.dts | 165 ++++++++++++++++++++++- > arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 56 +++++++- > 2 files changed, 219 insertions(+), 2 deletions(-) Reviewed-by: Udit Kumar <u-kumar1@ti.com> > > [1] https://lore.kernel.org/linux-arm-kernel/20230503083143.32369-1-t-konduru@ti.com/ > [2] https://lore.kernel.org/linux-arm-kernel/20230316104743.482972-3-sabiya.d@ti.com/
Hi Nishanth Menon, On Fri, 02 Jun 2023 16:49:29 -0500, Nishanth Menon wrote: > This series picks up from where [1] left off. After fixing the mux > regions, introduce the basic i2c, uarts, ethernet, and a few alias > fixups sprinkled along with it. > > This series also takes over [2] and rebased on top of [1] and my series. > > Test log: > > [...] I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/8] arm64: dts: ti: k3-j784s4-evm: Fix main_i2c0 alias commit: c10a9df30e3401bd5a5ee43f1afd6c2b2ca75ad7 [2/8] arm64: dts: ti: k3-j784s4-evm: Add mcu and wakeup uarts commit: 6fa5d37a2f34476613012789d4618c3dc6c68b35 [3/8] arm64: dts: ti: k3-j784s4-evm: Enable wakeup_i2c0 and eeprom commit: 5dfbd1debc8ce5123310265cd44b5d99d272b1fe [4/8] arm64: dts: ti: k3-am69-sk: Fix main_i2c0 alias commit: b38c6ced4ec5b3f6260ff6cc2b71e8a3d8c897d7 [5/8] arm64: dts: ti: k3-am69-sk: Enable mcu network port commit: 7b72bd25508de6a5eee2cb1679b9d4b8bc25de5a [6/8] arm64: dts: ti: k3-am69-sk: Add mcu and wakeup uarts commit: 45299dd1991b496ddab5ab4a86d7ae601e0e4c7f [7/8] arm64: dts: ti: k3-am69-sk: Enable wakeup_i2c0 and eeprom commit: 08ae12b637507cd22fbcdb82521b8b8a5ae96222 [8/8] arm64: dts: ti: k3-am69-sk: Add pinmux for RPi Header commit: 0ec1a48d99ddd11c265f7f1b2573fb2c8e0db0ab 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