From: Kevin Hilman <khilman@kernel.org>
To: Roger Lu <roger.lu@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Enric Balletbo Serra <eballetbo@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Nicolas Boichat <drinkcat@google.com>,
Stephen Boyd <sboyd@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Fan Chen <fan.chen@mediatek.com>,
HenryC Chen <HenryC.Chen@mediatek.com>,
Xiaoqing Liu <Xiaoqing.Liu@mediatek.com>,
Charles Yang <Charles.Yang@mediatek.com>,
Angus Lin <Angus.Lin@mediatek.com>,
Mark Rutland <mark.rutland@arm.com>, Nishanth Menon <nm@ti.com>,
Roger Lu <roger.lu@mediatek.com>,
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,
Project_Global_Chrome_Upstream_Group@mediatek.com,
Guenter Roeck <linux@roeck-us.net>,
Jia-wei Chang <jia-wei.chang@mediatek.com>
Subject: Re: [PATCH v24 0/7] soc: mediatek: SVS: introduce MTK SVS
Date: Wed, 20 Apr 2022 16:22:32 -0700 [thread overview]
Message-ID: <7hczhbe3wn.fsf@baylibre.com> (raw)
In-Reply-To: <20220420102044.10832-1-roger.lu@mediatek.com>
Hi Roger,
Roger Lu <roger.lu@mediatek.com> writes:
> The Smart Voltage Scaling(SVS) engine is a piece of hardware
> which calculates suitable SVS bank voltages to OPP voltage table.
> Then, DVFS driver could apply those SVS bank voltages to PMIC/Buck
> when receiving OPP_EVENT_ADJUST_VOLTAGE.
>
> 1. SVS driver uses OPP adjust event in [1] to update OPP table voltage part.
> 2. SVS driver gets thermal/GPU device by node [2][3] and CPU device by get_cpu_device().
> After retrieving subsys device, SVS driver calls device_link_add() to make sure probe/suspend callback priority.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git/commit/?h=opp/linux-next&id=25cb20a212a1f989385dfe23230817e69c62bee5
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git/commit/?h=opp/linux-next&id=b325ce39785b1408040d90365a6ab1aa36e94f87
> [3] https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/commit/?h=v5.16-next/dts64&id=a8168cebf1bca1b5269e8a7eb2626fb76814d6e2
>
> Change since v23:
> - Change wording from "Mediatek" to "MediaTek" (uppercase T) in mtk-svs.yaml.
> - Use cpuidle_pause_and_lock() to prevent system from entering cpuidle instead of applying pm_qos APIs.
> - Add kfree() at the end of svs_probe() when encountering probe fail.
> - Change MODULE_LICENSE from "GPL v2" to "GPL".
> - Add nvmem_cell_put() in error handling when nvmem_cell_read() encounters fail.
I also gave you a reviewed-by on v23, but here it is again:
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
That being said, it would be really nice to see an integration tree
where this was all tested on mainline (e.g. v5.17, or v5.18-rc)
For example, I can apply this to v5.18-rc2 and boot on my mt8183-pumpkin
board, it fails to probe[1] because there is no CCI node in the upstream
mt8183.dtsi.
I'm assuming this series is also not very useful without the CPUfreq
series from Rex, so being able to test this, CCI and CPUfreq together on
MT8183 on a mainline kernel would be very helpful.
Kevin
[1]
[ 0.573332] mtk-svs 1100b000.svs: cannot find cci node
[ 0.574061] mtk-svs 1100b000.svs: error -ENODEV: svs platform probe fail
next prev parent reply other threads:[~2022-04-20 23:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 10:20 [PATCH v24 0/7] soc: mediatek: SVS: introduce MTK SVS Roger Lu
2022-04-20 10:20 ` [PATCH v24 1/7] dt-bindings: soc: mediatek: add mtk svs dt-bindings Roger Lu
2022-04-20 10:20 ` [PATCH v24 2/7] arm64: dts: mt8183: add svs device information Roger Lu
2022-04-20 10:20 ` [PATCH v24 3/7] soc: mediatek: SVS: introduce MTK SVS engine Roger Lu
2022-04-21 0:06 ` Kevin Hilman
2022-04-21 9:11 ` Roger Lu
2022-04-20 10:20 ` [PATCH v24 4/7] soc: mediatek: SVS: add monitor mode Roger Lu
2022-04-20 10:20 ` [PATCH v24 5/7] soc: mediatek: SVS: add debug commands Roger Lu
2022-04-20 10:20 ` [PATCH v24 6/7] dt-bindings: soc: mediatek: add mt8192 svs dt-bindings Roger Lu
2022-04-20 10:20 ` [PATCH v24 7/7] soc: mediatek: SVS: add mt8192 SVS GPU driver Roger Lu
2022-04-20 23:22 ` Kevin Hilman [this message]
2022-04-21 9:28 ` [PATCH v24 0/7] soc: mediatek: SVS: introduce MTK SVS Roger Lu
2022-04-21 19:41 ` Kevin Hilman
2022-04-22 2:24 ` Roger Lu
2022-04-22 15:38 ` Matthias Brugger
2022-04-26 7:15 ` Chen-Yu Tsai
2022-05-02 22:07 ` Kevin Hilman
2022-05-03 6:13 ` Chen-Yu Tsai
2022-05-04 19:25 ` Kevin Hilman
2022-05-06 8:40 ` Chen-Yu Tsai
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=7hczhbe3wn.fsf@baylibre.com \
--to=khilman@kernel.org \
--cc=Angus.Lin@mediatek.com \
--cc=Charles.Yang@mediatek.com \
--cc=HenryC.Chen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Xiaoqing.Liu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@google.com \
--cc=eballetbo@gmail.com \
--cc=fan.chen@mediatek.com \
--cc=jia-wei.chang@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=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=nm@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=roger.lu@mediatek.com \
--cc=sboyd@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