linux-kernel - Re: [PATCH v3 3/4] mfd: arizona: Remove bindings covered in new subsystem specific docs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151028090306.GJ5828@x1>
Date:	Wed, 28 Oct 2015 09:03:06 +0000
From:	Lee Jones <lee.jones@...aro.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	broonie@...nel.org, cw00.choi@...sung.com,
	myungjoo.ham@...sung.com, lgirdwood@...il.com,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH v3 3/4] mfd: arizona: Remove bindings covered in new
 subsystem specific docs

On Tue, 27 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.
> 
> Signed-off-by: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
> ---
> 
> Changes since v2:
>  - No longer moving the core regulators into the regulator binding document,
>    as they are properties of the device as a whole not just the regulators
>  - Moved the maintainer updates into a seperate patch
> 
> Lee, I have removed your ack because the patch has changed a fair amount.
> Apologies if this would not have been your preference.

That was the right thing to do.

> Thanks,
> Charles
> 
>  Documentation/devicetree/bindings/mfd/arizona.txt |   15 +++------------
>  1 files changed, 3 insertions(+), 12 deletions(-)

Applied, thanks.

> diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt b/Documentation/devicetree/bindings/mfd/arizona.txt
> index a8fee60..18be0cb 100644
> --- a/Documentation/devicetree/bindings/mfd/arizona.txt
> +++ b/Documentation/devicetree/bindings/mfd/arizona.txt
> @@ -44,7 +44,6 @@ Required properties:
>  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 +66,13 @@ 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:
>  

-- 
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/