[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <201001251135.41611.jeremy.kerr@canonical.com>
Date: Mon, 25 Jan 2010 11:35:41 +1100
From: Jeremy Kerr <jeremy.kerr@...onical.com>
To: "Russell King - ARM Linux" <linux@....linux.org.uk>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: [RFC,PATCH 3/7 v2] arm/versatile: use generic struct clk
Hi Russell,
> This doesn't make any sense. What are you trying to do here?
>
> The get/put operations go together as one logical set - that's why you
> get both if you're using clkdev, and why you're asked to implement both
> __clk_get() and __clk_put() in arch code to do whatever's necessary
> with the clock.
I'm assuming that clk_put will be specific to the implementation; fixed clocks
probably won't need to do anything, but others may need a refcount, etc.
We don't have a struct clk to use clk_get on, so it remains a non-clock-
specific function.
We'll probably need the symmetry for some cases though, I think that a
__clk_get(struct clk *) member of clk_operations would work for this, to be
called by clk_get.
Cheers,
Jeremy
--
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/
Powered by blists - more mailing lists