linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
	Taniya Das <tdas@codeaurora.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
	linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org, robh+dt@kernel.org,
	Taniya Das <tdas@codeaurora.org>
Subject: Re: [PATCH v4 2/2] clk: qcom: lpass: Add support for LPASS clock controller for SC7280
Date: Thu, 17 Feb 2022 14:42:58 -0800	[thread overview]
Message-ID: <20220217224259.AED00C340E8@smtp.kernel.org> (raw)
In-Reply-To: <20220126081236.25255-3-tdas@codeaurora.org>

Quoting Taniya Das (2022-01-26 00:12:36)
> diff --git a/drivers/clk/qcom/lpassaudiocc-sc7280.c b/drivers/clk/qcom/lpassaudiocc-sc7280.c
> new file mode 100644
> index 000000000000..c97ead75f02a
> --- /dev/null
> +++ b/drivers/clk/qcom/lpassaudiocc-sc7280.c
> @@ -0,0 +1,838 @@
> +// SPDX-License-Identifier: GPL-2.0-only
[...]
> +
> +static int lpass_audio_cc_sc7280_probe(struct platform_device *pdev)
> +{
> +       const struct qcom_cc_desc *desc;
> +       struct regmap *regmap;
> +       int ret;
> +
> +       ret = lpassaudio_create_pm_clks(pdev);
> +       if (ret)
> +               return ret;
> +
> +       lpass_audio_cc_sc7280_regmap_config.name = "lpassaudio_cc";
> +       lpass_audio_cc_sc7280_regmap_config.max_register = 0x2f000;
> +       desc = &lpass_audio_cc_sc7280_desc;
> +
> +       regmap = qcom_cc_map(pdev, desc);
> +       if (IS_ERR(regmap)) {
> +               pm_runtime_disable(&pdev->dev);
> +               return PTR_ERR(regmap);
> +       }
> +
> +       clk_zonda_pll_configure(&lpass_audio_cc_pll, regmap, &lpass_audio_cc_pll_config);
> +
> +       ret = qcom_cc_really_probe(pdev, &lpass_audio_cc_sc7280_desc, regmap);
> +       if (ret) {
> +               dev_err(&pdev->dev, "Failed to register LPASS AUDIO CC clocks\n");
> +               pm_runtime_disable(&pdev->dev);
> +               return ret;
> +       }
> +
> +       /* PLL settings */
> +       regmap_write(regmap, 0x4, 0x3b);
> +       regmap_write(regmap, 0x8, 0xff05);

Shouldn't this be done before registering the clks? So after
zonda_pll_configure?

> +
> +       pm_runtime_mark_last_busy(&pdev->dev);
> +       pm_runtime_put_autosuspend(&pdev->dev);
> +       pm_runtime_put_sync(&pdev->dev);

  reply	other threads:[~2022-02-17 22:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  8:12 [PATCH v4 0/2] Add support for LPASS Core and Audio Clock for SC7280 Taniya Das
2022-01-26  8:12 ` [PATCH v4 1/2] dt-bindings: clock: Add YAML schemas for LPASS clocks on SC7280 Taniya Das
2022-02-04 23:17   ` Rob Herring
2022-02-17 22:40   ` Stephen Boyd
2022-01-26  8:12 ` [PATCH v4 2/2] clk: qcom: lpass: Add support for LPASS clock controller for SC7280 Taniya Das
2022-02-17 22:42   ` Stephen Boyd [this message]
2022-04-13 14:30 ` [PATCH v4 0/2] Add support for LPASS Core and Audio Clock " patchwork-bot+linux-arm-msm

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=20220217224259.AED00C340E8@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=rnayak@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=tdas@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).