From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: Mohit Sharma <mohit.sharma@oss.qualcomm.com>,
Srinivas Kandagatla <srini@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Mark Brown <broonie@kernel.org>
Cc: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: qcom: q6apm: Guard callbacks until probe data is ready
Date: Sun, 15 Nov 2026 10:06:24 +0000 [thread overview]
Message-ID: <9cde423b-e71a-4038-9e89-d6ecd7da5399@oss.qualcomm.com> (raw)
In-Reply-To: <20261022144130.2443667-2-mohit.sharma@oss.qualcomm.com>
On 10/22/26 3:41 PM, Mohit Sharma wrote:
> The GPR bus needs to make response callbacks available before invoking a
> client probe because clients can issue synchronous commands from probe.
> This creates a short interval where a callback can run before the client
> has published its private data.
>
> Make q6apm publish its driver data only after all callback-visible state
> has been initialized. Have the q6apm and q6prm callbacks ignore packets
> received before driver data is available.
>
> Fixes: ec1471a898cc ("soc: qcom: apr: Add GPR support")
> Cc: stable@vger.kernel.org
> Co-developed-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
> Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>
> Signed-off-by: Mohit Sharma <mohit.sharma@oss.qualcomm.com>
> ---
> sound/soc/qcom/qdsp6/q6apm.c | 6 ++++--
> sound/soc/qcom/qdsp6/q6prm.c | 3 +++
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/qcom/qdsp6/q6apm.c b/sound/soc/qcom/qdsp6/q6apm.c
> index 3ec3c5a18c7a..dbebb643cd5e 100644
> --- a/sound/soc/qcom/qdsp6/q6apm.c
> +++ b/sound/soc/qcom/qdsp6/q6apm.c
> @@ -872,8 +872,6 @@ static int apm_probe(gpr_device_t *gdev)
> if (!apm)
> return -ENOMEM;
>
> - dev_set_drvdata(dev, apm);
> -
> mutex_init(&apm->lock);
> apm->dev = dev;
> apm->gdev = gdev;
> @@ -887,6 +885,7 @@ static int apm_probe(gpr_device_t *gdev)
>
> idr_init(&apm->modules_idr);
>
> + dev_set_drvdata(dev, apm);
> g_apm = apm;
>
> q6apm_get_apm_state(apm);
> @@ -930,6 +929,9 @@ static int apm_callback(const struct gpr_resp_pkt *data, void *priv, int op)
> const struct gpr_hdr *hdr = &data->hdr;
> int graph_id, is_pos_buf;
>
> + if (!apm)
> + return 0;
This is going to silently drop the responses. What are these packets?
> +
> result = data->payload;
>
> switch (hdr->opcode) {
> diff --git a/sound/soc/qcom/qdsp6/q6prm.c b/sound/soc/qcom/qdsp6/q6prm.c
> index 2042ff1e8ff1..5c927ebd81f4 100644
> --- a/sound/soc/qcom/qdsp6/q6prm.c
> +++ b/sound/soc/qcom/qdsp6/q6prm.c
> @@ -194,6 +194,9 @@ static int prm_callback(const struct gpr_resp_pkt *data, void *priv, int op)
> const struct gpr_ibasic_rsp_result_t *result;
> const struct gpr_hdr *hdr = &data->hdr;
>
> + if (!prm)
> + return 0;
This is going to silently drop the responses.
> +
> switch (hdr->opcode) {
> case PRM_CMD_RSP_REQUEST_HW_RSC:
> case PRM_CMD_RSP_RELEASE_HW_RSC:
next prev parent reply other threads:[~2026-11-15 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 14:41 [PATCH 0/2] Fix GPR callback registration race during probe Mohit Sharma
2026-10-22 14:41 ` [PATCH 1/2] ASoC: qcom: q6apm: Guard callbacks until probe data is ready Mohit Sharma
2026-11-15 10:06 ` Srinivas Kandagatla [this message]
2026-10-22 14:41 ` [PATCH 2/2] soc: qcom: apr: Publish GPR callback before client probe Mohit Sharma
2026-11-14 15:25 ` Shawn Guo
2026-11-15 10:00 ` Srinivas Kandagatla
2026-11-02 22:38 ` (subset) [PATCH 0/2] Fix GPR callback registration race during probe Mark Brown
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=9cde423b-e71a-4038-9e89-d6ecd7da5399@oss.qualcomm.com \
--to=srinivas.kandagatla@oss.qualcomm.com \
--cc=ajay.nandam@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mohit.sharma@oss.qualcomm.com \
--cc=perex@perex.cz \
--cc=srini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
/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
all inboxes | Powered by JetHome®