linux-kernel - Re: [PATCH] ASoC: dwc: Add Single DMA mode support

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]

Message-Id: <20230913040902.1496711-1-mwkim@gaonchips.com>
Date:   Wed, 13 Sep 2023 13:09:03 +0900
From:   Myunguk Kim <mwkim@...nchips.com>
To:     broonie@...nel.org
Cc:     alsa-devel@...a-project.org, conor+dt@...nel.org,
        devicetree@...r.kernel.org, fido_max@...ox.ru,
        joabreu@...opsys.com, krzysztof.kozlowski+dt@...aro.org,
        kuninori.morimoto.gx@...esas.com, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, mwkim@...nchips.com, perex@...ex.cz,
        robh+dt@...nel.org, tiwai@...e.com, u.kleine-koenig@...gutronix.de,
        xingyu.wu@...rfivetech.com
Subject: Re: [PATCH] ASoC: dwc: Add Single DMA mode support

> This feels like something we ought to be discovering from the DMA API
> somehow, while it's not quite a property of the DMA controller (but
> rather of the SoC integration) in this case it could be a property of
> some DMA controller elsewhere and the whole process of finding and
> figuring out the properties of the DMA controler is handled by the DMA
> API.

In this case, it is not used through the DMA API. 
The connection relationship is as follows.
  i2s --- pcm_dmaengine ---  DMA IP (ie. pl330)
So, control was possible only by directly setting the maxburst property.

And, I will send v2 (separate code and bindings)

Thanks,
myunguk