linux-kernel - Re: Linux logs new warning `gpio gpiochip0: gpiochip_add_data_with_key: get

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdZbu=ii_Aq1rdNN_z+T0SBRpLEm-aoc-QnWW9OnA83+Vw@mail.gmail.com>
Date: Tue, 25 Feb 2025 22:25:00 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: brgl@...ev.pl, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Paul Menzel <pmenzel@...gen.mpg.de>, 
	Bartosz Golaszewski <bartosz.golaszewski@...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`

On Mon, Feb 24, 2025 at 9:51 AM <brgl@...ev.pl> wrote:

> In any case: Linus: what should be our policy here? There are some pinctrl
> drivers which return EINVAL if the pin in question is not in GPIO mode. I don't
> think this is an error. Returning errors should be reserved for read failures
> and so on. Are you fine with changing the logic here to explicitly default to
> INPUT as until recently all errors would be interpreted as such anyway?

Oh hm I guess. There was no defined semantic until now anyway. Maybe
Andy has something to say about it though, it's very much his pin controller.

Yours,
Linus Walleij