mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Johan Hovold <johan@kernel.org>, Alan Stern <stern@rowland.harvard.edu>
Cc: "Christoph Hellwig" <hch@lst.de>,
	"Marek Szyprowski" <m.szyprowski@samsung.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Andreas Färber" <afaerber@suse.de>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org,
	stable <stable@vger.kernel.org>,
	"Sricharan R" <sricharan@codeaurora.org>,
	"Stefan Wahren" <stefan.wahren@i2se.com>
Subject: Re: [PATCH v2] dma-mapping: skip USB devices when configuring DMA during probe
Date: Thu, 3 Aug 2017 15:48:06 +0100	[thread overview]
Message-ID: <ccee85b5-832f-b2b8-e4ac-69165efff184@arm.com> (raw)
In-Reply-To: <20170803142308.GU30136@localhost>

On 03/08/17 15:23, Johan Hovold wrote:
> On Thu, Aug 03, 2017 at 10:04:21AM -0400, Alan Stern wrote:
>> On Thu, 3 Aug 2017, Johan Hovold wrote:
>>
>>> USB devices use the DMA mask and offset of the controller, which have
>>> already been setup when a device is probed. Note that modifying the
>>> DMA mask of a USB device would change the mask for the controller (and
>>> all devices on the bus) as the mask is literally shared.
>>>
>>> Since commit 2bf698671205 ("USB: of: fix root-hub device-tree node
>>> handling"), of_dma_configure() would be called also for root hubs, which
>>> use the device node of the controller. A separate, long-standing bug
>>> that makes of_dma_configure() generate a 30-bit DMA mask from the RPI3's
>>> "dma-ranges" would thus set a broken mask also for the controller. This
>>> in turn prevents USB devices from enumerating when control transfers
>>> fail:
>>>
>>> 	dwc2 3f980000.usb: Cannot do DMA to address 0x000000003a166a00
>>>
>>> Note that the aforementioned DMA-mask bug was benign for the HCD itself
>>> as the dwc2 driver overwrites the mask previously set by
>>> of_dma_configure() for the platform device in its probe callback. The
>>> mask would only later get corrupted when the root-hub child device was
>>> probed.
>>>
>>> Fix this, and similar future problems, by simply skipping USB devices
>>> when dma_configure() is called during probe.
>>>
>>> Fixes: 09515ef5ddad ("of/acpi: Configure dma operations at probe time for platform/amba/pci bus devices")
>>> Cc: stable <stable@vger.kernel.org>	# 4.12
>>> Cc: Robin Murphy <robin.murphy@arm.com>
>>> Cc: Sricharan R <sricharan@codeaurora.org>
>>> Cc: Stefan Wahren <stefan.wahren@i2se.com>
>>> Reported-by: Hans Verkuil <hverkuil@xs4all.nl>
>>> Signed-off-by: Johan Hovold <johan@kernel.org>
>>> ---
> 
>>> diff --git a/include/linux/usb.h b/include/linux/usb.h
>>> index cb9fbd54386e..f86ad9d8c756 100644
>>> --- a/include/linux/usb.h
>>> +++ b/include/linux/usb.h
>>> @@ -1222,6 +1222,11 @@ struct usb_device_driver {
>>>  
>>>  extern struct bus_type usb_bus_type;
>>>  
>>> +static inline bool dev_is_usb(struct device *dev)
>>> +{
>>> +	return dev->bus == &usb_bus_type;
>>> +}
>>> +
>>
>> Will this work if the USB subsystem is built as a module?
> 
> Nope. :-/

Oh bum, I hadn't even realised usb_bus_type could be modular.

> Add another flag (e.g. skip_dma_configure) to struct device for now?

Would it be sufficient to look for dev->of_node_reused, or is it also
possible for USB devices to have OF nodes of their own such that
of_dma_configure() would still blat the mask with a 32-bit default?
(Although that would still un-break Rpi3, even if strictly wrong)

Robin.

  reply	other threads:[~2017-08-03 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 13:14 Johan Hovold
2017-08-03 13:20 ` Robin Murphy
2017-08-03 14:04 ` Alan Stern
2017-08-03 14:23   ` Johan Hovold
2017-08-03 14:48     ` Robin Murphy [this message]
2017-08-03 14:53       ` Johan Hovold
2017-08-03 14:49     ` Johan Hovold
2017-08-03 15:57       ` Johan Hovold
2017-08-06 11:27 ` kbuild test robot

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=ccee85b5-832f-b2b8-e4ac-69165efff184@arm.com \
    --to=robin.murphy@arm.com \
    --cc=afaerber@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=sricharan@codeaurora.org \
    --cc=stable@vger.kernel.org \
    --cc=stefan.wahren@i2se.com \
    --cc=stern@rowland.harvard.edu \
    /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

Powered by JetHome