From: "MINETTE Alexandre" <contact@alex-min.fr>
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: "David Heidelberg" <david@ixit.cz>,
"Linus Walleij" <linusw@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Guru Das Srinagesh" <linux@gurudas.dev>,
"Rob Clark" <robin.clark@oss.qualcomm.com>,
"Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Kees Cook" <kees@kernel.org>, "Tony Luck" <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
iommu@lists.linux.dev, phone-devel@vger.kernel.org
Subject: Re: [PATCH v3 3/8] pinctrl: qcom: Register functions before enabling pinctrl
Date: Wed, 03 Jun 2026 14:44:47 +0200 [thread overview]
Message-ID: <56ee469e-dab0-49fa-b808-d421b7505622@app.fastmail.com> (raw)
In-Reply-To: <thj65jrvef3z3dmn5f52jplewrjgklomc5s32grktsjejs72sw@npk26yx2hpf7>
Right, thanks for checking.
I do not own the Nexus 7 flo/deb, so I cannot verify whether it needs
this in the same way as jflte. I mentioned it because another
postmarketOS contributor told me this patch helped on that device, but
it is also possible that I misunderstood the failure they were seeing.
--
MINETTE Alexandre
contact@alex-min.fr
Mer 03 juin 2026, à 14:29, Dmitry Baryshkov a écrit :
> 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
>> contact@alex-min.fr
>>
>> 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
next prev parent reply other threads:[~2026-06-03 12:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 7:16 [PATCH v3 0/8] Add Samsung Galaxy S4 support Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` [PATCH v3 1/8] dt-bindings: arm: qcom: Add Samsung Galaxy S4 Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` [PATCH v3 2/8] dt-bindings: extcon: qcom,pm8941-misc: Add PM8921 compatible Alexandre MINETTE via B4 Relay
2026-05-19 7:42 ` sashiko-bot
2026-05-20 7:22 ` Krzysztof Kozlowski
2026-06-03 9:16 ` MINETTE Alexandre
2026-05-19 7:16 ` [PATCH v3 3/8] pinctrl: qcom: Register functions before enabling pinctrl Alexandre MINETTE via B4 Relay
2026-05-19 8:12 ` sashiko-bot
2026-05-19 8:31 ` Linus Walleij
2026-05-19 8:48 ` MINETTE Alexandre
2026-05-19 21:03 ` David Heidelberg
2026-06-03 8:58 ` MINETTE Alexandre
2026-06-03 12:29 ` Dmitry Baryshkov
2026-06-03 12:44 ` MINETTE Alexandre [this message]
2026-06-11 11:32 ` Konrad Dybcio
2026-06-11 13:01 ` Linus Walleij
2026-05-19 7:16 ` [PATCH v3 4/8] iommu/msm: Look up masters per IOMMU instance Alexandre MINETTE via B4 Relay
2026-05-19 8:43 ` sashiko-bot
2026-05-19 7:16 ` [PATCH v3 5/8] extcon: qcom-spmi-misc: Add PM8921 compatible Alexandre MINETTE via B4 Relay
2026-05-19 9:05 ` sashiko-bot
2026-05-19 7:16 ` [PATCH v3 6/8] ARM: dts: qcom: apq8064: Fix USB controller clocks Alexandre MINETTE via B4 Relay
2026-05-19 9:25 ` sashiko-bot
2026-05-19 7:16 ` [PATCH v3 7/8] ARM: dts: qcom: pm8921: Add USB ID extcon Alexandre MINETTE via B4 Relay
2026-05-19 9:41 ` sashiko-bot
2026-05-19 7:16 ` [PATCH v3 8/8] ARM: dts: qcom: Add Samsung Galaxy S4 Alexandre MINETTE via B4 Relay
2026-05-19 9:50 ` sashiko-bot
2026-05-25 9:01 ` Linus Walleij
2026-05-21 10:41 ` Konrad Dybcio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56ee469e-dab0-49fa-b808-d421b7505622@app.fastmail.com \
--to=contact@alex-min.fr \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gpiccoli@igalia.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@gurudas.dev \
--cc=myungjoo.ham@samsung.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=robin.murphy@arm.com \
--cc=tony.luck@intel.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox