[v2,0/2] arm64: dts: ti: k3-am625-sk: Enable Type-C dual-role

Message

Roger Quadros March 28, 2023, 12:43 p.m. UTC

Hi,

This series enables Type-C port on USB0.
Series is based on [1]

Although k3-am625-lp-sk USB is exactly the same as on k3-am625-sk,
it is missing the IRQ line from Type-C chip which is currently
required as per chip's DT binding. So we don't add Type-C support
for k3-am625-lp-sk till h/w is fixed or polling mode support for
Type-C chip is accepted [2]

Changelog:
v2:
- rebase off [1]
- add fixes tag to patch 1

[1] - https://lore.kernel.org/all/[e-mail]/
[2] - https://lore.kernel.org/lkml/[e-mail]/T/

cheers,
-roger

Dhruva Gole (1):
  arm64: dts: ti: k3-am625-sk: Add ti,vbus-divider property to usbss1

Roger Quadros (1):
  arm64: dts: ti: k3-am625-sk: Enable Type-C port for USB0

 arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts      |  4 ++
 arch/arm64/boot/dts/ti/k3-am625-sk.dts        | 44 ++++++++++++++++++-
 .../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi |  5 +--
 3 files changed, 48 insertions(+), 5 deletions(-)

Comments

Nishanth Menon March 30, 2023, 2:16 a.m. UTC | #1

Hi Roger Quadros,

On Tue, 28 Mar 2023 15:43:13 +0300, Roger Quadros wrote:
> This series enables Type-C port on USB0.
> Series is based on [1]
> 
> Although k3-am625-lp-sk USB is exactly the same as on k3-am625-sk,
> it is missing the IRQ line from Type-C chip which is currently
> required as per chip's DT binding. So we don't add Type-C support
> for k3-am625-lp-sk till h/w is fixed or polling mode support for
> Type-C chip is accepted [2]
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1]. I picked v1
version with v2 updates in commit message to help stable, while at it,
I had to rewrite history a bit so that cherry-pick to stable won't be a
problem.

Thank you!

[1/2] arm64: dts: ti: k3-am625-sk: Add ti,vbus-divider property to usbss1
      commit: 49af4ecdd8ad2a964dbb9f2e7e50082433b37f98

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] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git