From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Linux logs new warning `gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22`
Date: Sun, 23 Feb 2025 23:04:05 +0100 [thread overview]
Message-ID: <a8c9b81c-bc0d-4ed5-845e-ecbf5e341064@molgen.mpg.de> (raw)
In-Reply-To: <CAMRc=Mf-ObnFzau9OO1RvsdJ-pj4Tq2BSjVvCXkHgkK2t5DECQ@mail.gmail.com>
Dear Bortosz,
Am 23.02.25 um 21:54 schrieb Bartosz Golaszewski:
> On Fri, Feb 21, 2025 at 10:02 PM Paul Menzel <pmenzel@molgen.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
next prev parent reply other threads:[~2025-02-23 22:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 20:40 Linux logs new warning `gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22` Paul Menzel
2025-02-21 20:53 ` Bartosz Golaszewski
2025-02-21 21:02 ` Paul Menzel
2025-02-23 20:54 ` Bartosz Golaszewski
2025-02-23 22:04 ` Paul Menzel [this message]
2025-02-24 8:51 ` brgl
2025-02-25 20:43 ` Paul Menzel
2025-02-25 21:25 ` Linus Walleij
2025-02-26 13:37 ` Andy Shevchenko
2025-02-26 13:46 ` Andy Shevchenko
2025-02-26 14:14 ` Bartosz Golaszewski
2025-02-26 14:22 ` Andy Shevchenko
2025-03-14 11:54 ` Paul Menzel
2025-03-14 12:19 ` Bartosz Golaszewski
2025-03-14 12:25 ` Paul Menzel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8c9b81c-bc0d-4ed5-845e-ecbf5e341064@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).