linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan Riedmüller" <s.riedmueller@phytec.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: s.christ@phytec.de, chf.fritz@googlemail.com, robh+dt@kernel.org,
	linux-imx@nxp.com, kernel@pengutronix.de, c.hemp@phytec.de,
	shawnguo@kernel.org, festevam@gmail.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] ARM: dts: imx6: phycore-som: fix emmc supply
Date: Thu, 12 Dec 2019 10:00:00 +0100	[thread overview]
Message-ID: <27152e13-57c6-9668-4500-d79148ecb019@phytec.de> (raw)
In-Reply-To: <20191210090920.a5aswmgihjzvsk25@pengutronix.de>

Hi Marco,

On 10.12.19 10:09, Marco Felsch wrote:
> Hi Stefan,
> 
> On 19-12-05 13:00, Stefan Riedmüller wrote:
>> Hi Marco,
>>
>> On 29.11.19 17:48, Marco Felsch wrote:
>>> Currently the vmmc is supplied by the 1.8V pmic rail but this is wrong.
>>> The 1.8V pmic rail is connected to the emmc vccq (vqmmc).
>>
>> I just checked the schematics again and actually both VCC and VCCQ are
>> connected to the 3.3V power rail. VCCQ can be connected to the 1.8V PMIC
>> power rail by solder jumper but default is 3.3V.
> 
> That's right.
> 
>> So I think either both should be connected to a fixed 3.3V regulator or
>> removed, since the default system does not support switching these voltages.
> 
> The question is why the regulator output isn't the default case and
> setting regulator-max-microvolt to 3.3V and regulator-min-microvolt to
> 1.8V? The PMIC LDO4 supports output voltages up to 3.6V so this should
> be okay.

That is a reasonable question. But since we can't change this here we need 
to take it as it is. So it is probably best to just drop both regulators.

Regards,
Stefan

> 
> Anyway dropping both regulators and using dummy-regulators should be
> fine too. I only want to remove this issue.
> 
> Regards,
>    Marco
> 
>> Regards,
>> Stefan
>>
>>>
>>> Fixes: ddec5d1c0047 ("ARM: dts: imx6: Add initial support for phyCORE-i.MX 6 SOM")
>>> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
>>> ---
>>>    arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi | 2 +-
>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi b/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
>>> index 46d4953c5588..44e333848b4d 100644
>>> --- a/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
>>> +++ b/arch/arm/boot/dts/imx6qdl-phytec-phycore-som.dtsi
>>> @@ -183,7 +183,7 @@
>>>    	pinctrl-0 = <&pinctrl_usdhc4>;
>>>    	bus-width = <8>;
>>>    	non-removable;
>>> -	vmmc-supply = <&vdd_emmc_1p8>;
>>> +	vqmmc-supply = <&vdd_emmc_1p8>;
>>>    	status = "disabled";
>>>    };
>>>
>>
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-12-12  9:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 16:48 [PATCH 1/3] ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage Marco Felsch
2019-11-29 16:48 ` [PATCH 2/3] ARM: dts: imx6: phycore-som: fix emmc supply Marco Felsch
2019-12-05 12:00   ` Stefan Riedmüller
2019-12-10  9:09     ` Marco Felsch
2019-12-12  9:00       ` Stefan Riedmüller [this message]
2019-11-29 16:48 ` [PATCH 3/3] ARM: dts: imx6: phycore-som: add pmic onkey device Marco Felsch
2020-01-07 13:48   ` Marco Felsch
2020-01-09  6:46   ` Shawn Guo
2019-12-02 10:09 ` [PATCH 1/3] ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage Stefan Riedmüller
2019-12-02 12:42   ` Marco Felsch
2019-12-02 13:55     ` Stefan Riedmüller
2019-12-02 14:14       ` Marco Felsch
2019-12-02 14:30         ` Stefan Riedmüller
2019-12-02 14:53           ` Marco Felsch
2019-12-03  8:11             ` Stefan Riedmüller
2019-12-03  8:33               ` Marco Felsch
2019-12-03  9:07                 ` Stefan Riedmüller
2019-12-03 11:44                 ` Lucas Stach
2019-12-03 12:37                   ` Stefan Riedmüller
2019-12-05  7:19                     ` Marco Felsch

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=27152e13-57c6-9668-4500-d79148ecb019@phytec.de \
    --to=s.riedmueller@phytec.de \
    --cc=c.hemp@phytec.de \
    --cc=chf.fritz@googlemail.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=m.felsch@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=s.christ@phytec.de \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).