| Message ID | 20231201110840.37408-5-biju.das.jz@bp.renesas.com (mailing list archive) |
|---|---|
| State | Superseded |
| Delegated to: | Geert Uytterhoeven |
| Headers | show |
| Series | Add DA9062 PMIC and built-in RTC support for RZ/G2UL SMARC EVK | expand |
Hi Biju, On Fri, Dec 1, 2023 at 12:09 PM Biju Das <biju.das.jz@bp.renesas.com> wrote: > Convert the da9062 PMIC device tree binding documentation to json-schema. > > Update the example to match reality. > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com> Thanks for your patch! > --- a/Documentation/devicetree/bindings/mfd/da9062.txt > +++ /dev/null This file is still referred to from other files: $ git grep Documentation/devicetree/bindings/mfd/da9062.txt Documentation/devicetree/bindings/input/da9062-onkey.txt:DA9062 and DA9061 chips see Documentation/devicetree/bindings/mfd/da9062.txt Documentation/devicetree/bindings/thermal/da9062-thermal.txt:DA9062 and DA9061 chips see Documentation/devicetree/bindings/mfd/da9062.txt > -- onkey : See ../input/da9062-onkey.txt Documentation/devicetree/bindings/input/da9062-onkey.txt still exists, and covers more variants than your new dlg,da9062.yaml. > - > -- watchdog: See ../watchdog/da9062-wdt.txt This was replaced by Documentation/devicetree/bindings/watchdog/dlg,da9062-watchdog.yaml a while ago, and covers more variants than your new dlg,da9062.yaml. > - > -- thermal : See ../thermal/da9062-thermal.txt Documentation/devicetree/bindings/thermal/da9062-thermal.txt still exists, and covers more variants than your new dlg,da9062.yaml. > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/dlg,da9062.yaml > @@ -0,0 +1,220 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/mfd/dlg,da9062.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Dialog DA9062 Power Management Integrated Circuit (PMIC) > + > +maintainers: > + - Biju Das <biju.das.jz@bp.renesas.com> > + > +description: | > + Product information for the DA9062 and DA9061 devices can be found here: > + - https://www.dialog-semiconductor.com/products/da9062 > + - https://www.dialog-semiconductor.com/products/da9061 > + > + The DA9062 PMIC consists of: > + > + Device Supply Names Description > + ------ ------------ ----------- > + da9062-regulator : : LDOs & BUCKs > + da9062-rtc : : Real-Time Clock > + da9062-onkey : : On Key > + da9062-watchdog : : Watchdog Timer > + da9062-thermal : : Thermal > + da9062-gpio : : GPIOs > + > + The DA9061 PMIC consists of: > + > + Device Supply Names Description > + ------ ------------ ----------- > + da9062-regulator : : LDOs & BUCKs > + da9062-onkey : : On Key > + da9062-watchdog : : Watchdog Timer > + da9062-thermal : : Thermal da9061 (x4) > + > +properties: > + watchdog: Please sort subnodes alphabetically. > + type: object > + $ref: /schemas/watchdog/watchdog.yaml# > + unevaluatedProperties: false > + properties: > + compatible: > + const: dlg,da9062-watchdog What about dlg,da9061-watchdog? Probably this should refer to Documentation/devicetree/bindings/watchdog/dlg,da9062-watchdog.yaml instead? This applies to the other subnodes, too. Perhaps this binding should be merged with dlg,da9063.yaml? Or should it be split in dlg,da9061.yaml and dlg,da9062.yaml? Gr{oetje,eeting}s, Geert
On Fri, Dec 01, 2023 at 02:33:29PM +0100, Geert Uytterhoeven wrote: > Hi Biju, > > On Fri, Dec 1, 2023 at 12:09 PM Biju Das <biju.das.jz@bp.renesas.com> wrote: > > Convert the da9062 PMIC device tree binding documentation to json-schema. > > > > Update the example to match reality. > > > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com> > > Thanks for your patch! > > > --- a/Documentation/devicetree/bindings/mfd/da9062.txt > > +++ /dev/null > > This file is still referred to from other files: > > $ git grep Documentation/devicetree/bindings/mfd/da9062.txt > Documentation/devicetree/bindings/input/da9062-onkey.txt:DA9062 > and DA9061 chips see Documentation/devicetree/bindings/mfd/da9062.txt > Documentation/devicetree/bindings/thermal/da9062-thermal.txt:DA9062 > and DA9061 chips see Documentation/devicetree/bindings/mfd/da9062.txt > > > -- onkey : See ../input/da9062-onkey.txt > > Documentation/devicetree/bindings/input/da9062-onkey.txt still exists, > and covers more variants than your new dlg,da9062.yaml. > > > - > > -- watchdog: See ../watchdog/da9062-wdt.txt > > This was replaced by > Documentation/devicetree/bindings/watchdog/dlg,da9062-watchdog.yaml > a while ago, and covers more variants than your new dlg,da9062.yaml. > > > - > > -- thermal : See ../thermal/da9062-thermal.txt > > Documentation/devicetree/bindings/thermal/da9062-thermal.txt still exists, > and covers more variants than your new dlg,da9062.yaml. > > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/mfd/dlg,da9062.yaml > > @@ -0,0 +1,220 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/mfd/dlg,da9062.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Dialog DA9062 Power Management Integrated Circuit (PMIC) > > + > > +maintainers: > > + - Biju Das <biju.das.jz@bp.renesas.com> > > + > > +description: | > > + Product information for the DA9062 and DA9061 devices can be found here: > > + - https://www.dialog-semiconductor.com/products/da9062 > > + - https://www.dialog-semiconductor.com/products/da9061 > > + > > + The DA9062 PMIC consists of: > > + > > + Device Supply Names Description > > + ------ ------------ ----------- > > + da9062-regulator : : LDOs & BUCKs > > + da9062-rtc : : Real-Time Clock > > + da9062-onkey : : On Key > > + da9062-watchdog : : Watchdog Timer > > + da9062-thermal : : Thermal > > + da9062-gpio : : GPIOs > > + > > + The DA9061 PMIC consists of: > > + > > + Device Supply Names Description > > + ------ ------------ ----------- > > + da9062-regulator : : LDOs & BUCKs > > + da9062-onkey : : On Key > > + da9062-watchdog : : Watchdog Timer > > + da9062-thermal : : Thermal > > da9061 (x4) Is retaining this even needed with a yaml binding that correctly constrains the children? > > > + > > +properties: > > > + watchdog: > > Please sort subnodes alphabetically. > > > + type: object > > + $ref: /schemas/watchdog/watchdog.yaml# > > + unevaluatedProperties: false > > + properties: > > + compatible: > > + const: dlg,da9062-watchdog > > What about dlg,da9061-watchdog? Probably this should refer to > Documentation/devicetree/bindings/watchdog/dlg,da9062-watchdog.yaml > instead? > > This applies to the other subnodes, too. > > Perhaps this binding should be merged with dlg,da9063.yaml? > Or should it be split in dlg,da9061.yaml and dlg,da9062.yaml? The former sounds like a noble goal to me.
Hi Biju, kernel test robot noticed the following build warnings: [auto build test WARNING on abelloni/rtc-next] [also build test WARNING on lee-mfd/for-mfd-next geert-renesas-devel/next arm64/for-next/core linus/master v6.7-rc4 next-20231205] [cannot apply to lee-mfd/for-mfd-fixes] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Biju-Das/rtc-da9063-Use-device_get_match_data/20231201-231120 base: https://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git rtc-next patch link: https://lore.kernel.org/r/20231201110840.37408-5-biju.das.jz%40bp.renesas.com patch subject: [PATCH 4/6] dt-bindings: mfd: Convert da9062 to json-schema reproduce: (https://download.01.org/0day-ci/archive/20231206/202312061323.Zk81yCZU-lkp@intel.com/reproduce) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot <lkp@intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202312061323.Zk81yCZU-lkp@intel.com/ All warnings (new ones prefixed by >>): >> Warning: Documentation/devicetree/bindings/input/da9062-onkey.txt references a file that doesn't exist: Documentation/devicetree/bindings/mfd/da9062.txt >> Warning: Documentation/devicetree/bindings/thermal/da9062-thermal.txt references a file that doesn't exist: Documentation/devicetree/bindings/mfd/da9062.txt
Hi kernel test robot, > -----Original Message----- > From: kernel test robot <lkp@intel.com> > Subject: Re: [PATCH 4/6] dt-bindings: mfd: Convert da9062 to json-schema > > Hi Biju, > > kernel test robot noticed the following build warnings: > > > If you fix the issue in a separate patch/commit (i.e. not just a new > version of the same patch/commit), kindly add following tags > | Reported-by: kernel test robot <lkp@intel.com> > | Closes: > > All warnings (new ones prefixed by >>): > > >> Warning: Documentation/devicetree/bindings/input/da9062-onkey.txt > >> references a file that doesn't exist: > >> Documentation/devicetree/bindings/mfd/da9062.txt > >> Warning: Documentation/devicetree/bindings/thermal/da9062-thermal.txt > >> references a file that doesn't exist: > >> Documentation/devicetree/bindings/mfd/da9062.txt > There is an updated patch series available[1] and Please retest and provide feedback if any? [1] https://lore.kernel.org/all/20231204172510.35041-1-biju.das.jz@bp.renesas.com/ Cheers, Biju
On Wed, 06 Dec 2023, Biju Das wrote: > Hi kernel test robot, > > > -----Original Message----- > > From: kernel test robot <lkp@intel.com> > > Subject: Re: [PATCH 4/6] dt-bindings: mfd: Convert da9062 to json-schema > > > > Hi Biju, > > > > kernel test robot noticed the following build warnings: > > > > > > If you fix the issue in a separate patch/commit (i.e. not just a new > > version of the same patch/commit), kindly add following tags > > | Reported-by: kernel test robot <lkp@intel.com> > > | Closes: > > > > All warnings (new ones prefixed by >>): > > > > >> Warning: Documentation/devicetree/bindings/input/da9062-onkey.txt > > >> references a file that doesn't exist: > > >> Documentation/devicetree/bindings/mfd/da9062.txt > > >> Warning: Documentation/devicetree/bindings/thermal/da9062-thermal.txt > > >> references a file that doesn't exist: > > >> Documentation/devicetree/bindings/mfd/da9062.txt > > > > There is an updated patch series available[1] and Please retest and > provide feedback if any? Do you often find yourself chatting with inanimate/automated services? :)
Hi Lee Jones, > -----Original Message----- > From: Lee Jones <lee@kernel.org> > Sent: Wednesday, December 6, 2023 1:28 PM > Subject: Re: [PATCH 4/6] dt-bindings: mfd: Convert da9062 to json-schema > > On Wed, 06 Dec 2023, Biju Das wrote: > > > Hi kernel test robot, > > > > > -----Original Message----- > > > From: kernel test robot <lkp@intel.com> > > > Subject: Re: [PATCH 4/6] dt-bindings: mfd: Convert da9062 to > > > json-schema > > > > > > Hi Biju, > > > > > > kernel test robot noticed the following build warnings: > > > > > > > > > If you fix the issue in a separate patch/commit (i.e. not just a new > > > version of the same patch/commit), kindly add following tags > > > | Reported-by: kernel test robot <lkp@intel.com> > > > | Closes: > > > > > > All warnings (new ones prefixed by >>): > > > > > > >> Warning: Documentation/devicetree/bindings/input/da9062-onkey.txt > > > >> references a file that doesn't exist: > > > >> Documentation/devicetree/bindings/mfd/da9062.txt > > > >> Warning: > > > >> Documentation/devicetree/bindings/thermal/da9062-thermal.txt > > > >> references a file that doesn't exist: > > > >> Documentation/devicetree/bindings/mfd/da9062.txt > > > > > > > There is an updated patch series available[1] and Please retest and > > provide feedback if any? > > Do you often find yourself chatting with inanimate/automated services? :) FYI, based on the previous experience, there are some people used to respond even though it is addressed to kernel test robot <lkp@intel.com>. I don't know about the current situation. Cheers, Biju
Hi Biju, Hi Lee, On Wed, 2023-12-06 at 15:19 +0000, Biju Das wrote: > Hi Lee Jones, > > > -----Original Message----- > > From: Lee Jones <lee@kernel.org> > > Sent: Wednesday, December 6, 2023 1:28 PM > > Subject: Re: [PATCH 4/6] dt-bindings: mfd: Convert da9062 to json- > > schema > > > > On Wed, 06 Dec 2023, Biju Das wrote: > > > > > Hi kernel test robot, > > > > > > > -----Original Message----- > > > > From: kernel test robot <lkp@intel.com> > > > > Subject: Re: [PATCH 4/6] dt-bindings: mfd: Convert da9062 to > > > > json-schema > > > > > > > > Hi Biju, > > > > > > > > kernel test robot noticed the following build warnings: > > > > > > > > > > > > If you fix the issue in a separate patch/commit (i.e. not just > > > > a new > > > > version of the same patch/commit), kindly add following tags > > > > > Reported-by: kernel test robot <lkp@intel.com> > > > > > Closes: > > > > > > > > All warnings (new ones prefixed by >>): > > > > > > > > > > Warning: Documentation/devicetree/bindings/input/da9062- > > > > > > onkey.txt > > > > > > references a file that doesn't exist: > > > > > > Documentation/devicetree/bindings/mfd/da9062.txt > > > > > > Warning: > > > > > > Documentation/devicetree/bindings/thermal/da9062- > > > > > > thermal.txt > > > > > > references a file that doesn't exist: > > > > > > Documentation/devicetree/bindings/mfd/da9062.txt > > > > > > > > > > There is an updated patch series available[1] and Please retest > > > and > > > provide feedback if any? > > > > Do you often find yourself chatting with inanimate/automated > > services? :) > > FYI, based on the previous experience, there are some people used to > respond > even though it is addressed to kernel test robot <lkp@intel.com>. > > I don't know about the current situation. There are indeed humans behind the robot. Currently we are: Philip Li <philip.li@intel.com> Oliver Sang <oliver.sang@intel.com> Yujie Liu <yujie.liu@intel.com> We will respond if developers need help or have feedback on the robot, but sometimes we may not be able to respond in time due to bandwidth overload. Sorry for any delayed reply. As for Biju's request of testing the updated patch series, the robot cannot support auto-testing for it yet. Sorry for this. We suggest first trying the reproducer in the original report to see if the issue can be reproduced, then applying the updated patch series to check if the reported issue goes away. Please kindly contact us if any problems using the reproducer. Best Regards, Yujie
diff --git a/Documentation/devicetree/bindings/mfd/da9062.txt b/Documentation/devicetree/bindings/mfd/da9062.txt deleted file mode 100644 index e4eedd3bd233..000000000000 --- a/Documentation/devicetree/bindings/mfd/da9062.txt +++ /dev/null @@ -1,124 +0,0 @@ -* Dialog DA9062 Power Management Integrated Circuit (PMIC) - -Product information for the DA9062 and DA9061 devices can be found here: -- https://www.dialog-semiconductor.com/products/da9062 -- https://www.dialog-semiconductor.com/products/da9061 - -The DA9062 PMIC consists of: - -Device Supply Names Description ------- ------------ ----------- -da9062-regulator : : LDOs & BUCKs -da9062-rtc : : Real-Time Clock -da9062-onkey : : On Key -da9062-watchdog : : Watchdog Timer -da9062-thermal : : Thermal -da9062-gpio : : GPIOs - -The DA9061 PMIC consists of: - -Device Supply Names Description ------- ------------ ----------- -da9062-regulator : : LDOs & BUCKs -da9062-onkey : : On Key -da9062-watchdog : : Watchdog Timer -da9062-thermal : : Thermal - -====== - -Required properties: - -- compatible : Should be - "dlg,da9062" for DA9062 - "dlg,da9061" for DA9061 -- reg : Specifies the I2C slave address (this defaults to 0x58 but it can be - modified to match the chip's OTP settings). - -Optional properties: - -- gpio-controller : Marks the device as a gpio controller. -- #gpio-cells : Should be two. The first cell is the pin number and the - second cell is used to specify the gpio polarity. - -See Documentation/devicetree/bindings/gpio/gpio.txt for further information on -GPIO bindings. - -- interrupts : IRQ line information. -- interrupt-controller - -See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt for -further information on IRQ bindings. - -Sub-nodes: - -- regulators : This node defines the settings for the LDOs and BUCKs. - The DA9062 regulators are bound using their names listed below: - - buck1 : BUCK_1 - buck2 : BUCK_2 - buck3 : BUCK_3 - buck4 : BUCK_4 - ldo1 : LDO_1 - ldo2 : LDO_2 - ldo3 : LDO_3 - ldo4 : LDO_4 - - The DA9061 regulators are bound using their names listed below: - - buck1 : BUCK_1 - buck2 : BUCK_2 - buck3 : BUCK_3 - ldo1 : LDO_1 - ldo2 : LDO_2 - ldo3 : LDO_3 - ldo4 : LDO_4 - - The component follows the standard regulator framework and the bindings - details of individual regulator device can be found in: - Documentation/devicetree/bindings/regulator/regulator.txt - - regulator-initial-mode may be specified for buck regulators using mode values - from include/dt-bindings/regulator/dlg,da9063-regulator.h. - -- rtc : This node defines settings required for the Real-Time Clock associated - with the DA9062. There are currently no entries in this binding, however - compatible = "dlg,da9062-rtc" should be added if a node is created. - -- onkey : See ../input/da9062-onkey.txt - -- watchdog: See ../watchdog/da9062-wdt.txt - -- thermal : See ../thermal/da9062-thermal.txt - -Example: - - pmic0: da9062@58 { - compatible = "dlg,da9062"; - reg = <0x58>; - interrupt-parent = <&gpio6>; - interrupts = <11 IRQ_TYPE_LEVEL_LOW>; - interrupt-controller; - - rtc { - compatible = "dlg,da9062-rtc"; - }; - - regulators { - DA9062_BUCK1: buck1 { - regulator-name = "BUCK1"; - regulator-min-microvolt = <300000>; - regulator-max-microvolt = <1570000>; - regulator-min-microamp = <500000>; - regulator-max-microamp = <2000000>; - regulator-initial-mode = <DA9063_BUCK_MODE_SYNC>; - regulator-boot-on; - }; - DA9062_LDO1: ldo1 { - regulator-name = "LDO_1"; - regulator-min-microvolt = <900000>; - regulator-max-microvolt = <3600000>; - regulator-boot-on; - }; - }; - }; - diff --git a/Documentation/devicetree/bindings/mfd/dlg,da9062.yaml b/Documentation/devicetree/bindings/mfd/dlg,da9062.yaml new file mode 100644 index 000000000000..43ddf14a4a6d --- /dev/null +++ b/Documentation/devicetree/bindings/mfd/dlg,da9062.yaml @@ -0,0 +1,220 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/mfd/dlg,da9062.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Dialog DA9062 Power Management Integrated Circuit (PMIC) + +maintainers: + - Biju Das <biju.das.jz@bp.renesas.com> + +description: | + Product information for the DA9062 and DA9061 devices can be found here: + - https://www.dialog-semiconductor.com/products/da9062 + - https://www.dialog-semiconductor.com/products/da9061 + + The DA9062 PMIC consists of: + + Device Supply Names Description + ------ ------------ ----------- + da9062-regulator : : LDOs & BUCKs + da9062-rtc : : Real-Time Clock + da9062-onkey : : On Key + da9062-watchdog : : Watchdog Timer + da9062-thermal : : Thermal + da9062-gpio : : GPIOs + + The DA9061 PMIC consists of: + + Device Supply Names Description + ------ ------------ ----------- + da9062-regulator : : LDOs & BUCKs + da9062-onkey : : On Key + da9062-watchdog : : Watchdog Timer + da9062-thermal : : Thermal + +properties: + compatible: + enum: + - dlg,da9062 + - dlg,da9061 + + reg: + maxItems: 1 + + interrupts: + maxItems: 1 + + interrupt-controller: true + + "#interrupt-cells": + const: 2 + + gpio-controller: true + + "#gpio-cells": + const: 2 + + watchdog: + type: object + $ref: /schemas/watchdog/watchdog.yaml# + unevaluatedProperties: false + properties: + compatible: + const: dlg,da9062-watchdog + + dlg,use-sw-pm: + type: boolean + description: + Disable the watchdog during suspend. + Only use this option if you can't use the watchdog automatic suspend + function during a suspend (see register CONTROL_B). + + rtc: + type: object + $ref: /schemas/rtc/rtc.yaml# + unevaluatedProperties: false + properties: + compatible: + const: dlg,da9062-rtc + + thermal: + type: object + unevaluatedProperties: false + properties: + compatible: + const: dlg,da9062-thermal + + gpio: + type: object + $ref: /schemas/gpio/gpio.yaml# + unevaluatedProperties: false + properties: + compatible: + const: dlg,da9062-gpio + + onkey: + type: object + $ref: /schemas/input/input.yaml# + unevaluatedProperties: false + properties: + compatible: + const: dlg,da9062-onkey + + dlg,disable-key-power: + type: boolean + description: | + Disable power-down using a long key-press. + If this entry does not exist then by default the key-press triggered + power down is enabled and the OnKey will support both KEY_POWER and + KEY_SLEEP. + + regulators: + type: object + additionalProperties: false + patternProperties: + "^(ldo[1-9]|buck[1-4])$": + $ref: /schemas/regulator/regulator.yaml + unevaluatedProperties: false + +required: + - compatible + - reg + +additionalProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/irq.h> + #include <dt-bindings/regulator/dlg,da9063-regulator.h> + i2c { + #address-cells = <1>; + #size-cells = <0>; + pmic@58 { + compatible = "dlg,da9062"; + reg = <0x58>; + #interrupt-cells = <2>; + interrupt-parent = <&gpio1>; + interrupts = <2 IRQ_TYPE_LEVEL_LOW>; + interrupt-controller; + + rtc { + compatible = "dlg,da9062-rtc"; + }; + + onkey { + compatible = "dlg,da9062-onkey"; + }; + + watchdog { + compatible = "dlg,da9062-watchdog"; + dlg,use-sw-pm; + }; + + thermal { + compatible = "dlg,da9062-thermal"; + status = "disabled"; + }; + + gpio { + compatible = "dlg,da9062-gpio"; + status = "disabled"; + }; + + regulators { + buck1 { + regulator-name = "vdd_arm"; + regulator-min-microvolt = <925000>; + regulator-max-microvolt = <1380000>; + regulator-initial-mode = <DA9063_BUCK_MODE_SYNC>; + regulator-always-on; + }; + buck2 { + regulator-name = "vdd_soc"; + regulator-min-microvolt = <1150000>; + regulator-max-microvolt = <1380000>; + regulator-initial-mode = <DA9063_BUCK_MODE_SYNC>; + regulator-always-on; + }; + buck3 { + regulator-name = "vdd_ddr3"; + regulator-min-microvolt = <1500000>; + regulator-max-microvolt = <1500000>; + regulator-initial-mode = <DA9063_BUCK_MODE_SYNC>; + regulator-always-on; + }; + buck4 { + regulator-name = "vdd_eth"; + regulator-min-microvolt = <1200000>; + regulator-max-microvolt = <1200000>; + regulator-initial-mode = <DA9063_BUCK_MODE_SYNC>; + regulator-always-on; + }; + ldo1 { + regulator-name = "vdd_snvs"; + regulator-min-microvolt = <3000000>; + regulator-max-microvolt = <3000000>; + regulator-always-on; + }; + ldo2 { + regulator-name = "vdd_high"; + regulator-min-microvolt = <3000000>; + regulator-max-microvolt = <3000000>; + regulator-always-on; + }; + ldo3 { + regulator-name = "vdd_eth_io"; + regulator-min-microvolt = <2500000>; + regulator-max-microvolt = <2500000>; + }; + ldo4 { + regulator-name = "vdd_emmc"; + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <1800000>; + regulator-always-on; + }; + }; + }; + }; +...
Convert the da9062 PMIC device tree binding documentation to json-schema. Update the example to match reality. Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com> --- .../devicetree/bindings/mfd/da9062.txt | 124 ---------- .../devicetree/bindings/mfd/dlg,da9062.yaml | 220 ++++++++++++++++++ 2 files changed, 220 insertions(+), 124 deletions(-) delete mode 100644 Documentation/devicetree/bindings/mfd/da9062.txt create mode 100644 Documentation/devicetree/bindings/mfd/dlg,da9062.yaml