Skip to contentSkip to conversation

arm64: dts: ti: k3-am62*-main: Remove unwanted properties from crypto

PATCH Applied Kamlesh Gurudasani 2 participants 2 messages Jun 19, 2024 – Jul 1, 2024

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 arm64: dts: ti: k3-am62*-main: Remove unwanted properties from crypto

As there is no child node in crypto node, remove the properties that are not needed.

---
 arch/arm64/boot/dts/ti/k3-am62-main.dtsi  | 4 ----
 arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 4 ----
 2 files changed, 8 deletions(-)
arch/arm64/boot/dts/ti/k3-am62-main.dtsi +0 -4
index 0f2722c4bcc3..00776a9987c1 100644
@@ -207,10 +207,6 @@ k3_reset: reset-controller {
 	crypto: crypto@40900000 {
 		compatible = "ti,am62-sa3ul";
 		reg = <0x00 0x40900000 0x00 0x1200>;
-		#address-cells = <2>;
-		#size-cells = <2>;
-		ranges = <0x00 0x40900000 0x00 0x40900000 0x00 0x30000>;
-
 		dmas = <&main_pktdma 0xf501 0>, <&main_pktdma 0x7506 0>,
 		       <&main_pktdma 0x7507 0>;
 		dma-names = "tx", "rx1", "rx2";
arch/arm64/boot/dts/ti/k3-am62p-main.dtsi +0 -4
index eed06506f617..c1c74ce40f76 100644
@@ -227,10 +227,6 @@ k3_reset: reset-controller {
 	crypto: crypto@40900000 {
 		compatible = "ti,am62-sa3ul";
 		reg = <0x00 0x40900000 0x00 0x1200>;
-		#address-cells = <2>;
-		#size-cells = <2>;
-		ranges = <0x00 0x40900000 0x00 0x40900000 0x00 0x30000>;
-
 		dmas = <&main_pktdma 0xf501 0>, <&main_pktdma 0x7506 0>,
 		       <&main_pktdma 0x7507 0>;
 		dma-names = "tx", "rx1", "rx2";

---
base-commit: 6906a84c482f098d31486df8dc98cead21cce2d0
change-id: 20240618-remove-ranges-ac3bac5e2f9e

Best regards,

Signature · 1 line
Kamlesh Gurudasani <[email protected]>
maintainer Applied
#1 lore raw

Hi Kamlesh Gurudasani,

Quoted 4 lines · Kamlesh Gurudasani

As there is no child node in crypto node, remove the properties that are not needed.

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

[1/1] arm64: dts: ti: k3-am62*-main: Remove unwanted properties from crypto

      commit: b6861f152b4bf6f194b5e5162ee238f2c97e5aec

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