mbox series

[V2,0/3] arm64: dts: ti: k3-am62p/j722s: Add gpio-ranges properties

Message ID 20240627162539.691223-1-nm@ti.com (mailing list archive)
Headers show
Series arm64: dts: ti: k3-am62p/j722s: Add gpio-ranges properties | expand

Message

Nishanth Menon June 27, 2024, 4:25 p.m. UTC 
Hi,

This series was tested on BeagleY-AI[1] using the script[2].

This allows gpiod to request for a gpio that is not in the default GPIO
mux mode and the framework controls the mux over to required GPIO mode.

The series is based off next-20240617.

NOTE: there is also a dtb_warning that is added, The fix for which is in
the binding[3].

Changes since V1:
 - Mux definition PIN_GPIO_RANGE_IOPAD instead of PIN_GPIO_MUX_MODE
 - Refactored on top of next-20240626
 - Note: since the patches have changed, I have skipped Dhruva's
   reviewed-by

V1: https://lore.kernel.org/linux-arm-kernel/20240618173123.2592074-1-nm@ti.com/

Jared McArthur (1):
  arm64: dts: ti: k3-j722s: Add gpio-ranges properties

Nishanth Menon (2):
  arm64: dts: ti: k3-pinctrl: Define a generic GPIO MUX Mode
  arm64: dts: ti: k3-am62p: Add gpio-ranges properties

 .../boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi |  8 ++++++++
 arch/arm64/boot/dts/ti/k3-am62p-main.dtsi      | 17 +++++++++++++++++
 arch/arm64/boot/dts/ti/k3-j722s-main.dtsi      | 18 ++++++++++++++++++
 arch/arm64/boot/dts/ti/k3-pinctrl.h            |  3 +++
 4 files changed, 46 insertions(+)

base-commit: df9574a57d02b265322e77fb8628d4d33641dda9

[1] https://www.beagleboard.org/boards/beagley-ai
[2] https://gist.github.com/nmenon/4973770cf0df3f02c2e4f7f3d048d80d
[3] https://lore.kernel.org/linux-arm-kernel/20240627150610.469645-1-nm@ti.com/

Comments

Vignesh Raghavendra July 3, 2024, 4:35 a.m. UTC | #1 
Hi Nishanth Menon,

On Thu, 27 Jun 2024 11:25:36 -0500, Nishanth Menon wrote:
> This series was tested on BeagleY-AI[1] using the script[2].
> 
> This allows gpiod to request for a gpio that is not in the default GPIO
> mux mode and the framework controls the mux over to required GPIO mode.
> 
> The series is based off next-20240617.
> 
> [...]

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

[1/3] arm64: dts: ti: k3-pinctrl: Define a generic GPIO MUX Mode
      commit: 50d9981fa12212cdc0110c42db0411209bb5d765
[2/3] arm64: dts: ti: k3-am62p: Add gpio-ranges properties
      commit: d72d73a44c3c98109764bfb56c329cd628c518cc
[3/3] arm64: dts: ti: k3-j722s: Add gpio-ranges properties
      commit: 90d3d2eed998fef92f7bbc8557a843360516ccee

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