linux-kernel - Re: [PATCH v7 2/4] dmaengine: Forward slave device pointer to of

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 for Android: free password hash cracker in your pocket

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

Message-id: <625feb31-58c5-cf23-8833-5f928bf4603d@samsung.com>
Date:   Thu, 09 Feb 2017 14:30:13 +0100
From:   Marek Szyprowski <m.szyprowski@...sung.com>
To:     Ulf Hansson <ulf.hansson@...aro.org>
Cc:     Vinod Koul <vinod.koul@...el.com>,
        Lars-Peter Clausen <lars@...afoo.de>,
        linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
        dmaengine@...r.kernel.org, alsa-devel@...a-project.org,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        Mark Brown <broonie@...nel.org>,
        Inki Dae <inki.dae@...sung.com>
Subject: Re: [PATCH v7 2/4] dmaengine: Forward slave device pointer to of_xlate
 callback

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