From: "Andreas Färber" <afaerber@suse.de> To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, Lee Jones <lee.jones@linaro.org> Cc: Samuel Ortiz <sameo@linux.intel.com>, Mark Brown <broonie@kernel.org>, Mike Turquette <mturquette@linaro.org>, Liam Girdwood <lgirdwood@gmail.com>, Alessandro Zummo <a.zummo@towertech.it>, Kukjin Kim <kgene.kim@samsung.com>, Doug Anderson <dianders@chromium.org>, Olof Johansson <olof@lixom.net>, Sjoerd Simons <sjoerd.simons@collabora.co.uk>, Daniel Stone <daniels@collabora.com>, Tomeu Vizoso <tomeu.vizoso@collabora.com>, Krzysztof Kozlowski <k.kozlowski@samsung.com>, Yadwinder Singh Brar <yadi.brar01@gmail.com>, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v5 08/14] mfd: max77802: Add DT binding documentation Date: Fri, 27 Jun 2014 10:06:14 +0200 [thread overview] Message-ID: <53AD25F6.6030007@suse.de> (raw) In-Reply-To: <1403806546-31122-9-git-send-email-javier.martinez@collabora.co.uk> Am 26.06.2014 20:15, schrieb Javier Martinez Canillas: > Add Device Tree binding documentation for Maxim 77802 PMIC. > > Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk> > --- > > Changes since v4: None > > Changes since v3: None > > Changes since v2: > - Explain better the Dynamic Voltage Scaling (DVS) support in some Buck > regulators and the max77802,pmic-buck-{dvs,selb}-gpios properties. > Suggested by Mark Brown. > > Documentation/devicetree/bindings/mfd/max77802.txt | 97 ++++++++++++++++++++++ > 1 file changed, 97 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mfd/max77802.txt > > diff --git a/Documentation/devicetree/bindings/mfd/max77802.txt b/Documentation/devicetree/bindings/mfd/max77802.txt > new file mode 100644 > index 0000000..f3b67c5 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/max77802.txt > @@ -0,0 +1,97 @@ > +Maxim MAX77802 multi-function device > + > +MAX77802 is a Mulitifunction device with PMIC, RTC and Charger on chip. It is "Multifunction"? > +interfaced to host controller using i2c interface. PMIC, Charger and RTC > +submodules are addressed using same i2c slave address. > + > +Buck regulators 1, 2, 3, 4 and 6 include Dynamic Voltage Scaling (DVS) that > +allows each output voltage to change dynamically. Each Buck output voltage > +is selected using a set of external inputs: DVS1-3 and SELB1, 2, 3 and 6. > + > +There are 8 DVS registers that can be used to configure the output voltage > +for each Buck regulator and which one is active is controled by DVSx lines. > + > +SELBx lines are used to control if individual Buck lines are ON or OFF. > + > +This document describes the binding for mfd device and PMIC submodule. > + > +Binding for the built-in 32k clock generator block is defined separately > +in bindings/clk/maxim,max77802.txt file. > + > +Required properties: > +- compatible : Must be "maxim,max77802"; > +- reg : Specifies the i2c slave address of PMIC block. > +- interrupts : This i2c device has an IRQ line connected to the main SoC. > +- interrupt-parent : The parent interrupt controller. > + > +Optional properties: > +- max77802,pmic-buck-default-dvs-idx: We'll always write this DVS index in the > + PMIC for Bucks with DVS. > + NOTE: at the moment these bindings don't include enough details for actual > + GPIO-DVS--this just lets you choose which single slot to use. > + > +- max77802,pmic-buck-dvs-gpios: A GPIO array where each GPIO is connected to a > + DVS line. We'll try to set these GPIOs to match pmic-buck-default-dvs-idx at > + probe time if they are defined. If some or all of these GPIOs are not defined > + it's assumed that the board has any missing GPIOs hardwired to match > + pmic-buck-default-dvs-idx. > + > +- max77802,pmic-buck-selb-gpios: A GPIO array where each GPIO is connected to a > + SELBx line. Should be five values: 1, 2, 3, 4, 6. It is strongly suggested to > + include these GPIOs if there's any chance that changing DVS GPIOs one line at > + a time might glitch your DVS values. > + > +Optional node: > +- regulators : The regulators of max77802 have to be instantiated > + under subnode named "regulators" using the following format. > + > + regulator_name { The convention, I was told, would be regulator-name as node name. > + standard regulator constraints.... > + }; > + refer Documentation/devicetree/bindings/regulator/regulator.txt > + > + The regulator node name should be initialized with a string > +to get matched with their hardware counterparts as follow: > + > + -LDOn : for LDOs, where n can lie in range 1 to 35. > + example: LDO1, LDO2, LDO35. > + -BUCKn : for BUCKs, where n can lie in range 1 to 10. > + example: BUCK1, BUCK5, BUCK10. > +Example: > + > + max77802@09 { > + compatible = "maxim,max77802"; > + interrupt-parent = <&wakeup_eint>; > + interrupts = <26 0>; > + reg = <0x09>; > + #address-cells = <1>; > + #size-cells = <0>; > + > + max77802,pmic-buck-default-dvs-idx = <1>; > + max77802,pmic-buck-dvs-gpios = <&gpy7 6 0>, > + <&gpj4 2 0>, > + <&gpj4 3 0>; > + max77802,pmic-buck-selb-gpios = <&gph0 2 0>, > + <&gph0 3 0>, > + <&gph0 4 0>, > + <&gph0 5 0>, > + <&gph0 6 0>; > + > + regulators { > + ldo11_reg: LDO11 { > + regulator-compatible = "LDO11"; > + regulator-name = "vdd_ldo11"; > + regulator-min-microvolt = <1900000>; > + regulator-max-microvolt = <1900000>; > + regulator-always-on; > + }; > + > + buck1_reg { Missing ": BUCK1" > + regulator-compatible = "BUCK1"; > + regulator-name = "vdd_mif"; > + regulator-min-microvolt = <950000>; > + regulator-max-microvolt = <1300000>; > + regulator-always-on; > + regulator-boot-on; > + }; > + }; Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
WARNING: multiple messages have this Message-ID (diff)
From: afaerber@suse.de (Andreas Färber) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v5 08/14] mfd: max77802: Add DT binding documentation Date: Fri, 27 Jun 2014 10:06:14 +0200 [thread overview] Message-ID: <53AD25F6.6030007@suse.de> (raw) In-Reply-To: <1403806546-31122-9-git-send-email-javier.martinez@collabora.co.uk> Am 26.06.2014 20:15, schrieb Javier Martinez Canillas: > Add Device Tree binding documentation for Maxim 77802 PMIC. > > Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk> > --- > > Changes since v4: None > > Changes since v3: None > > Changes since v2: > - Explain better the Dynamic Voltage Scaling (DVS) support in some Buck > regulators and the max77802,pmic-buck-{dvs,selb}-gpios properties. > Suggested by Mark Brown. > > Documentation/devicetree/bindings/mfd/max77802.txt | 97 ++++++++++++++++++++++ > 1 file changed, 97 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mfd/max77802.txt > > diff --git a/Documentation/devicetree/bindings/mfd/max77802.txt b/Documentation/devicetree/bindings/mfd/max77802.txt > new file mode 100644 > index 0000000..f3b67c5 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mfd/max77802.txt > @@ -0,0 +1,97 @@ > +Maxim MAX77802 multi-function device > + > +MAX77802 is a Mulitifunction device with PMIC, RTC and Charger on chip. It is "Multifunction"? > +interfaced to host controller using i2c interface. PMIC, Charger and RTC > +submodules are addressed using same i2c slave address. > + > +Buck regulators 1, 2, 3, 4 and 6 include Dynamic Voltage Scaling (DVS) that > +allows each output voltage to change dynamically. Each Buck output voltage > +is selected using a set of external inputs: DVS1-3 and SELB1, 2, 3 and 6. > + > +There are 8 DVS registers that can be used to configure the output voltage > +for each Buck regulator and which one is active is controled by DVSx lines. > + > +SELBx lines are used to control if individual Buck lines are ON or OFF. > + > +This document describes the binding for mfd device and PMIC submodule. > + > +Binding for the built-in 32k clock generator block is defined separately > +in bindings/clk/maxim,max77802.txt file. > + > +Required properties: > +- compatible : Must be "maxim,max77802"; > +- reg : Specifies the i2c slave address of PMIC block. > +- interrupts : This i2c device has an IRQ line connected to the main SoC. > +- interrupt-parent : The parent interrupt controller. > + > +Optional properties: > +- max77802,pmic-buck-default-dvs-idx: We'll always write this DVS index in the > + PMIC for Bucks with DVS. > + NOTE: at the moment these bindings don't include enough details for actual > + GPIO-DVS--this just lets you choose which single slot to use. > + > +- max77802,pmic-buck-dvs-gpios: A GPIO array where each GPIO is connected to a > + DVS line. We'll try to set these GPIOs to match pmic-buck-default-dvs-idx at > + probe time if they are defined. If some or all of these GPIOs are not defined > + it's assumed that the board has any missing GPIOs hardwired to match > + pmic-buck-default-dvs-idx. > + > +- max77802,pmic-buck-selb-gpios: A GPIO array where each GPIO is connected to a > + SELBx line. Should be five values: 1, 2, 3, 4, 6. It is strongly suggested to > + include these GPIOs if there's any chance that changing DVS GPIOs one line at > + a time might glitch your DVS values. > + > +Optional node: > +- regulators : The regulators of max77802 have to be instantiated > + under subnode named "regulators" using the following format. > + > + regulator_name { The convention, I was told, would be regulator-name as node name. > + standard regulator constraints.... > + }; > + refer Documentation/devicetree/bindings/regulator/regulator.txt > + > + The regulator node name should be initialized with a string > +to get matched with their hardware counterparts as follow: > + > + -LDOn : for LDOs, where n can lie in range 1 to 35. > + example: LDO1, LDO2, LDO35. > + -BUCKn : for BUCKs, where n can lie in range 1 to 10. > + example: BUCK1, BUCK5, BUCK10. > +Example: > + > + max77802 at 09 { > + compatible = "maxim,max77802"; > + interrupt-parent = <&wakeup_eint>; > + interrupts = <26 0>; > + reg = <0x09>; > + #address-cells = <1>; > + #size-cells = <0>; > + > + max77802,pmic-buck-default-dvs-idx = <1>; > + max77802,pmic-buck-dvs-gpios = <&gpy7 6 0>, > + <&gpj4 2 0>, > + <&gpj4 3 0>; > + max77802,pmic-buck-selb-gpios = <&gph0 2 0>, > + <&gph0 3 0>, > + <&gph0 4 0>, > + <&gph0 5 0>, > + <&gph0 6 0>; > + > + regulators { > + ldo11_reg: LDO11 { > + regulator-compatible = "LDO11"; > + regulator-name = "vdd_ldo11"; > + regulator-min-microvolt = <1900000>; > + regulator-max-microvolt = <1900000>; > + regulator-always-on; > + }; > + > + buck1_reg { Missing ": BUCK1" > + regulator-compatible = "BUCK1"; > + regulator-name = "vdd_mif"; > + regulator-min-microvolt = <950000>; > + regulator-max-microvolt = <1300000>; > + regulator-always-on; > + regulator-boot-on; > + }; > + }; Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer; HRB 16746 AG N?rnberg
next prev parent reply other threads:[~2014-06-27 8:06 UTC|newest] Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-26 18:15 [PATCH v5 00/14] Add Maxim 77802 PMIC support Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 01/14] mfd: max77686: Convert to use regmap_irq Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 02/14] mfd: max77686: Allow the max77686 rtc to wakeup the system Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-27 9:21 ` Lee Jones 2014-06-27 9:21 ` Lee Jones 2014-06-27 9:32 ` Javier Martinez Canillas 2014-06-27 9:32 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 03/14] clk: max77686: Add DT include for MAX77686 PMIC clock Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-27 7:48 ` Andreas Färber 2014-06-27 7:48 ` Andreas Färber 2014-06-27 7:53 ` Javier Martinez Canillas 2014-06-27 7:53 ` Javier Martinez Canillas 2014-06-27 8:26 ` Andreas Färber 2014-06-27 8:26 ` Andreas Färber 2014-06-27 8:54 ` Javier Martinez Canillas 2014-06-27 8:54 ` Javier Martinez Canillas 2014-06-27 8:54 ` Javier Martinez Canillas 2014-07-01 17:30 ` Mike Turquette 2014-07-01 17:30 ` Mike Turquette 2014-07-01 17:30 ` Mike Turquette 2014-06-26 18:15 ` [PATCH v5 04/14] clk: max77686: Improve Maxim 77686 PMIC clocks binding Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-07-01 17:29 ` Mike Turquette 2014-07-01 17:29 ` Mike Turquette 2014-07-01 17:29 ` Mike Turquette 2014-07-02 10:17 ` Javier Martinez Canillas 2014-07-02 10:17 ` Javier Martinez Canillas 2014-07-02 15:21 ` Mike Turquette 2014-07-02 15:21 ` Mike Turquette 2014-06-26 18:15 ` [PATCH v5 05/14] clk: Add generic driver for Maxim PMIC clocks Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-30 4:01 ` Yadwinder Singh Brar 2014-06-30 4:01 ` Yadwinder Singh Brar 2014-06-30 4:01 ` Yadwinder Singh Brar 2014-06-30 10:58 ` Javier Martinez Canillas 2014-06-30 10:58 ` Javier Martinez Canillas 2014-06-30 10:58 ` Javier Martinez Canillas 2014-06-30 11:35 ` Russell King - ARM Linux 2014-06-30 11:35 ` Russell King - ARM Linux 2014-06-30 11:35 ` Russell King - ARM Linux 2014-06-30 16:00 ` Javier Martinez Canillas 2014-06-30 16:00 ` Javier Martinez Canillas 2014-06-30 16:00 ` Javier Martinez Canillas 2014-07-01 17:26 ` Mike Turquette 2014-07-01 17:26 ` Mike Turquette 2014-07-01 17:26 ` Mike Turquette 2014-07-02 10:13 ` Javier Martinez Canillas 2014-07-02 10:13 ` Javier Martinez Canillas 2014-07-02 10:13 ` Javier Martinez Canillas 2014-07-02 10:19 ` Krzysztof Kozlowski 2014-07-02 10:19 ` Krzysztof Kozlowski 2014-07-02 10:19 ` Krzysztof Kozlowski 2014-06-26 18:15 ` [PATCH v5 06/14] clk: max77686: Convert to the generic max clock driver Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 07/14] mfd: Add driver for Maxim 77802 Power Management IC Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-07-01 15:15 ` Lee Jones 2014-07-01 15:15 ` Lee Jones 2014-07-01 15:55 ` Javier Martinez Canillas 2014-07-01 15:55 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 08/14] mfd: max77802: Add DT binding documentation Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-27 8:06 ` Andreas Färber [this message] 2014-06-27 8:06 ` Andreas Färber 2014-06-27 8:50 ` Javier Martinez Canillas 2014-06-27 8:50 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 09/14] regmap: Add regmap_reg_copy function Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 10/14] regulator: Add driver for Maxim 77802 PMIC regulators Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-27 9:26 ` Lee Jones 2014-06-27 9:26 ` Lee Jones 2014-06-27 9:42 ` Javier Martinez Canillas 2014-06-27 9:42 ` Javier Martinez Canillas 2014-06-27 9:42 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 11/14] clk: Add driver for Maxim 77802 PMIC clocks Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 12/14] clk: max77802: Add DT binding documentation Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-27 7:52 ` Andreas Färber 2014-06-27 7:52 ` Andreas Färber 2014-06-27 7:52 ` Andreas Färber 2014-06-27 7:55 ` Javier Martinez Canillas 2014-06-27 7:55 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 13/14] rtc: Add driver for Maxim 77802 PMIC Real-Time-Clock Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-06-26 18:15 ` [PATCH v5 14/14] ARM: dts: Add max77802 to exynos5420-peach-pit and exynos5800-peach-pi Javier Martinez Canillas 2014-06-26 18:15 ` Javier Martinez Canillas 2014-07-02 9:20 ` Tushar Behera 2014-07-02 9:20 ` Tushar Behera 2014-07-02 9:22 ` Javier Martinez Canillas 2014-07-02 9:22 ` Javier Martinez Canillas
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=53AD25F6.6030007@suse.de \ --to=afaerber@suse.de \ --cc=a.zummo@towertech.it \ --cc=broonie@kernel.org \ --cc=daniels@collabora.com \ --cc=devicetree@vger.kernel.org \ --cc=dianders@chromium.org \ --cc=javier.martinez@collabora.co.uk \ --cc=k.kozlowski@samsung.com \ --cc=kgene.kim@samsung.com \ --cc=lee.jones@linaro.org \ --cc=lgirdwood@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=mturquette@linaro.org \ --cc=olof@lixom.net \ --cc=sameo@linux.intel.com \ --cc=sjoerd.simons@collabora.co.uk \ --cc=tomeu.vizoso@collabora.com \ --cc=yadi.brar01@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.