From: Krzysztof Kozlowski <krzk@kernel.org>
To: webgeek1234@gmail.com, Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v6] memory: tegra210: Support interconnect framework
Date: Fri, 31 Oct 2025 14:19:17 +0100 [thread overview]
Message-ID: <865037d1-c89f-4142-a66f-3283c17bf533@kernel.org> (raw)
In-Reply-To: <20251027-t210-actmon-p2-v6-1-1c4bd227d676@gmail.com>
On 27/10/2025 18:48, Aaron Kling via B4 Relay wrote:
> +
> + err = dev_pm_opp_of_add_table(emc->dev);
> + if (err) {
> + if (err == -ENODEV)
> + dev_err_probe(emc->dev, err,
> + "OPP table not found, please update your device tree\n");
> + else
> + dev_err_probe(emc->dev, err, "failed to add OPP table\n");
> +
> + goto put_hw_table;
> + }
> +
> + max_opps = dev_pm_opp_get_opp_count(emc->dev);
> + if (max_opps <= 0) {
> + dev_err_probe(emc->dev, err, "Failed to add OPPs\n");
> + goto remove_table;
> + }
> +
> + if (emc->num_timings != max_opps) {
> + dev_err_probe(emc->dev, err, "OPP table does not match emc table\n");
> + goto remove_table;
> + }
> +
> + for (i = 0; i < emc->num_timings; i++) {
> + rate = emc->timings[i].rate * 1000;
> + opp = dev_pm_opp_find_freq_exact(emc->dev, rate, true);
> + if (IS_ERR(opp)) {
> + dev_err_probe(emc->dev, err, "Rate %lu not found in OPP table\n", rate);
> + goto remove_table;
> + }
> +
> + dev_pm_opp_put(opp);
> + }
> +
> + dev_info_once(emc->dev, "OPP HW ver. 0x%x, current clock rate %lu MHz\n",
> + hw_version, clk_get_rate(emc->clk) / 1000000);
> +
> + return 0;
> +
> +remove_table:
> + dev_pm_opp_of_remove_table(emc->dev);
> +put_hw_table:
> + dev_pm_opp_put_supported_hw(opp_token);
> +
> + return err;
> +}
> +
> static void tegra210_emc_detect(struct tegra210_emc *emc)
> {
> u32 value;
> @@ -1966,6 +2222,14 @@ static int tegra210_emc_probe(struct platform_device *pdev)
>
> tegra210_emc_debugfs_init(emc);
>
> + err = tegra210_emc_opp_table_init(emc);
> + if (!err) {
> + tegra210_emc_rate_requests_init(emc);
> + tegra210_emc_interconnect_init(emc);
This looks like new ABI or did I miss something and it is already
documented? If so please always mention in the changelog that bindings
are already merged to master tree.
Same question for earlier PM OPP.
> + } else if (err != -ENODEV) {
> + return err;
> + }
> +
> cd = devm_thermal_of_cooling_device_register(emc->dev, np, "emc", emc,
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-31 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 17:48 [PATCH v6] memory: tegra210: Support interconnect framework Aaron Kling via B4 Relay
2025-10-31 13:19 ` Krzysztof Kozlowski [this message]
2025-10-31 17:33 ` Aaron Kling
2025-11-03 13:53 ` Krzysztof Kozlowski
2025-11-05 14:59 ` Dan Carpenter
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=865037d1-c89f-4142-a66f-3283c17bf533@kernel.org \
--to=krzk@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=webgeek1234@gmail.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