From: dhdang@apm.com (Duc Dang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/3] usb: xhci-platform: Configure 64-bit DMA mask if the platform is capable
Date: Thu, 17 Sep 2015 11:19:45 -0700 [thread overview]
Message-ID: <cover.1442513540.git.dhdang@apm.com> (raw)
In-Reply-To: <CADaLNDno0cLXH3_4NG75fk6T31Pe5BCrbcUpA0cGriCwSh6OyQ@mail.gmail.com>
The xhci platform driver does not work with system that only supports
64-bit DMA as it requests 32-bit DMA mask during driver initialization.
This patch set addresses this issue and also adds XHCI-compliant USB
Controller ACPI identification into xhci-platform driver.
Changes from v7:
- Only use dma_coerce_mask_and_coherent when
dma_mask is NULL
- Check the controller DMA capability and configure
32-bit dma_mask if it only supports 32-bit DMA
- Patches is generated over v4.3-rc1
Changes from v6:
-Add WARN_ON if dma_mask is NULL
-Use dma_coerce_mask_and_coherent to assign
dma_mask and coherent_dma_mask
Change from v5:
-Change comment to "XHCI-compliant USB Controller" as
"PNP0D10" ID is not X-Gene specific
-Change comment
-Assign dma_mask to coherent_dma_mask if dma_mask is NULL
to make sure dma_set_mask_and_coherent does not fail prematurely.
Changes from v4:
-Remove #ifdef CONFIG_ACPI
-Change comment
-Assign dma_mask to coherent_dma_mask if dma_mask is NULL
to make sure dma_set_mask_and_coherent does not fail prematurely.
Changes from v3:
-Regenerate the patch over 4.2-rc5
-No code change
Changes from v2
-Replaced tristate with a boolean as the driver doesn't
compile as a module
-Correct --help-- to ---help---
Changes from v1
-Consolidated to use dma_set_mask_and_coherent
-Got rid of the check against sizeof(dma_addr_t)
-Renamed from "add support for APM X-Gene to xhci-platform"
-Removed changes to arm64/Kconfig
-Made CONFIG_USB_XHCI_PLATFORM a user selectable config option
drivers/usb/host/xhci-plat.c | 29 ++++++++++++++++++++++-------
drivers/usb/host/xhci.c | 10 ++++++++++
2 files changed, 32 insertions(+), 7 deletions(-)
--
1.9.1
next prev parent reply other threads:[~2015-09-17 18:19 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 3:18 ` [PATCH v5 2/2] usb: Add support for ACPI identification to xhci-platform Duc Dang
2015-08-08 9:22 ` [PATCH v5 1/2] usb: make xhci platform driver use 64 bit or 32 bit DMA 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
2015-08-20 19:38 ` [PATCH v7 " Duc Dang
2015-08-20 19:38 ` [PATCH v7 2/2] usb: Add support for ACPI identification to xhci-platform Duc Dang
2015-08-31 18:58 ` [PATCH v7 1/2] usb: make xhci platform driver use 64 bit or 32 bit DMA 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 ` Duc Dang [this message]
2015-09-17 18:19 ` [PATCH v8 1/3] " 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-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 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=cover.1442513540.git.dhdang@apm.com \
--to=dhdang@apm.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).