From: andrew@lunn•ch (Andrew Lunn)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 0/3] ARM: mvebu: Enable XHCI on the Armada 385 AP
Date: Tue, 20 Jan 2015 21:43:07 +0100 [thread overview]
Message-ID: <20150120204307.GC13365@lunn.ch> (raw)
In-Reply-To: <20150120203028.GZ4367@lukather>
On Tue, Jan 20, 2015 at 09:30:28PM +0100, Maxime Ripard wrote:
> Hi Andrew,
>
> On Mon, Jan 19, 2015 at 10:35:07PM +0100, Andrew Lunn wrote:
> > On Mon, Jan 19, 2015 at 02:01:11PM +0100, Maxime Ripard wrote:
> > > Hi all,
> > >
> > > This serie enables the Armada 385 AP XHCI controller.
> > >
> > > Since the controller uses a GPIO-controlled VBUS, we used the
> > > phy-generic driver, and made the needed additions to the xhci-plat
> > > driver to retrieve a USB phy.
> > >
> > > Unfortunately, some glitches were also found along the way, mostly
> > > because of the probe deferring that was introduced by this phy
> > > retrieval.
> > >
> > > Since the introduction of the Armada 38x support in 3.16, the driver
> > > was attempting to write into registers while the clock wasn't enabled
> > > yet. This was working because the bootloader left it enabled, but in
> > > the case of a deferred probing, the clock would have been disabled by
> > > the error path of our driver, and this would fail. This should go in
> > > 3.19, and any stable kernel for 3.16+.
> > >
> > > The two patches remaining are "regular" patches, and are aimed at
> > > 3.20. The last patch depend on my previous serie to introduce support
> > > for the the A385 AP board.
> >
> > Hi Maxime
> >
> > I assume you want me to take 3/3? Any other route is not simple, since
> > this file only exists in mvebu/dt and maybe a staging branch of
> > arm-soc.
> >
> > What route do you think the other patches will take?
>
> There should be no merge dependency, but merging the third patch alone
> will probably result on a boot breakage. I don't think it really
> matters though, since this is a new board, so I guess it can go
> through the USB-PHY tree.
Hi Maxime
Humm, maybe i'm wrong, but i think
arch/arm/boot/dts/armada-385-db-ap.dts
only exists in the mvebu tree?
At least, i don't see it here:
https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/tree/arch/arm/boot/dts?h=next
Andrew
next prev parent reply other threads:[~2015-01-20 20:43 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
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 [this message]
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=20150120204307.GC13365@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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