[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a8c9b81c-bc0d-4ed5-845e-ecbf5e341064@molgen.mpg.de>
Date: Sun, 23 Feb 2025 23:04:05 +0100
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>, linux-gpio@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>, linux-pci@...r.kernel.org,
regressions@...ts.linux.dev
Subject: Re: Linux logs new warning `gpio gpiochip0:
gpiochip_add_data_with_key: get_direction failed: -22`
Dear Bortosz,
Am 23.02.25 um 21:54 schrieb Bartosz Golaszewski:
> On Fri, Feb 21, 2025 at 10:02 PM Paul Menzel <pmenzel@...gen.mpg.de> wrote:
>>
>>> What GPIO driver is it using? It's likely that it's not using the
>>> provider API correctly and this change uncovered it, I'd like to take
>>> a look at it and fix it.
>>
>> How do I find out? The commands below do not return anything.
>>
>> $ lsmod | grep gpio
>> $ lspci -nn | grep -i gpio
>> $ sudo dmesg | grep gpio
>> [ 5.150955] gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22
>> [Just these lines match.]
> If you have libgpiod-tools installed, you can post the output of
> gpiodetect here.
$ sudo gpiodetect
gpiochip0 [INT344B:00] (152 lines)
(In Debian the package name is *gpiod*.)
Kind regards,
Paul
Powered by blists - more mailing lists