From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] ARM: mvebu: armada-385-ap: Enable USB3 port
Date: Tue, 17 Mar 2015 18:00:04 +0100 [thread overview]
Message-ID: <20150317170004.GK4638@lukather> (raw)
In-Reply-To: <5508578D.607@linux.intel.com>
On Tue, Mar 17, 2015 at 06:34:21PM +0200, Mathias Nyman wrote:
> On 17.03.2015 11:51, Maxime Ripard wrote:
> > On Tue, Mar 03, 2015 at 06:12:44PM +0200, Mathias Nyman wrote:
> >> On 03.03.2015 11:59, Maxime Ripard wrote:
> >>> On Mon, Mar 02, 2015 at 08:23:37PM +0100, Gregory CLEMENT wrote:
> >>>> Hi Maxime,
> >>>>
> >>>> On 19/01/2015 14:01, Maxime Ripard wrote:
> >>>>> The Armada 385 AP board has a USB3 port exposed that uses a GPIO to drive the
> >>>>> VBUS line. Enable the needed drivers to support this.
> >>>>>
> >>>>
> >>>> it seems that this patch was not applied yet. Patch 1 is now in
> >>>> linux-next and should be part of 4.0-rc. But what about patch 2?
> >>>
> >>> IIRC, Greg or Matthias said that Matthias would look into these
> >>> patches after the merge window.
> >>>
> >>> It still didn't happen though.
> >>>
> >>> Maxime
> >>>
> >>
> >> Hi
> >>
> >> I understood that you wanted the first fix patch in as soon as possible so
> >> I sent it forward to Greg, and it's now in his usb-linus branch.
> >>
> >> The other two patches, 2/3 and 3/3 you said were "regual" patches (for usb-next?),
> >> Andrew said he can take 3/3 and wondered if 2/3 and 3/3 need to go together?
> >>
> >> It doesn't matter for me, I can take 2/3 if you like, but I'd prefer if someone
> >> with more USB PHY insight could ack it first.
> >
> > There's been around two weeks, and we didn't have any additional
> > reviews. How can we move forward on this?
> >
>
> Added to my for-usb-next branch and sent forward to Greg (a second a go)
Great, thanks!
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/20150317/59c3bd41/attachment.sig>
next prev parent reply other threads:[~2015-03-17 17:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 13:01 [PATCH v2 0/3] ARM: mvebu: Enable XHCI on the Armada 385 AP Maxime Ripard
2015-01-19 13:01 ` [PATCH v2 1/3] usb: XHCI: platform: Move the Marvell quirks after the enabling the clocks Maxime Ripard
2015-02-04 9:35 ` Maxime Ripard
2015-02-04 13:04 ` Greg Kroah-Hartman
2015-02-09 8:22 ` Maxime Ripard
2015-02-09 8:31 ` Greg Kroah-Hartman
2015-02-16 13:43 ` Mathias Nyman
2015-01-19 13:01 ` [PATCH v2 2/3] usb: xhci: plat: Add USB phy support Maxime Ripard
2015-01-19 13:01 ` [PATCH v2 3/3] ARM: mvebu: armada-385-ap: Enable USB3 port Maxime Ripard
2015-03-02 19:23 ` Gregory CLEMENT
2015-03-03 9:59 ` Maxime Ripard
2015-03-03 16:12 ` Mathias Nyman
2015-03-04 16:13 ` Maxime Ripard
2015-03-17 9:51 ` Maxime Ripard
2015-03-17 16:34 ` Mathias Nyman
2015-03-17 17:00 ` Maxime Ripard [this message]
2015-03-18 10:59 ` Gregory CLEMENT
2015-01-19 21:35 ` [PATCH v2 0/3] ARM: mvebu: Enable XHCI on the Armada 385 AP Andrew Lunn
2015-01-20 20:30 ` Maxime Ripard
2015-01-20 20:43 ` Andrew Lunn
2015-01-21 9:09 ` 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=20150317170004.GK4638@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