linux-kernel - Re: [PATCH v2 00/11] x86-android-tablets: convert to use GPIO references

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: <4wl35ypnwhklcloiqh6y5ejzhuhg24e5ogzo4flph667ft43pt@3pzl5fbv7lbw>
Date: Mon, 11 Aug 2025 09:03:36 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Hans de Goede <hansg@...nel.org>
Cc: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>, 
	Arnd Bergmann <arnd@...nel.org>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 00/11] x86-android-tablets: convert to use GPIO
 references

Hi Hans,

On Mon, Aug 11, 2025 at 11:41:46AM +0200, Hans de Goede wrote:
> Hi Dmitry,
> 
> On 11-Aug-25 4:22 AM, Dmitry Torokhov wrote:
> > This series came about because now software nodes can be used to
> > describe GPIOs (via PROPERTY_ENTRY_GPIO() macros) and I would like to
> > eventually get rid of gpio_keys_platform_data structure.
> > 
> > So while I was doing the conversions from GPIO_LOOKUP() tables for
> > gpio_keys devices I decided to convert the rest of them as well. Maybe
> > some time in the future we can drop support for GPIO_LOOKUP() and rely
> > on device properties exclusively.
> > 
> > This is completely untested.
> > 
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@...il.com>
> > ---
> > Changes in v2:
> > - Reworked on top of the current linux-next
> > - Link to v1: https://lore.kernel.org/r/20230512001815.591817-1-dmitry.torokhov@gmail.com
> 
> Thanks this is an interesting series. I don't know why I missed / dropped
> the ball on v1.

It's actually on me: I sent it as you were reworking/adding more devices
to the driver and I was supposed to update the series but did not have
time.

> 
> It will be a while before I can get around to this due to travel, but
> I'll take a look and either provide a Tested-by or fixup any issues
> I encounter and then post a fixed v3 myself.

Thanks!

-- 
Dmitry