[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <173651519218.65575.13189827123341171329.b4-ty@linaro.org>
Date: Fri, 10 Jan 2025 14:19:59 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Michael Walle <mwalle@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org,
Sander Vanheule <sander@...nheule.net>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Álvaro Fernández Rojas <noltari@...il.com>,
jonas.gorski@...il.com,
kylehendrydev@...il.com,
florian.fainelli@...adcom.com
Subject: Re: [PATCH] gpio: regmap: Use generic request/free ops
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
On Tue, 07 Jan 2025 21:16:20 +0100, Sander Vanheule wrote:
> Set the gpiochip request and free ops to the generic implementations.
> This way a user can provide a gpio-ranges property defined for a pinmux,
> easing muxing of gpio functions. Provided that the pin controller
> implementents the pinmux op .gpio_request_enable(), pins will
> automatically be muxed to their GPIO function when requested.
>
>
> [...]
Applied, thanks!
[1/1] gpio: regmap: Use generic request/free ops
commit: 5ab3b97ef9d4bff2513994ef9efc6d95722cb902
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Powered by blists - more mailing lists