From: Sriram Dash <sriram.dash@nxp.com>
To: <linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>
Cc: <mathias.nyman@intel.com>, <gregkh@linuxfoundation.org>,
<suresh.gupta@nxp.com>, <felipe.balbi@linux.intel.com>,
<stern@rowland.harvard.edu>, <pku.leo@gmail.com>,
Sriram Dash <sriram.dash@nxp.com>
Subject: [PATCH v3 0/6] inherit dma configuration from parent dev
Date: Thu, 10 Nov 2016 13:49:55 +0530 [thread overview]
Message-ID: <1478766001-26463-1-git-send-email-sriram.dash@nxp.com> (raw)
For xhci-hcd platform device, all the DMA parameters are not
configured properly, notably dma ops for dwc3 devices.
The idea here is that you pass in the parent of_node along
with the child device pointer, so it would behave exactly
like the parent already does. The difference is that it also
handles all the other attributes besides the mask.
Arnd Bergmann (6):
usb: separate out sysdev pointer from usb_bus
usb: chipidea: use bus->sysdev for DMA configuration
usb: ehci: fsl: use bus->sysdev for DMA configuration
usb: xhci: use bus->sysdev for DMA configuration
usb: dwc3: use bus->sysdev for DMA configuration
usb: dwc3: Do not set dma coherent mask
drivers/usb/chipidea/core.c | 3 ---
drivers/usb/chipidea/host.c | 3 ++-
drivers/usb/chipidea/udc.c | 10 +++++----
drivers/usb/core/buffer.c | 12 +++++------
drivers/usb/core/hcd.c | 48 +++++++++++++++++++++++++-----------------
drivers/usb/core/usb.c | 18 ++++++++--------
drivers/usb/dwc3/core.c | 28 ++++++++++++------------
drivers/usb/dwc3/core.h | 1 +
drivers/usb/dwc3/dwc3-exynos.c | 10 ---------
drivers/usb/dwc3/dwc3-st.c | 1 -
drivers/usb/dwc3/ep0.c | 8 +++----
drivers/usb/dwc3/gadget.c | 37 ++++++++++++++++----------------
drivers/usb/dwc3/host.c | 12 ++++-------
drivers/usb/host/ehci-fsl.c | 4 ++--
drivers/usb/host/xhci-mem.c | 12 +++++------
drivers/usb/host/xhci-plat.c | 33 +++++++++++++++++++++++------
drivers/usb/host/xhci.c | 15 +++++++++----
include/linux/usb.h | 1 +
include/linux/usb/hcd.h | 3 +++
19 files changed, 144 insertions(+), 115 deletions(-)
--
2.1.0
next reply other threads:[~2016-11-10 8:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 8:19 Sriram Dash [this message]
2016-11-10 8:19 ` [PATCH v3 1/6] usb: separate out sysdev pointer from usb_bus Sriram Dash
2016-11-10 8:19 ` [PATCH v3 2/6] usb: chipidea: use bus->sysdev for DMA configuration Sriram Dash
2016-11-10 8:19 ` [PATCH v3 3/6] usb: ehci: fsl: " Sriram Dash
2016-11-10 8:19 ` [PATCH v3 4/6] usb: xhci: " Sriram Dash
2016-11-10 8:20 ` [PATCH v3 5/6] usb: dwc3: " Sriram Dash
2016-11-10 11:02 ` Felipe Balbi
2016-11-11 10:42 ` Sriram Dash
2016-11-11 10:57 ` Felipe Balbi
2016-11-11 20:31 ` Arnd Bergmann
2016-11-14 1:51 ` Peter Chen
2016-11-14 4:46 ` Sriram Dash
2016-11-10 12:33 ` Baolin Wang
2016-11-11 10:43 ` Sriram Dash
2016-11-10 8:20 ` [PATCH v3 6/6] usb: dwc3: Do not set dma coherent mask Sriram Dash
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=1478766001-26463-1-git-send-email-sriram.dash@nxp.com \
--to=sriram.dash@nxp.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=pku.leo@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=suresh.gupta@nxp.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).