From: Genes Lists <lists@sapience.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: rc4 and later log message: gpiochip_add_data_with_key: get_direction failed
Date: Tue, 11 Mar 2025 10:03:59 -0400 [thread overview]
Message-ID: <1d8bf01be50646bb7b36abfc1ecb25eb997598dd.camel@sapience.com> (raw)
In-Reply-To: <579283e5c832d77aeed531e8680961c815557613.camel@sapience.com>
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
On Sat, 2025-03-08 at 15:45 -0500, Genes Lists wrote:
> ...
>
> there are now 194 lines logged on boot with:
>
> gpio gpiochip0: gpiochip_add_data_with_key: get_direction failed: -
> 22
>
For completeness - same log noise with rc5 and through commit
4d872d51bc9d7b899c1f61534e3dbde72613f627.
--
Gene
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-03-11 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 20:45 rc4 and later log message: gpiochip_add_data_with_key: get_direction failed Genes Lists
2025-03-11 14:03 ` Genes Lists [this message]
2025-03-11 17:40 ` Bartosz Golaszewski
2025-03-11 19:30 ` Genes Lists
2025-03-11 19:32 ` Genes Lists
2025-03-11 19:50 ` Bartosz Golaszewski
2025-03-11 20:53 ` Genes Lists
2025-03-16 12:48 ` Genes Lists
2025-03-28 10:00 ` rc4 and later log message: gpiochip_add_data_with_key: get_direction failed -> missing pinctrl patch Genes Lists
2025-03-28 11:00 ` Bartosz Golaszewski
2025-03-29 10:59 ` rc4 and later log message: gpiochip_add_data_with_key: get_direction failed -> pincntrl patch? Genes Lists
2025-03-31 7:36 ` Bartosz Golaszewski
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=1d8bf01be50646bb7b36abfc1ecb25eb997598dd.camel@sapience.com \
--to=lists@sapience.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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