On Mon, Feb 14, 2022 at 06:01:17PM +0100, Krzysztof Kozlowski wrote: > You mantioned new features - this approach does not change that. If you > add new properties to common schema, you already alter bindings. Just > because we use common part, it does not change the fact that it is a > bindings change. Adding new features in common schema is the same > binding change as adding new feature in the specific binding, except > more work. > I guess you though that work in scaling, so yes, this scales worse. The > benefit is that this really restricts usage of regulator to what is > supported, so allows to detect wrongly configured DTS. We should have a way of specifying generic properties that doesn't require us to go through every single user of a binding and updating them all, then auditing by hand any new users to make sure they didn't forget one of the generic properties. This is just error prone and miserable, especially when most of the checking is done by hand rather than automated. > Once coupling (or any other feature) is supported, each of such > restricted regulator bindings should be independently revised, instead > of adding this new feature to everything. Coupling is already supported - it doesn't require anything on the part of the driver, it's about defining the relationships between supplies rather than anything the driver or device does.
Attachment:
signature.asc
Description: PGP signature
