Re: [PATCH v8 0/9] gpio: realtek: Add support for Realtek DHC RTD1625

[Bartosz Golaszewski]

On Sun, 26 Jul 2026 20:51:51 +0800, Yu-Chun Lin wrote:
> For better review flow, this series includes Andy Shevchenko's
> gpio-regmap fix patches [1] as a prerequisite. The first patch
> reverts the previously applied patch from Bartosz Golaszewski.
> 
> This series then adds GPIO support for the Realtek DHC RTD1625 SoC.
> 
> Unlike the existing driver (gpio-rtd.c) which uses shared bank
> registers, the RTD1625 features a per-pin register architecture where
> each GPIO line is managed by its own dedicated 32-bit control register.
> This distinct hardware design requires a new, separate driver.
> 
> [...]

Applied, thanks!

[1/9] Revert "gpio: realtek: Add driver for Realtek DHC RTD1625 SoC"
      https://git.kernel.org/brgl/c/921ea990b651339d3d319f1ebb065c0f5431a7f9
[2/9] gpio: regmap: Provide default IRQ resource request and release callbacks
      https://git.kernel.org/brgl/c/65caf947fe021c1d2c59e08a9c48f25c38cca9e8
[3/9] gpio: regmap: Apply default resource callbacks for regmap IRQ chip
      https://git.kernel.org/brgl/c/2da8b903cf7039338e6cc1b1d0e9f9e1cf9159c3
[4/9] gpio: regmap: Order kernel-doc descriptions with the actual appearance
      https://git.kernel.org/brgl/c/cf0f6ddd08f37808fd6893e2d9045f069c07a5a7
[5/9] gpio: regmap: Add gpio_regmap_operation to extend reg_mask_xlate callback
      https://git.kernel.org/brgl/c/6c53312b7e2d9a972e509f5bac002e169e241eca
[6/9] gpio: regmap: Add value_xlate callback
      https://git.kernel.org/brgl/c/5f28e3dbd23199c778f5339c0d4488820435f6d5
[7/9] gpio: regmap: Add set_config callback
      https://git.kernel.org/brgl/c/ab91ecbc322424916efea4c4e6220e2046a80e8a
[8/9] gpio: regmap: Add IRQ enable/disable helpers
      https://git.kernel.org/brgl/c/de36d18cfc66519fd3bb0dabf92d5f7fbc1dc121
[9/9] gpio: realtek: Add driver for Realtek DHC RTD1625 SoC
      https://git.kernel.org/brgl/c/6435d21cbd42fea6c66dfd4cfef7d58b9612497e

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxxxxxxxx>