From: Lee Jones <lee.jones@linaro.org>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Cc: dbaryshkov@gmail.com, dwmw2@infradead.org,
santosh.shilimkar@ti.com, arnd@arndb.de, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
grant.likely@linaro.org, rdunlap@infradead.org,
mturquette@linaro.org, linux@arm.linux.org.uk,
grygorii.strashko@ti.com, olof@lixom.net, w-kwok2@ti.com,
sboyd@codeaurora.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, m-karicheri2@ti.com,
sergei.shtylyov@cogentembedded.com
Subject: Re: [Patch v7 3/7] mfd: ti-keystone-devctrl: add bindings for device state control
Date: Tue, 27 May 2014 10:24:28 +0100 [thread overview]
Message-ID: <20140527092428.GH5875@lee--X1> (raw)
In-Reply-To: <1400859812-5761-4-git-send-email-ivan.khoronzhuk@ti.com>
> The Keystone II devices have a set of registers that are used to control
> the status of its peripherals. This node is intended to allow access to
> this functionality.
>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Acked-by: Lee Jones <lee.jones@linaro.org>
> ---
> .../devicetree/bindings/mfd/ti-keystone-devctrl.txt | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt
>
> diff --git a/Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt b/Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt
> new file mode 100644
> index 0000000..20963c7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt
> @@ -0,0 +1,19 @@
> +* Device tree bindings for Texas Instruments keystone device state control
> +
> +The Keystone II devices have a set of registers that are used to control
> +the status of its peripherals. This node is intended to allow access to
> +this functionality.
> +
> +Required properties:
> +
> +- compatible: "ti,keystone-devctrl", "syscon"
> +
> +- reg: contains offset/length value for device state control
> + registers space.
> +
> +Example:
> +
> +devctrl: device-state-control@0x02620000 {
> + compatible = "ti,keystone-devctrl", "syscon";
> + reg = <0x02620000 0x1000>;
> +};
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-05-27 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 15:43 [Patch v7 0/7] Introduce keystone reset driver Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 1/7] power: reset: keystone-reset: introduce " Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 2/7] clock: keystone-pllctrl: add bindings for keystone pll controller Ivan Khoronzhuk
2014-05-23 18:32 ` Mike Turquette
2014-05-23 18:35 ` Santosh Shilimkar
2014-05-23 18:41 ` Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 3/7] mfd: ti-keystone-devctrl: add bindings for device state control Ivan Khoronzhuk
2014-05-27 9:24 ` Lee Jones [this message]
2014-05-23 15:43 ` [Patch v7 4/7] power: reset: add bindings for keystone reset driver Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 5/7] ARM: keystone: remove redundant reset stuff Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 6/7] ARM: dts: keystone: update reset node to work with reset driver Ivan Khoronzhuk
2014-05-23 15:43 ` [Patch v7 7/7] ARM: keystone: enable reset driver support Ivan Khoronzhuk
2014-05-23 21:28 ` [Patch v7 0/7] Introduce keystone reset driver Santosh Shilimkar
2014-05-23 21:38 ` Ivan Khoronzhuk
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=20140527092428.GH5875@lee--X1 \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.khoronzhuk@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m-karicheri2@ti.com \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=sboyd@codeaurora.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=w-kwok2@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).