devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: "André Przywara" <andre.przywara@arm.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Vishnu Patekar <vishnupatekar0510@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>, Jonathan Corbet <corbet@lwn.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>, Chen-Yu Tsai <wens@csie.org>,
	Icenowy Zheng <icenowy@aosc.xyz>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/3] ARM: dts: sunxi: add support for Orange Pi Zero board
Date: Thu, 1 Dec 2016 10:36:19 +0100	[thread overview]
Message-ID: <20161201093619.gs6lmoxtlptp2jr6@lukather> (raw)
In-Reply-To: <cdfd3c65-d473-badb-ea6a-035f7ab79217@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 1083 bytes --]

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.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2016-12-01  9:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-21 16:24 [PATCH v2 1/3] ARM: sunxi: add support for H2+ SoC Icenowy Zheng
2016-11-21 16:24 ` [PATCH v2 2/3] ARM: dts: sunxi: add support for Orange Pi Zero board Icenowy Zheng
2016-11-23  7:57   ` Maxime Ripard
2016-11-23  9:23     ` Andre Przywara
     [not found]       ` <a4393a37-5008-ec76-9886-05f8686dadd5-5wv7dgnIgG8@public.gmane.org>
2016-11-24 21:29         ` Maxime Ripard
2016-11-27  9:36   ` Icenowy Zheng
2016-11-28  0:29     ` André Przywara
2016-12-01  9:36       ` Maxime Ripard [this message]
2016-12-02 14:22         ` Icenowy Zheng
2016-12-02 14:30           ` Hans de Goede
2016-12-02 14:32             ` Icenowy Zheng
2016-12-02 16:10               ` Andre Przywara
2016-12-02 16:37                 ` Chen-Yu Tsai
2016-12-05  9:05                 ` Maxime Ripard
2016-12-05  8:52           ` Maxime Ripard
2016-11-21 16:24 ` [PATCH 3/3] ARM: dts: sunxi: enable SDIO Wi-Fi on Orange Pi Zero Icenowy Zheng
2016-11-23  7:59   ` 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
2016-11-23  7:54 ` [PATCH v2 1/3] ARM: sunxi: add support for H2+ SoC 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
2016-12-05 11:01   ` Icenowy Zheng
2016-12-06  8:00     ` Maxime Ripard
2016-12-06 15:16       ` Icenowy Zheng

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=20161201093619.gs6lmoxtlptp2jr6@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=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=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;
as well as URLs for NNTP newsgroup(s).