linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Duc Dang <dhdang@apm.com>
Cc: linux-arm <linux-arm-kernel@lists.infradead.org>,
	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: Thu, 20 Aug 2015 15:09:11 +0200	[thread overview]
Message-ID: <1522889.9kdnRk8vHo@wuerfel> (raw)
In-Reply-To: <CADaLNDmYt+k6Sw6q+t2-FA7muk=x6h_hfYV321B03qBPMD_=AA@mail.gmail.com>

On Wednesday 19 August 2015 14:28:33 Duc Dang wrote:
> 
> Hi Arnd,
> 
> So the check will look like this, please let me know what do you think:
>         if (!pdev->dev.dma_mask) {
>                 WARN_ON(1);
>                 /* Initialize dma_mask if the broken platform code has
> not done so */
>                 pdev->dev.dma_mask = &pdev->dev.coherent_dma_mask;
>         }

The condition can be written as 

	if (WARN_ON(!pdev->dev.dma_mask))

and I'd use dma_coerce_mask_and_coherent() instead of manually setting the
pointer, as an annotation for the fact that we are knowingly violating the
API here.

Those two points are just cosmetic though, aside from them, your code
above is what I had in mind.

Thanks,

	Arnd

  reply	other threads:[~2015-08-20 13:10 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
2015-08-19 21:28               ` Duc Dang
2015-08-20 13:09                 ` Arnd Bergmann [this message]
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=1522889.9kdnRk8vHo@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;
as well as URLs for NNTP newsgroup(s).