Skip to contentSkip to conversation

Voltage and current regulator: usage of 'regulators' parent node in device tree

DISCUSSION embedded (VIVAVIS AG) 1 participant 2 messages Jul 8, 2021 – Jul 14, 2021

lore
Share & tools
lore
#0 lore raw

I see a lot of Device trees wrapping the regulator nodes within a parent node like this

regulators {
    compatible = "simple-bus";
    #address-cells = <1>;
    #size-cells = <0>;
    reg_p3v3: regulator@0 {
        compatible = "regulator-fixed";
        [...]
        regulator-always-on;
    };
    [...]

Contrary to that, patches exist removing the 'regulators' node, because the 'simple-bus' doesn't really exist in hardware. Unfortunately, the documentation is unclear about wrapping regulator nodes like shown above.

Should I avoid the parent 'regulators' node and why?

Is the given naming schema in fixed-regulator.yaml best practice to follow?

    reg_xyz: regulator-xyz {
      compatible = "regulator-fixed";
      regulator-name = "xyz";

Thank you for clarification.

Carsten Stelling

#1 lore raw

Hi,

Quoted 22 lines

I see a lot of Device trees wrapping the regulator nodes within a parent node like this

regulators {
   compatible = "simple-bus";
   #address-cells = <1>;
   #size-cells = <0>;
   reg_p3v3: regulator@0 {
       compatible = "regulator-fixed";
       [...]
       regulator-always-on;
   };
   [...]

Contrary to that, patches exist removing the 'regulators' node, because the 'simple-bus' doesn't really exist in hardware. Unfortunately, the documentation is unclear about wrapping regulator nodes like shown above.

Should I avoid the parent 'regulators' node and why?

Is the given naming schema in fixed-regulator.yaml best practice to follow?

Quoted 7 lines
   reg_xyz: regulator-xyz {
     compatible = "regulator-fixed";
     regulator-name = "xyz";

Thank you for clarification.

Carsten Stelling

Possibly, the wrong list or recipients?
Any thoughts on this topic?

Thank you for your help.

Carsten