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@xxxxxx/ 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@xxxxxx/ -- 2.43.0
