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: <20081030201341.GD13678@sirena.org.uk>
Date:	Thu, 30 Oct 2008 20:13:44 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	Jonas Bonn <jonas.bonn@...il.com>
Cc:	Jon Smirl <jonsmirl@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] API for system clocks (oscillators)

On Thu, Oct 30, 2008 at 06:01:42PM +0100, Jonas Bonn wrote:

> > You could probably work those features into the existing clk framework.
> > clk_set_rate() could compute the constrains and return an error.
> > The API could be expanded with notifier support.

...

> What drove me to document a new interface is the fact that there are
> so many users of "struct clk" already, that it becomes conceptually
> easier to dream up something new that stays out of the way, even if
> that new  thing becomes just a wrapper around the existing interface

BTW, on this point I don't know if you've seen Dmitry Baryshkov's work
on a generic implementation of the existing clk API.
--
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/