mbox series

[v2,0/3] arm64: dts: ti: k3-am62p/j722s: Fix gpio-ranges

Message ID 20240801210414.715306-1-j-mcarthur@ti.com (mailing list archive)
Headers show
Series arm64: dts: ti: k3-am62p/j722s: Fix gpio-ranges | expand

Message

Jared McArthur Aug. 1, 2024, 9:04 p.m. UTC 
Hi,

Fixes issues within the am62p and j722s gpio-ranges. Adds the missing
holes within the ranges as well as the the missing gpio-ranges
property within the mcu_gpio0 node of the am62p.

v2 changes: Removes the duplicate ti,ngpio property from the mcu_gpio0
node of the k3-am62p-j722s-common-mcu.dtsi.

Tested with kernel_patch_verify
(https://github.com/nmenon/kernel_patch_verify.git) off of the
next-20240730 tag. Original series reported the following:

 0001-arm64-dts-ti-k3-am62p-Add-gpio-ranges-for-mcu_gpio0.patch
 Tests: Failed
	Fail tests:  btest_kbuild dtest_build_dtb 
	dtest_build_dtb_to_dts dtest_dtbs_check
	Pass tests:  defconfig ftest_check_kdoc ftest_check_includes
	ftest_check_headerdeps btest_basic btest_sparse btest_cocci
	btest_smatch ptest_am ptest_check ytest_dt_binding_check
	ytest_dtbs_check

 0002-arm64-dts-ti-k3-am62p-Fix-gpio-range-for-main_pmx0.patch
 Tests: Failed
	Fail tests:  btest_kbuild
	Pass tests:  defconfig ftest_check_kdoc ftest_check_includes
	ftest_check_headerdeps btest_basic btest_sparse btest_cocci
	btest_smatch ptest_am ptest_check ytest_dt_binding_check
	ytest_dtbs_check dtest_build_dtb dtest_build_dtb_to_dts
	dtest_dtbs_check

 0003-arm64-dts-ti-k3-j722s-Fix-gpio-range-for-main_pmx0.patch
 Tests: Failed
	Fail tests:  dtest_dtbs_check
	Pass tests:  defconfig btest_kbuild ftest_check_kdoc
	ftest_check_includes ftest_check_headerdeps btest_basic
	btest_sparse btest_cocci btest_smatch ptest_am ptest_check
	ytest_dt_binding_check ytest_dtbs_check dtest_build_dtb
	dtest_build_dtb_to_dts

The important log was:

arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi:
/bus@f0000/bus@4000000/gpio@4201000:ti,ngpio: Duplicate property name

With the v2 change (removing the duplicate ti,ngpio node), all of the
tests pass.

0001-arm64-dts-ti-k3-am62p-Add-gpio-ranges-for-mcu_gpio0.patch
Tests: Passed(ALL): defconfig btest_kbuild ftest_check_kdoc
ftest_check_includes ftest_check_headerdeps btest_basic btest_sparse
btest_cocci btest_smatch ptest_am ptest_check ytest_dt_binding_check
ytest_dtbs_check dtest_build_dtb dtest_build_dtb_to_dts
dtest_dtbs_check

0002-arm64-dts-ti-k3-am62p-Fix-gpio-range-for-main_pmx0.patch
Tests: Passed(ALL): defconfig btest_kbuild ftest_check_kdoc
ftest_check_includes ftest_check_headerdeps btest_basic btest_sparse
btest_cocci btest_smatch ptest_am ptest_check ytest_dt_binding_check
ytest_dtbs_check dtest_build_dtb dtest_build_dtb_to_dts
dtest_dtbs_check

0003-arm64-dts-ti-k3-j722s-Fix-gpio-range-for-main_pmx0.patch
Tests: Passed(ALL): defconfig btest_kbuild ftest_check_kdoc
ftest_check_includes ftest_check_headerdeps btest_basic btest_sparse
btest_cocci btest_smatch ptest_am ptest_check ytest_dt_binding_check
ytest_dtbs_check dtest_build_dtb dtest_build_dtb_to_dts
dtest_dtbs_check

Jared McArthur (3):
  arm64: dts: ti: k3-am62p: Add gpio-ranges for mcu_gpio0
  arm64: dts: ti: k3-am62p: Fix gpio-range for main_pmx0
  arm64: dts: ti: k3-j722s: Fix gpio-range for main_pmx0

 arch/arm64/boot/dts/ti/k3-am62p-j722s-common-mcu.dtsi | 2 ++
 arch/arm64/boot/dts/ti/k3-am62p-main.dtsi             | 3 ++-
 arch/arm64/boot/dts/ti/k3-j722s-main.dtsi             | 3 ++-
 3 files changed, 6 insertions(+), 2 deletions(-)

Best,
Jared McArthur

Comments

Nishanth Menon Aug. 6, 2024, 12:12 p.m. UTC | #1 
Hi Jared McArthur,

On Thu, 01 Aug 2024 16:04:11 -0500, Jared McArthur wrote:
> Fixes issues within the am62p and j722s gpio-ranges. Adds the missing
> holes within the ranges as well as the the missing gpio-ranges
> property within the mcu_gpio0 node of the am62p.
> 
> v2 changes: Removes the duplicate ti,ngpio property from the mcu_gpio0
> node of the k3-am62p-j722s-common-mcu.dtsi.
> 
> [...]

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

[1/3] arm64: dts: ti: k3-am62p: Add gpio-ranges for mcu_gpio0
      commit: 4e436f6fb95e507131df78c0d98052237db60ecc
[2/3] arm64: dts: ti: k3-am62p: Fix gpio-range for main_pmx0
      commit: 98897a300859dca62f834a5d1f60267032a9fe54
[3/3] arm64: dts: ti: k3-j722s: Fix gpio-range for main_pmx0
      commit: 04c90681144c40619524367c69e40736a6fa690c

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