[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <571F2357.9080509@ti.com>
Date: Tue, 26 Apr 2016 11:14:15 +0300
From: Grygorii Strashko <grygorii.strashko@...com>
To: Felipe Balbi <balbi@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Sekhar Nori <nsekhar@...com>,
David Fisher <david.fisher1@...opsys.com>,
Catalin Marinas <catalin.marinas@....com>,
"Thang Q. Nguyen" <tqnguyen@....com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
Subject: Re: [PATCH] usb: dwc3: host: inherit dma configuration from parent
dev
On 04/26/2016 09:17 AM, Felipe Balbi wrote:
>
> Hi,
>
> Grygorii Strashko <grygorii.strashko@...com> writes:
>> Now not all DMA paremters configured properly for "xhci-hcd" platform
>> device which is created manually. For example: dma_pfn_offset, dam_ops
>> and iommu configuration will not corresponds "dwc3" devices
>> configuration. As result, this will cause problems like wrong DMA
>> addresses translation on platforms with LPAE enabled like Keystone 2.
>>
>> When platform is using DT boot mode the DMA configuration will be
>> parsed and applied from DT, so, to fix this issue, reuse
>> of_dma_configure() API and retrieve DMA configuartion for "xhci-hcd"
>> from DWC3 device node.
>
> patch is incomplete. You left out non-DT users which might suffer from
> the same problem.
>
Honestly, I don't know how to fix it gracefully for non-DT case.
I can update commit message to mention that this is fix for DT case only.
--
regards,
-grygorii
Powered by blists - more mailing lists