| 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
| ||
|
Message-ID: <5076ED22.3060803@gmail.com> Date: Thu, 11 Oct 2012 18:00:34 +0200 From: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com> To: Daniel Mack <zonque@...il.com> CC: Sebastian Hesselbarh <sebastian.hesselbarth@...glemail.com>, linux-kernel@...r.kernel.org, Mark Brown <broonie@...nsource.wolfsonmicro.com>, mturquette@...com Subject: Re: [RFC] Common clock framework for external clock generators On 10/11/2012 10:34 AM, Daniel Mack wrote: >> I recently read about the newly introduced common clock framework (ccf) >> and wondered if this could be also used for external, e.g. i2c attached, >> clock generators. >> >> Based on my current understanding of the framework I wrote such a >> driver and now I want to present it here for clarification of some >> remarks I have regarding the framework itself. > > May I kindly ask what happened to this driver? Are you planning to do > another spin for submission? Daniel, the driver is still on my list but moved more and more downwards as I got caught by mach-dove DT integration. There is still some work to do, namely regmap and DT. It is used by some off-mainline tree for SolidRun CuBox quite successfully since then. Does any of you work rely on a working si5351 driver? Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists