From: Anand Moon <linux.amoon@gmail.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh+dt@kernel.org>
Subject: [PATCHv2 0/1] PATCHv2 Odroid c1+ usb fixes
Date: Sat, 9 Feb 2019 17:54:27 +0000 [thread overview]
Message-ID: <20190209175428.1199-1-linux.amoon@gmail.com> (raw)
From my side this changes fix the usb power issue on usb1 ports
This is follow up on my previous patches.
Changes from prevoius patch drop the initialization of usb0 otg port.
RFC
[0] https://patchwork.kernel.org/patch/10777359/
[1] https://patchwork.kernel.org/patch/10777369/
Patch v0
[0] https://lore.kernel.org/patchwork/patch/1031616/
[1] https://lore.kernel.org/patchwork/patch/1031617/
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 4 3 0 unknown 0mV 0mA 0mV 0mV
c90c0000.usb 1 0mA 0mV 0mV
c90c0000.usb 1 0mA 0mV 0mV
VCCK 1 1 0 unknown 860mV 0mA 860mV 1140mV
cpu0 0 0mA 860mV 860mV
P5V0 3 4 0 unknown 5000mV 0mA 5000mV 5000mV
VCC1V8 1 1 0 unknown 1800mV 0mA 1800mV 1800mV
c1108680.adc 1 0mA 0mV 0mV
VCC3V3 1 2 0 unknown 3300mV 0mA 3300mV 3300mV
VDD_RTC 0 0 0 unknown 900mV 0mA 900mV 900mV
TFLASH_VDD 1 1 0 unknown 3300mV 0mA 3300mV 3300mV
c1108c20.mmc:slot@1 1 0mA 3300mV 3400mV
DDR_VDDC 0 0 0 unknown 1500mV 0mA 1500mV 1500mV
USB_VBUS 2 1 0 unknown 5000mV 0mA 5000mV 5000mV
phy-c1108820.phy.0 2 0mA 0mV 0mV
TF_IO 0 1 0 unknown 3300mV 0mA 1800mV 3300mV
# lsusb -t
/: Bus 01.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 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 5, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 5, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 3: Dev 5, If 2, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 3: Dev 5, If 3, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 4: Dev 6, If 0, Class=Mass Storage, Driver=usb-storage, 480M
Now hotpluing of usb device is working on odroid c1+ boards.
TODO: need to initialize the otg usb port to accept usb device.
Any input are welcome
Best Regards
-Anand
Anand Moon (1):
ARM: dts: meson8b: odroidc1: fix USB power supplies for phy
arch/arm/boot/dts/meson8b-odroidc1.dts | 15 +++++++++++++++
1 file changed, 15 insertions(+)
--
2.20.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-02-09 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 17:54 Anand Moon [this message]
2019-02-09 17:54 ` [PATCHv2 1/1] ARM: dts: meson8b: odroidc1: fix USB power supplies for phy Anand Moon
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=20190209175428.1199-1-linux.amoon@gmail.com \
--to=linux.amoon@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=robh+dt@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).