All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Sumit Gupta <sumitg@nvidia.com>
Cc: viresh.kumar@linaro.org, rjw@rjwysocki.net, jonathanh@nvidia.com,
	linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, ksitaraman@nvidia.com,
	bbasu@nvidia.com
Subject: Re: [Patch 1/2] cpufreq: tegra194: get consistent cpuinfo_cur_freq
Date: Thu, 24 Sep 2020 10:56:35 +0200	[thread overview]
Message-ID: <20200924085635.GA2483160@ulmo> (raw)
In-Reply-To: <1600276277-7290-2-git-send-email-sumitg@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 711 bytes --]

On Wed, Sep 16, 2020 at 10:41:16PM +0530, Sumit Gupta wrote:
> Frequency returned by 'cpuinfo_cur_freq' using counters is not fixed
> and keeps changing slightly. This change returns a consistent value
> from freq_table. If the reconstructed frequency has acceptable delta
> from the last written value, then return the frequency corresponding
> to the last written ndiv value from freq_table. Otherwise, print a
> warning and return the reconstructed freq.
> 
> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
> ---
>  drivers/cpufreq/tegra194-cpufreq.c | 66 ++++++++++++++++++++++++++++++++------
>  1 file changed, 57 insertions(+), 9 deletions(-)

Acked-by: Thierry Reding <treding@nvidia.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Sumit Gupta <sumitg@nvidia.com>
Cc: linux-pm@vger.kernel.org, viresh.kumar@linaro.org,
	rjw@rjwysocki.net, linux-kernel@vger.kernel.org,
	jonathanh@nvidia.com, ksitaraman@nvidia.com, bbasu@nvidia.com,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [Patch 1/2] cpufreq: tegra194: get consistent cpuinfo_cur_freq
Date: Thu, 24 Sep 2020 10:56:35 +0200	[thread overview]
Message-ID: <20200924085635.GA2483160@ulmo> (raw)
In-Reply-To: <1600276277-7290-2-git-send-email-sumitg@nvidia.com>


[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]

On Wed, Sep 16, 2020 at 10:41:16PM +0530, Sumit Gupta wrote:
> Frequency returned by 'cpuinfo_cur_freq' using counters is not fixed
> and keeps changing slightly. This change returns a consistent value
> from freq_table. If the reconstructed frequency has acceptable delta
> from the last written value, then return the frequency corresponding
> to the last written ndiv value from freq_table. Otherwise, print a
> warning and return the reconstructed freq.
> 
> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
> ---
>  drivers/cpufreq/tegra194-cpufreq.c | 66 ++++++++++++++++++++++++++++++++------
>  1 file changed, 57 insertions(+), 9 deletions(-)

Acked-by: Thierry Reding <treding@nvidia.com>

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-09-24  8:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 17:11 [Patch 0/2] Tegra194 cpufreq driver misc changes Sumit Gupta
2020-09-16 17:11 ` Sumit Gupta
2020-09-16 17:11 ` [Patch 1/2] cpufreq: tegra194: get consistent cpuinfo_cur_freq Sumit Gupta
2020-09-16 17:11   ` Sumit Gupta
2020-09-17  8:36   ` Jon Hunter
2020-09-17  8:36     ` Jon Hunter
2020-09-17  8:44     ` Jon Hunter
2020-09-17  8:44       ` Jon Hunter
2020-09-23  8:34       ` Jon Hunter
2020-09-23  8:34         ` Jon Hunter
2020-10-05  4:34     ` Viresh Kumar
2020-10-05  4:34       ` Viresh Kumar
2020-10-05  9:12       ` Jon Hunter
2020-10-05  9:12         ` Jon Hunter
2020-09-24  8:56   ` Thierry Reding [this message]
2020-09-24  8:56     ` Thierry Reding
2020-10-05  4:46   ` Viresh Kumar
2020-10-05  4:46     ` Viresh Kumar
2020-10-05 18:40     ` Sumit Gupta
2020-10-05 18:40       ` Sumit Gupta
2020-09-16 17:11 ` [Patch 2/2] cpufreq: tegra194: Fix unlisted boot freq warning Sumit Gupta
2020-09-16 17:11   ` Sumit Gupta
2020-09-17  8:38   ` Jon Hunter
2020-09-17  8:38     ` Jon Hunter
2020-09-17  8:45     ` Jon Hunter
2020-09-17  8:45       ` Jon Hunter
2020-09-24  8:56   ` Thierry Reding
2020-09-24  8:56     ` Thierry Reding
2020-10-05  4:54   ` Viresh Kumar
2020-10-05  4:54     ` Viresh Kumar
2020-10-05 18:54     ` Sumit Gupta
2020-10-05 18:54       ` Sumit Gupta
2020-10-06  5:38       ` Viresh Kumar
2020-10-06  5:38         ` Viresh Kumar
2020-10-08 11:11         ` Sumit Gupta
2020-10-08 11:11           ` Sumit Gupta

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=20200924085635.GA2483160@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=bbasu@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=ksitaraman@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sumitg@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 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.