linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henry Chen <henryc.chen@mediatek.com>
To: Georgi Djakov <georgi.djakov@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Viresh Kumar <vireshk@kernel.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Ryan Case <ryandcase@chromium.org>,
	Mark Brown <broonie@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Nicolas Boichat <drinkcat@google.com>,
	Fan Chen <fan.chen@mediatek.com>,
	James Liao <jamesjj.liao@mediatek.com>,
	Arvin Wang <arvin.wang@mediatek.com>,
	Mike Turquette <mturquette@linaro.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-pm@vger.kernel.org>
Subject: [PATCH V5 00/17] Add driver for dvfsrc, support for active state of scpsys
Date: Mon, 14 Sep 2020 11:04:27 +0800	[thread overview]
Message-ID: <1600052684-21198-1-git-send-email-henryc.chen@mediatek.com> (raw)

This series is based on v5.9-rc1 and have dependency patches as following,
[v17,00/12] Mediatek MT8183 scpsys support
https://patchwork.kernel.org/cover/11703253/
[0/3] Mediatek MT8192 scpsys support
https://patchwork.kernel.org/cover/11755897/

The patchsets add support for MediaTek hardware module named DVFSRC
(dynamic voltage and frequency scaling resource collector). The DVFSRC is
a HW module which is used to collect all the requests from both software
and hardware and turn into the decision of minimum operating voltage and
minimum DRAM frequency to fulfill those requests.

So, This series is to implement the dvfsrc driver to collect all the
requests of operating voltage or DRAM bandwidth from other device drivers
likes GPU/Camera through 3 frameworks basically:

1. interconnect framework: to aggregate the bandwidth
   requirements from different clients

[1] https://patchwork.kernel.org/cover/10766329/

There has a hw module "DRAM scheduler", which used to control the throughput.
The DVFSRC will collect forecast data of dram bandwidth from
SW consumers(camera/gpu...), and according the forecast to change the DRAM
frequency

2. Active state management of power domains[1]: to handle the operating
   voltage/dram opp requirement from different power domains

[2] https://lwn.net/Articles/744047/

3. Regualtor framework: to handle the operating voltage requirement from user or
   cosumer which not belong any power domain

Changes in V5:
* Support more platform mt6873/mt8192
* Drop the compatible and interconnect provider node and make the parent node an
interconnect provider. (Rob/Georgi)
* Make modification of interconnect driver from coding suggestion. (Georgi)
* Move interconnect diagram into the commit text of patch. (Georgi)
* Register the interconnect provider as a platform sub-device. (Georgi)

Changes in V4:
* Add acked TAG on dt-bindings patches. (Rob)
* Declaration of emi_icc_aggregate since the prototype of aggregate function
has changed meanwhile. (Georgi)
* Used emi_icc_remove instead of icc_provider_del on probe. (Georgi)
* Add dvfsrc regulator driver into series.
* Bug fixed of mt8183_get_current_level.
* Add mutex protection for pstate operation on dvfsrc_set_performance.

Changes in V3:
* Remove RFC from the subject prefix of the series
* Combine dt-binding patch and move interconnect dt-binding document into
dvfsrc. (Rob)
* Remove unused header, add unit descirption to the bandwidth, rename compatible
name on interconnect driver. (Georgi)
* Fixed some coding style: check flow, naming, used readx_poll_timeout
on dvfsrc driver. (Ryan)
* Rename interconnect driver mt8183.c to mtk-emi.c
* Rename interconnect header mtk,mt8183.h to mtk,emi.h
* mtk-scpsys.c: Add opp table check first to avoid OF runtime parse failed

Changes in RFC V2:
* Remove the DT property dram_type. (Rob)
* Used generic dts property 'opp-level' to get the performace state. (Stephen)
* Remove unecessary dependency config on Kconfig. (Stephen)
* Remove unused header file, fixed some coding style issue, typo,
error handling on dvfsrc driver. (Nicolas/Stephen)
* Remove irq handler on dvfsrc driver. (Stephen)
* Remove init table on dvfsrc driver, combine hw init on trustzone.
* Add interconnect support of mt8183 to aggregate the emi bandwidth.
(Georgi)

V4: https://lore.kernel.org/patchwork/cover/1209284/
V3: https://patchwork.kernel.org/cover/11118867/
RFC V2: https://lore.kernel.org/patchwork/patch/1068113/
RFC V1: https://lore.kernel.org/patchwork/cover/1028535/

             reply	other threads:[~2020-09-14  3:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  3:04 Henry Chen [this message]
2020-09-14  3:04 ` [PATCH V5 01/17] dt-bindings: soc: Add dvfsrc driver bindings Henry Chen
2020-09-22 23:14   ` Rob Herring
2020-09-14  3:04 ` [PATCH V5 02/17] dt-bindings: soc: Add opp table on scpsys bindings Henry Chen
2020-09-14  3:04 ` [PATCH V5 03/17] soc: mediatek: add support for the performance state Henry Chen
2020-09-14  3:04 ` [PATCH V5 04/17] arm64: dts: mt8183: add performance state support of scpsys Henry Chen
2020-09-14  3:04 ` [PATCH V5 05/17] soc: mediatek: add header for mediatek SIP interface Henry Chen
2020-09-14  3:04 ` [PATCH V5 06/17] soc: mediatek: add driver for dvfsrc support Henry Chen
2020-09-14  3:04 ` [PATCH V5 07/17] arm64: dts: mt8183: add dvfsrc related nodes Henry Chen
2020-09-14  3:04 ` [PATCH V5 09/17] dt-bindings: interconnect: add MT8183 interconnect dt-bindings Henry Chen
2020-09-14  3:04 ` [PATCH V5 11/17] interconnect: mediatek: Add interconnect provider driver Henry Chen
2020-09-14  3:04 ` [PATCH V5 12/17] arm64: dts: mt8183: add dvfsrc related nodes Henry Chen
2020-09-14  3:04 ` [PATCH V5 13/17] arm64: dts: mt8192: " Henry Chen
2020-09-14  3:04 ` [PATCH V5 16/17] arm64: dts: mt8183: add dvfsrc regulator nodes Henry Chen
     [not found] ` <1600052684-21198-15-git-send-email-henryc.chen@mediatek.com>
2020-09-14 12:32   ` [PATCH V5 14/17] dt-bindings: regulator: add DVFSRC regulator dt-bindings Mark Brown
     [not found] ` <1600052684-21198-16-git-send-email-henryc.chen@mediatek.com>
2020-09-14 12:34   ` [PATCH V5 15/17] regulator: Regulator driver for the Mediatek DVFSRC Mark Brown

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=1600052684-21198-1-git-send-email-henryc.chen@mediatek.com \
    --to=henryc.chen@mediatek.com \
    --cc=arvin.wang@mediatek.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=drinkcat@google.com \
    --cc=fan.chen@mediatek.com \
    --cc=georgi.djakov@linaro.org \
    --cc=jamesjj.liao@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=mturquette@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=ryandcase@chromium.org \
    --cc=swboyd@chromium.org \
    --cc=vireshk@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;
as well as URLs for NNTP newsgroup(s).