From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: <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>
Cc: <rdunlap@infradead.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>,
Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Subject: [Patch v5 3/7] mfd: ti-keystone-devctrl: add bindings for device state control
Date: Thu, 22 May 2014 16:48:32 +0300 [thread overview]
Message-ID: <1400766516-14537-4-git-send-email-ivan.khoronzhuk@ti.com> (raw)
In-Reply-To: <1400766516-14537-1-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.
Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
---
.../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..35f7a66
--- /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 pll controller
+ registers space.
+
+Example:
+
+devctrl: device-state-control {
+ compatible = "ti,keystone-devctrl", "syscon";
+ reg = <0x02620000 0x1000>;
+};
--
1.8.3.2
next prev parent reply other threads:[~2014-05-22 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 13:48 [Patch v5 0/7] Introduce keystone reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 1/7] power: reset: keystone-reset: introduce " Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 2/7] clock: keystone-pllctrl: add bindings for keystone pll controller Ivan Khoronzhuk
2014-05-22 13:48 ` Ivan Khoronzhuk [this message]
2014-05-22 14:14 ` [Patch v5 3/7] mfd: ti-keystone-devctrl: add bindings for device state control Lee Jones
2014-05-22 14:32 ` Ivan Khoronzhuk
2014-05-22 15:33 ` Lee Jones
2014-05-22 16:14 ` Ivan Khoronzhuk
2014-05-22 16:30 ` Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 4/7] power: reset: add bindings for keystone reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 5/7] ARM: keystone: remove redundant reset stuff Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 6/7] ARM: dts: keystone: update reset node to work with reset driver Ivan Khoronzhuk
2014-05-22 13:48 ` [Patch v5 7/7] ARM: keystone: enable reset driver support Ivan Khoronzhuk
2014-05-22 13:52 ` [Patch v5 0/7] Introduce keystone reset driver Santosh Shilimkar
2014-05-22 13:54 ` Arnd Bergmann
2014-05-22 13:58 ` Ivan Khoronzhuk
2014-05-22 14:02 ` Santosh Shilimkar
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=1400766516-14537-4-git-send-email-ivan.khoronzhuk@ti.com \
--to=ivan.khoronzhuk@ti.com \
--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=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=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
all inboxes | Powered by JetHome®