From: Johan Hovold <johan@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: 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>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: x1e78100-t14s: Enable fingerprint reader
Date: Tue, 7 Jan 2025 17:16:36 +0100 [thread overview]
Message-ID: <Z31TZHRjIHiSw-gT@hovoldconsulting.com> (raw)
In-Reply-To: <Z31PaEckuGQEZxyh@linaro.org>
On Tue, Jan 07, 2025 at 05:59:36PM +0200, Abel Vesa wrote:
> On 25-01-07 16:19:26, Johan Hovold wrote:
> > But I do indeed see something similar here on resume:
> >
> > [ 1891.737726] arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0xe3f6ddbec0, fsynr=0x510000, cbfrsynra=0x14e0, cb=3
> > [ 1891.737738] arm-smmu 15000000.iommu: FSR = 00000402 [Format=2 TF], SID=0x14e0
> > [ 1891.737746] arm-smmu 15000000.iommu: FSYNR0 = 00510000 [S1CBNDX=81 PLVL=0]
> > [ 1891.804342] r8152 7-1:1.0 eth0: carrier on
> > [ 1902.039158] xhci-hcd xhci-hcd.1.auto: xHCI host not responding to stop endpoint command
> > [ 1902.039191] xhci-hcd xhci-hcd.1.auto: xHCI host controller not responding, assume dead
> > [ 1902.039795] xhci-hcd xhci-hcd.1.auto: HC died; cleaning up
> > [ 1902.040050] usb 1-1: PM: dpm_run_callback(): usb_dev_resume returns -5
> > [ 1902.040272] usb 1-1: PM: failed to resume async: error -5
> > [ 1902.581479] OOM killer enabled.
> > [ 1902.586673] Restarting tasks ...
> > [ 1902.587565] usb 1-1: USB disconnect, device number 2
>
> Turns out it is the GDSC that has power status flags PWRSTS_OFF_ON when it
> should've had PWRSTS_RET_ON. Sent a fix here:
>
> https://lore.kernel.org/all/20250107-x1e80100-clk-gcc-fix-usb2-gdsc-pwrsts-v1-1-e15d1a5e7d80@linaro.org/
>
> With this patch, the above resume issue goes away entirely.
Indeed it does.
Johan
next prev parent reply other threads:[~2025-01-07 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 13:35 [PATCH] arm64: dts: qcom: x1e78100-t14s: Enable fingerprint reader Abel Vesa
2025-01-07 14:38 ` Abel Vesa
2025-01-07 15:19 ` Johan Hovold
2025-01-07 15:59 ` Abel Vesa
2025-01-07 16:16 ` Johan Hovold [this message]
2025-01-08 2:13 ` Bjorn Andersson
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=Z31TZHRjIHiSw-gT@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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