From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
robh+dt@kernel.org, krzk+dt@kernel.org
Cc: alsa-devel@alsa-project.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: qcom: lpass: Fix apq8016 compat string to match yaml
Date: Tue, 19 Apr 2022 10:10:28 +0100 [thread overview]
Message-ID: <72ca1cd4-da90-9e4c-b326-46eef2e1cb58@linaro.org> (raw)
In-Reply-To: <20220418230956.3059563-2-bryan.odonoghue@linaro.org>
On 19/04/2022 00:09, Bryan O'Donoghue wrote:
> The documented yaml compat string for the apq8016 is
> "qcom,apq8016-lpass-cpu" not "qcom,lpass-cpu-apq8016". Looking at the other
> lpass compat strings the general form is "qcom,socnum-lpass-cpu".
>
> We need to fix both the driver and dts to match.
Fixes tag is missing.
>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
other than that it LGTM.
Reviewed-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
--srini
> ---
> sound/soc/qcom/lpass-apq8016.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/qcom/lpass-apq8016.c b/sound/soc/qcom/lpass-apq8016.c
> index 3efa133d1c64..10edc5e9c8ef 100644
> --- a/sound/soc/qcom/lpass-apq8016.c
> +++ b/sound/soc/qcom/lpass-apq8016.c
> @@ -292,7 +292,7 @@ static struct lpass_variant apq8016_data = {
> };
>
> static const struct of_device_id apq8016_lpass_cpu_device_id[] __maybe_unused = {
> - { .compatible = "qcom,lpass-cpu-apq8016", .data = &apq8016_data },
> + { .compatible = "qcom,apq8016-lpass-cpu", .data = &apq8016_data },
> {}
> };
> MODULE_DEVICE_TABLE(of, apq8016_lpass_cpu_device_id);
next prev parent reply other threads:[~2022-04-19 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 23:09 [PATCH 0/2] Fix apq8016 compat string Bryan O'Donoghue
2022-04-18 23:09 ` [PATCH 1/2] ASoC: qcom: lpass: Fix apq8016 compat string to match yaml Bryan O'Donoghue
2022-04-19 9:10 ` Srinivas Kandagatla [this message]
2022-04-18 23:09 ` [PATCH 2/2] arm64: dts: qcom: " Bryan O'Donoghue
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=72ca1cd4-da90-9e4c-b326-46eef2e1cb58@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).