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: <9e4733910810300840v7cd45c2cu629d23a27a02c61a@mail.gmail.com>
Date:	Thu, 30 Oct 2008 11:40:00 -0400
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Jonas Bonn" <jonas.bonn@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] API for system clocks (oscillators)

On Thu, Oct 30, 2008 at 10:41 AM, Jonas Bonn <jonas.bonn@...il.com> 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.

How does this compare to the framework in linux/include/linux/clk.h?

-- 
Jon Smirl
jonsmirl@...il.com
--
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/