From: Roger Lu <roger.lu@mediatek.com>
To: Kevin Hilman <khilman@kernel.org>,
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>,
<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 3/7] soc: mediatek: SVS: introduce MTK SVS engine
Date: Thu, 21 Apr 2022 17:11:26 +0800 [thread overview]
Message-ID: <87d953ecfae99e786b0bc3c3756816114e3af287.camel@mediatek.com> (raw)
In-Reply-To: <7h5yn3s3jq.fsf@baylibre.com>
Hi Kevin,
Thanks very much for the feedback.
On Wed, 2022-04-20 at 17:06 -0700, Kevin Hilman wrote:
> 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.
> >
> > Signed-off-by: Roger Lu <roger.lu@mediatek.com>
> > Reviewed-by: AngeloGioacchino Del Regno <
> > angelogioacchino.delregno@collabora.com>
>
> Can SVS work with one or the other clusters disabled? It seems like it
> should still be able to work. However, if you disable the 2nd cluster
> (e.g. by passing `maxcpus=4` on the kernel command-line, the SVS driver
> will fail to probe.
>
> I dont' think it's a blocker for merging this series, but making the
> probe a bit more robust so it can handle the cluster being disabled
> would be nice additional fix for later.
>
> For example, upstream kernel on mt8183-pumpkin board is very unstable
> with the 2nd cluster enabled (I'm still trying to debug why), but I have
> to boot with `maxcpus=4` on the cmdline, otherwise kernel fails to boot,
> so that's how I noticed this probe failure with SVS.
On mt8183 platform, I think SVS can work with one or the other clusters
disabled. However, SVS is supposed to be enabled after system is stable for not
involving any power unstable concern.
If we want part of SVS works at the development stage, we can disable non-
working svs bank as below. Thanks.
--- a/drivers/soc/mediatek/mtk-svs.c
+++ b/drivers/soc/mediatek/mtk-svs.c
@@ -2164,7 +2164,7 @@ static struct svs_bank svs_mt8183_banks[] = {
.cpu_id = 4,
.buck_name = "proc",
.volt_flags = SVSB_INIT01_VOLT_INC_ONLY,
- .mode_support = SVSB_MODE_INIT01 | SVSB_MODE_INIT02,
+ .mode_support = SVSB_MODE_ALL_DISABLE,
.opp_count = MAX_OPP_ENTRIES,
>
> Kevin
next prev parent reply other threads:[~2022-04-21 9:12 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 [this message]
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 ` [PATCH v24 0/7] soc: mediatek: SVS: introduce MTK SVS Kevin Hilman
2022-04-21 9:28 ` 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=87d953ecfae99e786b0bc3c3756816114e3af287.camel@mediatek.com \
--to=roger.lu@mediatek.com \
--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=khilman@kernel.org \
--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=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
all inboxes | Powered by JetHome®