linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Genes Lists <lists@sapience.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	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 15:30:52 -0400	[thread overview]
Message-ID: <962ff60ebdb9207354560f938de8f23e4d02f30a.camel@sapience.com> (raw)
In-Reply-To: <CAMRc=Mc6Tn9CZJA6EN_a0i=hiiz6jTr9oYLHdJ8iyrtsw+LmZw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

On Tue, 2025-03-11 at 10:40 -0700, Bartosz Golaszewski wrote:
> On Tue, 11 Mar 2025 15:03:59 +0100, Genes Lists <lists@sapience.com>
> said:
> > On Sat, 2025-03-08 at 15:45 -0500, Genes Lists wrote:
> > > 
> > >  gpio gpiochip0: gpiochip_add_data_with_key: get_direction
> > > failed: -
> > > 22
> 
> Hi Gene!
> 
> There are two problems here. The issue you're seeing is fixed in next
> but
> not in mainline due to my omission. I will send a patch for that.
> 
> On the other hand, the pinctrl driver in question should be fixed
> too.
> Can you try the following change:
> ...

> Bart


Thank you Bart.

I tested your pinctl patch on mainline (on commit
0b46b049d6eccd947c361018439fcb596e741d7a) and the same messages are
logged.  Presumably I also need the other patch from next as well.

I can wait till it gets to mainline or can pull from next - if so,
which commit(s) would I need to do that?

It's seems pretty minor, so happy to wait or can patch mainline and
test if you prefer.

thanks,

-- 
Gene


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-03-11 19:30 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
2025-03-11 17:40   ` Bartosz Golaszewski
2025-03-11 19:30     ` Genes Lists [this message]
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=962ff60ebdb9207354560f938de8f23e4d02f30a.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;
as well as URLs for NNTP newsgroup(s).