From: Andrej Picej <andrej.picej@norik.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
robh+dt@kernel.org, kernel@pengutronix.de, leoyang.li@nxp.com,
krzysztof.kozlowski@canonical.com, festevam@gmail.com,
linux@rempel-privat.de, arnd@arndb.de, linux-imx@nxp.com,
y.bas@phytec.de
Subject: Re: [PATCH RESEND 3/4] ARM: dts: imx6ul: phycore: Change USB LDO voltage for usb compliance
Date: Fri, 18 Feb 2022 10:16:05 +0100 [thread overview]
Message-ID: <c84bfc22-7fa7-d101-3f52-a775c72579f7@norik.com> (raw)
In-Reply-To: <20220212054627.GZ4909@dragon>
On 12. 02. 22 06:46, Shawn Guo wrote:
> On Mon, Jan 31, 2022 at 09:05:25AM +0100, Andrej Picej wrote:
>> From: Yunus Bas <y.bas@phytec.de>
>>
>> According to the NXP usb compliance reference, the USB data lines for
>> Full/Low speed are connected to the ARM USB LDO, which is set to
>> minimum-voltage = 2.6V and maximum-voltage = 3.4 V. When the regulator
>> is deactivated, the data lines are defaulty driven with 2.6V, which is
>> not USB Full-Speed compliant. To be compliant, we need to activate the
>> USB LDO regulator and set it to the value of 3V, which is the specified
>> value in the USB specification.
>>
>> Signed-off-by: Yunus Bas <y.bas@phytec.de>
>> Signed-off-by: Andrej Picej <andrej.picej@norik.com>
>> ---
>> arch/arm/boot/dts/imx6ul-phytec-phycore-som.dtsi | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/imx6ul-phytec-phycore-som.dtsi b/arch/arm/boot/dts/imx6ul-phytec-phycore-som.dtsi
>> index 3cddc68917a0..2e03be3d43ec 100644
>> --- a/arch/arm/boot/dts/imx6ul-phytec-phycore-som.dtsi
>> +++ b/arch/arm/boot/dts/imx6ul-phytec-phycore-som.dtsi
>> @@ -83,6 +83,11 @@ eeprom@52 {
>> };
>> };
>>
>> +®_3p0 {
>> + regulator-min-microvolt = <3000000>;
>> + regulator-always-on;
>
> Rather than setting it always-on, shouldn't the consumer of the
> regulator turn it on/off as needed?
Sorry for late response, but I had to look into this a bit to see the
reason for using always-on.
The consumer should turn the regulator on/off, but the consumer doesn't
do that. If regulator is not specified as always-on the regulator stays
in disabled state, even when usb device is used. That's why this was
added here.
This should probably be fixed on consumer side. If you want I can drop
the patch from this series and submit the fixed version when the stuff
gets resolved.
BR,
Andrej
next prev parent reply other threads:[~2022-02-18 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 8:05 [PATCH RESEND 0/4] PHYTEC i.MX 6UL/ULL devicetree patches Andrej Picej
2022-01-31 8:05 ` [PATCH RESEND 1/4] dt-bindings: arm: fsl: add PHYTEC phyGATE Tauri i.MX6 ULL Andrej Picej
2022-02-11 13:26 ` Rob Herring
2022-01-31 8:05 ` [PATCH RESEND 2/4] ARM: dts: imx6ull: Add support for PHYTEC phyGATE-Tauri-S with i.MX 6ULL Andrej Picej
2022-02-12 5:43 ` Shawn Guo
2022-02-17 6:47 ` Andrej Picej
2022-01-31 8:05 ` [PATCH RESEND 3/4] ARM: dts: imx6ul: phycore: Change USB LDO voltage for usb compliance Andrej Picej
2022-02-12 5:46 ` Shawn Guo
2022-02-18 9:16 ` Andrej Picej [this message]
2022-01-31 8:05 ` [PATCH RESEND 4/4] ARM: dts: imx6ul: peb-av-02: move to 3 cell pwm Andrej Picej
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=c84bfc22-7fa7-d101-3f52-a775c72579f7@norik.com \
--to=andrej.picej@norik.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski@canonical.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux@rempel-privat.de \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=y.bas@phytec.de \
/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).