[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z_gQyg_JXTBRjisf@surfacebook.localdomain>
Date: Thu, 10 Apr 2025 21:41:14 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Kees Bakker <kees@...erbout.nl>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-gpio@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, Mika Westerberg <westeri@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>
Subject: Re: [PATCH v1 2/2] gpiolib: acpi: Make sure we fill struct
acpi_gpio_info
Wed, Apr 09, 2025 at 08:16:59PM +0200, Kees Bakker kirjoitti:
> Op 09-04-2025 om 15:27 schreef Andy Shevchenko:
...
> Can you check and confirm that at least info.gpioint is filled in (or
> initialized)?
Yes, I can confirm this. And that's how I have tested it, on Intel
Edison/Arduino the first GPIO expander (PCAL9555, serviced by
drivers/gpio/gpio-pca953x.c) is able to deliver an interrupt to the SoC.
Before this series that doesn't show up, now it works as expected.
> The callers of `__acpi_find_gpio` pass in an uninitialized `struct
> acpi_gpio_info`
True.
> and after the call they read `info.gpioint`.
...when GPIO descriptor is valid.
...
Yes, I agree that NULLifying info maybe good to have, but I don't see currently
if we have bugs with it. Can you be more specific in case you have observed
anything wrong?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists