From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Boris BREZILLON <b.brezillon@overkiz.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Wolfram Sang <wsa@the-dreams.de>,
Wolfram Sang <wsa@the-dreams.de>
Cc: Rob Landley <rob@landley.net>, Arnd Bergmann <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
<devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] i2c: at91: document clock properties
Date: Thu, 19 Dec 2013 16:50:12 +0100 [thread overview]
Message-ID: <52B315B4.6000906@atmel.com> (raw)
In-Reply-To: <1387295644-7382-1-git-send-email-b.brezillon@overkiz.com>
On 17/12/2013 16:54, Boris BREZILLON :
> Document the clock properties required by the at91 i2c bus driver.
>
> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> Documentation/devicetree/bindings/i2c/i2c-at91.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-at91.txt b/Documentation/devicetree/bindings/i2c/i2c-at91.txt
> index b689a0d..4fade84 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-at91.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-at91.txt
> @@ -9,6 +9,7 @@ Required properties :
> - interrupts: interrupt number to the cpu.
> - #address-cells = <1>;
> - #size-cells = <0>;
> +- clocks: phandles to input clocks.
>
> Optional properties:
> - Child nodes conforming to i2c bus binding
> @@ -21,6 +22,7 @@ i2c0: i2c@fff84000 {
> interrupts = <12 4 6>;
> #address-cells = <1>;
> #size-cells = <0>;
> + clocks = <&twi0_clk>;
>
> 24c512@50 {
> compatible = "24c512";
>
--
Nicolas Ferre
next prev parent reply other threads:[~2013-12-19 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 15:54 [PATCH] i2c: at91: document clock properties Boris BREZILLON
2013-12-19 8:02 ` Ludovic Desroches
2013-12-19 15:50 ` Nicolas Ferre [this message]
2014-01-04 22:11 ` Wolfram Sang
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=52B315B4.6000906@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=b.brezillon@overkiz.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=rob@landley.net \
--cc=wsa@the-dreams.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox