public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cwchoi00@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "open list:DEVICE FREQUENCY (DEVFREQ)" <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Chanwoo Choi <chanwoo@kernel.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: [GIT PULL] devfreq next for 5.20
Date: Sat, 16 Jul 2022 03:03:12 +0900	[thread overview]
Message-ID: <06ba1e63-16a5-5659-e062-3c7e12f7e5cd@gmail.com> (raw)

Dear Rafael,

This is devfreq-next pull request for v5.20-rc1. I add detailed description of
this pull request on the following tag. Please pull devfreq with
following updates.

Best Regards,
Chanwoo Choi


The following changes since commit 32346491ddf24599decca06190ebca03ff9de7f8:

  Linux 5.19-rc6 (2022-07-10 14:40:51 -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.20

for you to fetch changes up to 53f853d55e312a639eaa910154248ce06eb754ac:

  PM / devfreq: tegra30: Add error message for devm_devfreq_add_device() (2022-07-15 11:40:08 +0900)
----------------------------------------------------------------

Update devfreq next for v5.20

Detailed description for this pull request:
1. Add new Mediatek CCI (Cache Coherent Interconnect) devfreq driver
- Add new MediaTek Cache Coherent Interconnect (CCI) devfreq drviver
  which supports the dynamic voltage and clock scaling.
  This driver uses the passive devfreq governor to get target frequencies
  and adjust voltages because it depends on MediaTek cpu frequency
  driver. In MT8183 and MT8186, the MediaTek CCI is supplied
  by the same regulators with the little core CPUs.

2. Update the devfreq drivers
- Convert the Samsung Exynos SoC Bus bindings to DT schema of exynos-bus.c

- Remove kernel-doc warnings by adding the description for unused
  fucntio parameters on devfreq core.

- Use NULL to pass a null pointer rather than zero according to function
  propotype on imx-bus.c

- Print error message instead of error interger value on tegra30-devfreq.c

----------------------------------------------------------------
Colin Ian King (1):
      PM / devfreq: imx-bus: use NULL to pass a null pointer rather than zero

Dmitry Osipenko (1):
      PM / devfreq: tegra30: Add error message for devm_devfreq_add_device()

Johnson Wang (2):
      dt-bindings: interconnect: Add MediaTek CCI dt-bindings
      PM / devfreq: mediatek: Introduce MediaTek CCI devfreq driver

Krzysztof Kozlowski (1):
      dt-bindings: interconnect: samsung,exynos-bus: convert to dtschema

Mauro Carvalho Chehab (1):
      PM / devfreq: shut up kernel-doc warnings

 .../devicetree/bindings/devfreq/exynos-bus.txt     | 488 ---------------------
 .../bindings/interconnect/mediatek,cci.yaml        | 141 ++++++
 .../bindings/interconnect/samsung,exynos-bus.yaml  | 290 ++++++++++++
 MAINTAINERS                                        |   3 +-
 drivers/devfreq/Kconfig                            |  10 +
 drivers/devfreq/Makefile                           |   1 +
 drivers/devfreq/devfreq.c                          |   4 +
 drivers/devfreq/imx-bus.c                          |   2 +-
 drivers/devfreq/mtk-cci-devfreq.c                  | 440 +++++++++++++++++++
 drivers/devfreq/tegra30-devfreq.c                  |   4 +-
 10 files changed, 892 insertions(+), 491 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/devfreq/exynos-bus.txt
 create mode 100644 Documentation/devicetree/bindings/interconnect/mediatek,cci.yaml
 create mode 100644 Documentation/devicetree/bindings/interconnect/samsung,exynos-bus.yaml
 create mode 100644 drivers/devfreq/mtk-cci-devfreq.c

             reply	other threads:[~2022-07-15 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 18:03 Chanwoo Choi [this message]
2022-07-18 18:37 ` [GIT PULL] devfreq next for 5.20 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=06ba1e63-16a5-5659-e062-3c7e12f7e5cd@gmail.com \
    --to=cwchoi00@gmail.com \
    --cc=chanwoo@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=rafael@kernel.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