linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ivan.khoronzhuk@ti.com (Ivan Khoronzhuk)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v5 3/7] mfd: ti-keystone-devctrl: add bindings for device state control
Date: Thu, 22 May 2014 17:32:39 +0300	[thread overview]
Message-ID: <537E0A87.5010408@ti.com> (raw)
In-Reply-To: <20140522141432.GA19747@lee--X1>


On 05/22/2014 05:14 PM, Lee Jones wrote:
> Why do I only have this patch?  Where is the rest of the set?  Also,
> it's on v5 and I don't recall seeing the other 4 versions?

It's strange I've sent whole series on

linux-kernel at vger.kernel.org
linux-arm-kernel at lists.infradead.org
linux-doc at vger.kernel.org
devicetree at vger.kernel.org

v4 is also was sent to lists in question:
https://lkml.org/lkml/2014/5/21/359

>> 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.
> Why have you tabbed out all that way?

I'll correct

>
>> +Example:
>> +
>> +devctrl: device-state-control {
> This node needs an address:
>
> devctrl: device-state-control at 02620000 {

Thanks!
I will correct

>> +	compatible = "ti,keystone-devctrl", "syscon";
>> +	reg = <0x02620000 0x1000>;
>> +};

-- 
Regards,
Ivan Khoronzhuk

  reply	other threads:[~2014-05-22 14:32 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 ` [Patch v5 3/7] mfd: ti-keystone-devctrl: add bindings for device state control Ivan Khoronzhuk
2014-05-22 14:14   ` Lee Jones
2014-05-22 14:32     ` Ivan Khoronzhuk [this message]
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=537E0A87.5010408@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 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).