linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH v2] dt-bindings: timer: renesas,cmt: add r8a779a0 CMT support
Date: Thu, 11 Mar 2021 10:27:30 +0100	[thread overview]
Message-ID: <YEnigsubARUgLe7u@oden.dyn.berto.se> (raw)
In-Reply-To: <20210311090918.2197-1-wsa+renesas@sang-engineering.com>

Hi Wolfram,

Thanks for your patch.

On 2021-03-11 10:09:18 +0100, Wolfram Sang wrote:
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>

> ---
> 
> Changes since V1:
> * none, but additional testing was done which revealed that this CMT
>   in deed behaves the same as other Gen3 SoCs. There was one hickup
>   which seemed unique to V3U but has been reproduced with M3N meanwhile.
>   This is something we need to tackle, but no reason to prevent adding
>   V3U support.
> 
>  Documentation/devicetree/bindings/timer/renesas,cmt.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/timer/renesas,cmt.yaml b/Documentation/devicetree/bindings/timer/renesas,cmt.yaml
> index 428db3a21bb9..363ec28e07da 100644
> --- a/Documentation/devicetree/bindings/timer/renesas,cmt.yaml
> +++ b/Documentation/devicetree/bindings/timer/renesas,cmt.yaml
> @@ -79,6 +79,7 @@ properties:
>                - renesas,r8a77980-cmt0     # 32-bit CMT0 on R-Car V3H
>                - renesas,r8a77990-cmt0     # 32-bit CMT0 on R-Car E3
>                - renesas,r8a77995-cmt0     # 32-bit CMT0 on R-Car D3
> +              - renesas,r8a779a0-cmt0     # 32-bit CMT0 on R-Car V3U
>            - const: renesas,rcar-gen3-cmt0 # 32-bit CMT0 on R-Car Gen3 and RZ/G2
>  
>        - items:
> @@ -94,6 +95,7 @@ properties:
>                - renesas,r8a77980-cmt1     # 48-bit CMT on R-Car V3H
>                - renesas,r8a77990-cmt1     # 48-bit CMT on R-Car E3
>                - renesas,r8a77995-cmt1     # 48-bit CMT on R-Car D3
> +              - renesas,r8a779a0-cmt1     # 48-bit CMT on R-Car V3U
>            - const: renesas,rcar-gen3-cmt1 # 48-bit CMT on R-Car Gen3 and RZ/G2
>  
>    reg:
> -- 
> 2.30.0
> 

-- 
Regards,
Niklas Söderlund

  parent reply	other threads:[~2021-03-11  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  9:09 [PATCH v2] dt-bindings: timer: renesas,cmt: add r8a779a0 CMT support Wolfram Sang
2021-03-11  9:23 ` Geert Uytterhoeven
2021-03-11  9:27 ` Niklas Söderlund [this message]
2021-03-11 11:15 ` Daniel Lezcano
2021-04-09 10:27 ` [tip: timers/core] dt-bindings: timer: renesas,cmt: Add " tip-bot2 for Wolfram Sang

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=YEnigsubARUgLe7u@oden.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --cc=daniel.lezcano@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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).