linux-kernel - Re: 32kHz clock removal causes problems omap

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]

Date:	Wed, 19 Dec 2012 10:09:09 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Peter Ujfalusi <peter.ujfalusi@...com>
Cc:	Felipe Balbi <balbi@...com>, Luciano Coelho <coelho@...com>,
	svenkatr@...com, linux-omap@...r.kernel.org,
	linux-mmc@...r.kernel.org, cjb@...top.org, lrg@...com,
	linux-kernel@...r.kernel.org, Tony Lindgren <tony@...mide.com>
Subject: Re: 32kHz clock removal causes problems omap_hsmmc

On Wed, Dec 19, 2012 at 11:00:32AM +0100, Peter Ujfalusi wrote:

> I don't know the state of the common clock framework for OMAPs. Is it already
> up in 3.7? Or going for 3.8? 3.9? 3.10?...
> We need CCF to resolve this. I can cook up the clock driver for the 32k clock
> from twl, but in order to use it we need CCF on OMAP.

Well, we at least ought to make sure it doesn't appear in the regulator
DT bindings even if it's handled via some OMAP magic - that was the key
point here.

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