[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <174117687651.61264.9467200851509383581.b4-ty@linaro.org>
Date: Wed, 5 Mar 2025 13:15:42 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: linux-gpio@...r.kernel.org,
Koichiro Den <koichiro.den@...onical.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
brgl@...ev.pl,
geert+renesas@...der.be,
linus.walleij@...aro.org,
maciej.borzecki@...onical.com,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v5 0/9] Introduce configfs-based interface for gpio-aggregator
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
On Mon, 24 Feb 2025 23:31:25 +0900, Koichiro Den wrote:
> This patch series introduces a configfs-based interface to gpio-aggregator
> to address limitations in the existing 'new_device' interface.
>
> The existing 'new_device' interface has several limitations:
>
> Issue#1. No way to determine when GPIO aggregator creation is complete.
> Issue#2. No way to retrieve errors when creating a GPIO aggregator.
> Issue#3. No way to trace a GPIO line of an aggregator back to its
> corresponding physical device.
> Issue#4. The 'new_device' echo does not indicate which virtual
> gpiochip<N> was created.
> Issue#5. No way to assign names to GPIO lines exported through an
> aggregator.
>
> [...]
I don't see anything wrong with this patch so I queued it for fixes. I
will pull it back into my gpio/for-next branch once it's upstream and
apply the rest of the aggregator changes for v6.15.
[1/9] gpio: aggregator: protect driver attr handlers against module unload
commit: 12f65d1203507f7db3ba59930fe29a3b8eee9945
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Powered by blists - more mailing lists