From: Stephen Boyd <sboyd@codeaurora.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
mturquette@baylibre.com, cw00.choi@samsung.com,
lee.jones@linaro.org
Cc: myungjoo.ham@samsung.com, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v3 4/4] mfd: arizona: Add device tree binding documentation for new clock driver
Date: Fri, 6 May 2016 17:47:40 -0700 [thread overview]
Message-ID: <572D3B2C.8000304@codeaurora.org> (raw)
In-Reply-To: <1452252582-20834-4-git-send-email-ckeepax@opensource.wolfsonmicro.com>
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@opensource.wolfsonmicro.com>
> Acked-by: Rob Herring <robh@kernel.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
next prev parent reply other threads:[~2016-05-07 0:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 11:29 [PATCH v3 1/4] extcon: arizona: Remove enable/disable of 32k clock Charles Keepax
2016-01-08 11:29 ` Charles Keepax
2016-01-08 11:29 ` [PATCH v3 2/4] clk: arizona: Add clock driver for the Arizona devices Charles Keepax
2016-01-08 11:29 ` Charles Keepax
2016-05-07 0:55 ` Stephen Boyd
2016-05-07 0:55 ` Stephen Boyd
2016-05-09 10:47 ` Charles Keepax
2016-05-09 10:47 ` Charles Keepax
2016-05-09 21:48 ` Stephen Boyd
2016-05-10 9:58 ` Charles Keepax
2016-05-10 9:58 ` Charles Keepax
2016-01-08 11:29 ` [PATCH v3 3/4] mfd: arizona: Switch to using clock driver for 32k clock Charles Keepax
2016-01-08 11:29 ` Charles Keepax
2016-01-11 10:25 ` Lee Jones
2016-01-11 11:03 ` Charles Keepax
2016-01-11 11:03 ` Charles Keepax
2016-05-07 0:55 ` Stephen Boyd
2016-05-09 7:44 ` Lee Jones
2016-05-09 19:34 ` Stephen Boyd
2016-05-10 7:41 ` Lee Jones
2016-01-08 11:29 ` [PATCH v3 4/4] mfd: arizona: Add device tree binding documentation for new clock driver Charles Keepax
2016-01-08 11:29 ` Charles Keepax
2016-01-11 10:23 ` Lee Jones
2016-05-07 0:47 ` Stephen Boyd [this message]
2016-05-07 0:49 ` Stephen Boyd
2016-01-25 6:24 ` [PATCH v3 1/4] extcon: arizona: Remove enable/disable of 32k clock Chanwoo Choi
2016-01-25 6:24 ` Chanwoo Choi
2016-05-07 0:50 ` Stephen Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=572D3B2C.8000304@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.