On Tue, Mar 20, 2012 at 10:45:36PM -0700, Turquette, Mike wrote: > IIRC, that discussion was with respect to the .parent member of struct > clk. It was decided that having .parent = NULL does not imply that a > clock is a root clock, but instead we rely on the CLK_IS_ROOT flag. I > can't think of any other instance where a NULL clk when returned from > a registration function would be useful. No. What I've been saying is that in _drivers_ which use clk_get(), the error range is defined by IS_ERR(clk). Every other value of clk must be assumed by the driver to be valid, no ifs or buts. What the clk API assumes about struct clk is its own business. If it wishes to interpret the NULL clk in a specific way, that's its business to do so. But it's still not the drivers business to then go and interpret NULL as being any different from any other valid clock. This is part of the clk API contract, which is as I said in the first paragraph, and I keep on saying. I'm not sure what's so difficult about this. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
