public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sumit Gupta <sumitg@nvidia.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: <rafael@kernel.org>, <treding@nvidia.com>, <jonathanh@nvidia.com>,
	<linux-pm@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <bbasu@nvidia.com>
Subject: Re: [Patch v2] cpufreq: tegra194: remove opp table in exit hook
Date: Mon, 28 Aug 2023 17:55:01 +0530	[thread overview]
Message-ID: <d3318a98-4d61-73f7-07ab-787624edfdcd@nvidia.com> (raw)
In-Reply-To: <20230828101721.zq5vlc53p5umi63c@vireshk-i7>



On 28/08/23 15:47, Viresh Kumar wrote:
> External email: Use caution opening links or attachments
> 
> 
> On 28-08-23, 11:41, Viresh Kumar wrote:
>> On 25-08-23, 16:46, Sumit Gupta wrote:
>>> Add exit hook and remove OPP table when the device gets unregistered.
>>> This will fix the error messages when the CPU FREQ driver module is
>>> removed and then re-inserted. It also fixes these messages while
>>> onlining the first CPU from a policy whose all CPU's were previously
>>> offlined.
>>>
>>>   debugfs: File 'cpu5' in directory 'opp' already present!
>>>   debugfs: File 'cpu6' in directory 'opp' already present!
>>>   debugfs: File 'cpu7' in directory 'opp' already present!
>>>
>>> Fixes: f41e1442ac5b ("cpufreq: tegra194: add OPP support and set bandwidth")
>>> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
>>> ---
>>>
>>> v1[1] -> v2:
>>> - updated commit description.
>>>
>>> [1] https://lore.kernel.org/lkml/20230809153455.29056-1-sumitg@nvidia.com/
>>>
>>>   drivers/cpufreq/tegra194-cpufreq.c | 13 +++++++++++++
>>>   1 file changed, 13 insertions(+)
>>>
>>> diff --git a/drivers/cpufreq/tegra194-cpufreq.c b/drivers/cpufreq/tegra194-cpufreq.c
>>> index c90b30469165..66a9c23544db 100644
>>> --- a/drivers/cpufreq/tegra194-cpufreq.c
>>> +++ b/drivers/cpufreq/tegra194-cpufreq.c
>>> @@ -454,6 +454,8 @@ static int tegra_cpufreq_init_cpufreq_table(struct cpufreq_policy *policy,
>>>              if (ret < 0)
>>>                      return ret;
>>>
>>> +           dev_pm_opp_put(opp);
>>> +
>>
>> Missed this earlier, can you please do this in a separate patch please
>> ?
> 
> I have pushed rest of this commit and dropped this part. Send it
> separately. Thanks.
> 
> --
> viresh

Thank you.
Sent the change separately @
  https://lore.kernel.org/lkml/20230828120959.24680-1-sumitg@nvidia.com/

Regards,
Sumit Gupta

      reply	other threads:[~2023-08-28 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 11:16 [Patch v2] cpufreq: tegra194: remove opp table in exit hook Sumit Gupta
2023-08-28  6:11 ` Viresh Kumar
2023-08-28 10:17   ` Viresh Kumar
2023-08-28 12:25     ` Sumit Gupta [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=d3318a98-4d61-73f7-07ab-787624edfdcd@nvidia.com \
    --to=sumitg@nvidia.com \
    --cc=bbasu@nvidia.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=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox