linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Duc Nguyen <duc.nguyen.ub@renesas.com>,
	LUU HOAI <hoai.luu.ub@renesas.com>, Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a779a0: Add TPU node
Date: Mon, 6 Sep 2021 11:38:57 +0200	[thread overview]
Message-ID: <CAMuHMdUY4m29MneDZV7ir=8i0nSuh+u6qhH9s7Z3Km3N_DzGDA@mail.gmail.com> (raw)
In-Reply-To: <20210901091725.35610-3-wsa+renesas@sang-engineering.com>

On Wed, Sep 1, 2021 at 11:17 AM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> From: Duc Nguyen <duc.nguyen.ub@renesas.com>
>
> This patch adds TPU node for R-Car V3U (r8a779a0) SoC.
>
> Signed-off-by: Duc Nguyen <duc.nguyen.ub@renesas.com>
> Signed-off-by: LUU HOAI <hoai.luu.ub@renesas.com>
> Signed-off-by: Wolfram Sang <wsa@kernel.org>

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-devel for v5.16.

> --- a/arch/arm64/boot/dts/renesas/r8a779a0.dtsi
> +++ b/arch/arm64/boot/dts/renesas/r8a779a0.dtsi
> @@ -1023,6 +1023,17 @@ msiof5: spi@e6c28000 {
>                         status = "disabled";
>                 };
>
> +               tpu: pwm@e6e80000 {

I'll move this just before "msiof0: spi@e6e90000" while applying,
to preserve sort order.

> +                       compatible = "renesas,tpu-r8a779a0", "renesas,tpu";
> +                       reg = <0 0xe6e80000 0 0x148>;
> +                       interrupts = <GIC_SPI 515 IRQ_TYPE_LEVEL_HIGH>;
> +                       clocks = <&cpg CPG_MOD 718>;
> +                       power-domains = <&sysc R8A779A0_PD_ALWAYS_ON>;
> +                       resets = <&cpg 718>;
> +                       #pwm-cells = <3>;
> +                       status = "disabled";
> +               };
> +
>                 dmac1: dma-controller@e7350000 {
>                         compatible = "renesas,dmac-r8a779a0";
>                         reg = <0 0xe7350000 0 0x1000>,

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2021-09-06  9:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01  9:17 [PATCH 0/3] v3u: add support for TPU Wolfram Sang
2021-09-01  9:17 ` [PATCH 1/3] clk: renesas: r8a779a0: Add TPU clock Wolfram Sang
2021-09-06  9:36   ` Geert Uytterhoeven
2021-09-01  9:17 ` [PATCH 2/3] arm64: dts: renesas: r8a779a0: Add TPU node Wolfram Sang
2021-09-06  9:38   ` Geert Uytterhoeven [this message]
2021-09-01  9:17 ` [RFC PATCH 3/3] arm64: dts: r8a779a0-falcon-cpu: Add TPU support Wolfram Sang
2021-09-06  9:45   ` Geert Uytterhoeven
2021-09-06  9:50     ` 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='CAMuHMdUY4m29MneDZV7ir=8i0nSuh+u6qhH9s7Z3Km3N_DzGDA@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=duc.nguyen.ub@renesas.com \
    --cc=hoai.luu.ub@renesas.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@kernel.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).