On 21/03/2025 18:24, Guenter Roeck wrote:That is not in driver control: If regulators_node is set by the driver,
I would recommend keep the nesting, so don't touch it. There might be
Figured. As it turns out, there is also a patch series pending which tries
to fix the problem for ir38060 by changing its bindings.
I'll dig up my patch series to add a new macro and send it out as RFT.
Question for DT maintainers:
Existing bindings, such as
Documentation/devicetree/bindings/regulator/mps,mpq2286.yaml
expect a nested regulators node even though there is only a single
regulator. What is the correct approach: Keep the nesting requirement
for those regulators as is (even if there are no in-tree bindings
using them), or update the code and the bindings to drop the nesting ?
external users, other projects relying on this. You can however
deprecate old node (nesting), if the driver can support both. Not sure
if it is worth the effort.