linux-kernel - Re: [RFC PATCH 2/3] ASoC: rt5659: Expose internal clock relationships

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] [day] [month] [year] [list]

Date:   Thu, 10 Mar 2022 12:14:49 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Sameer Pujar <spujar@...dia.com>
Cc:     lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
        oder_chiou@...ltek.com, robh@...nel.org, thierry.reding@...il.com,
        jonathanh@...dia.com, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org
Subject: Re: [RFC PATCH 2/3] ASoC: rt5659: Expose internal clock relationships

On Thu, Mar 10, 2022 at 05:11:16PM +0530, Sameer Pujar wrote:

> This patch uses standard clock bindings to establish the codec clock
> relationships. Specific configurations can be applied by DT bindings
> from codec device node. The codec driver registers PLL and MUX clocks
> to provide this flexibility.

Doesn't this need a binding document update to document what clocks are
being provided?

Download attachment "signature.asc" of type "application/pgp-signature" (485 bytes)