From: Kalle Valo <kvalo@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] wifi: ath11k: Defer on rproc_get failure
Date: Fri, 27 Oct 2023 11:25:28 +0300 [thread overview]
Message-ID: <87lebowjyf.fsf@kernel.org> (raw)
In-Reply-To: <20231027-ath11k-rproc-defer-v1-1-f6b6a812cd18@fairphone.com> (Luca Weiss's message of "Fri, 27 Oct 2023 08:57:18 +0200")
Luca Weiss <luca.weiss@fairphone.com> writes:
> If we already have gotten the rproc_handle (meaning the "qcom,rproc"
> property is defined in the devicetree), it's a valid state that the
> remoteproc module hasn't probed yet so we should defer probing instead
> of just failing to probe.
>
> This resolves a race condition when the ath11k driver probes and fails
> before the wpss remoteproc driver has probed, like the following:
>
> [ 6.232360] ath11k 17a10040.wifi: failed to get rproc
> [ 6.232366] ath11k 17a10040.wifi: failed to get rproc: -22
> [ 6.232478] ath11k: probe of 17a10040.wifi failed with error -22
> ...
> [ 6.252415] remoteproc remoteproc2: 8a00000.remoteproc is available
> [ 6.252776] remoteproc remoteproc2: powering up 8a00000.remoteproc
> [ 6.252781] remoteproc remoteproc2: Booting fw image qcom/qcm6490/fairphone5/wpss.mdt, size 7188
>
> So, defer the probe if we hit that so we can retry later once the wpss
> remoteproc is available.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
Did you test this on a real device? If yes, what ath11k hardware and firmware
did you use? We use Tested-on tag to document that:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/submittingpatches#tested-on_tag
I can add that in the pending branch if you provide the info.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: Jeff Johnson <quic_jjohnson@quicinc.com>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, ath11k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] wifi: ath11k: Defer on rproc_get failure
Date: Fri, 27 Oct 2023 11:25:28 +0300 [thread overview]
Message-ID: <87lebowjyf.fsf@kernel.org> (raw)
In-Reply-To: <20231027-ath11k-rproc-defer-v1-1-f6b6a812cd18@fairphone.com> (Luca Weiss's message of "Fri, 27 Oct 2023 08:57:18 +0200")
Luca Weiss <luca.weiss@fairphone.com> writes:
> If we already have gotten the rproc_handle (meaning the "qcom,rproc"
> property is defined in the devicetree), it's a valid state that the
> remoteproc module hasn't probed yet so we should defer probing instead
> of just failing to probe.
>
> This resolves a race condition when the ath11k driver probes and fails
> before the wpss remoteproc driver has probed, like the following:
>
> [ 6.232360] ath11k 17a10040.wifi: failed to get rproc
> [ 6.232366] ath11k 17a10040.wifi: failed to get rproc: -22
> [ 6.232478] ath11k: probe of 17a10040.wifi failed with error -22
> ...
> [ 6.252415] remoteproc remoteproc2: 8a00000.remoteproc is available
> [ 6.252776] remoteproc remoteproc2: powering up 8a00000.remoteproc
> [ 6.252781] remoteproc remoteproc2: Booting fw image qcom/qcm6490/fairphone5/wpss.mdt, size 7188
>
> So, defer the probe if we hit that so we can retry later once the wpss
> remoteproc is available.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
Did you test this on a real device? If yes, what ath11k hardware and firmware
did you use? We use Tested-on tag to document that:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/submittingpatches#tested-on_tag
I can add that in the pending branch if you provide the info.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-10-27 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 6:57 [PATCH] wifi: ath11k: Defer on rproc_get failure Luca Weiss
2023-10-27 6:57 ` Luca Weiss
2023-10-27 8:25 ` Kalle Valo [this message]
2023-10-27 8:25 ` Kalle Valo
2023-10-27 10:07 ` Luca Weiss
2023-10-27 10:07 ` Luca Weiss
2023-11-13 15:37 ` Kalle Valo
2023-11-13 15:37 ` Kalle Valo
2023-11-13 15:44 ` Luca Weiss
2023-11-13 15:44 ` Luca Weiss
2023-11-13 15:39 ` Kalle Valo
2023-11-13 15:39 ` Kalle Valo
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=87lebowjyf.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.