[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdas4qF51eesZ-M2+7wzp1t81qYSZSyxsmm-zAuvcaE2Pg@mail.gmail.com>
Date: Fri, 3 Aug 2018 19:18:43 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Dmitry Osipenko <digetx@...il.com>
Cc: "thierry.reding@...il.com" <thierry.reding@...il.com>,
Jon Hunter <jonathanh@...dia.com>,
Stefan Agner <stefan@...er.ch>,
Marcel Ziswiler <marcel@...wiler.com>,
linux-tegra@...r.kernel.org,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 1/2] pinctrl: tegra: Move drivers registration to
arch_init level
On Thu, Aug 2, 2018 at 1:12 PM Dmitry Osipenko <digetx@...il.com> wrote:
> There is a bug in regards to deferred probing within the drivers core
> that causes GPIO-driver to suspend after its users. The bug appears if
> GPIO-driver probe is getting deferred, which happens after introducing
> dependency on PINCTRL-driver for the GPIO-driver by defining "gpio-ranges"
> property in device-tree. The bug in the drivers core is old (more than 4
> years now) and is well known, unfortunately there is no easy fix for it.
> The good news is that we can workaround the deferred probe issue by
> changing GPIO / PINCTRL drivers registration order and hence by moving
> PINCTRL driver registration to the arch_init level and GPIO to the
> subsys_init.
>
> Signed-off-by: Dmitry Osipenko <digetx@...il.com>
Patch applied with Stefan's ACK.
Yours,
Linus Walleij
Powered by blists - more mailing lists