linux-kernel - Re: [RFC PATCH] clk: add extension API

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: <20120531100112.GR5377@arwen.pp.htv.fi>
Date:	Thu, 31 May 2012 13:01:29 +0300
From:	Felipe Balbi <balbi@...com>
To:	Peter De Schrijver <pdeschrijver@...dia.com>
Cc:	Felipe Balbi <balbi@...com>, Stephen Boyd <sboyd@...eaurora.org>,
	Russell King <linux@....linux.org.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Mike Turquette <mturquette@...com>,
	Paul Walmsley <paul@...an.com>, Kevin Hilman <khilman@...com>,
	Benoit Cousson <b-cousson@...com>
Subject: Re: [RFC PATCH] clk: add extension API

On Thu, May 31, 2012 at 12:57:23PM +0300, Peter De Schrijver wrote:
> 
> > 
> > Well, that's just because struct device doesn't know about its own clock
> > providers, right ? Should that be patched too ?
> > 
> > Russell, as the orignal author of the clk API, what do you think ?
> 
> Even if it would know, how would that solve the problem? only the
> clockframework is supposed to know about struct clk.

you have the device and you have the clock, you need to toggle a bit on
the clock address space. I guess that pretty much says it, no ? Unless
your implementation of struct clk doesn't tell you clk register offset
which is rather unlikely.

-- 
balbi

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