Re: [PATCH v3 1/4] extcon: arizona: Add extcon specific device tree binding document

From: Lee Jones
Date: Wed Oct 28 2015 - 05:19:23 EST


On Tue, 27 Oct 2015, Charles Keepax wrote:

> Subsystem specific bindings for the Arizona devices are being factored
> out of the MFD binding document into separate documents for each
> subsystem. This patch adds a binding document that covers the existing
> extcon specific bindings.
>
> Signed-off-by: Charles Keepax <ckeepax@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Acked-by: Chanwoo Choi <cw00.choi@xxxxxxxxxxx>
> ---
>
> Changes since v2:
> - Moved the maintainer updates into a separate patch
>
> Thanks,
> Charles
>
> .../devicetree/bindings/extcon/extcon-arizona.txt | 15 +++++++++++++++
> 1 files changed, 15 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/extcon/extcon-arizona.txt

Replied on Chanwoo's request.

> diff --git a/Documentation/devicetree/bindings/extcon/extcon-arizona.txt b/Documentation/devicetree/bindings/extcon/extcon-arizona.txt
> new file mode 100644
> index 0000000..e1705fa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/extcon/extcon-arizona.txt
> @@ -0,0 +1,15 @@
> +Cirrus Logic Arizona class audio SoCs
> +
> +These devices are audio SoCs with extensive digital capabilities and a range
> +of analogue I/O.
> +
> +This document lists Extcon specific bindings, see the primary binding document:
> + ../mfd/arizona.txt
> +
> +Optional properties:
> +
> + - 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.

--
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/