Hi Stephen Thank you for your feedback > In your case > it sounds like you want to still be able to read the clk hardware? Does > anything go wrong if you let some consumer get the clk and change > settings? Do you want to prevent that from happening? We want to do by this patch-set is to ignoring specific device/clk from Linux. If Linux side change the specific clk settings, other OS side will get damage. > I'm mostly > thinking it may be useful to have this logic be common in the clk > framework by having the framework search through DT and figure out that > the only consumers are reserved and thus we should treat those clks as > read-only in the framework. "this logic" = "this patch-set idea" = "check status=reserved" ? If so, now I quick checked the code. I think it is difficult or makes the code complex if we try implement it on framework or common code. Because the idea itself is very easy (= just adding the CLK_IGNORE_UNUSED), but how to judge the clks is very vender/driver specific. In our case, we need to think about total clock number, conver Linux number to HW number, etc, etc. # I will goto OSS-Japan conference after tomorrow, thus no response # from me until next week. Thank you for your help !! Best regards --- Renesas Electronics Ph.D. Kuninori Morimoto
