From: Aaron Kling via B4 Relay <devnull+webgeek1234.gmail.com@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, Aaron Kling <webgeek1234@gmail.com>
Subject: [PATCH v2 1/2] cpufreq: tegra124: Remove use of disable_cpufreq
Date: Mon, 21 Apr 2025 03:13:31 -0500 [thread overview]
Message-ID: <20250421-tegra124-cpufreq-v2-1-2f148cefa418@gmail.com> (raw)
In-Reply-To: <20250421-tegra124-cpufreq-v2-0-2f148cefa418@gmail.com>
From: Aaron Kling <webgeek1234@gmail.com>
Instead, unregister the cpufreq device for this fatal fail case.
Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
drivers/cpufreq/tegra124-cpufreq.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq/tegra124-cpufreq.c b/drivers/cpufreq/tegra124-cpufreq.c
index 514146d98bca2d8aa59980a14dff3487cd8045f6..dc83b1631b13ec428f3b6bbea89462448a62adb4 100644
--- a/drivers/cpufreq/tegra124-cpufreq.c
+++ b/drivers/cpufreq/tegra124-cpufreq.c
@@ -168,7 +168,8 @@ static int __maybe_unused tegra124_cpufreq_resume(struct device *dev)
disable_dfll:
clk_disable_unprepare(priv->dfll_clk);
disable_cpufreq:
- disable_cpufreq();
+ if (!IS_ERR(priv->cpufreq_dt_pdev))
+ platform_device_unregister(priv->cpufreq_dt_pdev);
return err;
}
--
2.48.1
next prev parent reply other threads:[~2025-04-21 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 8:13 [PATCH v2 0/2] Support building tegra124-cpufreq as a module Aaron Kling via B4 Relay
2025-04-21 8:13 ` Aaron Kling via B4 Relay [this message]
2025-04-21 10:56 ` [PATCH v2 1/2] cpufreq: tegra124: Remove use of disable_cpufreq Viresh Kumar
2025-04-21 8:13 ` [PATCH v2 2/2] cpufreq: tegra124: Allow building as a module Aaron Kling via B4 Relay
2025-04-21 10:58 ` Viresh Kumar
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=20250421-tegra124-cpufreq-v2-1-2f148cefa418@gmail.com \
--to=devnull+webgeek1234.gmail.com@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=viresh.kumar@linaro.org \
--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