Am 2022-03-17 09:37, schrieb Andy Shevchenko:
On Thu, Mar 17, 2022 at 7:36 AM Michael Walle <michael@xxxxxxxx> wrote:
Am 2022-03-15 16:32, schrieb Bartosz Golaszewski:
> On Mon, Mar 14, 2022 at 4:55 PM Michael Walle <michael@xxxxxxxx> wrote:
...
I started to try this out, but then I was wondering if there weren't
other gpio/pinctrl drivers with the same problem. And judging by the
reports [1], I'd say there are. Then I wasn't sure if this is actually
the correct fix here - or if that old workaround [2] doesn't work
anymore because it might have that empty ranges "feature".
To answer your question: I don't know. But I don't know if that is
actually the correct way of fixing this either.
>> Also, I'm not sure if there are any other other driver which get
>> broken by this. I.e. ones falling into the gpio_stub_drv category.
I know that OF is a mess, but I want to understand why in ACPI we
haven't experienced such an issue. Any pointers would be appreciated.
During debugging I've seen that the pinctrl-microchip-sgpio will
report itself as gpio_stub_drv. You'll find that this driver
was added by the following commit:
commit 4731210c09f5977300f439b6c56ba220c65b2348
Author: Saravana Kannan <saravanak@xxxxxxxxxx>
Date: Fri Jan 22 11:35:59 2021 -0800
gpiolib: Bind gpio_device to a driver to enable fw_devlink=on by
default
The microchip driver has actually a binding which was described in
that commit message. Thus I concluded, that it makes sense this driver
falls into that workaround. That is where I stopped and wrote this mail.
Actually, I haven't found out yet where that fallback to gpio_stub_drv
is happening.
-michael
