From: mathias.nyman@linux.intel.com (Mathias Nyman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] usb: XHCI: platform: Move the Marvell quirks after the enabling the clocks
Date: Mon, 16 Feb 2015 15:43:38 +0200 [thread overview]
Message-ID: <54E1F40A.3020507@linux.intel.com> (raw)
In-Reply-To: <20150209083144.GA29855@kroah.com>
On 09.02.2015 10:31, Greg Kroah-Hartman wrote:
> On Mon, Feb 09, 2015 at 09:22:50AM +0100, Maxime Ripard wrote:
>> On Wed, Feb 04, 2015 at 05:04:18AM -0800, Greg Kroah-Hartman wrote:
>>> On Wed, Feb 04, 2015 at 10:35:22AM +0100, Maxime Ripard wrote:
>>>> Hi Mathias, Greg,
>>>>
>>>> On Mon, Jan 19, 2015 at 02:01:12PM +0100, Maxime Ripard wrote:
>>>>> The commit 973747928514 ("usb: host: xhci-plat: add support for the Armada
>>>>> 375/38x XHCI controllers") extended the xhci-plat driver to support the Armada
>>>>> 375/38x SoCs, mostly by adding a quirk configuring the MBUS window.
>>>>>
>>>>> However, that quirk was run before the clock the controllers needs has been
>>>>> enabled. This usually worked because the clock was first enabled by the
>>>>> bootloader, and left as such until the driver is probe, where it tries to
>>>>> access the MBUS configuration registers before enabling the clock.
>>>>>
>>>>> Things get messy when EPROBE_DEFER is involved during the probe, since as part
>>>>> of its error path, the driver will rightfully disable the clock. When the
>>>>> driver will be reprobed, it will retry to access the MBUS registers, but this
>>>>> time with the clock disabled, which hangs forever.
>>>>>
>>>>> Fix this by running the quirks after the clock has been enabled by the driver.
>>>>>
>>>>> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>>>>> Cc: <stable@vger.kernel.org> # v3.16+
>>>>
>>>> Any chance for this to go in 3.19?
>>>
>>> For 3.19? It's too late, I'm not sending anything else to Linus as 3.19
>>> will be out in a few days.
>>
>> Ok. I'll resend it when 3.20-rc1 is out then.
>
> Why resend? Mathias should be queueing this up properly. Mathias?
>
Yep, I'll send it forward to Greg once 3.20-rc1 is tagged
-Mathias
next prev parent reply other threads:[~2015-02-16 13: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 [this message]
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
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=54E1F40A.3020507@linux.intel.com \
--to=mathias.nyman@linux.intel.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;
as well as URLs for NNTP newsgroup(s).