cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: nobuhiro.iwamatsu.x90@mail.toshiba
Cc: prabhakar.mahadev-lad.rj@bp.renesas.com,
	cip-dev@lists.cip-project.org, pavel@nabladev.com,
	biju.das.jz@bp.renesas.com
Subject: Re: [cip-dev] [PATCH 6.12.y-cip v2 00/10] Add pin configuration and GPIO IRQ support to Renesas RZ/T2H SoC
Date: Tue, 7 Jul 2026 22:17:13 +0200	[thread overview]
Message-ID: <ak1eyZZU2KzTw3TP@duo.ucw.cz> (raw)
In-Reply-To: <TY7PR01MB1481845D862F3FDD700499334CDF02@TY7PR01MB14818.jpnprd01.prod.outlook.com>

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

Hi!

> > This patch series aims to backport pin configuration and GPIO IRQ support to
> > Renesas RZ/T2H and RZ/N2H SoCs. Enabling of GPIO IRQ support to
> > SoC/board DTS/I will be done as a follow-up series along with xSPI support.
> > 
> > All the patches have been cherry-picked from upstream kernel 7.2-rc1.
> > Patches apply on top v6.12.94-cip26 (commit-id e00178e6fe853).
> 
> I reviewed this series, looks good to me.
> I apply this, thanks.

I had some minor comments here, but those should be fixed in mainline,
first, so they should not block the merge.

This looks okay to me.

Reviewed-by: Pavel Machek <pavel@nabladev.com>

Best regards,
                                                                Pavel

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

      reply	other threads:[~2026-07-07 20:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 10:23 [PATCH 6.12.y-cip v2 00/10] Add pin configuration and GPIO IRQ support to Renesas RZ/T2H SoC Lad Prabhakar
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 01/10] pinctrl: renesas: Remove unneeded semicolons Lad Prabhakar
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 02/10] pinctrl: renesas: rzt2h: Move GPIO enable/disable into separate function Lad Prabhakar
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 03/10] pinctrl: renesas: rzt2h: Allow .get_direction() for IRQ function GPIOs Lad Prabhakar
2026-07-07 20:17   ` Pavel Machek
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 04/10] pinctrl: renesas: rzt2h: Add GPIO IRQ chip to handle interrupts Lad Prabhakar
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 05/10] pinctrl: renesas: rzt2h: Fix device node leak in rzt2h_gpio_register() Lad Prabhakar
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 06/10] pinctrl: renesas: rzt2h: Fix invalid wait context Lad Prabhakar
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 07/10] dt-bindings: pinctrl: renesas,r9a09g077: Document pin configuration properties Lad Prabhakar
2026-07-07 20:17   ` Pavel Machek
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 08/10] pinctrl: renesas: rzt2h: Add pin configuration support Lad Prabhakar
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 09/10] pinctrl: renesas: rzt2h: Remove unused variable in rzt2h_pinctrl_register() Lad Prabhakar
2026-07-02 10:23 ` [PATCH 6.12.y-cip v2 10/10] pinctrl: renesas: rzt2h: Skip PFC mode configuration if already set Lad Prabhakar
2026-07-07  8:19 ` [PATCH 6.12.y-cip v2 00/10] Add pin configuration and GPIO IRQ support to Renesas RZ/T2H SoC nobuhiro.iwamatsu.x90
2026-07-07 20:17   ` Pavel Machek [this message]

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=ak1eyZZU2KzTw3TP@duo.ucw.cz \
    --to=pavel@nabladev.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro.iwamatsu.x90@mail.toshiba \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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).