linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sriram Dash <sriram.dash@nxp.com>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	USB <linux-usb@vger.kernel.org>,
	"mathias.nyman@intel.com" <mathias.nyman@intel.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	Suresh Gupta <suresh.gupta@nxp.com>,
	"Felipe Balbi" <felipe.balbi@linux.intel.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	"pku.leo@gmail.com" <pku.leo@gmail.com>,
	"Arnd Bergmann" <arnd@arndb.de>
Subject: RE: [PATCH v3 5/6] usb: dwc3: use bus->sysdev for DMA configuration
Date: Fri, 11 Nov 2016 10:43:54 +0000	[thread overview]
Message-ID: <DB5PR0401MB1925DE96D0F2F7275988647BF5BB0@DB5PR0401MB1925.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAMz4kuKg=KT+GkWYO_t1F_2_ioPempc9VFaE2AkCcdTqDpxNCQ@mail.gmail.com>

>From: Baolin Wang [mailto:baolin.wang@linaro.org]
>
>Hi,
>
>On 10 November 2016 at 16:20, Sriram Dash <sriram.dash@nxp.com> wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> The dma ops for dwc3 devices are not set properly. So, use a physical
>> device sysdev, which will be inherited from parent, to set the
>> hardware / firmware parameters like dma.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> Signed-off-by: Sriram Dash <sriram.dash@nxp.com>
>> ---
>> Changes in v3:
>>   - No update
>>
>> Changes in v2:
>>   - integrate dwc3 driver changes together
>>
>>  drivers/usb/dwc3/core.c   | 28 +++++++++++++++-------------
>>  drivers/usb/dwc3/core.h   |  1 +
>>  drivers/usb/dwc3/ep0.c    |  8 ++++----
>>  drivers/usb/dwc3/gadget.c | 37 +++++++++++++++++++------------------
>>  drivers/usb/dwc3/host.c   | 12 ++++--------
>>  5 files changed, 43 insertions(+), 43 deletions(-)
>>
>
>Tested on my dwc3 platform, it can work well as host or gadget. You can add my
>tested tag for patch 1/4/5 after fixing Felipe's issue.
>Tested-by: Baolin Wang <baolin.wang@linaro.org>
>

Thanks Baolin.

>--
>Baolin.wang
>Best Regards

  reply	other threads:[~2016-11-11 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10  8:19 [PATCH v3 0/6] inherit dma configuration from parent dev Sriram Dash
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 [this message]
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=DB5PR0401MB1925DE96D0F2F7275988647BF5BB0@DB5PR0401MB1925.eurprd04.prod.outlook.com \
    --to=sriram.dash@nxp.com \
    --cc=arnd@arndb.de \
    --cc=baolin.wang@linaro.org \
    --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).