arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 1 + 1 file changed, 1 insertion(+)
To keep things as organized as possible, copy the bootph-all properties
from U-Boot for the packet DMA controller to indicate it should be
available during all phases of bootup.
Signed-off-by: Bryan Brattlof <bb@ti.com>
---
arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index 9e0b6eee9ac77d66869915b2d7bec3e2275c03ea..2a727caf36ec44e4a023c5985d1bad9b80737633 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -150,6 +150,7 @@ main_pktdma: dma-controller@485c0000 {
"ring", "tchan", "rchan", "rflow";
msi-parent = <&inta_main_dmss>;
#dma-cells = <2>;
+ bootph-all;
ti,sci = <&dmsc>;
ti,sci-dev-id = <30>;
---
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
change-id: 20250623-62-uboot-cleanup-dbec66f9e257
Best regards,
--
Bryan Brattlof <bb@ti.com>
On 24/06/25 20:20, Bryan Brattlof wrote: > To keep things as organized as possible, copy the bootph-all properties > from U-Boot for the packet DMA controller to indicate it should be > available during all phases of bootup. > Above isn't a valid reason to add bootph-all properties to a node. You would need to say why this DMA controller is needed during all phases of boot, does this enable a certain boot-mode? Fix $subject to reflect the same. > Signed-off-by: Bryan Brattlof <bb@ti.com> > --- > arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi > index 9e0b6eee9ac77d66869915b2d7bec3e2275c03ea..2a727caf36ec44e4a023c5985d1bad9b80737633 100644 > --- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi > +++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi > @@ -150,6 +150,7 @@ main_pktdma: dma-controller@485c0000 { > "ring", "tchan", "rchan", "rflow"; > msi-parent = <&inta_main_dmss>; > #dma-cells = <2>; > + bootph-all; > > ti,sci = <&dmsc>; > ti,sci-dev-id = <30>; > > --- > base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494 > change-id: 20250623-62-uboot-cleanup-dbec66f9e257 > > Best regards, -- Regards Vignesh https://ti.com/opensource
On June 26, 2025 thus sayeth Vignesh Raghavendra: > > > On 24/06/25 20:20, Bryan Brattlof wrote: > > To keep things as organized as possible, copy the bootph-all properties > > from U-Boot for the packet DMA controller to indicate it should be > > available during all phases of bootup. > > > > Above isn't a valid reason to add bootph-all properties to a node. You > would need to say why this DMA controller is needed during all phases of > boot, does this enable a certain boot-mode? Fix $subject to reflect the > same. Ok will do ~Bryan
© 2016 - 2025 Red Hat, Inc.