linux-kernel - Re: [PATCH v5 0/6] inherit dma configuration from parent dev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 5 Jan 2017 18:16:05 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Roger Quadros <rogerq@...com>
Cc:     Sriram Dash <sriram.dash@....com>, linux-kernel@...r.kernel.org,
        linux-usb@...r.kernel.org, felipe.balbi@...ux.intel.com,
        Mathias Nyman <mathias.nyman@...ux.intel.com>,
        mathias.nyman@...el.com, suresh.gupta@....com,
        stern@...land.harvard.edu, pku.leo@...il.com
Subject: Re: [PATCH v5 0/6] inherit dma configuration from parent dev

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 :)