From: Aaron Kling <webgeek1234@gmail.com>
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 v4 1/2] cpufreq: tegra124: Remove use of disable_cpufreq
Date: Thu, 08 May 2025 19:04:14 -0500 [thread overview]
Message-ID: <20250508-tegra124-cpufreq-v4-1-d142bcbd0234@gmail.com> (raw)
In-Reply-To: <20250508-tegra124-cpufreq-v4-0-d142bcbd0234@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 | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq/tegra124-cpufreq.c b/drivers/cpufreq/tegra124-cpufreq.c
index 514146d98bca2d8aa59980a14dff3487cd8045f6..bc0691e8971f9454def37f489e4a3e244100b9f4 100644
--- a/drivers/cpufreq/tegra124-cpufreq.c
+++ b/drivers/cpufreq/tegra124-cpufreq.c
@@ -168,7 +168,10 @@ 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);
+ priv->cpufreq_dt_pdev = ERR_PTR(-ENODEV);
+ }
return err;
}
--
2.48.1
WARNING: multiple messages have this Message-ID (diff)
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 v4 1/2] cpufreq: tegra124: Remove use of disable_cpufreq
Date: Thu, 08 May 2025 19:04:14 -0500 [thread overview]
Message-ID: <20250508-tegra124-cpufreq-v4-1-d142bcbd0234@gmail.com> (raw)
In-Reply-To: <20250508-tegra124-cpufreq-v4-0-d142bcbd0234@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 | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq/tegra124-cpufreq.c b/drivers/cpufreq/tegra124-cpufreq.c
index 514146d98bca2d8aa59980a14dff3487cd8045f6..bc0691e8971f9454def37f489e4a3e244100b9f4 100644
--- a/drivers/cpufreq/tegra124-cpufreq.c
+++ b/drivers/cpufreq/tegra124-cpufreq.c
@@ -168,7 +168,10 @@ 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);
+ priv->cpufreq_dt_pdev = ERR_PTR(-ENODEV);
+ }
return err;
}
--
2.48.1
next prev parent reply other threads:[~2025-05-09 0:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 0:04 [PATCH v4 0/2] Support building tegra124-cpufreq as a module Aaron Kling
2025-05-09 0:04 ` Aaron Kling via B4 Relay
2025-05-09 0:04 ` Aaron Kling [this message]
2025-05-09 0:04 ` [PATCH v4 1/2] cpufreq: tegra124: Remove use of disable_cpufreq Aaron Kling via B4 Relay
2025-05-09 11:04 ` Jon Hunter
2025-05-09 16:57 ` Aaron Kling
2025-05-14 16:26 ` Aaron Kling
2025-05-19 10:17 ` Viresh Kumar
2025-05-20 9:53 ` Jon Hunter
2025-05-20 10:02 ` Viresh Kumar
2025-05-28 17:29 ` Aaron Kling
2025-05-29 5:16 ` Viresh Kumar
2025-06-05 10:34 ` Jon Hunter
2025-06-05 10:51 ` Viresh Kumar
2025-06-30 18:43 ` Aaron Kling
2025-07-01 6:23 ` Viresh Kumar
2025-05-09 0:04 ` [PATCH v4 2/2] cpufreq: tegra124: Allow building as a module Aaron Kling
2025-05-09 0:04 ` Aaron Kling via B4 Relay
2025-05-09 13:37 ` Jon Hunter
2025-05-13 4:26 ` Aaron Kling
2025-05-14 10:31 ` Jon Hunter
2025-05-14 16:43 ` Aaron Kling
2025-05-15 6:41 ` Jon Hunter
2025-05-19 10:37 ` Viresh Kumar
2025-05-20 9:57 ` Jon Hunter
2025-05-20 10:33 ` Viresh Kumar
2025-05-20 15:38 ` Aaron Kling
2025-05-14 10:31 ` Jon Hunter
2025-05-14 16:30 ` Aaron Kling
2025-05-15 6:21 ` Jon Hunter
2025-05-19 10:26 ` Viresh Kumar
2025-05-20 10:03 ` Jon Hunter
2025-05-20 10:30 ` Viresh Kumar
2025-05-20 11:46 ` Jon Hunter
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=20250508-tegra124-cpufreq-v4-1-d142bcbd0234@gmail.com \
--to=webgeek1234@gmail.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.