[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <572D3B2C.8000304@codeaurora.org>
Date: Fri, 6 May 2016 17:47:40 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>,
mturquette@...libre.com, cw00.choi@...sung.com,
lee.jones@...aro.org
Cc: myungjoo.ham@...sung.com, devicetree@...r.kernel.org,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH v3 4/4] mfd: arizona: Add device tree binding
documentation for new clock driver
On 01/08/2016 03:29 AM, Charles Keepax wrote:
> Specify the device tree binding for the input clocks to Arizona devices.
>
> Signed-off-by: Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
> Acked-by: Rob Herring <robh@...nel.org>
> ---
>
> No changes since v2.
>
> Thanks,
> Charles
>
> Documentation/devicetree/bindings/mfd/arizona.txt | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt b/Documentation/devicetree/bindings/mfd/arizona.txt
> index 18be0cb..39f76f8 100644
> --- a/Documentation/devicetree/bindings/mfd/arizona.txt
> +++ b/Documentation/devicetree/bindings/mfd/arizona.txt
> @@ -45,6 +45,13 @@ Optional properties:
>
> - wlf,reset : GPIO specifier for the GPIO controlling /RESET
>
> + - clocks: Should reference the clocks supplied on MCLK1 and MCLK2
> + - clock-names: Should contains two strings:
Can't this be clock-output-names instead? That's standard and already
accepted per clock-bindings.txt
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
Powered by blists - more mailing lists