Lars Melin writes:
> On 2016-09-13 12:47, Felipe Balbi wrote:
>> "Steven J. Hill" writes:
>>
>>> On 09/12/2016 02:18 PM, Felipe Balbi wrote:
Please give this a shot. Patches are still RFT
because, well, they need testing. Note also that I
haven't, yet, added a binding documen
On 2016-09-13 12:47, Felipe Balbi wrote:
"Steven J. Hill" writes:
On 09/12/2016 02:18 PM, Felipe Balbi wrote:
Please give this a shot. Patches are still RFT
because, well, they need testing. Note also that I
haven't, yet, added a binding documentation for your
compatible flag. I'll do that o
"Steven J. Hill" writes:
> On 09/12/2016 02:18 PM, Felipe Balbi wrote:
>>
>> Please give this a shot. Patches are still RFT
>> because, well, they need testing. Note also that I
>> haven't, yet, added a binding documentation for your
>> compatible flag. I'll do that on V2 of the patchset.
>>
>
On 09/12/2016 02:18 PM, Felipe Balbi wrote:
>
> Please give this a shot. Patches are still RFT
> because, well, they need testing. Note also that I
> haven't, yet, added a binding documentation for your
> compatible flag. I'll do that on V2 of the patchset.
>
Hey Felipe.
Using your changes, the
Hi Steven,
Here's my take on adding support for your DWC3
implementation. Note that for this to work you need
to properly describe your core with proper
dma-ranges and dma-coherent properties. With that,
OF core will (or should) be able to call
dma_coerce_mask_and_coherent() with appropriate
argum
