On Tue, Apr 24, 2012 at 01:28:20PM +0530, Viresh Kumar wrote: > On 4/24/2012 1:12 PM, Russell King - ARM Linux wrote: > > If you don't have the clk API configured, you have no clocks to control. > > So, why not make clk_get() return NULL, and make the rest of the API > > calls do nothing? That's what you'll end up codifying in the drivers > > anyway. > > Ok. We can return NULL from calls that return clk *. What about other > routines that return integers. Like, clk_enable(). > > Is returning 0 correct? Which would mean we were able to enable clk, but > actually we haven't. Think about this case: if you don't have the means to control the clock inputs to a device (for example, you don't support the clk API on your CPU arch) then for the device to be functional, it must be supplied with all its necessary clocks. Therefore, the clock is already enabled. It makes sense for the clk API to stub-out to be completely transparent and non-error inducing to the driver. The problem comes with clk_get_rate(). I'd suggest merely returning zero for that in this case. If the clock rate is really required by a driver, then the clk API would need to be enabled. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
