From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3 repost] clocksource: sh_mtu2: Document r7s72100 binding
Date: Wed, 27 Aug 2014 09:52:40 +0000 [thread overview]
Message-ID: <20140827095240.GC7295@leverpostej> (raw)
In-Reply-To: <1409117300-2133-3-git-send-email-horms+renesas@verge.net.au>
On Wed, Aug 27, 2014 at 06:28:19AM +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 Multi-Function Timer Pulse
> Unit 2 (MTU2) 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 r7s72100 SoC.
> ---
> Documentation/devicetree/bindings/timer/renesas,mtu2.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/timer/renesas,mtu2.txt b/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> index 917453f..ec4d334 100644
> --- a/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> +++ b/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> @@ -8,7 +8,9 @@ are independent. The MTU2 hardware supports five channels indexed from 0 to 4.
>
> Required Properties:
>
> - - compatible: must contain "renesas,mtu2"
> + - compatible: must be one of the following.
Surely "one or more", follwing the example?
> + - "renesas,mtu2" for generic MTU2
s/generic/any/ to make it clearer this should be present in all lists
for the moment?
> + - "renesas,mtu2-r7s72100" for R7S72100 MTU2
It might make sense to move this above the "renesas,mtu2" entry to make
the ordering a bit clearer.
Cheers,
Mark.
>
> - reg: base address and length of the registers block for the timer module.
>
> @@ -26,7 +28,7 @@ Required Properties:
> Example: R7S72100 (RZ/A1H) MTU2 node
>
> mtu2: timer@fcff0000 {
> - compatible = "renesas,mtu2";
> + compatible = "renesas,mtu2-r7s72100", "renesas,mtu2";
> reg = <0xfcff0000 0x400>;
> interrupts = <0 139 IRQ_TYPE_LEVEL_HIGH>,
> <0 146 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
>
WARNING: multiple messages have this Message-ID (diff)
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3 repost] clocksource: sh_mtu2: Document r7s72100 binding
Date: Wed, 27 Aug 2014 10:52:40 +0100 [thread overview]
Message-ID: <20140827095240.GC7295@leverpostej> (raw)
In-Reply-To: <1409117300-2133-3-git-send-email-horms+renesas@verge.net.au>
On Wed, Aug 27, 2014 at 06:28:19AM +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 Multi-Function Timer Pulse
> Unit 2 (MTU2) 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 r7s72100 SoC.
> ---
> Documentation/devicetree/bindings/timer/renesas,mtu2.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/timer/renesas,mtu2.txt b/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> index 917453f..ec4d334 100644
> --- a/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> +++ b/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> @@ -8,7 +8,9 @@ are independent. The MTU2 hardware supports five channels indexed from 0 to 4.
>
> Required Properties:
>
> - - compatible: must contain "renesas,mtu2"
> + - compatible: must be one of the following.
Surely "one or more", follwing the example?
> + - "renesas,mtu2" for generic MTU2
s/generic/any/ to make it clearer this should be present in all lists
for the moment?
> + - "renesas,mtu2-r7s72100" for R7S72100 MTU2
It might make sense to move this above the "renesas,mtu2" entry to make
the ordering a bit clearer.
Cheers,
Mark.
>
> - reg: base address and length of the registers block for the timer module.
>
> @@ -26,7 +28,7 @@ Required Properties:
> Example: R7S72100 (RZ/A1H) MTU2 node
>
> mtu2: timer at fcff0000 {
> - compatible = "renesas,mtu2";
> + compatible = "renesas,mtu2-r7s72100", "renesas,mtu2";
> reg = <0xfcff0000 0x400>;
> interrupts = <0 139 IRQ_TYPE_LEVEL_HIGH>,
> <0 146 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 at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
WARNING: multiple messages have this Message-ID (diff)
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 2/3 repost] clocksource: sh_mtu2: Document r7s72100 binding
Date: Wed, 27 Aug 2014 10:52:40 +0100 [thread overview]
Message-ID: <20140827095240.GC7295@leverpostej> (raw)
In-Reply-To: <1409117300-2133-3-git-send-email-horms+renesas@verge.net.au>
On Wed, Aug 27, 2014 at 06:28:19AM +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 Multi-Function Timer Pulse
> Unit 2 (MTU2) 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 r7s72100 SoC.
> ---
> Documentation/devicetree/bindings/timer/renesas,mtu2.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/timer/renesas,mtu2.txt b/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> index 917453f..ec4d334 100644
> --- a/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> +++ b/Documentation/devicetree/bindings/timer/renesas,mtu2.txt
> @@ -8,7 +8,9 @@ are independent. The MTU2 hardware supports five channels indexed from 0 to 4.
>
> Required Properties:
>
> - - compatible: must contain "renesas,mtu2"
> + - compatible: must be one of the following.
Surely "one or more", follwing the example?
> + - "renesas,mtu2" for generic MTU2
s/generic/any/ to make it clearer this should be present in all lists
for the moment?
> + - "renesas,mtu2-r7s72100" for R7S72100 MTU2
It might make sense to move this above the "renesas,mtu2" entry to make
the ordering a bit clearer.
Cheers,
Mark.
>
> - reg: base address and length of the registers block for the timer module.
>
> @@ -26,7 +28,7 @@ Required Properties:
> Example: R7S72100 (RZ/A1H) MTU2 node
>
> mtu2: timer@fcff0000 {
> - compatible = "renesas,mtu2";
> + compatible = "renesas,mtu2-r7s72100", "renesas,mtu2";
> reg = <0xfcff0000 0x400>;
> interrupts = <0 139 IRQ_TYPE_LEVEL_HIGH>,
> <0 146 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
>
next prev parent reply other threads:[~2014-08-27 9:52 UTC|newest]
Thread overview: 39+ 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 ` Simon Horman
2014-08-27 5:28 ` Simon Horman
2014-08-27 5:28 ` [PATCH 1/3 repost] clocksource: sh_cmt: Document " Simon Horman
2014-08-27 5:28 ` Simon Horman
2014-08-27 5:28 ` Simon Horman
2014-08-27 6:55 ` Geert Uytterhoeven
2014-08-27 6:55 ` Geert Uytterhoeven
2014-08-27 6:55 ` Geert Uytterhoeven
2014-08-27 8:09 ` Simon Horman
2014-08-27 8:09 ` Simon Horman
2014-08-27 8:09 ` Simon Horman
2014-08-27 9:51 ` Mark Rutland
2014-08-27 9:51 ` Mark Rutland
2014-08-27 9:51 ` Mark Rutland
2014-09-03 1:27 ` Simon Horman
2014-09-03 1:27 ` Simon Horman
2014-09-03 1:27 ` Simon Horman
2014-09-03 9:17 ` Mark Rutland
2014-09-03 9:17 ` Mark Rutland
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 5:28 ` Simon Horman
2014-08-27 5:28 ` Simon Horman
2014-08-27 9:52 ` Mark Rutland [this message]
2014-08-27 9:52 ` Mark Rutland
2014-08-27 9:52 ` Mark Rutland
2014-09-03 1:02 ` Simon Horman
2014-09-03 1:02 ` Simon Horman
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 5:28 ` Simon Horman
2014-08-27 5:28 ` Simon Horman
2014-08-27 9:53 ` Mark Rutland
2014-08-27 9:53 ` Mark Rutland
2014-08-27 9:53 ` Mark Rutland
2014-09-03 1:05 ` Simon Horman
2014-09-03 1:05 ` Simon Horman
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=20140827095240.GC7295@leverpostej \
--to=mark.rutland@arm.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.