From: Sander Vanheule <sander@svanheule.net>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Michael Walle <mwalle@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, Lee Jones <lee@kernel.org>,
Pavel Machek <pavel@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/8] RTL8231 GPIO expander support
Date: Thu, 23 Oct 2025 11:09:57 +0200 [thread overview]
Message-ID: <69a020e444bfbd3b72971dec3a34261ff8d39f24.camel@svanheule.net> (raw)
In-Reply-To: <CAMRc=MeGehj3EHP=W3E3fJOpOAqXXg_D8XRRuv2SMxF8_UYpbQ@mail.gmail.com>
Hi,
On Thu, 2025-10-23 at 11:05 +0200, Bartosz Golaszewski wrote:
> On Tue, Oct 21, 2025 at 4:24 PM Sander Vanheule <sander@svanheule.net> wrote:
> >
> > The RTL8231 GPIO and LED expander can be configured for use as an MDIO
> > or SMI bus device. Currently only the MDIO mode is supported, although
> > SMI mode support should be fairly straightforward, once an SMI bus
> > driver is available.
> >
> > Provided features by the RTL8231:
> > - Up to 37 GPIOs
> > - Configurable drive strength: 8mA or 4mA (currently unsupported)
> > - Input debouncing on GPIOs 31-36
> > - Up to 88 LEDs in multiple scan matrix groups
> > - On, off, or one of six toggling intervals
> > - "single-color mode": 2×36 single color LEDs + 8 bi-color LEDs
> > - "bi-color mode": (12 + 2×6) bi-color LEDs + 24 single color LEDs
> > - Up to one PWM output (currently unsupported)
> > - Fixed duty cycle, 8 selectable frequencies (1.2kHz - 4.8kHz)
> >
> > The patches have been in use downstream by OpenWrt for some months. As
> > the original patches are already a few years old, I would like to request
> > all patches to be reviewed again (and I've dropped all provided tags and
> > changelogs).
> > ---
> > RFC for gpio-regmap changes:
> > Link:
> > https://lore.kernel.org/lkml/20251020115636.55417-1-sander@svanheule.net/
> >
> > Patch series v5 (June 2021):
> > Link:
> > https://lore.kernel.org/lkml/cover.1623532208.git.sander@svanheule.net/
> >
> > Sander Vanheule (8):
> > gpio: regmap: Force writes for aliased data regs
> > gpio: regmap: Bypass cache for aliased inputs
>
> If I'm not mistaken, nothing depends on these two at build-time, so I
> can just take them through the GPIO tree for v6.19?
That's okay for me.
Best,
Sander
next prev parent reply other threads:[~2025-10-23 9:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 14:23 [PATCH v6 0/8] RTL8231 GPIO expander support Sander Vanheule
2025-10-21 14:23 ` [PATCH v6 1/8] gpio: regmap: Force writes for aliased data regs Sander Vanheule
2025-10-21 14:23 ` [PATCH v6 2/8] gpio: regmap: Bypass cache for aliased inputs Sander Vanheule
2025-10-23 12:06 ` Bartosz Golaszewski
2025-10-21 14:23 ` [PATCH v6 3/8] dt-bindings: leds: Binding for RTL8231 scan matrix Sander Vanheule
2025-10-26 21:59 ` Rob Herring
2025-10-27 17:12 ` Sander Vanheule
2025-10-21 14:23 ` [PATCH v6 4/8] dt-bindings: mfd: Binding for RTL8231 Sander Vanheule
2025-10-26 22:04 ` Rob Herring
2025-10-21 14:24 ` [PATCH v6 5/8] mfd: Add RTL8231 core device Sander Vanheule
2025-11-06 16:33 ` Lee Jones
2025-11-13 21:25 ` Sander Vanheule
2025-10-21 14:24 ` [PATCH v6 6/8] pinctrl: Add RTL8231 pin control and GPIO support Sander Vanheule
2025-10-22 1:47 ` kernel test robot
2025-10-22 5:01 ` kernel test robot
2025-10-22 7:42 ` Linus Walleij
2025-10-22 7:52 ` Linus Walleij
2025-10-22 8:24 ` Sander Vanheule
2025-10-21 14:24 ` [PATCH v6 7/8] leds: Add support for RTL8231 LED scan matrix Sander Vanheule
2025-10-21 14:24 ` [PATCH v6 8/8] MAINTAINERS: Add RTL8231 MFD driver Sander Vanheule
2025-10-23 9:05 ` [PATCH v6 0/8] RTL8231 GPIO expander support Bartosz Golaszewski
2025-10-23 9:09 ` Sander Vanheule [this message]
2025-10-23 12:05 ` (subset) " Bartosz Golaszewski
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=69a020e444bfbd3b72971dec3a34261ff8d39f24.camel@svanheule.net \
--to=sander@svanheule.net \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=pavel@kernel.org \
--cc=robh@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