From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Taniya Das <quic_tdas@quicinc.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/8] clk: qcom: lpassaudiocc-sc7280: Fix the regmap conflict warning
Date: Mon, 18 Mar 2024 08:52:28 +0100 [thread overview]
Message-ID: <97e4e9e6-76e3-4f26-8482-7641e5169549@linaro.org> (raw)
In-Reply-To: <20240318053555.20405-4-quic_tdas@quicinc.com>
On 18/03/2024 06:35, Taniya Das wrote:
> Update the lpassaudio_cc_reset regmap name and max register details
> to handle the regmap conflict warning between lpassaudio_cc_reset
> and lpassaudio_cc.
What conflict? How does this bug affect users? Explain this in commit msg.
>
> Fixes: a9dd26639d05 ("clk: qcom: lpass: Add support for LPASS clock controller for SC7280")
> Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
> ---
> drivers/clk/qcom/lpassaudiocc-sc7280.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/clk/qcom/lpassaudiocc-sc7280.c b/drivers/clk/qcom/lpassaudiocc-sc7280.c
> index d68139762a80..3f1e756a6e71 100644
> --- a/drivers/clk/qcom/lpassaudiocc-sc7280.c
> +++ b/drivers/clk/qcom/lpassaudiocc-sc7280.c
> @@ -755,6 +755,9 @@ static int lpass_audio_cc_sc7280_probe(struct platform_device *pdev)
> int ret;
>
> if (of_device_is_compatible(pdev->dev.of_node, "qcom,qcm6490-lpassaudiocc")) {
> + lpass_audio_cc_sc7280_regmap_config.name = "lpassaudio_cc_reset";
> + lpass_audio_cc_sc7280_regmap_config.max_register = 0xc8;
> +
> ret = qcom_cc_probe_by_index(pdev, 1, &lpass_audio_cc_reset_sc7280_desc);
> if (ret)
> dev_err(&pdev->dev, "Failed to register LPASS AUDIO CC Resets\n");
> @@ -787,6 +790,9 @@ static int lpass_audio_cc_sc7280_probe(struct platform_device *pdev)
> goto exit;
> }
>
> + lpass_audio_cc_sc7280_regmap_config.name = "lpassaudio_cc_reset";
> + lpass_audio_cc_sc7280_regmap_config.max_register = 0xc8;
Why do you have it in two places?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-03-18 7:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 5:35 [PATCH v2 0/8] Add updates for clock controllers to support QCM6490 Taniya Das
2024-03-18 5:35 ` [PATCH v2 1/8] dt-bindings: clock: qcom: Add compatible for QCM6490 boards Taniya Das
2024-03-18 7:11 ` Luca Weiss
2024-05-31 9:28 ` Taniya Das
2024-05-31 9:58 ` Luca Weiss
2024-03-18 7:47 ` Krzysztof Kozlowski
2024-05-31 9:28 ` Taniya Das
2024-03-18 7:50 ` Krzysztof Kozlowski
2024-03-18 5:35 ` [PATCH v2 2/8] clk: qcom: lpassaudiocc-sc7280: Add support for LPASS resets for QCM6490 Taniya Das
2024-03-18 7:50 ` Krzysztof Kozlowski
2024-05-31 9:28 ` Taniya Das
2024-03-18 7:51 ` Krzysztof Kozlowski
2024-03-18 5:35 ` [PATCH v2 3/8] clk: qcom: lpassaudiocc-sc7280: Fix the regmap conflict warning Taniya Das
2024-03-18 7:52 ` Krzysztof Kozlowski [this message]
2024-03-18 5:35 ` [PATCH v2 4/8] clk: qcom: sc7280: Update the transition delay for GDSC Taniya Das
2024-03-18 7:53 ` Krzysztof Kozlowski
2024-05-31 9:30 ` Taniya Das
2024-05-31 10:20 ` Dmitry Baryshkov
2024-03-18 5:35 ` [PATCH v2 5/8] clk: qcom: gcc-sc7280: Update force mem core bit for UFS ICE clock Taniya Das
2024-04-23 13:14 ` Konrad Dybcio
2024-03-18 5:35 ` [PATCH v2 6/8] clk: qcom: camcc-sc7280: Add parent dependency to all camera GDSCs Taniya Das
2024-04-23 13:14 ` Konrad Dybcio
2024-03-18 5:35 ` [PATCH v2 7/8] arm64: dts: qcom: qcm6490-idp: Update protected clocks list Taniya Das
2024-03-18 7:54 ` Krzysztof Kozlowski
2024-05-31 9:34 ` Taniya Das
2024-05-31 10:19 ` Dmitry Baryshkov
2024-03-18 5:35 ` [PATCH v2 8/8] arm64: dts: qcom: qcs6490-rb3gen2: Update the LPASS audio node Taniya Das
2024-03-18 7:55 ` Krzysztof Kozlowski
2024-04-23 13:16 ` Konrad Dybcio
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=97e4e9e6-76e3-4f26-8482-7641e5169549@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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