[v2,0/2] Add support for multiple can instances as well as describe main_uart5

Message

Bhavya Kapoor Aug. 27, 2024, 10:56 a.m. UTC

This series adds support for multiple can instances present on J722S
EVM as well as describe the main_uart5 for J722S EVM.

CAN instances 0 and 1 in the mcu domain and 0 in the main domain are
brought on the evm through headers J5, J8 and J10 respectively. Thus,
add their respective transceiver's 0, 1 and 2 dt nodes as well as
add the required pinmux to add support for these CAN instances.

Describe main_uart5 in device tree for completeness, adding the pinmux
and mark it as reserved since system firmware uses it in J722S EVM for
trace data.

Rebased to : next-20240827

Bhavya Kapoor (2):
  arm64: dts: ti: k3-j722s-evm: Add support for multiple CAN instances
  arm64: dts: ti: k3-j722s-evm: Describe main_uart5

 arch/arm64/boot/dts/ti/k3-j722s-evm.dts | 89 +++++++++++++++++++++++++
 1 file changed, 89 insertions(+)

Comments

Nishanth Menon Aug. 28, 2024, 7:02 p.m. UTC | #1

Hi Bhavya Kapoor,

On Tue, 27 Aug 2024 16:26:42 +0530, Bhavya Kapoor wrote:
> This series adds support for multiple can instances present on J722S
> EVM as well as describe the main_uart5 for J722S EVM.
> 
> CAN instances 0 and 1 in the mcu domain and 0 in the main domain are
> brought on the evm through headers J5, J8 and J10 respectively. Thus,
> add their respective transceiver's 0, 1 and 2 dt nodes as well as
> add the required pinmux to add support for these CAN instances.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j722s-evm: Add support for multiple CAN instances
      commit: 46ca5c7207703b36025228a6b7a29198a1539d10
[2/2] arm64: dts: ti: k3-j722s-evm: Describe main_uart5
      commit: 010b035ab4d7a1c4fd13936f42eef857ddbeede7

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