public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Roger Lu <roger.lu@mediatek•com>
To: Rob Herring <robh+dt@kernel•org>,
	Matthias Brugger <matthias.bgg@gmail•com>,
	Viresh Kumar <vireshk@kernel•org>,
	Stephen Boyd <sboyd@kernel•org>,
	"Rafael J . Wysocki" <rjw@rjwysocki•net>
Cc: Mark Rutland <mark.rutland@arm•com>, Nishanth Menon <nm@ti•com>,
	devicetree@vger•kernel.org, linux-pm@vger•kernel.org,
	Kevin Hilman <khilman@kernel•org>,
	Roger Lu <roger.lu@mediatek•com>,
	linux-kernel@vger•kernel.org, linux-mediatek@lists•infradead.org,
	linux-arm-kernel@lists•infradead.org
Subject: PM / AVS: SVS: Introduce SVS engine
Date: Tue, 30 Apr 2019 19:20:09 +0800	[thread overview]
Message-ID: <20190430112012.4514-1-roger.lu@mediatek.com> (raw)

The SVS (Smart Voltage Scaling) engine is a piece of hardware which is
used to calculate optimized voltage values of several power domains, e.g.
CPU/GPU/CCI, according to chip process corner, temperatures, and other
factors. Then DVFS driver could apply those optimized voltage values to
reduce power consumption.

Roger Lu (3):
  dt-bindings: soc: add mtk svs dt-bindings
  arm64: dts: mt8183: add svs device information
  PM / AVS: SVS: Introduce SVS engine

 .../devicetree/bindings/power/mtk-svs.txt     |   70 +
 arch/arm64/boot/dts/mediatek/mt8183-evb.dts   |   16 +
 arch/arm64/boot/dts/mediatek/mt8183.dtsi      |   46 +
 drivers/power/avs/Kconfig                     |   10 +
 drivers/power/avs/Makefile                    |    1 +
 drivers/power/avs/mtk_svs.c                   | 2084 +++++++++++++++++
 include/linux/power/mtk_svs.h                 |   23 +
 7 files changed, 2250 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/power/mtk-svs.txt
 create mode 100644 drivers/power/avs/mtk_svs.c
 create mode 100644 include/linux/power/mtk_svs.h

--
2.18.0



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

             reply	other threads:[~2019-04-30 11:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 11:20 Roger Lu [this message]
2019-04-30 11:20 ` [RFC v1 1/3] dt-bindings: soc: add mtk svs dt-bindings Roger Lu
2019-04-30 20:31   ` Stephen Boyd
2019-05-02  6:19     ` Roger Lu
2019-05-03 21:08       ` Stephen Boyd
2019-05-07  7:50         ` Roger Lu
2019-05-07 20:49           ` Stephen Boyd
2019-05-13  0:34             ` Roger Lu
2019-05-02 21:06     ` Rob Herring
2019-04-30 11:20 ` [RFC v1 2/3] arm64: dts: mt8183: add svs device information Roger Lu
2019-04-30 11:20 ` [RFC v1 3/3] PM / AVS: SVS: Introduce SVS engine Roger Lu
  -- strict thread matches above, loose matches on Subject: below --
2019-06-18  7:02 Roger Lu
2019-07-29  8:20 Roger Lu
2020-01-07  7:01 Roger Lu

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=20190430112012.4514-1-roger.lu@mediatek.com \
    --to=roger.lu@mediatek$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=khilman@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mediatek@lists$(echo .)infradead.org \
    --cc=linux-pm@vger$(echo .)kernel.org \
    --cc=mark.rutland@arm$(echo .)com \
    --cc=matthias.bgg@gmail$(echo .)com \
    --cc=nm@ti$(echo .)com \
    --cc=rjw@rjwysocki$(echo .)net \
    --cc=robh+dt@kernel$(echo .)org \
    --cc=sboyd@kernel$(echo .)org \
    --cc=vireshk@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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