All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a779f0: Add TMU nodes
Date: Mon, 22 Aug 2022 12:17:38 +0200	[thread overview]
Message-ID: <YwNXwuhDM6wESmo4@shikoro> (raw)
In-Reply-To: <CAMuHMdXBiM_=V0XueJGcc4fVf1EkOjLVNqyhHZv0XXe0ox-Ekg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Hi Geert,

> > +                       interrupts = <GIC_SPI 477 IRQ_TYPE_LEVEL_HIGH>,
> > +                                    <GIC_SPI 478 IRQ_TYPE_LEVEL_HIGH>,
> > +                                    <GIC_SPI 479 IRQ_TYPE_LEVEL_HIGH>;
> 
> We really should update the DT bindings so we can describe the fourth
> interrupt on TMU instances that support input capture.

Yes, but I also think this should be a separate series then.

> I don't think we need a new compatible value, as we can just look at
> the presence of the fourth (actually renesas-channels + 1) interrupt
> to enable the feature (if the driver ever gains support).

Good approach. But then, we should also switch to interrupt names to be
future proof, or? Who knows what other interrupts might be added later.

> As the above matches how TMU is handled on other SoCs:
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> i.e. will queue in renesas-devel for v6.1.

Thanks!

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-08-22 10:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 21:01 [PATCH 0/3] r8a779f0: enable TMU Wolfram Sang
2022-07-26 21:01 ` [PATCH 1/3] clk: renesas: r8a779f0: Add TMU and parent SASYNC clocks Wolfram Sang
2022-08-20  8:18   ` Geert Uytterhoeven
2022-07-26 21:01 ` [PATCH 2/3] arm64: dts: renesas: r8a779f0: Add TMU nodes Wolfram Sang
2022-08-20  8:39   ` Geert Uytterhoeven
2022-08-22 10:17     ` Wolfram Sang [this message]
2022-07-26 21:01 ` [PATCH 3/3] TEST: arm64: dts: renesas: spider: Enable TMU 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=YwNXwuhDM6wESmo4@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.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 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.