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: <644e3564-994d-0b51-7d58-dac6afc1e0ec@linaro.org>
Date:   Wed, 13 Sep 2023 08:38:55 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Myunguk Kim <mwkim@...nchips.com>
Cc:     alsa-devel@...a-project.org, broonie@...nel.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, 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

On 13/09/2023 04:53, Myunguk Kim wrote:
>> Bindings are always separate patch.
> 
> Okay, I will send v2.
> 
>> This was not tested. Missing vendor prefix, type.
>>
>> Anyway please provide some explanation why this cannot be deduced from
>> the compatible.
> 
> This is not dependent on a specific vendor, 
> but is intended to describe 
> the properties of the signal(single/burst request) connection 
> relationship between i2s and dma.

How does this relationship depend on hardware?

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ