mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: "Rafael J. Wysocki <rjw@rjwysocki.net>" <rjw@rjwysocki.net>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Chanwoo Choi (chanwoo@kernel.org)" <chanwoo@kernel.org>,
	"Chanwoo Choi (samsung.com)" <cw00.choi@samsung.com>,
	함명주 <myungjoo.ham@samsung.com>,
	"Kyungmin Park" <kyungmin.park@samsung.com>
Subject: [GIT PULL] devfreq fixes for v5.5-rc2
Date: Mon, 9 Dec 2019 15:57:34 +0900	[thread overview]
Message-ID: <f2f33725-5a73-0553-ef8a-52b192b80cfb@samsung.com> (raw)
In-Reply-To: <CGME20191209065107epcas1p4eaa96dffa943add96359b15cbd4d3b62@epcas1p4.samsung.com>

Dear Rafael,

This is devfreq-fixes pull request for v5.5-rc2. I add detailed description of
this pull request on the following tag. Please pull devfreq with following updates.
- tag name : devfreq-fixes-for-5.5-rc2

Regards,
Chanwoo Choi

The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:

  Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-fixes-for-5.5-rc2

for you to fetch changes up to 27dbc542f651ed09de910f274b32634904103774:

  PM / devfreq: Use PM QoS for sysfs min/max_freq (2019-12-09 12:19:16 +0900)

----------------------------------------------------------------

Update devfreq for 5.5-rc2

Detailed description for this pull request:
1. Update devfreq core
- Add PM QoS support for devfreq device with following QoS type. External user
of devfreq device can request the minimum and maximum frequency according to
their multiple requirements.
: DEV_PM_QOS_MIN_FREQUENCY is used for requesting the minimum device frequency.
: DEV_PM_QOS_MAX_FREQUENCY is used for requesting the maximum device frequency.

- Use PM QoS interface when entering the min/max_freq via sysfs interface.

- Add get_freq_range() helper function in order to get the final min/max
frequency among the multiple requirements of min/max frequency.

- Fix the issue such as fixing the return value and modify code
for more correct exception handling if error happen.

----------------------------------------------------------------

Leonard Crestez (6):
      PM / devfreq: Fix devfreq_notifier_call returning errno
      PM / devfreq: Set scaling_max_freq to max on OPP notifier error
      PM / devfreq: Introduce get_freq_range helper
      PM / devfreq: Don't fail devfreq_dev_release if not in list
      PM / devfreq: Add PM QoS support
      PM / devfreq: Use PM QoS for sysfs min/max_freq

 drivers/devfreq/devfreq.c | 273 ++++++++++++++++++++++++++++++++++------------
 include/linux/devfreq.h   |  14 ++-
 2 files changed, 212 insertions(+), 75 deletions(-)

       reply	other threads:[~2019-12-09  6:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191209065107epcas1p4eaa96dffa943add96359b15cbd4d3b62@epcas1p4.samsung.com>
2019-12-09  6:57 ` Chanwoo Choi [this message]
2019-12-09  8:44   ` Rafael J. Wysocki

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=f2f33725-5a73-0553-ef8a-52b192b80cfb@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=chanwoo@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=rjw@rjwysocki.net \
    /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

all inboxes | Powered by JetHome®