[PATCH 1/3] Add a common struct clk
Jeremy Kerr
jeremy.kerr at canonical.com
Tue Dec 7 20:02:37 EST 2010
Hi Uwe,
> I assume the initial feedback should be provided from someone internal
> to Canonical or Linaro? Can you give an estimate when you can post it,
> I really thing that's the way to go for simplifying the clock code on
> imx which is on my todo list.
No, I was waiting on feedback from the ST-E platform folks, who will need the
atomic clocks. However, I've been out of action for a couple of weeks, hence
the delay.
I'll get the next revision posted this week.
> While reading quickly over the patch I wondered if there isn't a better
> way to get that spinlock/mutex thingy implemented.
>
> You currently have:
>
> struct clk {
> const struct clk_ops *ops;
> unsigned int enable_count;
> int flags;
> union {
> struct mutex mutex;
> spinlock_t spinlock;
> } lock;
> };
>
> What about using this one instead?:
>
> struct clk_base {
> /* merge that with ops? Probably not */
> const struct clk_lock_ops *lock_ops;
> const struct clk_ops *ops;
> unsigned int enable_count;
> };
>
> struct clk {
> struct clk_base base;
> struct mutex lock;
> };
>
> struct clk_atomic {
> struct clk_base base;
> spinlock_t lock;
> };
This means we'll need a separate API (clk_get_rate, etc) for the atomic
clocks, or change the API to take a clk_base (and then fix up all the users of
the API).
Regardless, I'd prefer to keep the separation to just the lock itself, rather
than percolating down to other interfaces.
> This way and when I prefer to use the sleeping variant only I don't need
> to bother with spinlocks at all.
How do you mean? You shouldn't need to deal with spinlocks with the current
code if you're just using non-atomic clocks.
Cheers,
Jeremy
More information about the linux-arm-kernel
mailing list