All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sumit Gupta <sumitg@nvidia.com>
To: <viresh.kumar@linaro.org>, <rjw@rjwysocki.net>,
	<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
	<linux-pm@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Cc: <ksitaraman@nvidia.com>, <bbasu@nvidia.com>, <sumitg@nvidia.com>
Subject: [Patch 0/2] Tegra194 cpufreq driver misc changes
Date: Wed, 16 Sep 2020 22:41:15 +0530	[thread overview]
Message-ID: <1600276277-7290-1-git-send-email-sumitg@nvidia.com> (raw)

This patch set has below two changes:
1) get consistent cpuinfo_cur_freq value from freq_table.
2) Fix unlisted boot freq warning by setting closest ndiv value
   from freq_table if the boot frequency gets filtered while
   creating freq_table in kernel.

Sumit Gupta (2):
  cpufreq: tegra194: get consistent cpuinfo_cur_freq
  cpufreq: tegra194: Fix unlisted boot freq warning

 drivers/cpufreq/tegra194-cpufreq.c | 182 ++++++++++++++++++++++++++++++++++---
 1 file changed, 167 insertions(+), 15 deletions(-)

-- 
2.7.4


WARNING: multiple messages have this Message-ID (diff)
From: Sumit Gupta <sumitg@nvidia.com>
To: <viresh.kumar@linaro.org>, <rjw@rjwysocki.net>,
	<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
	<linux-pm@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Cc: ksitaraman@nvidia.com, sumitg@nvidia.com, bbasu@nvidia.com
Subject: [Patch 0/2] Tegra194 cpufreq driver misc changes
Date: Wed, 16 Sep 2020 22:41:15 +0530	[thread overview]
Message-ID: <1600276277-7290-1-git-send-email-sumitg@nvidia.com> (raw)

This patch set has below two changes:
1) get consistent cpuinfo_cur_freq value from freq_table.
2) Fix unlisted boot freq warning by setting closest ndiv value
   from freq_table if the boot frequency gets filtered while
   creating freq_table in kernel.

Sumit Gupta (2):
  cpufreq: tegra194: get consistent cpuinfo_cur_freq
  cpufreq: tegra194: Fix unlisted boot freq warning

 drivers/cpufreq/tegra194-cpufreq.c | 182 ++++++++++++++++++++++++++++++++++---
 1 file changed, 167 insertions(+), 15 deletions(-)

-- 
2.7.4


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

             reply	other threads:[~2020-09-16 20:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 17:11 Sumit Gupta [this message]
2020-09-16 17:11 ` [Patch 0/2] Tegra194 cpufreq driver misc changes 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
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=1600276277-7290-1-git-send-email-sumitg@nvidia.com \
    --to=sumitg@nvidia.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=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.