From: Andre Przywara <andre.przywara@arm.com>
To: Icenowy Zheng <icenowy@aosc.xyz>,
Hans de Goede <hdegoede@redhat.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Chen-Yu Tsai <wens@csie.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
Vishnu Patekar <vishnupatekar0510@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] ARM: dts: sunxi: add support for Orange Pi Zero board
Date: Fri, 2 Dec 2016 16:10:46 +0000 [thread overview]
Message-ID: <324c8820-aeea-3fad-0e02-1bdb8f675677@arm.com> (raw)
In-Reply-To: <11535601480689127@web2g.yandex.ru>
Hi,
On 02/12/16 14:32, Icenowy Zheng wrote:
>
>
> 02.12.2016, 22:30, "Hans de Goede" <hdegoede@redhat.com>:
>> Hi,
>>
>> On 02-12-16 15:22, Icenowy Zheng wrote:
>>> 01.12.2016, 17:36, "Maxime Ripard" <maxime.ripard@free-electrons.com>:
>>>> On Mon, Nov 28, 2016 at 12:29:07AM +0000, André Przywara wrote:
>>>>> > Something more interesting happened.
>>>>> >
>>>>> > Xunlong made a add-on board for Orange Pi Zero, which exposes the
>>>>> > two USB Controllers exported at expansion bus as USB Type-A
>>>>> > connectors.
>>>>> >
>>>>> > Also it exposes a analog A/V jack and a microphone.
>>>>> >
>>>>> > Should I enable {e,o}hci{2.3} in the device tree?
>>>>>
>>>>> Actually we should do this regardless of this extension board. The USB
>>>>> pins are not multiplexed and are exposed on user accessible pins (just
>>>>> not soldered, but that's a detail), so I think they qualify for DT
>>>>> enablement. And even if a user can't use them, it doesn't hurt to have
>>>>> them (since they are not multiplexed).
>>>>
>>>> My main concern about this is that we'll leave regulators enabled by
>>>> default, for a minority of users. And that minority will prevent to do
>>>> a proper power management when the times come since we'll have to keep
>>>> that behaviour forever.
>>>
>>> I think these users can add a 'fdt set /xxx/xxx status "disabled" ' .
>>
>> I don't think that will be necessary I'm pretty sure these extra usb
>> ports do not have a regulator for the Vbus, they just hook directly
>> to the 5V rail, can someone with a schematic check ?
>
> We seems to have still no schematics for the add-on board.
>From looking at the picture of that expansion board on the Aliexpress
page and chasing the tracks, there is clearly no voltage regulator on
there, it's just passive components. The 5V pin from the headers is
routed forth and back between the two layers via some vias directly to
the 5V pins of the USB sockets.
> But something is sure is that there's no any regulator-related pins
> on the add-on pinout. There's only USB DM and DP pins.
>
> So the Vbus must be directly connected to +5V.
So yes, it is.
But I think the question is moot anyways, since we don't provide DT
support for that add-on board at that point anyways.
One could imagine another board, though, which has regulators switched
by GPIOs, but that would be their problem and they would have regulators
specified in their specific DT snippet, then.
So to summarize:
- For that specific Orange Pi Zero board which we discuss the DT for
there is no regulator support for the additional USB ports. Thus nothing
we could turn off to save power.
- A user could just take these USB brackets with pin headers that are so
common in PCs to connect additional USB ports to the back of the box.
One just needs to re-sort the pins, which is a matter of a minute.
- As long as we don't provide any easy way of handling DT changes, we
should enable the USB ports for the sake of the users of either those
brackets or the expansion board. Any more sophisticated USB expansion
board with regulators would need to amend the DT anyway.
Does that make sense?
Cheers,
Andre.
next prev parent reply other threads:[~2016-12-02 16:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161121162421.800-1-icenowy@aosc.xyz>
2016-11-23 7:54 ` [PATCH v2 1/3] ARM: sunxi: add support for H2+ SoC Maxime Ripard
[not found] ` <20161121162421.800-2-icenowy@aosc.xyz>
2016-11-23 7:57 ` [PATCH v2 2/3] ARM: dts: sunxi: add support for Orange Pi Zero board Maxime Ripard
2016-11-23 9:23 ` Andre Przywara
2016-11-24 21:29 ` Maxime Ripard
[not found] ` <5373671480239408@web31m.yandex.ru>
2016-11-28 0:29 ` André Przywara
2016-12-01 9:36 ` Maxime Ripard
[not found] ` <11498641480688550@web2g.yandex.ru>
2016-12-02 14:30 ` Hans de Goede
[not found] ` <11535601480689127@web2g.yandex.ru>
2016-12-02 16:10 ` Andre Przywara [this message]
2016-12-02 16:37 ` Chen-Yu Tsai
2016-12-05 9:05 ` Maxime Ripard
2016-12-05 8:52 ` Maxime Ripard
[not found] ` <20161121162421.800-3-icenowy@aosc.xyz>
2016-11-23 7:59 ` [PATCH 3/3] ARM: dts: sunxi: enable SDIO Wi-Fi on Orange Pi Zero Maxime Ripard
2016-11-23 14:25 ` Chen-Yu Tsai
2016-11-23 14:29 ` Hans de Goede
2016-11-24 21:30 ` Maxime Ripard
[not found] <20161205120021.0GBGtAl4@smtp3m.mail.yandex.net>
2016-12-05 9:40 ` [PATCH v2 2/3] ARM: dts: sunxi: add support for Orange Pi Zero board Maxime Ripard
[not found] ` <17819681480935706@web24g.yandex.ru>
2016-12-06 8:00 ` Maxime Ripard
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=324c8820-aeea-3fad-0e02-1bdb8f675677@arm.com \
--to=andre.przywara@arm.com \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=vishnupatekar0510@gmail.com \
--cc=wens@csie.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