Re: [PATCH v3 3/8] pinctrl: qcom: Register functions before enabling pinctrl
Dmitry Baryshkov <[email protected]>
| Newsgroups | org.kernel.vger.phone-devel,dev.linux.lists.iommu,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-gpio,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <thj65jrvef3z3dmn5f52jplewrjgklomc5s32grktsjejs72sw@npk26yx2hpf7> |
On Wed, Jun 03, 2026 at 10:58:24AM +0200, MINETTE Alexandre wrote: > Thanks David. > > I initially considered adding a Fixes: tag, but I do not have a commit I > can point to. This looks like a latent ordering issue in the > Qualcomm pinctrl probe path and could have happened at any time until now. > > The failure became visible on APQ8064 boards such as this jflte, and I also > have a report that the same change helps flo/deb, but I do not want to > add a misleading Fixes tag as we don't really know which commit really triggered the race condition. But there are no gpio-hogs on Nexus7/flo. > -- > MINETTE Alexandre > [email protected] > > Mar 19 mai 2026, à 23:03, David Heidelberg a écrit : > > On 19/05/2026 10:48, MINETTE Alexandre wrote: > >> Thanks a lot Linus! > >> > >> This patch is required for my Samsung Galaxy S4 GT-I9505 to boot but I also > >> have confirmation from another contributor that the same pinctrl patch > >> helped boot the ASUS Nexus 7 (2013), codenamed flo, which is also based > >> on APQ8064. > >> > > > > Hello Alex, > > > > if what you wrote about asus-flo/deb is true, then this patch should have > > `Fixes: ` tag, as I remember it was booting with few limited patches ~5 years > > back then (only one serious was hack for proper clock bringup). > > > > David > > > > -- > > David Heidelberg -- With best wishes Dmitry