devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH 3/3 repost] clocksource: sh_tmu: Document r8a7779 binding
Date: Wed, 27 Aug 2014 10:53:08 +0100	[thread overview]
Message-ID: <20140827095308.GD7295@leverpostej> (raw)
In-Reply-To: <1409117300-2133-4-git-send-email-horms+renesas@verge.net.au>

On Wed, Aug 27, 2014 at 06:28:20AM +0100, Simon Horman wrote:
> In general Renesas hardware is not documented to the extent
> where the relationship between IP blocks on different SoCs can be assumed
> although they may appear to operate the same way. Furthermore the
> documentation typically does not specify a version for individual
> IP blocks. For these reasons a convention of using the SoC name in place
> of a version and providing SoC-specific compat strings has been adopted.
> 
> Although not universally liked this convention is used in the bindings
> for the drivers a number of drivers for Renesas hardware. The purpose
> of this patch is to update the Renesas R-Car Timer Unit (TMU)
> driver to follow this convention.
> 
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> 
> ---
> * I plan to follow up with a patch patch to use the new binding in the
>   dtsi files for the r8a7779 SoC.
> ---
>  Documentation/devicetree/bindings/timer/renesas,tmu.txt | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/timer/renesas,tmu.txt b/Documentation/devicetree/bindings/timer/renesas,tmu.txt
> index 425d0c5..712ddfa 100644
> --- a/Documentation/devicetree/bindings/timer/renesas,tmu.txt
> +++ b/Documentation/devicetree/bindings/timer/renesas,tmu.txt
> @@ -8,7 +8,9 @@ are independent. The TMU hardware supports up to three channels.
>  
>  Required Properties:
>  
> -  - compatible: must contain "renesas,tmu"
> +  - compatible: must contain one of the following.
> +    - "renesas,tmu" generic TMU
> +    - "renesas,tmu-r8a7779" R8A7779 TMU

Similarly to patch 2, "one or more" and swap the order here?

Mark.

>  
>    - reg: base address and length of the registers block for the timer module.
>  
> @@ -27,7 +29,7 @@ Optional Properties:
>  Example: R8A7779 (R-Car H1) TMU0 node
>  
>  	tmu0: timer@ffd80000 {
> -		compatible = "renesas,tmu";
> +		compatible = "renesas,tmu-r8a7779", "renesas,tmu";
>  		reg = <0xffd80000 0x30>;
>  		interrupts = <0 32 IRQ_TYPE_LEVEL_HIGH>,
>  			     <0 33 IRQ_TYPE_LEVEL_HIGH>,
> -- 
> 2.0.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2014-08-27  9:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  5:28 [PATCH 0/3 repost] clocksource: Document Renesas SoC specific bindings Simon Horman
2014-08-27  5:28 ` [PATCH 1/3 repost] clocksource: sh_cmt: Document " Simon Horman
2014-08-27  6:55   ` Geert Uytterhoeven
2014-08-27  8:09     ` Simon Horman
2014-08-27  9:51   ` Mark Rutland
2014-09-03  1:27     ` Simon Horman
2014-09-03  9:17       ` Mark Rutland
2014-08-27  5:28 ` [PATCH 2/3 repost] clocksource: sh_mtu2: Document r7s72100 binding Simon Horman
2014-08-27  9:52   ` Mark Rutland
2014-09-03  1:02     ` Simon Horman
2014-08-27  5:28 ` [PATCH 3/3 repost] clocksource: sh_tmu: Document r8a7779 binding Simon Horman
2014-08-27  9:53   ` Mark Rutland [this message]
2014-09-03  1:05     ` Simon Horman

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=20140827095308.GD7295@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms+renesas@verge.net.au \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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).