[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210203220210.gm7j66cagcjd6g45@viti.kaiser.cx>
Date: Wed, 3 Feb 2021 23:02:10 +0100
From: Martin Kaiser <martin@...ser.cx>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Saravana Kannan <saravanak@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Marc Zyngier <maz@...nel.org>,
Tudor Ambarus <Tudor.Ambarus@...rochip.com>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Len Brown <lenb@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH v2 0/3] Make fw_devlink=on more forgiving
Thus wrote Geert Uytterhoeven (geert@...ux-m68k.org):
> > The property you are using is not a standard GPIO binding (-gpios,
> > gpio, gpios) and I'm not surprised it's not working. The gpio1 is
> > probably getting probe deferred and ends up running after "my_driver".
> So my_driver doesn't support deferred probe,
I know that the gpio definition in the device-tree is non-standard (and
should have been done differently).
Apart from this, the driver uses module_platform_driver_probe. My
understanding is that this prevents probe deferral.
Does this mean that from now on, a driver which requests a gpio must not
use module_platform_driver_probe?
Thanks,
Martin
Powered by blists - more mailing lists