devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Barry Song <21cnbao@gmail.com>,
	ohad@wizery.com, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: workgroup.linux@csr.com, Wei Chen <wei.chen@csr.com>,
	Bjorn Andersson <bjorn@kryo.se>, Barry Song <Baohua.Song@csr.com>
Subject: Re: [PATCH 2/3 v3] Documentation: dt: add the CSR atlas7 hwspinlock bindings document
Date: Fri, 22 May 2015 17:44:26 -0500	[thread overview]
Message-ID: <555FB14A.2070505@ti.com> (raw)
In-Reply-To: <1432017698-23725-2-git-send-email-21cnbao@gmail.com>

Hi Barry,

On 05/19/2015 01:41 AM, Barry Song wrote:
> From: Wei Chen <wei.chen@csr.com>
> 
> The Hardware Spinlock device on atlas7 provides hardware assistance
> for synchronization between the multiple processors in the system
> (dual Cortex-A7, CAN bus Cortex-M3 and audio DSP).
> This patch adds the DT bindings information for this hwspinlock
> module.
> 
> Cc: Suman Anna <s-anna@ti.com>
> Cc: Bjorn Andersson <bjorn@kryo.se>
> Signed-off-by: Wei Chen <wei.chen@csr.com>
> Signed-off-by: Barry Song <Baohua.Song@csr.com>
> ---
>  .../devicetree/bindings/hwlock/sirf,hwspinlock.txt | 25 ++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/hwlock/sirf,hwspinlock.txt
> 
> diff --git a/Documentation/devicetree/bindings/hwlock/sirf,hwspinlock.txt b/Documentation/devicetree/bindings/hwlock/sirf,hwspinlock.txt
> new file mode 100644
> index 0000000..cc6d351
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwlock/sirf,hwspinlock.txt
> @@ -0,0 +1,25 @@
> +SIRF Hardware spinlock device Binding
> +-----------------------------------------------
> +
> +Required properties :
> +- compatible : shall contain only one of the following:
> +	"sirf,hwspinlock"
> +
> +- reg : the register address of hwspinlock

Also suggest to document the value to be used for #hwlock-cells, the
generic hwlock binding does not mention that.

> +
> +Please look at the generic hwlock binding for usage information for consumers,
> +"Documentation/devicetree/bindings/hwlock/hwlock.txt"
> +

regards
Suman

  reply	other threads:[~2015-05-22 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  6:41 [PATCH 1/3 v3] drivers: hwspinlock: add CSR atlas7 implementation Barry Song
     [not found] ` <1432017698-23725-1-git-send-email-21cnbao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-19  6:41   ` [PATCH 2/3 v3] Documentation: dt: add the CSR atlas7 hwspinlock bindings document Barry Song
2015-05-22 22:44     ` Suman Anna [this message]
     [not found]       ` <555FB14A.2070505-l0cyMroinI0@public.gmane.org>
2015-05-25  5:33         ` Barry Song
2015-05-26 17:02           ` Suman Anna
2015-05-19  6:41   ` [PATCH 3/3 v3] ARM: dts: atlas7: use general dt-binding for hwspinlock Barry Song
2015-05-22 22:51   ` [PATCH 1/3 v3] drivers: hwspinlock: add CSR atlas7 implementation Suman Anna
     [not found]     ` <555FB2F2.7080109-l0cyMroinI0@public.gmane.org>
2015-05-25  5:37       ` Barry Song
2015-05-26 17:03         ` Suman Anna

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=555FB14A.2070505@ti.com \
    --to=s-anna@ti.com \
    --cc=21cnbao@gmail.com \
    --cc=Baohua.Song@csr.com \
    --cc=bjorn@kryo.se \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=wei.chen@csr.com \
    --cc=workgroup.linux@csr.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).