From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: sun9i: cubieboard4: Enable USB support
Date: Fri, 8 May 2015 13:40:40 +0200 [thread overview]
Message-ID: <20150508114040.GR11057@lukather> (raw)
In-Reply-To: <CAGb2v64VQpNkd2zmHdhTXQEfk8z1FnhYZMQW0vmLVq1Ahzg2Zw@mail.gmail.com>
On Fri, May 08, 2015 at 04:01:14PM +0800, Chen-Yu Tsai wrote:
> >> +&ehci0 {
> >> + status = "okay";
> >> +};
> >> +
> >> +&ehci2 {
> >> + status = "okay";
> >> +};
> >> +
> >> +/* usb1 is connected to a GL850G USB hub chip, so no need to enable OHCI */
> >
> > You're mentionning usb1, but I don't see it enabled anywhere, is that
> > a typo?
>
> usb1 (or usbphy1) == ehci/ohci0. usb0 is otg.
>
> This numbering matches the fex files, and (mostly) matches the
> specs.
Ok, having this comment between ehci2 and ohci2 is confusing then :)
It's not the first board that has a hub, we usually don't really care
as it's kind of obvious. Maybe we can just remove it?
> >> &mmc0 {
> >> @@ -92,8 +130,30 @@
> >> status = "okay";
> >> };
> >>
> >> +®_usb1_vbus {
> >> + pinctrl-0 = <&usb1_vbus_pin_cubieboard4>;
> >> + gpio = <&pio 7 14 GPIO_ACTIVE_HIGH>; /* PH14 */
> >> + status = "okay";
> >> +};
> >> +
> >> &uart0 {
> >> pinctrl-names = "default";
> >> pinctrl-0 = <&uart0_pins_a>;
> >> status = "okay";
> >> };
> >> +
> >> +&usbphy1 {
> >> + phy-supply = <®_usb1_vbus>;
> >> + status = "okay";
> >> +};
> >> +
> >> +/*
> >> + * Unfortunately reg_usb1_vbus also powers one of the ports from usb3's hub.
> >> + * One should always make sure both regulators are enabled and working for
> >> + * all USB ports to have power.
> >> + */
> >
> > Can't we just provide the two regulators, and enable both of them so
> > that we know that we always have the needed regulators enabled,
> > disregarding which USB port is used?
>
> Would setting "always-on" for both regulators work for you?
> Or maybe just the one that's used by both USB hosts?
I was more thinking of giving to the phy an additional regulator, so
that it would enable both the regulators needed to power up all ports.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150508/3a2d6a1c/attachment.sig>
next prev parent reply other threads:[~2015-05-08 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 16:43 [PATCH 0/2] ARM: sun9i: cubieboard4: Enable USB hosts and LEDs Chen-Yu Tsai
2015-05-07 16:43 ` [PATCH 1/2] ARM: dts: sun9i: cubieboard4: Enable USB support Chen-Yu Tsai
2015-05-08 7:46 ` Maxime Ripard
2015-05-08 8:01 ` Chen-Yu Tsai
2015-05-08 11:40 ` Maxime Ripard [this message]
2015-05-11 8:26 ` Chen-Yu Tsai
2015-05-12 14:57 ` Maxime Ripard
2015-05-12 15:49 ` Chen-Yu Tsai
2015-05-07 16:43 ` [PATCH 2/2] ARM: dts: sun9i: cubieboard4: Enable LEDs Chen-Yu Tsai
2015-05-08 1:10 ` [PATCH 0/2] ARM: sun9i: cubieboard4: Enable USB hosts and LEDs Tyler Baker
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=20150508114040.GR11057@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).