From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, regressions@lists.linux.dev
Subject: Linux logs new warning `gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22`
Date: Fri, 21 Feb 2025 21:40:25 +0100 [thread overview]
Message-ID: <9ded85ef-46f1-4682-aabd-531401b511e5@molgen.mpg.de> (raw)
Dear Bartosz,
On the Intel Kaby Lake Dell XPS 13 9360, Linux 6.14-rc3+ with your
commit 9d846b1aebbe (gpiolib: check the return value of
gpio_chip::get_direction()) prints 52 new warnings:
$ dmesg
[…]
[ 0.000000] DMI: Dell Inc. XPS 13 9360/0596KF, BIOS 2.21.0
06/02/2022
[…]
[ 5.148927] pci 0000:00:1d.0: PCI bridge to [bus 3c]
[ 5.150955] gpio gpiochip0: gpiochip_add_data_with_key:
get_direction failed: -22
[50 times the same]
[ 5.151639] gpio gpiochip0: gpiochip_add_data_with_key:
get_direction failed: -22
[ 5.151768] ACPI: PCI: Interrupt link LNKA configured for IRQ 11
[…]
$ lspci -nn -k -s 1d.0
00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI
Express Root Port #9 [8086:9d18] (rev f1)
Subsystem: Dell Device [1028:075b]
Kernel driver in use: pcieport
Judging from the commit messages, this is expected. But what should a
user seeing this do now?
Also, it probably should not be applied to the stable series, as people
might monitor warnings and new warnings in stable series might be
unexpected.
Kind regards,
Paul
[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9d846b1aebbe488f245f1aa463802ff9c34cc078
next reply other threads:[~2025-02-21 20:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 20:40 Paul Menzel [this message]
2025-02-21 20:53 ` Linux logs new warning `gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -22` Bartosz Golaszewski
2025-02-21 21:02 ` Paul Menzel
2025-02-23 20:54 ` Bartosz Golaszewski
2025-02-23 22:04 ` Paul Menzel
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=9ded85ef-46f1-4682-aabd-531401b511e5@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=bartosz.golaszewski@linaro.org \
--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).