Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Frieder Schrempf <frieder.schrempf@kontron.de>
To: Wojciech Dubowik <Wojciech.Dubowik@mt.com>, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	devicetree@vger.kernel.org, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	Francesco Dolcini <francesco@dolcini.it>,
	Philippe Schenker <philippe.schenker@impulsing.ch>,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: imx8mm-verdin: Link reg_usdhc2_vqmmc to usdhc2
Date: Wed, 23 Apr 2025 08:50:54 +0200	[thread overview]
Message-ID: <522decdf-faa0-433b-8b92-760f8fd04388@kontron.de> (raw)
In-Reply-To: <20250422124619.713235-1-Wojciech.Dubowik@mt.com>

Hi Wojciech,

Am 22.04.25 um 14:46 schrieb Wojciech Dubowik:
> [Sie erhalten nicht häufig E-Mails von wojciech.dubowik@mt.com. Weitere Informationen, warum dies wichtig ist, finden Sie unter https://aka.ms/LearnAboutSenderIdentification ]
> 
> Define vqmmc regulator-gpio for usdhc2 with vin-supply
> coming from LDO5.
> 
> Without this definition LDO5 will be powered down, disabling
> SD card after bootup. This has been introduced in commit
> f5aab0438ef1 ("regulator: pca9450: Fix enable register for LDO5").
> 
> Fixes: f5aab0438ef1 ("regulator: pca9450: Fix enable register for LDO5")
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Wojciech Dubowik <Wojciech.Dubowik@mt.com>
> ---
> v1 -> v2: https://lore.kernel.org/all/20250417112012.785420-1-Wojciech.Dubowik@mt.com/
>  - define gpio regulator for LDO5 vin controlled by vselect signal
> ---
>  .../boot/dts/freescale/imx8mm-verdin.dtsi     | 23 +++++++++++++++----
>  1 file changed, 19 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/freescale/imx8mm-verdin.dtsi b/arch/arm64/boot/dts/freescale/imx8mm-verdin.dtsi
> index 7251ad3a0017..9b56a36c5f77 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mm-verdin.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mm-verdin.dtsi
> @@ -144,6 +144,19 @@ reg_usdhc2_vmmc: regulator-usdhc2 {
>                 startup-delay-us = <20000>;
>         };
> 
> +       reg_usdhc2_vqmmc: regulator-usdhc2-vqmmc {
> +               compatible = "regulator-gpio";
> +               pinctrl-names = "default";
> +               pinctrl-0 = <&pinctrl_usdhc2_vsel>;
> +               gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>;
> +               regulator-max-microvolt = <3300000>;
> +               regulator-min-microvolt = <1800000>;
> +               states = <1800000 0x1>,
> +                        <3300000 0x0>;
> +               regulator-name = "PMIC_USDHC_VSELECT";
> +               vin-supply = <&reg_nvcc_sd>;
> +       };

Please do not describe the SD_VSEL of the PMIC as gpio-regulator. There
already is a regulator node reg_nvcc_sd for the LDO5 of the PMIC.

> +
>         reserved-memory {
>                 #address-cells = <2>;
>                 #size-cells = <2>;
> @@ -785,6 +798,7 @@ &usdhc2 {
>         pinctrl-2 = <&pinctrl_usdhc2_200mhz>, <&pinctrl_usdhc2_cd>;
>         pinctrl-3 = <&pinctrl_usdhc2_sleep>, <&pinctrl_usdhc2_cd_sleep>;
>         vmmc-supply = <&reg_usdhc2_vmmc>;
> +       vqmmc-supply = <&reg_usdhc2_vqmmc>;

You should reference the reg_nvcc_sd directly here and actually this
should be the only change you need to fix things, no?

>  };
> 
>  &wdog1 {
> @@ -1206,13 +1220,17 @@ pinctrl_usdhc2_pwr_en: usdhc2pwrengrp {
>                         <MX8MM_IOMUXC_NAND_CLE_GPIO3_IO5                0x6>;   /* SODIMM 76 */
>         };
> 
> +       pinctrl_usdhc2_vsel: usdhc2vselgrp {
> +               fsl,pins =
> +                       <MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT 0x10>; /* PMIC_USDHC_VSELECT */
> +       };
> +
>         /*
>          * Note: Due to ERR050080 we use discrete external on-module resistors pulling-up to the
>          * on-module +V3.3_1.8_SD (LDO5) rail and explicitly disable the internal pull-ups here.
>          */
>         pinctrl_usdhc2: usdhc2grp {
>                 fsl,pins =
> -                       <MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT         0x10>,

You should keep these pin definitions, but while at it make sure to
enable the SION bit so the PMIC driver can read back the status of the
SD_VSEL signal while the USDHC controller controls it in hardware.

Adding sd-vsel-gpios to the reg_nvcc_sd node makes this work. See [1]
for an example.

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8472751c4d96b558d60d0f6aede6b24b64bcb3c9

Thanks
Frieder

>                         <MX8MM_IOMUXC_SD2_CLK_USDHC2_CLK                0x90>,  /* SODIMM 78 */
>                         <MX8MM_IOMUXC_SD2_CMD_USDHC2_CMD                0x90>,  /* SODIMM 74 */
>                         <MX8MM_IOMUXC_SD2_DATA0_USDHC2_DATA0            0x90>,  /* SODIMM 80 */
> @@ -1223,7 +1241,6 @@ pinctrl_usdhc2: usdhc2grp {
> 
>         pinctrl_usdhc2_100mhz: usdhc2-100mhzgrp {
>                 fsl,pins =
> -                       <MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT         0x10>,
>                         <MX8MM_IOMUXC_SD2_CLK_USDHC2_CLK                0x94>,
>                         <MX8MM_IOMUXC_SD2_CMD_USDHC2_CMD                0x94>,
>                         <MX8MM_IOMUXC_SD2_DATA0_USDHC2_DATA0            0x94>,
> @@ -1234,7 +1251,6 @@ pinctrl_usdhc2_100mhz: usdhc2-100mhzgrp {
> 
>         pinctrl_usdhc2_200mhz: usdhc2-200mhzgrp {
>                 fsl,pins =
> -                       <MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT         0x10>,
>                         <MX8MM_IOMUXC_SD2_CLK_USDHC2_CLK                0x96>,
>                         <MX8MM_IOMUXC_SD2_CMD_USDHC2_CMD                0x96>,
>                         <MX8MM_IOMUXC_SD2_DATA0_USDHC2_DATA0            0x96>,
> @@ -1246,7 +1262,6 @@ pinctrl_usdhc2_200mhz: usdhc2-200mhzgrp {
>         /* Avoid backfeeding with removed card power */
>         pinctrl_usdhc2_sleep: usdhc2slpgrp {
>                 fsl,pins =
> -                       <MX8MM_IOMUXC_GPIO1_IO04_USDHC2_VSELECT         0x0>,
>                         <MX8MM_IOMUXC_SD2_CLK_USDHC2_CLK                0x0>,
>                         <MX8MM_IOMUXC_SD2_CMD_USDHC2_CMD                0x0>,
>                         <MX8MM_IOMUXC_SD2_DATA0_USDHC2_DATA0            0x0>,
> --
> 2.47.2
> 
> 


  parent reply	other threads:[~2025-04-23  6:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 12:46 [PATCH v2] arm64: dts: imx8mm-verdin: Link reg_usdhc2_vqmmc to usdhc2 Wojciech Dubowik
2025-04-22 13:01 ` Francesco Dolcini
2025-04-23  6:50 ` Frieder Schrempf [this message]
2025-04-23  7:08   ` Francesco Dolcini
2025-04-23  8:00     ` Frieder Schrempf
2025-04-23 10:26       ` Francesco Dolcini
2025-04-23 11:22         ` Frieder Schrempf

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=522decdf-faa0-433b-8b92-760f8fd04388@kontron.de \
    --to=frieder.schrempf@kontron.de \
    --cc=Wojciech.Dubowik@mt.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=francesco@dolcini.it \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philippe.schenker@impulsing.ch \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=stable@vger.kernel.org \
    /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