Re: [RFC,PATCH 0/7 v2] Common struct clk implementation

2010-01-12 Thread Jeremy Kerr
Hi Russell, > But the point I was trying to convey is that OMAP doesn't work with > _either_ a pure operations struct _or_ a bunch of per-clock function > pointers - it currently uses a mixture of the two. With the common clk, you can do exactly that: struct clk_foo { /* ->ops provides f

Re: [RFC,PATCH 0/7 v2] Common struct clk implementation

2010-01-12 Thread Russell King - ARM Linux
On Tue, Jan 12, 2010 at 05:58:31PM +1100, Jeremy Kerr wrote: > The first two patches are for the architecture-independent kernel code, > introducing the common clk API. The remaining patches are specific to > the ARM 'versatile' and 'realview' platforms. You're still only touching the "easy" platf

[RFC,PATCH 0/7 v2] Common struct clk implementation

2010-01-11 Thread Jeremy Kerr
Hi all, These patches are an attempt to allow platforms to share clock code. At present, the definitions of struct clk are local to platform code, which makes allocating and initialising cross-platform clock sources difficult. The first two patches are for the architecture-independent kernel code