[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174732127889.17102.8532614606603162153.b4-ty@linaro.org>
Date: Thu, 15 May 2025 17:01:29 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
Ahmad Fatoum <a.fatoum@...gutronix.de>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
linux-gpio@...r.kernel.org,
Dario Binacchi <dario.binacchi@...rulasolutions.com>,
Haibo Chen <haibo.chen@....com>,
Catalin Popescu <catalin.popescu@...ca-geosystems.com>,
imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] gpio: mxc: configure dynamic GPIO base for CONFIG_GPIO_SYSFS=n
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
On Wed, 07 May 2025 15:07:25 +0200, Ahmad Fatoum wrote:
> i.MX GPIO numbering has been deterministic since commit 7e6086d9e54a
> ("gpio/mxc: specify gpio base for device tree probe"), a year after
> device tree support was first added back in 2011.
>
> Reverting to dynamically allocated GPIO base now would break most
> systems making use of the sysfs API. These systems will be eventually
> broken by the removal of the sysfs API, but that would result in GPIO
> scripts not working instead of essentially toggling at random according
> to probe order, which would happen if we unconditionally set base to -1.
>
> [...]
Applied, thanks!
[1/1] gpio: mxc: configure dynamic GPIO base for CONFIG_GPIO_SYSFS=n
https://git.kernel.org/brgl/linux/c/0a45c1a002705c8622738fbd2a2913acf886ea27
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Powered by blists - more mailing lists