From: Stephen Boyd <sboyd@kernel.org>
To: Mohammad Rafi Shaik <quic_mohs@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_visr@quicinc.com
Subject: Re: [PATCH v9 4/4] clk: qcom: lpassaudiocc-sc7280: Modify qcom_cc_probe to qcom_cc_probe_by_index
Date: Thu, 23 Mar 2023 13:46:33 -0700 [thread overview]
Message-ID: <8e0fac7e756272e2593e7c220f9ae69f.sboyd@kernel.org> (raw)
In-Reply-To: <5b3fcceb-1a0d-d0c7-910d-eb4e65892676@quicinc.com>
Quoting Mohammad Rafi Shaik (2023-03-23 00:45:26)
>
> On 3/17/2023 11:57 PM, Stephen Boyd wrote:
> > Quoting Mohammad Rafi Shaik (2023-03-17 07:16:22)
> >> Modify AHB clocks explicit registration from qcom_cc_probe to
> >> qcom_cc_probe_by_index.
> > Why? Isn't it the same?
> yes, it is same.
>
> As per the previous version review comment, modified qcom_cc_probe to
> qcom_cc_probe_by_index.
Previously you were probing with index 1. That necessitated using
qcom_cc_probe_by_index() instead of qcom_cc_probe(). That is no longer
the case though, so this patch is unnecessary.
prev parent reply other threads:[~2023-03-23 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 14:16 [PATCH v9 0/4] Add resets for ADSP based audio clock controller driver Mohammad Rafi Shaik
2023-03-17 14:16 ` [PATCH v9 1/4] dt-bindings: clock: qcom,sc7280-lpasscc: Add qcom,adsp-pil-mode property Mohammad Rafi Shaik
2023-03-17 14:16 ` [PATCH v9 2/4] clk: qcom: lpasscc-sc7280: Skip qdsp6ss clock registration Mohammad Rafi Shaik
2023-03-17 18:30 ` Stephen Boyd
2023-03-17 14:16 ` [PATCH v9 3/4] clk: qcom: lpassaudiocc-sc7280: Add required gdsc power domain clks in lpass_cc_sc7280_desc strcuture Mohammad Rafi Shaik
2023-03-17 18:43 ` Stephen Boyd
2023-03-20 5:46 ` Mohammad Rafi Shaik
2023-03-17 14:16 ` [PATCH v9 4/4] clk: qcom: lpassaudiocc-sc7280: Modify qcom_cc_probe to qcom_cc_probe_by_index Mohammad Rafi Shaik
2023-03-17 18:27 ` Stephen Boyd
2023-03-23 7:45 ` Mohammad Rafi Shaik
2023-03-23 20:46 ` Stephen Boyd [this message]
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=8e0fac7e756272e2593e7c220f9ae69f.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mohs@quicinc.com \
--cc=quic_visr@quicinc.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