Re: [PATCH 3/3] mfd: arizona: Remove bindings covered in new subsystem specific docs

[Lee Jones]

On Wed, 14 Oct 2015, Charles Keepax wrote:

> Binding documentation has been added in new subsystem specific binding
> documents. This patch removes the now duplicate documentation from the
> MFD documentation. Also whilst we are at it add a missing maintainers
> entry for the MFD binding document.
> 
> Signed-off-by: Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> ---
>  Documentation/devicetree/bindings/mfd/arizona.txt |   30 ++------------------
>  MAINTAINERS                                       |    1 +
>  2 files changed, 4 insertions(+), 27 deletions(-)

Nice.  For my own reference:

  Acked-by: Lee Jones <lee.jones@xxxxxxxxxx>

Once everyone is happy with the other two patches, I'll pick this.

> diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt b/Documentation/devicetree/bindings/mfd/arizona.txt
> index a8fee60..077c4fe 100644
> --- a/Documentation/devicetree/bindings/mfd/arizona.txt
> +++ b/Documentation/devicetree/bindings/mfd/arizona.txt
> @@ -30,21 +30,9 @@ Required properties:
>    - #gpio-cells : Must be 2. The first cell is the pin number and the
>      second cell is used to specify optional parameters (currently unused).
>  
> -  - AVDD-supply, DBVDD1-supply, CPVDD-supply : Power supplies for the device,
> -    as covered in Documentation/devicetree/bindings/regulator/regulator.txt
> -
> -  - DBVDD2-supply, DBVDD3-supply : Additional databus power supplies (wm5102,
> -    wm5110, wm8280, wm8998, wm1814)
> -
> -  - SPKVDDL-supply, SPKVDDR-supply : Speaker driver power supplies (wm5102,
> -    wm5110, wm8280, wm8998, wm1814)
> -
> -  - SPKVDD-supply : Speaker driver power supply (wm8997)
> -
>  Optional properties:
>  
>    - wlf,reset : GPIO specifier for the GPIO controlling /RESET
> -  - wlf,ldoena : GPIO specifier for the GPIO controlling LDOENA
>  
>    - wlf,gpio-defaults : A list of GPIO configuration register values. Defines
>      for the appropriate values can found in <dt-bindings/mfd/arizona.txt>. If
> @@ -67,21 +55,9 @@ Optional properties:
>      present, the number of values should be less than or equal to the
>      number of inputs, unspecified inputs will use the chip default.
>  
> -  - wlf,hpdet-channel : Headphone detection channel.
> -    ARIZONA_ACCDET_MODE_HPL or 1 - Headphone detect mode is set to HPDETL
> -    ARIZONA_ACCDET_MODE_HPR or 2 - Headphone detect mode is set to HPDETR
> -    If this node is not mentioned or if the value is unknown, then
> -    headphone detection mode is set to HPDETL.
> -
> -  - DCVDD-supply, MICVDD-supply : Power supplies, only need to be specified if
> -    they are being externally supplied. As covered in
> -    Documentation/devicetree/bindings/regulator/regulator.txt
> -
> -Optional subnodes:
> -  - ldo1 : Initial data for the LDO1 regulator, as covered in
> -    Documentation/devicetree/bindings/regulator/regulator.txt
> -  - micvdd : Initial data for the MICVDD regulator, as covered in
> -    Documentation/devicetree/bindings/regulator/regulator.txt
> +Also see child specific device properties:
> +  Regulator - ../regulator/arizona-regulator.txt
> +  Extcon    - ../extcon/extcon-arizona.txt
>  
>  Example:
>  
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f353491..544c747 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11395,6 +11395,7 @@ S:	Supported
>  F:	Documentation/hwmon/wm83??
>  F:	Documentation/devicetree/bindings/extcon/extcon-arizona.txt
>  F:	Documentation/devicetree/bindings/regulator/arizona-regulator.txt
> +F:	Documentation/devicetree/bindings/mfd/arizona.txt
>  F:	arch/arm/mach-s3c64xx/mach-crag6410*
>  F:	drivers/clk/clk-wm83*.c
>  F:	drivers/extcon/extcon-arizona.c

-- 
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 linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/