No subject

the actual rate does not matter, only enabling/disabling the clock for
register accesses is important. When a driver sets a rate on a clock it
does it on purpose and if this clock is not even present on other SoCs
it looks like a bug or at least a very special case for me. So I think
clk_set_rate for a NULL clock should fail.
Other than that it's not a good behaviour when clk_get_rate() returns
0 for clock which rate has been successfully set to another rate using
clk_set_rate().

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |