From: "Thang Q. Nguyen" <tqnguyen@apm.com>
To: Felipe Balbi <felipe.balbi@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm@lists.infradead.org
Cc: Thang Nguyen <tqnguyen@apm.com>, Phong Vo <pvo@apm.com>,
Loc Ho <lho@apm.com>,
patches@apm.com
Subject: [PATCH v3 2/2] usb:dwc3: pass arch data to xhci-hcd child
Date: Thu, 10 Mar 2016 14:18:52 +0700 [thread overview]
Message-ID: <1457594332-7490-3-git-send-email-tqnguyen@apm.com> (raw)
In-Reply-To: <1457594332-7490-1-git-send-email-tqnguyen@apm.com>
From: "Thang Q. Nguyen" <tqnguyen@apm.com>
The xhci-hcd child node needs to inherit archdata attribute to use
dma_ops functions and attributes. This patch enables the USB DWC3
driver to pass archdata attributes to its xhci-hcd child node.
Changes from v2:
- None
Changes from v1:
- None
Signed-off-by: Thang Q. Nguyen <tqnguyen@apm.com>
---
drivers/usb/dwc3/host.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/dwc3/host.c b/drivers/usb/dwc3/host.c
index c679f63..661fbae 100644
--- a/drivers/usb/dwc3/host.c
+++ b/drivers/usb/dwc3/host.c
@@ -37,6 +37,7 @@ int dwc3_host_init(struct dwc3 *dwc)
xhci->dev.parent = dwc->dev;
xhci->dev.dma_mask = dwc->dev->dma_mask;
xhci->dev.dma_parms = dwc->dev->dma_parms;
+ xhci->dev.archdata = dwc->dev->archdata;
dwc->xhci = xhci;
--
2.2.0
next prev parent reply other threads:[~2016-03-10 7:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 7:18 [PATCH v3 0/2] usb:dwc3: Enable USB DWC3 support for 64-bit system Thang Q. Nguyen
2016-03-10 7:18 ` [PATCH v3 1/2] usb:dwc3: Enable " Thang Q. Nguyen
[not found] ` <1457594332-7490-2-git-send-email-tqnguyen-qTEPVZfXA3Y@public.gmane.org>
2016-03-30 13:09 ` Felipe Balbi
2016-03-31 7:34 ` Thang Q. Nguyen
2016-03-31 8:04 ` Felipe Balbi
2016-03-10 7:18 ` Thang Q. Nguyen [this message]
2016-03-30 13:10 ` [PATCH v3 2/2] usb:dwc3: pass arch data to xhci-hcd child Felipe Balbi
2016-03-30 13:52 ` Grygorii Strashko
2016-03-30 13:55 ` Felipe Balbi
[not found] ` <87egashxz8.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-03-31 7:39 ` Thang Q. Nguyen
2016-03-31 8:04 ` Felipe Balbi
2016-03-31 15:07 ` Grygorii Strashko
[not found] ` <56FD3D2F.8070501-l0cyMroinI0@public.gmane.org>
2016-04-01 7:58 ` Felipe Balbi
2016-04-01 9:46 ` Grygorii Strashko
[not found] ` <56FE4378.3030205-l0cyMroinI0@public.gmane.org>
2016-04-01 10:20 ` Felipe Balbi
[not found] ` <87shz58wbw.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-01 11:00 ` Grygorii Strashko
[not found] ` <56FE54DB.5000201-l0cyMroinI0@public.gmane.org>
2016-04-01 11:57 ` Felipe Balbi
[not found] ` <878u0x8ru4.fsf-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-04-01 18:15 ` santosh shilimkar
[not found] ` <56FEBAC1.2040509-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-04-04 6:28 ` Felipe Balbi
2016-04-04 16:11 ` santosh shilimkar
2016-04-05 5:18 ` Felipe Balbi
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=1457594332-7490-3-git-send-email-tqnguyen@apm.com \
--to=tqnguyen@apm.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lho@apm.com \
--cc=linux-arm@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patches@apm.com \
--cc=pvo@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).