On Sat, 30 Aug 2014, Beniamino Galvani wrote:
> This adds the device tree bindings documentation for Ricoh RN5T618.
>
> Signed-off-by: Beniamino Galvani <b.galvani@xxxxxxxxx>
> Reviewed-by: Mark Brown <broonie@xxxxxxxxxx>
> ---
> Documentation/devicetree/bindings/mfd/rn5t618.txt | 36 +++++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/rn5t618.txt
Whoops, should have replied to this one instead of the other one
twice.
Applied, thanks.
> diff --git a/Documentation/devicetree/bindings/mfd/rn5t618.txt b/Documentation/devicetree/bindings/mfd/rn5t618.txt
> new file mode 100644
> index 0000000..937785a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/rn5t618.txt
> @@ -0,0 +1,36 @@
> +* Ricoh RN5T618 PMIC
> +
> +Ricoh RN5T618 is a power management IC which integrates 3 step-down
> +DCDC converters, 7 low-dropout regulators, a Li-ion battery charger,
> +fuel gauge, ADC, GPIOs and a watchdog timer. It can be controlled
> +through a I2C interface.
> +
> +Required properties:
> + - compatible: should be "ricoh,rn5t618"
> + - reg: the I2C slave address of the device
> +
> +Sub-nodes:
> + - regulators: the node is required if the regulator functionality is
> + needed. The valid regulator names are: DCDC1, DCDC2, DCDC3, LDO1,
> + LDO2, LDO3, LDO4, LDO5, LDORTC1 and LDORTC2.
> + The common bindings for each individual regulator can be found in:
> + Documentation/devicetree/bindings/regulator/regulator.txt
> +
> +Example:
> +
> + pmic@32 {
> + compatible = "ricoh,rn5t618";
> + reg = <0x32>;
> +
> + regulators {
> + DCDC1 {
> + regulator-min-microvolt = <1050000>;
> + regulator-max-microvolt = <1050000>;
> + };
> +
> + DCDC2 {
> + regulator-min-microvolt = <1175000>;
> + regulator-max-microvolt = <1175000>;
> + };
> + };
> + };
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
