[0/2] arm64: dts: ti: k3-am62p/j722s: Add gpio-reserved-ranges for main_gpio1

Message

Jared McArthur Aug. 9, 2024, 4:28 p.m. UTC

Hi,

The current main_gpio1 gpio controllers for the am62p and
j722s have holes that are not obvious to a user. Add the
gpio-reserved-ranges property to the davinci-gpio properties list and
add gpio-reserved-ranges to the am62p and j722s device trees. Prevents
users from trying to access gpios that don't exist.

The holes are taken from the am62p datasheet [1] (Table 5-24) and
am67x datasheet [2] (Table 5-27).

Patches depend on patch: dt-bindings: gpio: gpio-davinci: Add the
gpio-reserved-ranges property [3]

[1] https://www.ti.com/lit/ds/symlink/am62p.pdf
[2] https://www.ti.com/lit/ds/symlink/am67.pdf
[3] https://lore.kernel.org/all/[e-mail]/

Best,
Jared McArthur

Jared McArthur (2):
  arm64: dts: ti: k3-am62p: Add gpio-reserved-ranges for main_gpio1
  arm64: dts: ti: k3-j722s: Add gpio-reserved-ranges for main_gpio1

 arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 1 +
 arch/arm64/boot/dts/ti/k3-j722s-main.dtsi | 1 +
 2 files changed, 2 insertions(+)

Comments

Nishanth Menon Aug. 24, 2024, 7:51 p.m. UTC | #1

Hi Jared McArthur,

On Fri, 09 Aug 2024 11:28:26 -0500, Jared McArthur wrote:
> The current main_gpio1 gpio controllers for the am62p and
> j722s have holes that are not obvious to a user. Add the
> gpio-reserved-ranges property to the davinci-gpio properties list and
> add gpio-reserved-ranges to the am62p and j722s device trees. Prevents
> users from trying to access gpios that don't exist.
> 
> The holes are taken from the am62p datasheet [1] (Table 5-24) and
> am67x datasheet [2] (Table 5-27).
> 
> [...]

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

[1/2] arm64: dts: ti: k3-am62p: Add gpio-reserved-ranges for main_gpio1
      commit: 235b5b08ea3cb2743309d7d27b85d34387ee4b54
[2/2] arm64: dts: ti: k3-j722s: Add gpio-reserved-ranges for main_gpio1
      commit: 67d820656fd87581e9ea8b27e42fbcdd0202b3b5

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