linux-kernel - Re: [RFC] API for system clocks (oscillators)

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]

Message-ID: <4909D33B.4050108@tuffmail.co.uk>
Date:	Thu, 30 Oct 2008 15:31:07 +0000
From:	Alan Jenkins <aj504@...dent.cs.york.ac.uk>
To:	Jonas Bonn <jonas.bonn@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] API for system clocks (oscillators)

Jonas Bonn wrote:
> I'd be happy to get some feedback on this, whether or not it is a good
> idea or even the right way to approach this problem.  This is part of
> the puzzle for solving the problem of frequency scaling on (primarily)
> embedded systems where there are many clocks, (changeable)
> relationships between clocks, device dependencies on clock
> availability, and device constraints on frequency that appear and
> disappear as devices are enabled and disabled.
> 
> This is a first draft (almost thinking-out-loud version), so please
> read it as such... there is much room for improvement and all
> suggestions are welcome.  Release early, release often, right?  Well,
> this is an "early" specification...

Hmm, how does this relate to the OMAP clock domain work?  I read about
it on LWN and was impressed...

omap2-clock merge: <http://thread.gmane.org/gmane.linux.ports.arm.omap/9464>

Len's OLS notes: <http://lwn.net/Articles/292447/>

Regards
Alan
--
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/