From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] ARM: dts: rockchip: rock2: Setup usb vbus-supply
Date: Fri, 07 Apr 2017 00:23:39 +0200 [thread overview]
Message-ID: <2204588.mS7ruK0rnT@phil> (raw)
In-Reply-To: <20170405140613.4444-3-sjoerd.simons@collabora.co.uk>
Am Mittwoch, 5. April 2017, 16:06:11 CEST schrieb Sjoerd Simons:
> Now that the rockchip usb phy has a vbus-supply property use that to
> control the vbus regulator on rock2.
>
> Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
I've queued this for 4.13 .
Not eligible for 4.12, as the patch alone (when testing my tree or armsoc)
would regress the sata-bridge, due to the regulator-always-on going away.
Heiko
prev parent reply other threads:[~2017-04-06 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 14:06 [PATCH 0/3] rockchip dwc2: Turn off vbus on shutdown Sjoerd Simons
2017-04-05 14:06 ` [PATCH 1/3] phy: rockchip-usb: Add vbus regulator support Sjoerd Simons
2017-04-06 10:37 ` Kishon Vijay Abraham I
2017-04-05 14:06 ` [PATCH 2/3] ARM: dts: rockchip: rock2: Setup usb vbus-supply Sjoerd Simons
2017-04-06 22:23 ` Heiko Stuebner [this message]
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=2204588.mS7ruK0rnT@phil \
--to=heiko@sntech.de \
--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).