From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Duc Dang <dhdang@apm.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Feng Kan <fkan@apm.com>, Mark Langsdorf <mlangsdo@redhat.com>,
mathias.nyman@intel.com, Greg KH <gregkh@linuxfoundation.org>,
USB list <linux-usb@vger.kernel.org>, patches <patches@apm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Loc Ho <lho@apm.com>
Subject: Re: [PATCH v5 1/2] usb: make xhci platform driver use 64 bit or 32 bit DMA
Date: Sat, 15 Aug 2015 22:05:09 +0200 [thread overview]
Message-ID: <1643536.i8Q5EFEN01@wuerfel> (raw)
In-Reply-To: <CADaLNDn4SvW3hvi7H0c_z2xgVSgRHLOK06xMyTYJd+ddFqc7Nw@mail.gmail.com>
On Saturday 08 August 2015 13:31:02 Duc Dang wrote:
> >
> > If we know that pdev->dev.dma_mask will always be initialised at this
> > point, then the above change is fine. If not, it's introducing a
> > regression - dma_set_mask_and_coherent() will fail if pdev->dev.dma_mask
> > is NULL (depending on the architectures implementation of dma_set_mask()).
> >
> > Prefixing the above change with the two lines I mention above would
> > ensure equivalent behaviour. Even if we do want to get rid of this,
> > I'd advise to do it as a separate patch after this change, which can
> > be independently reverted if there's problems with its removal.
> >
> Hi Russell,
>
> I will add the 2 lines you mentioned back to next version of the
> patch. It is safer to do it that way as I do not see
> pdev->dev.dma_mask gets initialized before the call
> dma_set_mask_and_coherent inside this xhci_plat.c file.
It would be good to add a WARN_ON() to the case where dma_mask
is a NULL pointer at the least. That way, we will at least
find out if there are some broken platforms that do not correctly
initialize the mask pointer.
Arnd
next prev parent reply other threads:[~2015-08-15 20:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADaLNDkeOP+gBw0qdSDha551w+w+q4ry9-EevDw5giyiQGdnqA@mail.gmail.com>
2015-08-08 1:03 ` [PATCH v4 1/2] usb: make xhci platform driver use 64 bit or 32 bit DMA Duc Dang
2015-08-08 1:03 ` [PATCH v4 2/2] usb: Add support for ACPI identification to xhci-platform Duc Dang
2015-08-08 1:29 ` Greg KH
2015-08-08 2:40 ` Duc Dang
2015-08-08 3:18 ` [PATCH v5 1/2] usb: make xhci platform driver use 64 bit or 32 bit DMA Duc Dang
2015-08-08 9:22 ` Russell King - ARM Linux
2015-08-08 20:31 ` Duc Dang
2015-08-15 20:05 ` Arnd Bergmann [this message]
2015-08-19 21:28 ` Duc Dang
2015-08-20 13:09 ` Arnd Bergmann
2015-08-20 19:38 ` [PATCH v7 " Duc Dang
2015-08-31 18:58 ` Duc Dang
2015-09-01 11:54 ` Mathias Nyman
2015-09-01 12:07 ` Russell King - ARM Linux
2015-09-10 20:53 ` Duc Dang
2015-09-17 18:19 ` [PATCH v8 0/3] usb: xhci-platform: Configure 64-bit DMA mask if the platform is capable Duc Dang
2015-09-17 18:19 ` [PATCH v8 1/3] usb: make xhci platform driver use 64 bit or 32 bit DMA Duc Dang
2015-09-17 19:51 ` Arnd Bergmann
2015-09-17 20:29 ` Duc Dang
2015-09-17 18:19 ` [PATCH v8 2/3] usb: Add support for ACPI identification to xhci-platform Duc Dang
2015-09-17 18:19 ` [PATCH v8 3/3] usb: xhci: configure 32-bit DMA if the controller does not support 64-bit DMA Duc Dang
2015-09-30 21:24 ` [PATCH v8 0/3] usb: xhci-platform: Configure 64-bit DMA mask if the platform is capable Duc Dang
2015-10-04 9:10 ` Greg KH
2015-10-07 13:20 ` Mathias Nyman
2015-08-20 19:38 ` [PATCH v7 2/2] usb: Add support for ACPI identification to xhci-platform Duc Dang
2015-08-10 7:37 ` [PATCH v6 1/2] usb: make xhci platform driver use 64 bit or 32 bit DMA Duc Dang
2015-08-10 7:37 ` [PATCH v6 2/2] usb: Add support for ACPI identification to xhci-platform Duc Dang
2015-08-08 3:18 ` [PATCH v5 " Duc Dang
2015-08-08 5:43 ` [PATCH v4 " Javier Martinez Canillas
2015-08-08 15:37 ` Greg KH
2015-08-08 16:45 ` Duc Dang
2015-08-08 21:05 ` Javier Martinez Canillas
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=1643536.i8Q5EFEN01@wuerfel \
--to=arnd@arndb.de \
--cc=dhdang@apm.com \
--cc=fkan@apm.com \
--cc=gregkh@linuxfoundation.org \
--cc=lho@apm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mathias.nyman@intel.com \
--cc=mlangsdo@redhat.com \
--cc=patches@apm.com \
/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