* [PATCHv3 0/2] Odroid c2 usb fixs
@ 2019-01-29 10:25 Anand Moon
2019-01-29 10:25 ` [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning Anand Moon
2019-01-29 10:25 ` [PATCHv3 2/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy regulator power failed warning Anand Moon
0 siblings, 2 replies; 9+ messages in thread
From: Anand Moon @ 2019-01-29 10:25 UTC (permalink / raw)
To: devicetree, linux-arm-kernel, linux-amlogic, linux-kernel
Cc: Martin Blumenstingl, Kevin Hilman, Rob Herring, Jerome Brunet,
Neil Armstrong
This is follow up on my previous patches.
Changes rebase on mainline: 5.0-rc4
[0] https://lore.kernel.org/patchwork/patch/1031243/
[1] https://lore.kernel.org/patchwork/patch/1031243/
changes depend on phy patch
[2] https://patchwork.kernel.org/patch/10777359/
As per Martin's suggestion and input I have tried to fix below issue.
Fixed the phy power issue on the usb port.
# cat /sys/kernel/debug/regulator/regulator_summary
regulator use open bypass opmode voltage current min max
---------------------------------------------------------------------------------------
regulator-dummy 5 4 0 unknown 0mV 0mA 0mV 0mV
c9100000.usb 1 0mA 0mV 0mV
c9100000.usb 1 0mA 0mV 0mV
c9000000.usb 1 0mA 0mV 0mV
c9000000.usb 1 0mA 0mV 0mV
P5V0 1 1 0 unknown 5000mV 0mA 5000mV 5000mV
USB_OTG_PWR 4 2 0 unknown 5000mV 0mA 5000mV 5000mV
phy-c0000020.phy.1 2 0mA 0mV 0mV
phy-c0000000.phy.0 2 0mA 0mV 0mV
# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 3, If 2, Class=Audio, Driver=, 480M
|__ Port 3: Dev 3, If 3, Class=Audio, Driver=, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
Now hotpluing of usb device is working on odroid c2 boards.
TODO: need to initialize the otg usb port to accept usb device.
Any input are welcome
Best Regards
-Anand
Anand Moon (2):
ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning
ARM64: dts: meson-gxbb-odroidc2: Fix usb phy regulator power failed
warning
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 10 ++++++++++
1 file changed, 10 insertions(+)
--
2.20.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply [flat|nested] 9+ messages in thread* [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning
2019-01-29 10:25 [PATCHv3 0/2] Odroid c2 usb fixs Anand Moon
@ 2019-01-29 10:25 ` Anand Moon
2019-02-04 13:58 ` Martin Blumenstingl
2019-01-29 10:25 ` [PATCHv3 2/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy regulator power failed warning Anand Moon
1 sibling, 1 reply; 9+ messages in thread
From: Anand Moon @ 2019-01-29 10:25 UTC (permalink / raw)
To: devicetree, linux-arm-kernel, linux-amlogic, linux-kernel
Cc: Martin Blumenstingl, Kevin Hilman, Rob Herring, Jerome Brunet,
Neil Armstrong
Add missing vin-supply node 5.0V regulator setting to power
to usb ports, changes help fix the usb reset warning.
[ 795.380156] usb 1-1.2: reset high-speed USB device number 3 using dwc2
[ 798.356073] usb 1-1.2: reset high-speed USB device number 3 using dwc2
[ 801.331999] usb 1-1.2: reset high-speed USB device number 3 using dwc2
[ 804.307919] usb 1-1.2: reset high-speed USB device number 3 using dwc2
[ 807.283844] usb 1-1.2: reset high-speed USB device number 3 using dwc2
Fixes: 5a0803bd5ae (ARM64: dts: meson-gxbb-odroidc2: Enable USB Nodes)
Tested-by: Kevin Hilman <khilman@baylibre.com>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>
Cc: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Anand Moon <linux.amoon@gmail.com>
---
changes from prevoius
regulator use open bypass opmode voltage current min max
---------------------------------------------------------------------------------------
regulator-dummy 5 4 0 unknown 0mV 0mA 0mV 0mV
c9100000.usb 1 0mA 0mV 0mV
c9100000.usb 1 0mA 0mV 0mV
c9000000.usb 1 0mA 0mV 0mV
c9000000.usb 1 0mA 0mV 0mV
P5V0 1 1 0 unknown 5000mV 0mA 5000mV 5000mV
USB_OTG_PWR 4 2 0 unknown 5000mV 0mA 5000mV 5000mV
phy-c0000020.phy.1 2 0mA 0mV 0mV
phy-c0000000.phy.0 2 0mA 0mV 0mV
--
---
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 2e1cd5e3a246..da729ed00408 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -28,6 +28,13 @@
reg = <0x0 0x0 0x0 0x80000000>;
};
+ p5v0: regulator-p5v0 {
+ compatible = "regulator-fixed";
+ regulator-name = "P5V0";
+ regulator-min-microvolt = <5000000>;
+ regulator-max-microvolt = <5000000>;
+ };
+
usb_otg_pwr: regulator-usb-pwrs {
compatible = "regulator-fixed";
@@ -36,6 +43,8 @@
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
+ vin-supply = <&p5v0>;
+
gpio = <&gpio_ao GPIOAO_5 GPIO_ACTIVE_HIGH>;
enable-active-high;
};
--
2.20.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning
2019-01-29 10:25 ` [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning Anand Moon
@ 2019-02-04 13:58 ` Martin Blumenstingl
2019-02-04 20:04 ` Anand Moon
0 siblings, 1 reply; 9+ messages in thread
From: Martin Blumenstingl @ 2019-02-04 13:58 UTC (permalink / raw)
To: Anand Moon
Cc: devicetree, Neil Armstrong, Kevin Hilman, linux-kernel,
Rob Herring, linux-amlogic, linux-arm-kernel, Jerome Brunet
Hi Anand,
On Tue, Jan 29, 2019 at 11:25 AM Anand Moon <linux.amoon@gmail.com> wrote:
>
> Add missing vin-supply node 5.0V regulator setting to power
> to usb ports, changes help fix the usb reset warning.
>
> [ 795.380156] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> [ 798.356073] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> [ 801.331999] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> [ 804.307919] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> [ 807.283844] usb 1-1.2: reset high-speed USB device number 3 using dwc2
>
> Fixes: 5a0803bd5ae (ARM64: dts: meson-gxbb-odroidc2: Enable USB Nodes)
> Tested-by: Kevin Hilman <khilman@baylibre.com>
> Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Cc: Jerome Brunet <jbrunet@baylibre.com>
> Cc: Neil Armstrong <narmstrong@baylibre.com>
> Signed-off-by: Anand Moon <linux.amoon@gmail.com>
> ---
> changes from prevoius
>
> regulator use open bypass opmode voltage current min max
> ---------------------------------------------------------------------------------------
> regulator-dummy 5 4 0 unknown 0mV 0mA 0mV 0mV
> c9100000.usb 1 0mA 0mV 0mV
> c9100000.usb 1 0mA 0mV 0mV
> c9000000.usb 1 0mA 0mV 0mV
> c9000000.usb 1 0mA 0mV 0mV
> P5V0 1 1 0 unknown 5000mV 0mA 5000mV 5000mV
> USB_OTG_PWR 4 2 0 unknown 5000mV 0mA 5000mV 5000mV
> phy-c0000020.phy.1 2 0mA 0mV 0mV
> phy-c0000000.phy.0 2 0mA 0mV 0mV
> --
> ---
> arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> index 2e1cd5e3a246..da729ed00408 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> +++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> @@ -28,6 +28,13 @@
> reg = <0x0 0x0 0x0 0x80000000>;
> };
>
> + p5v0: regulator-p5v0 {
> + compatible = "regulator-fixed";
> + regulator-name = "P5V0";
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + };
> +
> usb_otg_pwr: regulator-usb-pwrs {
> compatible = "regulator-fixed";
>
> @@ -36,6 +43,8 @@
> regulator-min-microvolt = <5000000>;
> regulator-max-microvolt = <5000000>;
>
> + vin-supply = <&p5v0>;
did you find out why this patch fixes the USB_OTG_PWR regulator?
based on just reading the patch I can't find an explanation myself
have you tested without this patch to rule out that you hit some bug
in the regulator framework back when you wrote the patch?
(I don't have an Odroid-C2 so I can't test this myself).
Regards
Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning
2019-02-04 13:58 ` Martin Blumenstingl
@ 2019-02-04 20:04 ` Anand Moon
2019-02-04 20:49 ` Martin Blumenstingl
0 siblings, 1 reply; 9+ messages in thread
From: Anand Moon @ 2019-02-04 20:04 UTC (permalink / raw)
To: Martin Blumenstingl
Cc: devicetree, Neil Armstrong, Kevin Hilman, Linux Kernel,
Rob Herring, linux-amlogic, linux-arm-kernel, Jerome Brunet
Hi Martin,
Thanks for your review comments.
On Mon, 4 Feb 2019 at 19:29, Martin Blumenstingl
<martin.blumenstingl@googlemail.com> wrote:
>
> Hi Anand,
>
> On Tue, Jan 29, 2019 at 11:25 AM Anand Moon <linux.amoon@gmail.com> wrote:
> >
> > Add missing vin-supply node 5.0V regulator setting to power
> > to usb ports, changes help fix the usb reset warning.
> >
> > [ 795.380156] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> > [ 798.356073] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> > [ 801.331999] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> > [ 804.307919] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> > [ 807.283844] usb 1-1.2: reset high-speed USB device number 3 using dwc2
> >
> > Fixes: 5a0803bd5ae (ARM64: dts: meson-gxbb-odroidc2: Enable USB Nodes)
> > Tested-by: Kevin Hilman <khilman@baylibre.com>
> > Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> > Cc: Jerome Brunet <jbrunet@baylibre.com>
> > Cc: Neil Armstrong <narmstrong@baylibre.com>
> > Signed-off-by: Anand Moon <linux.amoon@gmail.com>
> > ---
> > changes from prevoius
> >
> > regulator use open bypass opmode voltage current min max
> > ---------------------------------------------------------------------------------------
> > regulator-dummy 5 4 0 unknown 0mV 0mA 0mV 0mV
> > c9100000.usb 1 0mA 0mV 0mV
> > c9100000.usb 1 0mA 0mV 0mV
> > c9000000.usb 1 0mA 0mV 0mV
> > c9000000.usb 1 0mA 0mV 0mV
> > P5V0 1 1 0 unknown 5000mV 0mA 5000mV 5000mV
> > USB_OTG_PWR 4 2 0 unknown 5000mV 0mA 5000mV 5000mV
> > phy-c0000020.phy.1 2 0mA 0mV 0mV
> > phy-c0000000.phy.0 2 0mA 0mV 0mV
> > --
> > ---
> > arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 9 +++++++++
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> > index 2e1cd5e3a246..da729ed00408 100644
> > --- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> > +++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> > @@ -28,6 +28,13 @@
> > reg = <0x0 0x0 0x0 0x80000000>;
> > };
> >
> > + p5v0: regulator-p5v0 {
> > + compatible = "regulator-fixed";
> > + regulator-name = "P5V0";
> > + regulator-min-microvolt = <5000000>;
> > + regulator-max-microvolt = <5000000>;
> > + };
> > +
> > usb_otg_pwr: regulator-usb-pwrs {
> > compatible = "regulator-fixed";
> >
> > @@ -36,6 +43,8 @@
> > regulator-min-microvolt = <5000000>;
> > regulator-max-microvolt = <5000000>;
> >
> > + vin-supply = <&p5v0>;
> did you find out why this patch fixes the USB_OTG_PWR regulator?
> based on just reading the patch I can't find an explanation myself
>
As per the device tree binding we need this setting to enable power input source
[0] Documentation/devicetree/bindings/regulator/fixed-regulator.txt
*I have observed few more place where this setting is missing*
> have you tested without this patch to rule out that you hit some bug
> in the regulator framework back when you wrote the patch?
> (I don't have an Odroid-C2 so I can't test this myself).
>
Yes I have tested this patch.Some device like usb camera and usb hard drive
when connected to usb port will generate warning message.
which shows us that not enough power is being set to the port.
>
> Regards
> Martin
Best Regards
-Anand
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning
2019-02-04 20:04 ` Anand Moon
@ 2019-02-04 20:49 ` Martin Blumenstingl
2019-02-05 19:53 ` Anand Moon
0 siblings, 1 reply; 9+ messages in thread
From: Martin Blumenstingl @ 2019-02-04 20:49 UTC (permalink / raw)
To: Anand Moon
Cc: devicetree, Neil Armstrong, Kevin Hilman, Linux Kernel,
Rob Herring, linux-amlogic, linux-arm-kernel, Jerome Brunet
Hi Anand,
On Mon, Feb 4, 2019 at 9:04 PM Anand Moon <linux.amoon@gmail.com> wrote:
[...]
> > > @@ -36,6 +43,8 @@
> > > regulator-min-microvolt = <5000000>;
> > > regulator-max-microvolt = <5000000>;
> > >
> > > + vin-supply = <&p5v0>;
> > did you find out why this patch fixes the USB_OTG_PWR regulator?
> > based on just reading the patch I can't find an explanation myself
> >
>
> As per the device tree binding we need this setting to enable power input source
> [0] Documentation/devicetree/bindings/regulator/fixed-regulator.txt
>
> *I have observed few more place where this setting is missing*
OK, I understand that we should describe the hierarchy of the regulators
> > have you tested without this patch to rule out that you hit some bug
> > in the regulator framework back when you wrote the patch?
> > (I don't have an Odroid-C2 so I can't test this myself).
> >
>
> Yes I have tested this patch.Some device like usb camera and usb hard drive
> when connected to usb port will generate warning message.
> which shows us that not enough power is being set to the port.
I don't understand why adding "p5v0" as parent of "usb_otg_pwr"
changes the output of "usb_otg_pwr":
- "p5v0" is a fixed regulator which cannot be controlled at all (apart
from removing power from it)
- "usb_otg_pwr" does not have any current limits set inside the .dts
- "usb_otg_pwr" has the same fixed voltage as the new "p5v0" regulator
what are your steps-to-reproduce for your original issue ("reset
high-speed USB device number 3 using dwc2")?
Regards
Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning
2019-02-04 20:49 ` Martin Blumenstingl
@ 2019-02-05 19:53 ` Anand Moon
0 siblings, 0 replies; 9+ messages in thread
From: Anand Moon @ 2019-02-05 19:53 UTC (permalink / raw)
To: Martin Blumenstingl
Cc: devicetree, Neil Armstrong, Kevin Hilman, Linux Kernel,
Rob Herring, linux-amlogic, linux-arm-kernel, Jerome Brunet
hi Martin,
On Tue, 5 Feb 2019 at 02:19, Martin Blumenstingl
<martin.blumenstingl@googlemail.com> wrote:
>
> Hi Anand,
>
> On Mon, Feb 4, 2019 at 9:04 PM Anand Moon <linux.amoon@gmail.com> wrote:
> [...]
> > > > @@ -36,6 +43,8 @@
> > > > regulator-min-microvolt = <5000000>;
> > > > regulator-max-microvolt = <5000000>;
> > > >
> > > > + vin-supply = <&p5v0>;
> > > did you find out why this patch fixes the USB_OTG_PWR regulator?
> > > based on just reading the patch I can't find an explanation myself
> > >
> >
> > As per the device tree binding we need this setting to enable power input source
> > [0] Documentation/devicetree/bindings/regulator/fixed-regulator.txt
> >
> > *I have observed few more place where this setting is missing*
> OK, I understand that we should describe the hierarchy of the regulators
>
> > > have you tested without this patch to rule out that you hit some bug
> > > in the regulator framework back when you wrote the patch?
> > > (I don't have an Odroid-C2 so I can't test this myself).
> > >
> >
> > Yes I have tested this patch.Some device like usb camera and usb hard drive
> > when connected to usb port will generate warning message.
> > which shows us that not enough power is being set to the port.
> I don't understand why adding "p5v0" as parent of "usb_otg_pwr"
> changes the output of "usb_otg_pwr":
> - "p5v0" is a fixed regulator which cannot be controlled at all (apart
> from removing power from it)
> - "usb_otg_pwr" does not have any current limits set inside the .dts
> - "usb_otg_pwr" has the same fixed voltage as the new "p5v0" regulator
>
> what are your steps-to-reproduce for your original issue ("reset
> high-speed USB device number 3 using dwc2")?
>
I have tried to reproduce this but some how I cannot get the logs
I might have enable some more debug options to reproduce but currently
it's lost.
because of over flashing of the operating system on sdcards.
But definitely this fix the power issue needed to get usb-storage
device to work on Odroid c1/c2 boards.
>
> Regards
> Martin
Best Regards
-Anand
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply [flat|nested] 9+ messages in thread
* [PATCHv3 2/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy regulator power failed warning
2019-01-29 10:25 [PATCHv3 0/2] Odroid c2 usb fixs Anand Moon
2019-01-29 10:25 ` [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning Anand Moon
@ 2019-01-29 10:25 ` Anand Moon
2019-02-04 14:06 ` Martin Blumenstingl
1 sibling, 1 reply; 9+ messages in thread
From: Anand Moon @ 2019-01-29 10:25 UTC (permalink / raw)
To: devicetree, linux-arm-kernel, linux-amlogic, linux-kernel
Cc: Martin Blumenstingl, Kevin Hilman, Rob Herring, Jerome Brunet,
Neil Armstrong
Override the dr_mode from "host" to "otg" for USB_HOST controller (usb0)
changes help usb_phy0->usb0 initialization of OTG bus port.
Changes fix the below warning.
[ 1.183681] dwc2 c9000000.usb: c9000000.usb supply vusb_d not found, using dummy regulator
[ 1.190627] dwc2 c9000000.usb: Linked as a consumer to regulator.0
[ 1.196696] dwc2 c9000000.usb: c9000000.usb supply vusb_a not found, using dummy regulator
[ 1.206094] phy phy-c0000000.phy.0: USB ID detect failed!
[ 1.210243] phy phy-c0000000.phy.0: phy poweron failed --> -22
[ 1.216072] WARNING: CPU: 0 PID: 78 at drivers/regulator/core.c:2054 _regulator_put.part.11+0xf0/0xf8
[ 1.225147] Modules linked in:
[ 1.228169] CPU: 0 PID: 78 Comm: kworker/0:1 Not tainted 5.0.0-rc4-xc2ml #1
[ 1.235066] Hardware name: Hardkernel ODROID-C2 (DT)
[ 1.239987] Workqueue: events deferred_probe_work_func
[ 1.245072] pstate: 80000005 (Nzcv daif -PAN -UAO)
[ 1.249816] pc : _regulator_put.part.11+0xf0/0xf8
[ 1.254473] lr : regulator_put+0x34/0x48
[ 1.258353] sp : ffff0000117b3b00
[ 1.261630] x29: ffff0000117b3b00 x28: 0000000000000000
[ 1.266891] x27: ffff80007ec1a7b8 x26: ffff000010eec280
[ 1.272153] x25: 0000000000000000 x24: 0000000000000009
[ 1.277414] x23: ffff0000117b3bc8 x22: ffff80007ecd3c00
[ 1.282675] x21: ffff0000111ad6c8 x20: ffff80007ecd3e00
[ 1.287936] x19: ffff80007ecd3e00 x18: 0000000000000124
[ 1.293198] x17: 0000000000000000 x16: 0000000000000000
[ 1.298459] x15: 0000000000000400 x14: 0000000000000400
[ 1.303720] x13: ff00000000000000 x12: ffffffffffffffff
[ 1.308981] x11: 0000000000000038 x10: 0000000000000040
[ 1.314243] x9 : ffff0000111c58b0 x8 : ffff0000111c58a8
[ 1.319504] x7 : ffff80006b055200 x6 : ffff80007edd2880
[ 1.324765] x5 : ffff80007f400248 x4 : ffff80007fb92b00
[ 1.330026] x3 : ffff0000112c9d58 x2 : ffff80007edd2880
[ 1.335288] x1 : 0000000000000000 x0 : 0000000000000001
[ 1.340549] Call trace:
[ 1.342966] _regulator_put.part.11+0xf0/0xf8
[ 1.347278] regulator_put+0x34/0x48
[ 1.350814] regulator_bulk_free+0x30/0x50
[ 1.354868] devm_regulator_bulk_release+0x18/0x20
[ 1.359612] release_nodes+0x1b0/0x220
[ 1.363320] devres_release_all+0x34/0x50
[ 1.367288] really_probe+0xec/0x290
[ 1.370824] driver_probe_device+0x54/0xe8
[ 1.374878] __device_attach_driver+0xb8/0xe8
[ 1.379190] bus_for_each_drv+0x78/0xc8
[ 1.382985] __device_attach+0xd4/0x130
[ 1.386780] device_initial_probe+0x10/0x18
[ 1.390920] bus_probe_device+0x90/0x98
[ 1.394715] deferred_probe_work_func+0x6c/0xa0
[ 1.399203] process_one_work+0x1e0/0x318
[ 1.403168] worker_thread+0x228/0x428
[ 1.406877] kthread+0x124/0x128
[ 1.410070] ret_from_fork+0x10/0x18
[ 1.413603] ---[ end trace 498aca4cb07e5377 ]---
[ 1.418251] WARNING: CPU: 0 PID: 78 at drivers/regulator/core.c:2054 _regulator_put.part.11+0xf0/0xf8
[ 1.427316] Modules linked in:
[ 1.430338] CPU: 0 PID: 78 Comm: kworker/0:1 Tainted: G W 5.0.0-rc4-xc2ml #1
[ 1.438615] Hardware name: Hardkernel ODROID-C2 (DT)
[ 1.443534] Workqueue: events deferred_probe_work_func
[ 1.448621] pstate: 80000005 (Nzcv daif -PAN -UAO)
[ 1.453366] pc : _regulator_put.part.11+0xf0/0xf8
[ 1.458023] lr : regulator_put+0x34/0x48
[ 1.461903] sp : ffff0000117b3b00
[ 1.465180] x29: ffff0000117b3b00 x28: 0000000000000000
[ 1.470441] x27: ffff80007ec1a7b8 x26: ffff000010eec280
[ 1.475703] x25: 0000000000000000 x24: 0000000000000009
[ 1.480964] x23: ffff0000117b3bc8 x22: ffff80007ecd3c00
[ 1.486225] x21: ffff0000111ad6c8 x20: ffff80007ecd3f00
[ 1.491486] x19: ffff80007ecd3f00 x18: 0000000000000007
[ 1.496748] x17: 0000000000000000 x16: 0000000000000000
[ 1.502009] x15: 0000000000000400 x14: ffff80000531da90
[ 1.507270] x13: ffff80007f4ae050 x12: 0000000000000000
[ 1.512531] x11: ffff80007f4adff0 x10: 0000000000000040
[ 1.517793] x9 : ffff80000531da98 x8 : 0000000040000000
[ 1.523054] x7 : ffff80006b054700 x6 : 0000000000000001
[ 1.528315] x5 : ffff0000105a868c x4 : ffff80007edd2880
[ 1.533576] x3 : ffff0000112c9d58 x2 : ffff80007edd2880
[ 1.538838] x1 : 0000000000000000 x0 : 0000000000000001
[ 1.544098] Call trace:
[ 1.546516] _regulator_put.part.11+0xf0/0xf8
[ 1.550828] regulator_put+0x34/0x48
[ 1.554364] regulator_bulk_free+0x30/0x50
[ 1.558417] devm_regulator_bulk_release+0x18/0x20
[ 1.563161] release_nodes+0x1b0/0x220
[ 1.566870] devres_release_all+0x34/0x50
[ 1.570838] really_probe+0xec/0x290
[ 1.574374] driver_probe_device+0x54/0xe8
[ 1.578428] __device_attach_driver+0xb8/0xe8
[ 1.582740] bus_for_each_drv+0x78/0xc8
[ 1.586535] __device_attach+0xd4/0x130
[ 1.590330] device_initial_probe+0x10/0x18
[ 1.594470] bus_probe_device+0x90/0x98
[ 1.598265] deferred_probe_work_func+0x6c/0xa0
[ 1.602751] process_one_work+0x1e0/0x318
[ 1.606718] worker_thread+0x228/0x428
[ 1.610427] kthread+0x124/0x128
[ 1.613618] ret_from_fork+0x10/0x18
[ 1.617153] ---[ end trace 498aca4cb07e5378 ]---
[ 1.621778] dwc2: probe of c9000000.usb failed with error -22
Fixes: 5a0803bd5ae (ARM64: dts: meson-gxbb-odroidc2: Enable USB Nodes)
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>
Cc: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Anand Moon <linux.amoon@gmail.com>
---
Changes from previous patch
change dr_mode from "peripheral" to "otg"
Since usb_phy0 is otg port as per the shematic
Fixed the commit messages with latest warning
This patch depend on this below patch
[0] https://patchwork.kernel.org/patch/10777359/
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 3, If 2, Class=Audio, Driver=, 480M
|__ Port 3: Dev 3, If 3, Class=Audio, Driver=, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
drop tested but from Kevin
---
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index da729ed00408..5d81ad02483b 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -312,6 +312,7 @@
&usb0 {
status = "okay";
+ dr_mode = "otg";
};
&usb1 {
--
2.20.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: [PATCHv3 2/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy regulator power failed warning
2019-01-29 10:25 ` [PATCHv3 2/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy regulator power failed warning Anand Moon
@ 2019-02-04 14:06 ` Martin Blumenstingl
2019-02-04 20:05 ` Anand Moon
0 siblings, 1 reply; 9+ messages in thread
From: Martin Blumenstingl @ 2019-02-04 14:06 UTC (permalink / raw)
To: Anand Moon
Cc: devicetree, Neil Armstrong, Kevin Hilman, linux-kernel,
Rob Herring, linux-amlogic, linux-arm-kernel, Jerome Brunet
Hi Anand,
On Tue, Jan 29, 2019 at 11:25 AM Anand Moon <linux.amoon@gmail.com> wrote:
>
> Override the dr_mode from "host" to "otg" for USB_HOST controller (usb0)
> changes help usb_phy0->usb0 initialization of OTG bus port.
>
> Changes fix the below warning.
>
> [ 1.183681] dwc2 c9000000.usb: c9000000.usb supply vusb_d not found, using dummy regulator
> [ 1.190627] dwc2 c9000000.usb: Linked as a consumer to regulator.0
> [ 1.196696] dwc2 c9000000.usb: c9000000.usb supply vusb_a not found, using dummy regulator
> [ 1.206094] phy phy-c0000000.phy.0: USB ID detect failed!
> [ 1.210243] phy phy-c0000000.phy.0: phy poweron failed --> -22
I wonder if the warning below are a side-effect of "phy poweron failed"...
> [ 1.216072] WARNING: CPU: 0 PID: 78 at drivers/regulator/core.c:2054 _regulator_put.part.11+0xf0/0xf8
> [ 1.225147] Modules linked in:
> [ 1.228169] CPU: 0 PID: 78 Comm: kworker/0:1 Not tainted 5.0.0-rc4-xc2ml #1
> [ 1.235066] Hardware name: Hardkernel ODROID-C2 (DT)
> [ 1.239987] Workqueue: events deferred_probe_work_func
> [ 1.245072] pstate: 80000005 (Nzcv daif -PAN -UAO)
> [ 1.249816] pc : _regulator_put.part.11+0xf0/0xf8
> [ 1.254473] lr : regulator_put+0x34/0x48
> [ 1.258353] sp : ffff0000117b3b00
> [ 1.261630] x29: ffff0000117b3b00 x28: 0000000000000000
> [ 1.266891] x27: ffff80007ec1a7b8 x26: ffff000010eec280
> [ 1.272153] x25: 0000000000000000 x24: 0000000000000009
> [ 1.277414] x23: ffff0000117b3bc8 x22: ffff80007ecd3c00
> [ 1.282675] x21: ffff0000111ad6c8 x20: ffff80007ecd3e00
> [ 1.287936] x19: ffff80007ecd3e00 x18: 0000000000000124
> [ 1.293198] x17: 0000000000000000 x16: 0000000000000000
> [ 1.298459] x15: 0000000000000400 x14: 0000000000000400
> [ 1.303720] x13: ff00000000000000 x12: ffffffffffffffff
> [ 1.308981] x11: 0000000000000038 x10: 0000000000000040
> [ 1.314243] x9 : ffff0000111c58b0 x8 : ffff0000111c58a8
> [ 1.319504] x7 : ffff80006b055200 x6 : ffff80007edd2880
> [ 1.324765] x5 : ffff80007f400248 x4 : ffff80007fb92b00
> [ 1.330026] x3 : ffff0000112c9d58 x2 : ffff80007edd2880
> [ 1.335288] x1 : 0000000000000000 x0 : 0000000000000001
> [ 1.340549] Call trace:
> [ 1.342966] _regulator_put.part.11+0xf0/0xf8
> [ 1.347278] regulator_put+0x34/0x48
> [ 1.350814] regulator_bulk_free+0x30/0x50
> [ 1.354868] devm_regulator_bulk_release+0x18/0x20
> [ 1.359612] release_nodes+0x1b0/0x220
> [ 1.363320] devres_release_all+0x34/0x50
> [ 1.367288] really_probe+0xec/0x290
> [ 1.370824] driver_probe_device+0x54/0xe8
> [ 1.374878] __device_attach_driver+0xb8/0xe8
> [ 1.379190] bus_for_each_drv+0x78/0xc8
> [ 1.382985] __device_attach+0xd4/0x130
> [ 1.386780] device_initial_probe+0x10/0x18
> [ 1.390920] bus_probe_device+0x90/0x98
> [ 1.394715] deferred_probe_work_func+0x6c/0xa0
> [ 1.399203] process_one_work+0x1e0/0x318
> [ 1.403168] worker_thread+0x228/0x428
> [ 1.406877] kthread+0x124/0x128
> [ 1.410070] ret_from_fork+0x10/0x18
> [ 1.413603] ---[ end trace 498aca4cb07e5377 ]---
phy_power_on fails above with -EINVAL and then something else breaks
(it seems like you're hitting the WARN_ON in drivers/regulator/core.c
below the comment which states: "Docs say you must disable before
calling regulator_put()")
so this looks like a bug in either the dwc2 driver or the PHY
framework. can you please report that to the dwc2 and PHY maintainers
so it can be fixed independently?
Regards
Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [PATCHv3 2/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy regulator power failed warning
2019-02-04 14:06 ` Martin Blumenstingl
@ 2019-02-04 20:05 ` Anand Moon
0 siblings, 0 replies; 9+ messages in thread
From: Anand Moon @ 2019-02-04 20:05 UTC (permalink / raw)
To: Martin Blumenstingl
Cc: devicetree, Neil Armstrong, Kevin Hilman, Linux Kernel,
Rob Herring, linux-amlogic, linux-arm-kernel, Jerome Brunet
Hi Martin,
On Mon, 4 Feb 2019 at 19:36, Martin Blumenstingl
<martin.blumenstingl@googlemail.com> wrote:
>
> Hi Anand,
>
> On Tue, Jan 29, 2019 at 11:25 AM Anand Moon <linux.amoon@gmail.com> wrote:
> >
> > Override the dr_mode from "host" to "otg" for USB_HOST controller (usb0)
> > changes help usb_phy0->usb0 initialization of OTG bus port.
> >
> > Changes fix the below warning.
> >
> > [ 1.183681] dwc2 c9000000.usb: c9000000.usb supply vusb_d not found, using dummy regulator
> > [ 1.190627] dwc2 c9000000.usb: Linked as a consumer to regulator.0
> > [ 1.196696] dwc2 c9000000.usb: c9000000.usb supply vusb_a not found, using dummy regulator
> > [ 1.206094] phy phy-c0000000.phy.0: USB ID detect failed!
> > [ 1.210243] phy phy-c0000000.phy.0: phy poweron failed --> -22
> I wonder if the warning below are a side-effect of "phy poweron failed"...
As pointed by you we need the fix this issue earlier email.
unless we enable the phy and set the correct dr_mode to tune the phy
we cannot the tune and power on phy bus properly.
After this patch we get phy and power correctly registered.
# cat /sys/kernel/debug/regulator/regulator_summary
regulator use open bypass opmode voltage
current min max
---------------------------------------------------------------------------------------
regulator-dummy 5 4 0 unknown 0mV
0mA 0mV 0mV
c9100000.usb 1
0mA 0mV 0mV
c9100000.usb 1
0mA 0mV 0mV
c9000000.usb 1
0mA 0mV 0mV
c9000000.usb 1
0mA 0mV 0mV
P5V0 1 1 0 unknown 5000mV
0mA 5000mV 5000mV
USB_OTG_PWR 4 2 0 unknown 5000mV
0mA 5000mV 5000mV
phy-c0000020.phy.1 2
0mA 0mV 0mV
phy-c0000000.phy.0 2
0mA 0mV 0mV
>
> > [ 1.216072] WARNING: CPU: 0 PID: 78 at drivers/regulator/core.c:2054 _regulator_put.part.11+0xf0/0xf8
> > [ 1.225147] Modules linked in:
> > [ 1.228169] CPU: 0 PID: 78 Comm: kworker/0:1 Not tainted 5.0.0-rc4-xc2ml #1
> > [ 1.235066] Hardware name: Hardkernel ODROID-C2 (DT)
> > [ 1.239987] Workqueue: events deferred_probe_work_func
> > [ 1.245072] pstate: 80000005 (Nzcv daif -PAN -UAO)
> > [ 1.249816] pc : _regulator_put.part.11+0xf0/0xf8
> > [ 1.254473] lr : regulator_put+0x34/0x48
> > [ 1.258353] sp : ffff0000117b3b00
> > [ 1.261630] x29: ffff0000117b3b00 x28: 0000000000000000
> > [ 1.266891] x27: ffff80007ec1a7b8 x26: ffff000010eec280
> > [ 1.272153] x25: 0000000000000000 x24: 0000000000000009
> > [ 1.277414] x23: ffff0000117b3bc8 x22: ffff80007ecd3c00
> > [ 1.282675] x21: ffff0000111ad6c8 x20: ffff80007ecd3e00
> > [ 1.287936] x19: ffff80007ecd3e00 x18: 0000000000000124
> > [ 1.293198] x17: 0000000000000000 x16: 0000000000000000
> > [ 1.298459] x15: 0000000000000400 x14: 0000000000000400
> > [ 1.303720] x13: ff00000000000000 x12: ffffffffffffffff
> > [ 1.308981] x11: 0000000000000038 x10: 0000000000000040
> > [ 1.314243] x9 : ffff0000111c58b0 x8 : ffff0000111c58a8
> > [ 1.319504] x7 : ffff80006b055200 x6 : ffff80007edd2880
> > [ 1.324765] x5 : ffff80007f400248 x4 : ffff80007fb92b00
> > [ 1.330026] x3 : ffff0000112c9d58 x2 : ffff80007edd2880
> > [ 1.335288] x1 : 0000000000000000 x0 : 0000000000000001
> > [ 1.340549] Call trace:
> > [ 1.342966] _regulator_put.part.11+0xf0/0xf8
> > [ 1.347278] regulator_put+0x34/0x48
> > [ 1.350814] regulator_bulk_free+0x30/0x50
> > [ 1.354868] devm_regulator_bulk_release+0x18/0x20
> > [ 1.359612] release_nodes+0x1b0/0x220
> > [ 1.363320] devres_release_all+0x34/0x50
> > [ 1.367288] really_probe+0xec/0x290
> > [ 1.370824] driver_probe_device+0x54/0xe8
> > [ 1.374878] __device_attach_driver+0xb8/0xe8
> > [ 1.379190] bus_for_each_drv+0x78/0xc8
> > [ 1.382985] __device_attach+0xd4/0x130
> > [ 1.386780] device_initial_probe+0x10/0x18
> > [ 1.390920] bus_probe_device+0x90/0x98
> > [ 1.394715] deferred_probe_work_func+0x6c/0xa0
> > [ 1.399203] process_one_work+0x1e0/0x318
> > [ 1.403168] worker_thread+0x228/0x428
> > [ 1.406877] kthread+0x124/0x128
> > [ 1.410070] ret_from_fork+0x10/0x18
> > [ 1.413603] ---[ end trace 498aca4cb07e5377 ]---
> phy_power_on fails above with -EINVAL and then something else breaks
> (it seems like you're hitting the WARN_ON in drivers/regulator/core.c
> below the comment which states: "Docs say you must disable before
> calling regulator_put()")
Ok will look into this later.
> so this looks like a bug in either the dwc2 driver or the PHY
> framework. can you please report that to the dwc2 and PHY maintainers
> so it can be fixed independently?
>
>
> Regards
> Martin
Best Regards
-Anand
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2019-02-05 19:54 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-29 10:25 [PATCHv3 0/2] Odroid c2 usb fixs Anand Moon
2019-01-29 10:25 ` [PATCHv3 1/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy reset warning Anand Moon
2019-02-04 13:58 ` Martin Blumenstingl
2019-02-04 20:04 ` Anand Moon
2019-02-04 20:49 ` Martin Blumenstingl
2019-02-05 19:53 ` Anand Moon
2019-01-29 10:25 ` [PATCHv3 2/2] ARM64: dts: meson-gxbb-odroidc2: Fix usb phy regulator power failed warning Anand Moon
2019-02-04 14:06 ` Martin Blumenstingl
2019-02-04 20:05 ` Anand Moon
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).