Re: [PATCH v2] gpiolib: Fix triggering "kobject: 'gpiochipX' is not initialized, yet" kobject_get() errors

[Bartosz Golaszewski <brgl@xxxxxxxx>]

On Wed, Apr 3, 2024 at 10:17 AM Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
>
> Hi,
>
> On 4/2/24 6:51 PM, Andy Shevchenko wrote:
> > On Tue, Apr 2, 2024 at 7:43 PM Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
> >>
> >> When a gpiochip gets added by loading a module, then another driver may
> >> be waiting for that gpiochip to load on the deferred-probe list.
> >>
> >> If the deferred-probe for the consumer of gpiochip then triggers between
> >> the gpiodev_add_to_list_unlocked() calls which makes gpio_device_find()
> >> see the chip and the gpiochip_setup_dev() later then gpio_device_find()
> >> does a kobject_get() on an uninitialzed kobject since the kobject is
> >
> > uninitialized
>
> Bartosz, can you fix this up while merging or do you prefer a v3?
>

Yes, queued for fixes.

Bart