Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Bartosz Golaszewski" <brgl@kernel.org>
Cc: <u.kleine-koenig@baylibre.com>, <dakr@kernel.org>,
	<bhelgaas@google.com>, <dlechner@baylibre.com>,
	<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
	<linux@analog.com>, <linux-iio@vger.kernel.org>,
	<cy.huang@realtek.com>, <james.tai@realtek.com>,
	<stanley_chang@realtek.com>,
	"Yu-Chun Lin" <eleanor.lin@realtek.com>, <linusw@kernel.org>,
	<andriy.shevchenko@intel.com>, <mwalle@kernel.org>,
	<tychang@realtek.com>, <wbg@kernel.org>, <nuno.sa@analog.com>,
	<Michael.Hennerich@analog.com>, <jic23@kernel.org>,
	<andy@kernel.org>, <o-takashi@sakamocchi.jp>
Subject: Re: [PATCH v8 9/9] gpio: realtek: Add driver for Realtek DHC RTD1625 SoC
Date: Mon, 27 Jul 2026 13:23:24 +0200	[thread overview]
Message-ID: <DK9BCXS5YATK.30EPJ4G8Y72OT@bootlin.com> (raw)
In-Reply-To: <CAMRc=MffrnN3awvAB2Ov2h=pLPNpvmZcwU=v9HBFrjLaotjskA@mail.gmail.com>

On Mon Jul 27, 2026 at 1:10 PM CEST, Bartosz Golaszewski wrote:
> On Mon, 27 Jul 2026 10:20:35 +0200, Mathieu Dubois-Briand
> <mathieu.dubois-briand@bootlin.com> said:
>> On Sun Jul 26, 2026 at 2:52 PM CEST, Yu-Chun Lin wrote:
>>> From: Tzuyi Chang <tychang@realtek.com>
>>>
>>> Add support for the GPIO controller found on Realtek DHC RTD1625 SoCs.
>>>
>>> Unlike the existing Realtek GPIO driver (drivers/gpio/gpio-rtd.c),
>>> which manages pins via shared bank registers, the RTD1625 introduces
>>> a per-pin register architecture. Each GPIO line now has its own
>>> dedicated 32-bit control register to manage configuration independently,
>>> including direction, output value, input value, interrupt enable, and
>>> debounce. Therefore, this distinct hardware design requires a separate
>>> driver.
>>>
>>> The RTD1625 GPIO controller has a hardware quirk where both 'assert'
>>> and 'de-assert' interrupts are fired simultaneously on any edge toggle.
>>> The driver works around this quirk to correctly handle edge interrupts.
>>>
>>> Interrupt support is optional for this device, matching the dt-bindings.
>>> If the interrupts property is not provided, the driver simply skips IRQ
>>> initialization and operates purely as a basic GPIO controller.
>>>
>>> Reviewed-by: Linus Walleij <linusw@kernel.org>
>>> Signed-off-by: Tzuyi Chang <tychang@realtek.com>
>>> Co-developed-by: Yu-Chun Lin <eleanor.lin@realtek.com>
>>> Signed-off-by: Yu-Chun Lin <eleanor.lin@realtek.com>
>>> ---
>>> Changes in v8:
>>> - Add error handlers in td1625_gpio_irq_handle().
>>> - Move the direction-checking logic from the core to our custom
>>> reg_mask_xlate() callback.
>>> - Add Reviewed-by tag from Linus.
>>> ---
>>
>> Thanks for the fixes.
>>
>> Reviewed-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
>>
>
> Hi!
>
> Please leave series-wide tags under the cover letter, otherwise b4 will only
> apply it to the specific patch under which you commented.
>
> Bart

Sorry, this was a patch-specific review, but the way I sent it was a bit
misleading.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2026-07-27 11:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26 12:51 [PATCH v8 0/9] gpio: realtek: Add support for Realtek DHC RTD1625 Yu-Chun Lin
2026-07-26 12:51 ` [PATCH v8 1/9] Revert "gpio: realtek: Add driver for Realtek DHC RTD1625 SoC" Yu-Chun Lin
2026-07-26 12:51 ` [PATCH v8 2/9] gpio: regmap: Provide default IRQ resource request and release callbacks Yu-Chun Lin
2026-07-26 12:51 ` [PATCH v8 3/9] gpio: regmap: Apply default resource callbacks for regmap IRQ chip Yu-Chun Lin
2026-07-26 12:51 ` [PATCH v8 4/9] gpio: regmap: Order kernel-doc descriptions with the actual appearance Yu-Chun Lin
2026-07-26 12:51 ` [PATCH v8 5/9] gpio: regmap: Add gpio_regmap_operation to extend reg_mask_xlate callback Yu-Chun Lin
2026-07-26 12:51 ` [PATCH v8 6/9] gpio: regmap: Add value_xlate callback Yu-Chun Lin
2026-07-26 12:51 ` [PATCH v8 7/9] gpio: regmap: Add set_config callback Yu-Chun Lin
2026-07-26 12:51 ` [PATCH v8 8/9] gpio: regmap: Add IRQ enable/disable helpers Yu-Chun Lin
2026-07-26 12:52 ` [PATCH v8 9/9] gpio: realtek: Add driver for Realtek DHC RTD1625 SoC Yu-Chun Lin
2026-07-27  8:20   ` Mathieu Dubois-Briand
2026-07-27 11:10     ` Bartosz Golaszewski
2026-07-27 11:23       ` Mathieu Dubois-Briand [this message]
2026-07-27 13:04         ` Bartosz Golaszewski
2026-07-27 14:07           ` Mathieu Dubois-Briand

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=DK9BCXS5YATK.30EPJ4G8Y72OT@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=brgl@kernel.org \
    --cc=cy.huang@realtek.com \
    --cc=dakr@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=eleanor.lin@realtek.com \
    --cc=james.tai@realtek.com \
    --cc=jic23@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=mwalle@kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=o-takashi@sakamocchi.jp \
    --cc=stanley_chang@realtek.com \
    --cc=tychang@realtek.com \
    --cc=u.kleine-koenig@baylibre.com \
    --cc=wbg@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