public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
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 v6 0/3] Support building tegra124-cpufreq as a module
Date: Mon, 07 Jul 2025 16:17:12 -0500	[thread overview]
Message-ID: <20250707-tegra124-cpufreq-v6-0-fe69c0f9bbab@gmail.com> (raw)

This adds remove and exit routines that were not previously needed when
this was only available builtin.

Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
---
Changes in v6:
- Simplify one of the error checks, per review
- Rename the global platform device to be more descriptive
- Link to v5: https://lore.kernel.org/r/20250702-tegra124-cpufreq-v5-0-66ab3640a570@gmail.com

Changes in v5:
- Add register helper function to cpufreq-dt for kernel users to use to
  establish a depmod dependency
- Drop patch that removes use of disable_cpufreq and re-add the patch to
  export said function
- Link to v4: https://lore.kernel.org/r/20250508-tegra124-cpufreq-v4-0-d142bcbd0234@gmail.com

Changes in v4:
- Move clock puts to remove instead of exit
- Link to v3: https://lore.kernel.org/r/20250421-tegra124-cpufreq-v3-0-95eaba968467@gmail.com

Changes in v3:
- In patch 1, set cpufreq_dt_pdev to an error after unregister on fail
  to prevent a potential double unregister on remove
- In patch 2, clean up clocks on exit
- Link to v2: https://lore.kernel.org/r/20250421-tegra124-cpufreq-v2-0-2f148cefa418@gmail.com

Changes in v2:
- Replace patch 1 with a patch to not use the unexported function
- Update patch 2 to add remove and exit routines
- Link to v1: https://lore.kernel.org/r/20250420-tegra124-cpufreq-v1-0-0a47fe126091@gmail.com

---
Aaron Kling (3):
      cpufreq: Export disable_cpufreq()
      cpufreq: dt: Add register helper
      cpufreq: tegra124: Allow building as a module

 drivers/cpufreq/Kconfig.arm        |  2 +-
 drivers/cpufreq/cpufreq-dt.c       | 11 ++++++++++
 drivers/cpufreq/cpufreq-dt.h       |  2 ++
 drivers/cpufreq/cpufreq.c          |  1 +
 drivers/cpufreq/tegra124-cpufreq.c | 44 +++++++++++++++++++++++++++++---------
 5 files changed, 49 insertions(+), 11 deletions(-)
---
base-commit: 91e5bfe317d8f8471fbaa3e70cf66cae1314a516
change-id: 20250401-tegra124-cpufreq-fd944fdce62c

Best regards,
-- 
Aaron Kling <webgeek1234@gmail.com>



             reply	other threads:[~2025-07-07 21:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-07 21:17 Aaron Kling via B4 Relay [this message]
2025-07-07 21:17 ` [PATCH v6 1/3] cpufreq: Export disable_cpufreq() Aaron Kling via B4 Relay
2025-07-09  7:19   ` Rafael J. Wysocki
2025-07-07 21:17 ` [PATCH v6 2/3] cpufreq: dt: Add register helper Aaron Kling via B4 Relay
2025-07-07 21:17 ` [PATCH v6 3/3] cpufreq: tegra124: Allow building as a module Aaron Kling via B4 Relay
2025-07-09  8:12 ` [PATCH v6 0/3] Support building tegra124-cpufreq " 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=20250707-tegra124-cpufreq-v6-0-fe69c0f9bbab@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