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]
Date:   Wed, 20 Dec 2017 15:50:00 +0000
From:   Mark Brown <>
To:     Olivier MOYSAN <>
Cc:     "" <>,
        "" <>,
        "" <>,
        "" <>,
        Alexandre TORGUE <>,
        "" <>,
        "" <>,
        "" <>,
        Arnaud POULIQUEN <>,
        Benjamin GAIGNARD <>,
Subject: Re: [RFC PATCH 2/2] ASoC: select sysclk clock from mlck clock
 provider in wm8994 driver

On Wed, Dec 20, 2017 at 12:42:10PM +0000, Olivier MOYSAN wrote:

> As a generic machine, simple or audio graph cards are not able to manage 
> codec clock muxing.
> If we exclude the management of muxing through codec controls,
> the remaining solution is to handle it fully through clock framework.
> The current patch only supports a limited range of muxing capabilities 
> of the codec.
> To have a full management of the muxing, I think it is necessary to add
> a device tree node for each codec interface and to define an aif clock 
> in these nodes.
> Then parent clock assignment of these aif clocks would allow to handle 
> the muxing.

Controlling clocking through a clock API binding would be good, yes.
That'd solve a bunch of other problems with use of multi-purpose clocks
for audio as well.

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

Powered by blists - more mailing lists