> Yeah, that's not ok, where are these bits coming from There has been a few more iterations on the patch, in the latest state only Clock Scaling and Write Booster are exposed as individual nodes. > what userspace tools will be using them? In ChromeOS we want to explicitly control WriteBooster state, but for that the user space needs to know when it is supported but off, and when it is not supported at all. On top of it, Clock Scaling complicates the story since it disables the control via wb_on node. That is something I need to figure out separately. --Daniil
