public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Herve Codina (Schneider Electric)" <herve.codina@bootlin.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Saravana Kannan <saravanak@google.com>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Pascal Eberhard <pascal.eberhard@se.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v7 0/8] gpio: renesas: Add support for GPIO and related interrupts in RZ/N1 SoC
Date: Sat, 20 Dec 2025 07:37:17 +0100	[thread overview]
Message-ID: <aUZEHSNqiMuHrCWb@shikoro> (raw)
In-Reply-To: <20251215142836.167101-1-herve.codina@bootlin.com>

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

Hi everyone,

> This series adds support for GPIO and GPIO IRQ mux available in the
> RZ/N1 SoCs.
> 
> The first patches in this series are related to a new helper introduced
> to parse an interrupt-map property.
>   - patch 1: Introduce the helper (for_each_of_imap_item)
>   - patch 2: Add a unittest for the new helper
>   - patch 3 and 4: convert existing drivers to use this new helper
> 
> Patch 5 adds support for GPIO (device-tree description)
> 
> The last patches (6, 7 and 8) of the series are related to GPIO
> interrupts and GPIO IRQ multiplexer.

I think this series is ready and I would really like to see it upstream
soon. I wonder, however, if the path to upstream has already been
discussed? It touches various subsystems, so I don't see immediately who
should pick the whole series? Or if parts should go to different
subsystems offering immutable branches? I bring this up because I want
to avoid losing a cycle just because this is unclear...

Happy hacking,

   Wolfram


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

  parent reply	other threads:[~2025-12-20  6:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 14:28 [PATCH v7 0/8] gpio: renesas: Add support for GPIO and related interrupts in RZ/N1 SoC Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 1/8] of/irq: Introduce for_each_of_imap_item Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 2/8] of: unittest: Add a test case for for_each_of_imap_item iterator Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 3/8] irqchip/ls-extirq: Use " Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 4/8] irqchip/renesas-rza1: " Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 5/8] ARM: dts: r9a06g032: Add GPIO controllers Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 6/8] dt-bindings: soc: renesas: Add the Renesas RZ/N1 GPIO Interrupt Multiplexer Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 7/8] soc: renesas: Add support for " Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 8/8] ARM: dts: r9a06g032: Add support for GPIO interrupts Herve Codina (Schneider Electric)
2025-12-20  6:41   ` Wolfram Sang
2025-12-20  6:37 ` Wolfram Sang [this message]
2025-12-22 15:35   ` [PATCH v7 0/8] gpio: renesas: Add support for GPIO and related interrupts in RZ/N1 SoC Geert Uytterhoeven
2026-01-07 19:13     ` 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=aUZEHSNqiMuHrCWb@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=herve.codina@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=pascal.eberhard@se.com \
    --cc=robh@kernel.org \
    --cc=saravanak@google.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@bootlin.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