From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Ajit Pandey <ajitp@codeaurora.org>,
broonie@kernel.org, plai@codeaurora.org, bgoswami@codeaurora.org
Cc: alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/7] ASoC: qcom: Add common array to initialize soc based core clocks
Date: Mon, 18 May 2020 10:11:06 +0100 [thread overview]
Message-ID: <aa1ad5a5-94e8-0a6a-1937-e9d2abbb67f7@linaro.org> (raw)
On 14/05/2020 17:38, Ajit Pandey wrote:
> AHB-I/X bus clocks inside LPASS coreis not a mandatory clocks for
> SC7180 soc lpass variants, hence make it an optional one.
>
> Signed-off-by: Ajit Pandey <ajitp@codeaurora.org>
> ---
For some reason patch subject seems messed up!
I see two patches with same subject "[PATCH v2 2/7] ASoC: qcom: Add
common array to initialize soc based core clocks" and totally different
content and PATCH v2 3/7 is missing as well!
--srini
> sound/soc/qcom/lpass-cpu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/soc/qcom/lpass-cpu.c b/sound/soc/qcom/lpass-cpu.c
> index e00a4af..729ca78 100644
> --- a/sound/soc/qcom/lpass-cpu.c
> +++ b/sound/soc/qcom/lpass-cpu.c
> @@ -594,7 +594,7 @@ int asoc_qcom_lpass_cpu_platform_probe(struct platform_device *pdev)
> }
> }
>
> - drvdata->ahbix_clk = devm_clk_get(dev, "ahbix-clk");
> + drvdata->ahbix_clk = devm_clk_get_optional(dev, "ahbix-clk");
> if (IS_ERR(drvdata->ahbix_clk)) {
> dev_err(dev, "error getting ahbix-clk: %ld\n",
> PTR_ERR(drvdata->ahbix_clk));
>
next reply other threads:[~2020-05-18 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 9:11 Srinivas Kandagatla [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-16 18:06 [PATCH v2 2/7] ASoC: qcom: Add common array to initialize soc based core clocks Ajit Pandey
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=aa1ad5a5-94e8-0a6a-1937-e9d2abbb67f7@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=ajitp@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plai@codeaurora.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).