From: Lee Jones <lee.jones@linaro.org>
To: Tony Xie <tony.xie@rock-chips.com>
Cc: heiko@sntech.de, broonie@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, a.zummo@towertech.it,
alexandre.belloni@bootlin.com, sboyd@kernel.org,
linux-clk@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, chenjh@rock-chips.com,
xsf@rock-chips.com, zhangqing@rock-chips.com,
huangtao@rock-chips.com
Subject: Re: [PATCH v5 3/5] dt-bindings: mfd: rk808: Add binding information for RK809 and RK817.
Date: Thu, 25 Oct 2018 10:38:27 +0100 [thread overview]
Message-ID: <20181025093827.GP4939@dell> (raw)
In-Reply-To: <1540294467-25813-4-git-send-email-tony.xie@rock-chips.com>
On Tue, 23 Oct 2018, Tony Xie wrote:
> Add device tree bindings documentation for Rockchip's RK809 & RK817 PMIC.
>
> Signed-off-by: Tony Xie <tony.xie@rock-chips.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/mfd/rk808.txt | 44 +++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/rk808.txt b/Documentation/devicetree/bindings/mfd/rk808.txt
> index 91b6522..d575780 100644
> --- a/Documentation/devicetree/bindings/mfd/rk808.txt
> +++ b/Documentation/devicetree/bindings/mfd/rk808.txt
> @@ -3,11 +3,15 @@ RK8XX Power Management Integrated Circuit
> The rk8xx family current members:
> rk805
> rk808
> +rk809
> +rk817
> rk818
>
> Required properties:
> - compatible: "rockchip,rk805"
> - compatible: "rockchip,rk808"
> +- compatible: "rockchip,rk809"
> +- compatible: "rockchip,rk817"
> - compatible: "rockchip,rk818"
> - reg: I2C slave address
> - interrupt-parent: The parent interrupt controller.
> @@ -46,6 +50,23 @@ Optional RK808 properties:
> the gpio controller. If DVS GPIOs aren't present, voltage changes will happen
> very quickly with no slow ramp time.
>
> +Optional shared RK809 and RK817 properties:
> +- vcc1-supply: The input supply for DCDC_REG1
> +- vcc2-supply: The input supply for DCDC_REG2
> +- vcc3-supply: The input supply for DCDC_REG3
> +- vcc4-supply: The input supply for DCDC_REG4
> +- vcc5-supply: The input supply for LDO_REG1, LDO_REG2, LDO_REG3
> +- vcc6-supply: The input supply for LDO_REG4, LDO_REG5, LDO_REG6
> +- vcc7-supply: The input supply for LDO_REG7, LDO_REG8, LDO_REG9
> +
> +Optional RK809 properties:
> +- vcc8-supply: The input supply for SWITCH_REG1
> +- vcc9-supply: The input supply for DCDC_REG5, SWITCH_REG2
> +
> +Optional RK817 properties:
> +- vcc8-supply: The input supply for BOOST
> +- vcc9-supply: The input supply for OTG_SWITCH
> +
> Optional RK818 properties:
> - vcc1-supply: The input supply for DCDC_REG1
> - vcc2-supply: The input supply for DCDC_REG2
> @@ -87,6 +108,21 @@ number as described in RK808 datasheet.
> - SWITCH_REGn
> - valid values for n are 1 to 2
>
> +Following regulators of the RK809 and RK817 PMIC blocks are supported. Note that
> +the 'n' in regulator name, as in DCDC_REGn or LDOn, represents the DCDC or LDO
> +number as described in RK809 and RK817 datasheets.
> +
> + - DCDC_REGn
> + - valid values for n are 1 to 5 for RK809.
> + - valid values for n are 1 to 4 for RK817.
> + - LDO_REGn
> + - valid values for n are 1 to 9 for RK809.
> + - valid values for n are 1 to 9 for RK817.
> + - SWITCH_REGn
> + - valid values for n are 1 to 2 for RK809.
> + - BOOST for RK817
> + - OTG_SWITCH for RK817
> +
> Following regulators of the RK818 PMIC block are supported. Note that
> the 'n' in regulator name, as in DCDC_REGn or LDOn, represents the DCDC or LDO
> number as described in RK818 datasheet.
> @@ -99,6 +135,14 @@ number as described in RK818 datasheet.
> - HDMI_SWITCH
> - OTG_SWITCH
>
> +There are three pins needed to config for each of RK809 and RK817,
Nit: "configure" in full please.
Actually: "It is necessary to configure three pins for both the RK809 and RK817"
> +named "gpio_ts" "gpio_gt" "gpio_slp".
> + The gpio_gt and gpio_ts pins support the gpio function.
> + The gpio_slp pin is for controlling the pmic states, as below:
> + - reset
> + - power down
> + - sleep
> +
> Standard regulator bindings are used inside regulator subnodes. Check
> Documentation/devicetree/bindings/regulator/regulator.txt
> for more details
Once that's fixed, please apply my:
For my own reference:
Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 3/5] dt-bindings: mfd: rk808: Add binding information for RK809 and RK817.
Date: Thu, 25 Oct 2018 10:38:27 +0100 [thread overview]
Message-ID: <20181025093827.GP4939@dell> (raw)
In-Reply-To: <1540294467-25813-4-git-send-email-tony.xie@rock-chips.com>
On Tue, 23 Oct 2018, Tony Xie wrote:
> Add device tree bindings documentation for Rockchip's RK809 & RK817 PMIC.
>
> Signed-off-by: Tony Xie <tony.xie@rock-chips.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> Documentation/devicetree/bindings/mfd/rk808.txt | 44 +++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/rk808.txt b/Documentation/devicetree/bindings/mfd/rk808.txt
> index 91b6522..d575780 100644
> --- a/Documentation/devicetree/bindings/mfd/rk808.txt
> +++ b/Documentation/devicetree/bindings/mfd/rk808.txt
> @@ -3,11 +3,15 @@ RK8XX Power Management Integrated Circuit
> The rk8xx family current members:
> rk805
> rk808
> +rk809
> +rk817
> rk818
>
> Required properties:
> - compatible: "rockchip,rk805"
> - compatible: "rockchip,rk808"
> +- compatible: "rockchip,rk809"
> +- compatible: "rockchip,rk817"
> - compatible: "rockchip,rk818"
> - reg: I2C slave address
> - interrupt-parent: The parent interrupt controller.
> @@ -46,6 +50,23 @@ Optional RK808 properties:
> the gpio controller. If DVS GPIOs aren't present, voltage changes will happen
> very quickly with no slow ramp time.
>
> +Optional shared RK809 and RK817 properties:
> +- vcc1-supply: The input supply for DCDC_REG1
> +- vcc2-supply: The input supply for DCDC_REG2
> +- vcc3-supply: The input supply for DCDC_REG3
> +- vcc4-supply: The input supply for DCDC_REG4
> +- vcc5-supply: The input supply for LDO_REG1, LDO_REG2, LDO_REG3
> +- vcc6-supply: The input supply for LDO_REG4, LDO_REG5, LDO_REG6
> +- vcc7-supply: The input supply for LDO_REG7, LDO_REG8, LDO_REG9
> +
> +Optional RK809 properties:
> +- vcc8-supply: The input supply for SWITCH_REG1
> +- vcc9-supply: The input supply for DCDC_REG5, SWITCH_REG2
> +
> +Optional RK817 properties:
> +- vcc8-supply: The input supply for BOOST
> +- vcc9-supply: The input supply for OTG_SWITCH
> +
> Optional RK818 properties:
> - vcc1-supply: The input supply for DCDC_REG1
> - vcc2-supply: The input supply for DCDC_REG2
> @@ -87,6 +108,21 @@ number as described in RK808 datasheet.
> - SWITCH_REGn
> - valid values for n are 1 to 2
>
> +Following regulators of the RK809 and RK817 PMIC blocks are supported. Note that
> +the 'n' in regulator name, as in DCDC_REGn or LDOn, represents the DCDC or LDO
> +number as described in RK809 and RK817 datasheets.
> +
> + - DCDC_REGn
> + - valid values for n are 1 to 5 for RK809.
> + - valid values for n are 1 to 4 for RK817.
> + - LDO_REGn
> + - valid values for n are 1 to 9 for RK809.
> + - valid values for n are 1 to 9 for RK817.
> + - SWITCH_REGn
> + - valid values for n are 1 to 2 for RK809.
> + - BOOST for RK817
> + - OTG_SWITCH for RK817
> +
> Following regulators of the RK818 PMIC block are supported. Note that
> the 'n' in regulator name, as in DCDC_REGn or LDOn, represents the DCDC or LDO
> number as described in RK818 datasheet.
> @@ -99,6 +135,14 @@ number as described in RK818 datasheet.
> - HDMI_SWITCH
> - OTG_SWITCH
>
> +There are three pins needed to config for each of RK809 and RK817,
Nit: "configure" in full please.
Actually: "It is necessary to configure three pins for both the RK809 and RK817"
> +named "gpio_ts" "gpio_gt" "gpio_slp".
> + The gpio_gt and gpio_ts pins support the gpio function.
> + The gpio_slp pin is for controlling the pmic states, as below:
> + - reset
> + - power down
> + - sleep
> +
> Standard regulator bindings are used inside regulator subnodes. Check
> Documentation/devicetree/bindings/regulator/regulator.txt
> for more details
Once that's fixed, please apply my:
For my own reference:
Acked-for-MFD-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [???]
Linaro Services Technical Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2018-10-25 9:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 11:34 [PATCH v5 0/5] support a new type of PMIC,including two chips(rk817 and rk809) Tony Xie
2018-10-23 11:34 ` [PATCH v5 0/5] support a new type of PMIC, including " Tony Xie
2018-10-23 11:34 ` [PATCH v5 1/5] mfd: rk808: Add RK817 and RK809 support Tony Xie
2018-10-23 11:34 ` Tony Xie
2018-10-25 9:33 ` Lee Jones
2018-10-25 9:33 ` Lee Jones
2018-10-23 11:34 ` [PATCH v5 2/5] regulator: rk808: add RK809 and RK817 support Tony Xie
2018-10-23 11:34 ` Tony Xie
2018-10-25 9:36 ` Lee Jones
2018-10-25 9:36 ` Lee Jones
2018-10-23 11:34 ` [PATCH v5 3/5] dt-bindings: mfd: rk808: Add binding information for RK809 and RK817 Tony Xie
2018-10-23 11:34 ` Tony Xie
2018-10-25 9:38 ` Lee Jones [this message]
2018-10-25 9:38 ` Lee Jones
2018-10-23 11:34 ` [PATCH v5 4/5] rtc: rk808: add RK809 and RK817 support Tony Xie
2018-10-23 11:34 ` Tony Xie
2018-10-23 11:36 ` [PATCH v5 5/5] clk: RK808: " Tony Xie
2018-10-23 11:36 ` Tony Xie
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=20181025093827.GP4939@dell \
--to=lee.jones@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=chenjh@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tony.xie@rock-chips.com \
--cc=xsf@rock-chips.com \
--cc=zhangqing@rock-chips.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: link
Be 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.