[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAO-hwJJOW6QT-weKqTC5QJnP5e6EjJD3-d0-cxePpdHOj3Epkg@mail.gmail.com>
Date: Mon, 3 Jul 2023 16:06:38 +0200
From: Benjamin Tissoires <benjamin.tissoires@...hat.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
linux-gpio@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>
Subject: Re: [PATCH v1 0/3] gpiolib: Avpid modifying GPIO chip fwnode
On Mon, Jul 3, 2023 at 2:18 PM Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> wrote:
>
> Ideally the GPIO chip data structure has to be constant.
> In real life it's not true, but we can make it closer to
> that. Hence the series.
>
> Benjamin, would be nice it you can perform regression test for your
> case.
FWIW:
Tested-by: Benjamin Tissoires <bentiss@...nel.org>
I've tested Danny's series + my SSDT override, with and without your
series on top of the master of hid.git (v6.4+merge of the hid.git tree
for v6.5-rc1), and in both cases, I can access the I2C-HID node that
sits on top of the CP2112 USB adapter.
Cheers,
Benjamin
>
>
> Bart, the idea is that this series has to land immediately after
> v6.5-rc1 is out so we will have longer time to fix any downsides
> and regressions found, if any.
>
> Andy Shevchenko (3):
> gpiolib: of: Don't use GPIO chip fwnode in of_gpiochip_*()
> gpiolib: acpi: Don't use GPIO chip fwnode in acpi_gpiochip_find()
> gpiolib: Do not alter GPIO chip fwnode member
>
> drivers/gpio/gpiolib-acpi.c | 2 +-
> drivers/gpio/gpiolib-of.c | 6 +++---
> drivers/gpio/gpiolib.c | 16 ++++++++--------
> 3 files changed, 12 insertions(+), 12 deletions(-)
>
> --
> 2.40.0.1.gaa8946217a0b
>
Powered by blists - more mailing lists