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>,
	Rob Herring <robh+dt@kernel.org>,
	Chris Brandt <chris.brandt@renesas.com>,
	Biju Das <biju.das.jz@bp.renesas.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Linux I2C <linux-i2c@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH/RFC 0/4] dt-bindings: i2c: renesas,riic: Add interrupt-names
Date: Wed, 11 Aug 2021 17:29:59 +0200	[thread overview]
Message-ID: <CAMuHMdVmKuYo7XhrQsLhXCOyRa=-aKwbtub=yi5nuSvJ22An2Q@mail.gmail.com> (raw)
In-Reply-To: <YRPdTiAakb6OBd2k@shikoro>

Hi Wolfram,

On Wed, Aug 11, 2021 at 4:23 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> > The Renesas RZ/A and RZ/G2L I2C Bus Interface has no less than 8
> > interrupts.  So I think it makes sense to use "interrupt-names"
> > property, to make it easier to review the interrupt mappings in DTS
> > files.
> >
> > Hence this series documents the "interrupt-names" property in the DT
> > bindings, adds the property to the DTS files, and marks it required in
> > the DT bindings. Obviously the last step cannot be applied until all
> > earlier patches are upstream.
> >
> > What do you think?
>
> I like it and I'd think it is good to go. It is probably easiest if you
> take the series via your tree to avoid merge conflicts and/or subsystem
> dependencies. It's unlikely the YAML file will see further updates. So,
> for the series:

Probably it is not worth doing this in lockstep (1/4 in v5.15 through
i2c, 2/4 and 3/4 in v5.16 through renesas-devel, and 4/4 in v5.17
through i2c).
I have different branches for DT binding and DTS, but I guess it
doesn't hurt to deviate and apply both to renesas-arm-dt-for-v5.15...

> Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

Thanks!

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-08-11 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 13:19 [PATCH/RFC 0/4] dt-bindings: i2c: renesas,riic: Add interrupt-names Geert Uytterhoeven
2021-07-14 13:20 ` [PATCH/RFC 1/4] " Geert Uytterhoeven
2021-07-16 19:19   ` Rob Herring
2021-07-14 13:20 ` [PATCH/RFC 2/4] ARM: dts: rza: Add I2C interrupt-names Geert Uytterhoeven
2021-07-14 13:20 ` [PATCH/RFC 3/4] arm64: dts: renesas: r9a07g044: " Geert Uytterhoeven
2021-07-14 17:21   ` Biju Das
2021-07-14 13:20 ` [PATCH/RFC 4/4] dt-bindings: i2c: renesas,riic: Make interrupt-names required Geert Uytterhoeven
2021-07-16 19:20   ` Rob Herring
2021-08-11 14:23 ` [PATCH/RFC 0/4] dt-bindings: i2c: renesas,riic: Add interrupt-names Wolfram Sang
2021-08-11 15:29   ` Geert Uytterhoeven [this message]
2021-08-11 19:04     ` 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='CAMuHMdVmKuYo7XhrQsLhXCOyRa=-aKwbtub=yi5nuSvJ22An2Q@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=chris.brandt@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=robh+dt@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).