lkml.org 
[lkml]   [2017]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v7 2/4] dmaengine: Forward slave device pointer to of_xlate callback
From
Date
Hi Ulf,

On 2017-02-09 10:55, Ulf Hansson wrote:
>>> Yes agreed on that, plus the runtime handling needs to be built in, right
>>> now the APIs dont work well with it, we disucssed these during the KS and
>>> this goes without saying, patches are welcome :)
>> Okay, so what is the conclusion? Do you want me to do the whole rework of
>> dma
>> engine core to get this runtime pm patchset for pl330 merged??? Is there any
>> roadmap for this rework prepared, so I can at least take a look at the
>> amount
>> of work needed to be done?
>>
>> I'm rather new to dma engine framework and I only wanted to fix pl330 driver
>> not to block turning off the power domain on Exynos5422/5433 SoCs.
> As you probably know, this is a common problem for many dma devices,
> slave devices and platforms.

Right, this is a common issue and someone has to finally find a solution
for it.

> If possible, it would be great if we could avoid a solution that
> doesn't force changes to lots of "dma consumer" drivers.

My current solution doesn't require changing ANY "dma consumer" driver.
However,
I have one more idea how to avoid touching dma engine ("provider")
drivers as
well. This will also address some issues pointed by Lars.

Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland

\
 
 \ /
  Last update: 2017-02-09 14:35    [W:0.065 / U:0.508 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site