From: wangdich9700@163.com
To: srini@kernel.org, broonie@kernel.org, tiwai@suse.com,
wangdich9700@163.com
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
wangdicheng@kylinos.cn
Subject: [PATCH 2/3] ASoC: qcom: lpass-hdmi: fix invalid rate error message
Date: Wed, 2 Sep 2026 15:19:42 +0800 [thread overview]
Message-ID: <20260902071943.522194-3-wangdich9700@163.com> (raw)
In-Reply-To: <20260902071943.522194-1-wangdich9700@163.com>
From: wangdicheng <wangdicheng@kylinos.cn>
The sampling rate switch reused the bitwidth error path, so an
unsupported rate logged "invalid bit width" with the bitwidth value.
Print the rate instead.
Signed-off-by: wangdicheng <wangdicheng@kylinos.cn>
---
sound/soc/qcom/lpass-hdmi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/soc/qcom/lpass-hdmi.c b/sound/soc/qcom/lpass-hdmi.c
index 8bbe43facdc1..dd0ae4fbc841 100644
--- a/sound/soc/qcom/lpass-hdmi.c
+++ b/sound/soc/qcom/lpass-hdmi.c
@@ -64,8 +64,8 @@ static int lpass_hdmi_daiops_hw_params(struct snd_pcm_substream *substream,
sampling_freq = LPASS_SAMPLING_FREQ48;
break;
default:
- dev_err(dai->dev, "%s invalid bit width given : %d\n",
- __func__, bitwidth);
+ dev_err(dai->dev, "%s invalid sampling rate given : %d\n",
+ __func__, rate);
return -EINVAL;
}
data_format = LPASS_DATA_FORMAT_LINEAR;
--
2.25.1
next prev parent reply other threads:[~2026-09-02 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 7:19 [PATCH 0/3] ASoC: qcom: misc fixes for LPASS driver wangdich9700
2026-09-02 7:19 ` [PATCH 1/3] ASoC: qcom: fix assorted whitespace issues wangdich9700
2026-09-02 7:19 ` wangdich9700 [this message]
2026-09-02 14:45 ` [PATCH 2/3] ASoC: qcom: lpass-hdmi: fix invalid rate error message Mark Brown
2026-09-02 7:19 ` [PATCH 3/3] ASoC: qcom: fix VA CDC DMA DAI range handling wangdich9700
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=20260902071943.522194-3-wangdich9700@163.com \
--to=wangdich9700@163.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=srini@kernel.org \
--cc=tiwai@suse.com \
--cc=wangdicheng@kylinos.cn \
/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.