From: Greg KH <gregkh@linuxfoundation.org>
To: Roger Quadros <rogerq@ti.com>
Cc: Sriram Dash <sriram.dash@nxp.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
felipe.balbi@linux.intel.com,
Mathias Nyman <mathias.nyman@linux.intel.com>,
mathias.nyman@intel.com, suresh.gupta@nxp.com,
stern@rowland.harvard.edu, pku.leo@gmail.com
Subject: Re: [PATCH v5 0/6] inherit dma configuration from parent dev
Date: Thu, 5 Jan 2017 18:16:05 +0100 [thread overview]
Message-ID: <20170105171605.GA21589@kroah.com> (raw)
In-Reply-To: <6ac3f225-674d-2329-a79b-e4f0652cc03d@ti.com>
On Thu, Jan 05, 2017 at 05:21:09PM +0200, Roger Quadros wrote:
> Hi,
>
> On 17/11/16 13:43, Sriram Dash wrote:
> > 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
>
> Only the dwc3 patches have been picked up for v4.10 and the rest are still missing.
> Any plans to pick them in the rc cycle?
>
> DMA configuration is still broken for XHCI on v4.10 and -next.
It's always been broken, so it's not a big deal for 4.10 :)
next prev parent reply other threads:[~2017-01-05 17:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 11:43 [PATCH v5 0/6] inherit dma configuration from parent dev Sriram Dash
2016-11-17 11:43 ` [PATCH v5 1/6] usb: separate out sysdev pointer from usb_bus Sriram Dash
2016-12-03 0:19 ` Brian Norris
[not found] ` <20161203001953.GA123997-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2017-01-06 19:33 ` Grygorii Strashko
2017-01-06 19:33 ` Grygorii Strashko
2016-12-13 16:09 ` [v5,1/6] " Alexander Sverdlin
2016-11-17 11:43 ` [PATCH v5 2/6] usb: chipidea: use bus->sysdev for DMA configuration Sriram Dash
2016-11-17 11:43 ` [PATCH v5 3/6] usb: ehci: fsl: " Sriram Dash
2016-11-17 11:43 ` [PATCH v5 4/6] usb: xhci: " Sriram Dash
2016-12-09 11:56 ` Roger Quadros
2016-12-13 16:09 ` [v5,4/6] " Alexander Sverdlin
2017-01-11 14:21 ` [PATCH v5 4/6] " Mathias Nyman
2017-01-11 15:08 ` Alan Stern
2017-01-12 8:38 ` Roger Quadros
2017-01-18 11:58 ` Mathias Nyman
2017-01-19 9:22 ` Greg KH
2017-01-19 11:33 ` Mathias Nyman
2016-11-17 11:43 ` [PATCH v5 5/6] usb: dwc3: " Sriram Dash
2016-12-13 16:09 ` [v5,5/6] " Alexander Sverdlin
2016-11-17 11:43 ` [PATCH v5 6/6] usb: dwc3: Do not set dma coherent mask Sriram Dash
2016-12-13 16:09 ` [v5,6/6] " Alexander Sverdlin
2016-12-22 6:23 ` [PATCH v5 0/6] inherit dma configuration from parent dev Vivek Gautam
2017-01-05 15:21 ` Roger Quadros
2017-01-05 17:16 ` Greg KH [this message]
2017-01-10 12:11 ` Roger Quadros
2017-01-11 21:32 ` 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=20170105171605.GA21589@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=mathias.nyman@linux.intel.com \
--cc=pku.leo@gmail.com \
--cc=rogerq@ti.com \
--cc=sriram.dash@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.