From: Moteen Shah <m-shah@ti.com>
To: Judith Mendez <jm@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/5] arm64: dts: ti: k3-am6*: Add boot phase flag to support MMC boot
Date: Tue, 22 Apr 2025 11:15:31 +0530 [thread overview]
Message-ID: <c660f217-9bb1-4ba2-8d59-851f69b41042@ti.com> (raw)
In-Reply-To: <20250417233040.3658761-3-jm@ti.com>
Hey Judith,
On 18/04/25 05:00, Judith Mendez wrote:
> The bootph-all flag was introduced in dt-schema
> (dtschema/schemas/bootph.yaml) to define node usage across
> different boot phases.
>
> For eMMC and SD boot modes, voltage regulator nodes, io-expander
> nodes, gpio nodes, and MMC nodes need to be present in all boot
> stages, so add missing bootph-all phase flag to these nodes to
> support SD boot and eMMC boot.
>
> Signed-off-by: Judith Mendez <jm@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts | 12 ++++++++++++
> arch/arm64/boot/dts/ti/k3-am62a7-sk.dts | 2 ++
> 2 files changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts b/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts
> index 8e9fc00a6b3c7..aafdb90c0eb70 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62-lp-sk.dts
> @@ -69,6 +69,7 @@ vddshv_sdio: regulator-4 {
> gpios = <&main_gpio0 31 GPIO_ACTIVE_HIGH>;
> states = <1800000 0x0>,
> <3300000 0x1>;
> + bootph-all;
> };
> };
>
> @@ -77,12 +78,14 @@ vddshv_sdio_pins_default: vddshv-sdio-default-pins {
> pinctrl-single,pins = <
> AM62X_IOPAD(0x07c, PIN_OUTPUT, 7) /* (M19) GPMC0_CLK.GPIO0_31 */
> >;
> + bootph-all;
> };
>
> main_gpio1_ioexp_intr_pins_default: main-gpio1-ioexp-intr-default-pins {
> pinctrl-single,pins = <
> AM62X_IOPAD(0x01d4, PIN_INPUT, 7) /* (C13) UART0_RTSn.GPIO1_23 */
> >;
> + bootph-all;
> };
>
> pmic_irq_pins_default: pmic-irq-default-pins {
> @@ -118,6 +121,7 @@ exp1: gpio@22 {
>
> pinctrl-names = "default";
> pinctrl-0 = <&main_gpio1_ioexp_intr_pins_default>;
> + bootph-all;
> };
>
> exp2: gpio@23 {
> @@ -229,6 +233,14 @@ &tlv320aic3106 {
> DVDD-supply = <&buck2_reg>;
> };
>
> +&main_gpio0 {
> + bootph-all;
> +};
> +
> +&main_gpio1 {
> + bootph-all;
> +};
> +
> &gpmc0 {
> ranges = <0 0 0x00 0x51000000 0x01000000>; /* CS0 space. Min partition = 16MB */
> };
> diff --git a/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts b/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
> index 1c9d95696c839..7de4a9f139ad4 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
> @@ -313,6 +313,7 @@ AM62AX_IOPAD(0x200, PIN_INPUT_PULLUP, 0) /* (AC1) MMC0_DAT5 */
> AM62AX_IOPAD(0x1fc, PIN_INPUT_PULLUP, 0) /* (AD2) MMC0_DAT6 */
> AM62AX_IOPAD(0x1f8, PIN_INPUT_PULLUP, 0) /* (AC2) MMC0_DAT7 */
> >;
> + bootph-all;
> };
>
> main_mmc1_pins_default: main-mmc1-default-pins {
> @@ -615,6 +616,7 @@ &sdhci0 {
> pinctrl-names = "default";
> pinctrl-0 = <&main_mmc0_pins_default>;
> disable-wp;
> + bootph-all;
> };
>
Do we have the bootph-all flags in *-uboot.dtsi for the board to boot up?
If yes we will have to clean that up after this series gets merged.
Reviewed-by: Moteen Shah <m-shah@ti.com>
Regards,
Moteen Shah
> &sdhci1 {
next prev parent reply other threads:[~2025-04-22 5:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 23:30 [PATCH v2 0/5] Misc MMC updates Judith Mendez
2025-04-17 23:30 ` [PATCH v2 1/5] arm64: dts: ti: k3-am6*: Set eMMC clock parents to default Judith Mendez
2025-04-19 15:00 ` Kumar, Udit
2025-04-21 14:36 ` Judith Mendez
2025-04-22 4:08 ` Kumar, Udit
2025-04-22 12:37 ` Nishanth Menon
2025-04-22 14:08 ` Kumar, Udit
2025-04-22 17:17 ` Judith Mendez
2025-04-22 17:21 ` Kumar, Udit
2025-04-25 22:01 ` Judith Mendez
2025-04-17 23:30 ` [PATCH v2 2/5] arm64: dts: ti: k3-am6*: Add boot phase flag to support MMC boot Judith Mendez
2025-04-22 5:45 ` Moteen Shah [this message]
2025-04-17 23:30 ` [PATCH v2 3/5] arm64: dts: ti: k3-am65-main: Add missing taps to sdhci0 Judith Mendez
2025-04-22 5:00 ` Moteen Shah
2025-04-17 23:30 ` [PATCH v2 4/5] arm64: dts: ti: k3-am62*: Add non-removable flag for eMMC Judith Mendez
2025-04-19 14:47 ` Kumar, Udit
2025-04-17 23:30 ` [PATCH v2 5/5] arm64: dts: ti: k3-am6*: Remove disable-wp " Judith Mendez
2025-04-22 6:08 ` Moteen Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c660f217-9bb1-4ba2-8d59-851f69b41042@ti.com \
--to=m-shah@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jm@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox