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 (samsung.com)" <cw00.choi@samsung.com>,
"Chanwoo Choi (chanwoo@kernel.org)" <chanwoo@kernel.org>,
함명주 <myungjoo.ham@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>
Subject: [GIT PULL] devfreq next for v5.8
Date: Fri, 29 May 2020 11:47:42 +0900 [thread overview]
Message-ID: <eba2afce-78d0-50ba-8907-da2f61f0df9e@samsung.com> (raw)
In-Reply-To: CGME20200529023722epcas1p4062a6826d015c249adddd45bf28c0a29@epcas1p4.samsung.com
Dear Rafael,
This is devfreq-next pull request for v5.8-rc1. I add detailed description of
this pull request on the following tag. Please pull devfreq with following updates.
- tag name : devfreq-next-for-5.8
Best Regards,
Chanwoo Choi
The following changes since commit 9cb1fd0efd195590b828b9b865421ad345a4a145:
Linux 5.7-rc7 (2020-05-24 15:32:54 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git tags/devfreq-next-for-5.8
for you to fetch changes up to 8fc0e48e0faefef5064f3cb803d3d12314e16ec4:
PM / devfreq: Use lockdep asserts instead of manual checks for locked mutex (2020-05-28 18:02:40 +0900)
----------------------------------------------------------------
Update devfreq for 5.8
Detailed description for this pull request:
1. Update devfreq core
- Use lockdep function for checking mutex state instead of manual checking.
- Replace strncpy with strscpy to fix the compile warning.
2. Update devfreq driver
- Add new imx-bus.c devfreq driver for controlling the bus frequenncy
and it registers the imx interconnect device which indicates the imx-bus.c
as the parent device. This relation make the connection between imx-bus.c
and imx interconnect nodes. In result, the imx-bus.c devfreq driver handles
the DEV_PM_QOS_MIN_FREQUENCY requirements from imx interconnect nodes
in order to support the minimum bus bandwidth of interconnect nodes.
- Delete unneed error message and update the boosting on tegra30-devfreq.c.
----------------------------------------------------------------
Dmitry Osipenko (2):
PM / devfreq: tegra30: Make CPUFreq notifier to take into account boosting
PM / devfreq: Replace strncpy with strscpy
Gustavo A. R. Silva (1):
PM / devfreq: imx-bus: Fix inconsistent IS_ERR and PTR_ERR
Krzysztof Kozlowski (1):
PM / devfreq: Use lockdep asserts instead of manual checks for locked mutex
Leonard Crestez (2):
PM / devfreq: Add generic imx bus scaling driver
PM / devfreq: imx: Register interconnect device
Markus Elfring (1):
PM / devfreq: tegra30: Delete an error message in tegra_devfreq_probe()
drivers/devfreq/Kconfig | 8 ++
drivers/devfreq/Makefile | 1 +
drivers/devfreq/devfreq.c | 19 ++--
drivers/devfreq/imx-bus.c | 179 ++++++++++++++++++++++++++++++++++++++
drivers/devfreq/tegra30-devfreq.c | 7 +-
5 files changed, 199 insertions(+), 15 deletions(-)
create mode 100644 drivers/devfreq/imx-bus.c
next parent reply other threads:[~2020-05-29 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200529023722epcas1p4062a6826d015c249adddd45bf28c0a29@epcas1p4.samsung.com>
2020-05-29 2:47 ` Chanwoo Choi [this message]
2020-05-29 14:42 ` [GIT PULL] devfreq next for v5.8 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=eba2afce-78d0-50ba-8907-da2f61f0df9e@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;
as well as URLs for NNTP newsgroup(s).