From: ivan.khoronzhuk@ti.com (Ivan Khoronzhuk)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v6 3/7] mfd: ti-keystone-devctrl: add bindings for device state control
Date: Thu, 22 May 2014 20:16:16 +0300 [thread overview]
Message-ID: <537E30E0.8050403@ti.com> (raw)
In-Reply-To: <20140522171148.GL19747@lee--X1>
On 05/22/2014 08:11 PM, Lee Jones wrote:
> On Thu, 22 May 2014, Ivan Khoronzhuk wrote:
>
>> 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>
>> ---
>> .../devicetree/bindings/mfd/ti-keystone-devctrl.txt | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt
> Applied, thanks.
>
Thanks.
--
Regards,
Ivan Khoronzhuk
WARNING: multiple messages have this Message-ID (diff)
From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: Lee Jones <lee.jones@linaro.org>
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,
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 v6 3/7] mfd: ti-keystone-devctrl: add bindings for device state control
Date: Thu, 22 May 2014 20:16:16 +0300 [thread overview]
Message-ID: <537E30E0.8050403@ti.com> (raw)
In-Reply-To: <20140522171148.GL19747@lee--X1>
On 05/22/2014 08:11 PM, Lee Jones wrote:
> On Thu, 22 May 2014, Ivan Khoronzhuk wrote:
>
>> 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>
>> ---
>> .../devicetree/bindings/mfd/ti-keystone-devctrl.txt | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt
> Applied, thanks.
>
Thanks.
--
Regards,
Ivan Khoronzhuk
WARNING: multiple messages have this Message-ID (diff)
From: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
To: Lee Jones <lee.jones@linaro.org>
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>,
<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 v6 3/7] mfd: ti-keystone-devctrl: add bindings for device state control
Date: Thu, 22 May 2014 20:16:16 +0300 [thread overview]
Message-ID: <537E30E0.8050403@ti.com> (raw)
In-Reply-To: <20140522171148.GL19747@lee--X1>
On 05/22/2014 08:11 PM, Lee Jones wrote:
> On Thu, 22 May 2014, Ivan Khoronzhuk wrote:
>
>> 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>
>> ---
>> .../devicetree/bindings/mfd/ti-keystone-devctrl.txt | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/mfd/ti-keystone-devctrl.txt
> Applied, thanks.
>
Thanks.
--
Regards,
Ivan Khoronzhuk
next prev parent reply other threads:[~2014-05-22 17:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 16:44 [Patch v6 0/7] Introduce keystone reset driver Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 1/7] power: reset: keystone-reset: introduce " Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 2/7] clock: keystone-pllctrl: add bindings for keystone pll controller Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 3/7] mfd: ti-keystone-devctrl: add bindings for device state control Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 17:11 ` Lee Jones
2014-05-22 17:11 ` Lee Jones
2014-05-22 17:16 ` Ivan Khoronzhuk [this message]
2014-05-22 17:16 ` Ivan Khoronzhuk
2014-05-22 17:16 ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 4/7] power: reset: add bindings for keystone reset driver Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 18:03 ` Sergei Shtylyov
2014-05-22 18:03 ` Sergei Shtylyov
2014-05-22 18:19 ` Ivan Khoronzhuk
2014-05-22 18:19 ` Ivan Khoronzhuk
2014-05-22 18:19 ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 5/7] ARM: keystone: remove redundant reset stuff Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 6/7] ARM: dts: keystone: update reset node to work with reset driver Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` [Patch v6 7/7] ARM: keystone: enable reset driver support Ivan Khoronzhuk
2014-05-22 16:44 ` Ivan Khoronzhuk
2014-05-22 16:44 ` 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=537E30E0.8050403@ti.com \
--to=ivan.khoronzhuk@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.