| Message ID | 20240628-am642-evm-nand-bootph-v2-1-387bfa1533a6@kernel.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [v2] arm: dts: k3-am642-evm-nand: Add bootph-all to NAND related nodes | expand |
Hi Roger Quadros, On Fri, 28 Jun 2024 13:30:38 +0300, Roger Quadros wrote: > NAND boot would require these nodes to be present at early stage. > Ensure that by adding "bootph-all" to relevant nodes. > > I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/1] arm: dts: k3-am642-evm-nand: Add bootph-all to NAND related nodes commit: 447f85b70f6553218e0aa7889e8615e4b31c8a2f 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
diff --git a/arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso b/arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso index dc70b6fbc3d7..f08c0e272b53 100644 --- a/arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso +++ b/arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso @@ -13,6 +13,7 @@ &main_pmx0 { gpmc0_pins_default: gpmc0-pins-default { + bootph-all; pinctrl-single,pins = < AM64X_IOPAD(0x0094, PIN_INPUT, 7) /* (T19) GPMC0_BE1n.GPIO0_36 */ AM64X_IOPAD(0x003c, PIN_INPUT, 0) /* (T20) GPMC0_AD0 */ @@ -50,6 +51,7 @@ AM64X_IOPAD(0x00a4, PIN_OUTPUT, 0) /* (N17) GPMC0_DIR */ &main_gpio0 { gpio0-36 { + bootph-all; gpio-hog; gpios = <36 0>; input; @@ -58,6 +60,7 @@ gpio0-36 { }; &elm0 { + bootph-all; status = "okay"; }; @@ -106,30 +109,37 @@ partitions { #size-cells = <1>; partition@0 { + bootph-all; label = "NAND.tiboot3"; reg = <0x00000000 0x00200000>; /* 2M */ }; partition@200000 { + bootph-all; label = "NAND.tispl"; reg = <0x00200000 0x00200000>; /* 2M */ }; partition@400000 { + bootph-all; label = "NAND.tiboot3.backup"; /* 2M */ reg = <0x00400000 0x00200000>; /* BootROM looks at 4M */ }; partition@600000 { + bootph-all; label = "NAND.u-boot"; reg = <0x00600000 0x00400000>; /* 4M */ }; partition@a00000 { + bootph-all; label = "NAND.u-boot-env"; reg = <0x00a00000 0x00040000>; /* 256K */ }; partition@a40000 { + bootph-all; label = "NAND.u-boot-env.backup"; reg = <0x00a40000 0x00040000>; /* 256K */ }; partition@a80000 { + bootph-all; label = "NAND.file-system"; reg = <0x00a80000 0x3f580000>; };
NAND boot would require these nodes to be present at early stage. Ensure that by adding "bootph-all" to relevant nodes. Signed-off-by: Roger Quadros <rogerq@kernel.org> --- Changes in v2: - Add 'bootph-all' only to leaf nodes --- arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso | 10 ++++++++++ 1 file changed, 10 insertions(+) --- base-commit: 4031a2866a9f0f5c585cfee65b3fb5ab17c95276 change-id: 20240623-am642-evm-nand-bootph-03b68b4c9d9e Best regards,