mbox series

[0/2] Add bootph-all to SERDES3 for USB DFU Boot on J721E

Message ID 20250209081738.1874749-1-s-vadapalli@ti.com (mailing list archive)
Headers show
Series Add bootph-all to SERDES3 for USB DFU Boot on J721E | expand

Message

Siddharth Vadapalli Feb. 9, 2025, 8:17 a.m. UTC
Hello,

This series is based on linux-next tagged next-20250207.

J721E SoC supports USB DFU Boot via USB0 instance of USB. On both
J721E-EVM - (J721E SoM + J7 Common Processor Board) and
J721E-SK, the USB Type-C interface which is connected to USB0 via
SERDES3 is used for USB DFU boot.

Series adds "bootph-all" tag to the "serdes3_usb_link" device-tree node
which is the USB3 PHY for USB0, thereby enabling USB DFU boot.

Regards,
Siddharth.

Siddharth Vadapalli (2):
  arm64: dts: ti: k3-j721e-common-proc-board: Add boot phase tag to
    SERDES3
  arm64: dts: ti: k3-j721e-sk: Add boot phase tag to SERDES3

 arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts | 1 +
 arch/arm64/boot/dts/ti/k3-j721e-sk.dts                | 1 +
 2 files changed, 2 insertions(+)

Comments

Vignesh Raghavendra March 3, 2025, 4:54 a.m. UTC | #1
Hi Siddharth Vadapalli,

On Sun, 09 Feb 2025 13:47:31 +0530, Siddharth Vadapalli wrote:
> This series is based on linux-next tagged next-20250207.
> 
> J721E SoC supports USB DFU Boot via USB0 instance of USB. On both
> J721E-EVM - (J721E SoM + J7 Common Processor Board) and
> J721E-SK, the USB Type-C interface which is connected to USB0 via
> SERDES3 is used for USB DFU boot.
> 
> [...]

I have applied the following to branch ti-next on [1].
Thank you!

[1/2] arm64: dts: ti: k3-j721e-common-proc-board: Add boot phase tag to SERDES3
      commit: 59ac3f9f54db76f676ac5db05054586956c57e39
[2/2] arm64: dts: ti: k3-j721e-sk: Add boot phase tag to SERDES3
      commit: 871c73229bd276fbdb43c42fb3f5a25bcd8a9c85

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