All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: webgeek1234@gmail.com, "Rafael J. Wysocki" <rafael@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v4 2/2] cpufreq: tegra124: Allow building as a module
Date: Tue, 20 May 2025 12:46:45 +0100	[thread overview]
Message-ID: <c4dc20c6-d0cd-4a2f-81be-e672ace75e67@nvidia.com> (raw)
In-Reply-To: <20250520103035.udl25zv2uriljrby@vireshk-i7>


On 20/05/2025 11:30, Viresh Kumar wrote:
> On 20-05-25, 11:03, Jon Hunter wrote:
>> On 19/05/2025 11:26, Viresh Kumar wrote:
>>> Not sure if we can do that. The clks belong to the CPU device, while
>>> the devm_* functions are using &pdev->dev. The CPU device never goes
>>> away and so the resources won't get freed if we use devm for the CPU
>>> device.
> 
> That would have been the case, if we can actually do a devm_clk_get()
> in the first place, but...
> 
>> I don't follow. If they are allocated in the probe using the pdev->dev
>> device by using devm_clk_get() they should get freed when the platform
>> device is removed.
> 
> ... devm_clk_get(&pdev->dev, ...) won't work here IIUC. The clks
> belong to the CPU device and not pdev->dev. That's why we are doing
> of_clk_get_by_name() over the CPU device's OF node here.
> 
> Maybe I am wrong, but I don't see how devm_* can be used here for
> clks.

Ah yes, we are using the 'np' pointer for the CPU node and not the 
platform device node. OK scratch that.

Jon

-- 
nvpublic


      reply	other threads:[~2025-05-20 11:46 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 ` [PATCH v4 1/2] cpufreq: tegra124: Remove use of disable_cpufreq Aaron Kling
2025-05-09  0:04   ` 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 [this message]

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=c4dc20c6-d0cd-4a2f-81be-e672ace75e67@nvidia.com \
    --to=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 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.