linux-kernel - Re: [alsa-devel] [RFC PATCH] mfd: arizona: Add gating of external MCLKn clocks

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

Date:   Thu, 25 Aug 2016 15:26:41 +0200
From:   Sylwester Nawrocki <s.nawrocki@...sung.com>
To:     Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:     broonie@...nel.org, alsa-devel@...a-project.org,
        lee.jones@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [alsa-devel] [RFC PATCH] mfd: arizona: Add gating of external
 MCLKn clocks

On 08/25/2016 03:02 PM, Charles Keepax wrote:
> Yes so the MCLK needs to be available before we start the FLL, so
> my thinking was we would enable the clock that corresponds
> to the source for the FLL in arizona_set_fll before we start
> enabling the FLL.
> 
> The direct MCLK would require a little more work but we could
> probably enable the clock in this case from wm5110_sysclk_ev.
> 
> I have sent you through a copy of my prototype clock patches you
> can have a look at. I am going to have a bit of a look over this
> today and hopefully will be able to get back to you with more
> concrete thoughts later today.

Thanks, I will have a closer look at the patches.

I have hard coded the MCLK frequency in the tm2_wm511 machine driver
as its fixed anyway and now if the MCLK gating was taken care of by
the CODEC we wouldn't need at all to get at the MCLK clocks in the
machine driver.