public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Lu <roger.lu@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	Enric Balletbo Serra <eballetbo@gmail.com>,
	Kevin Hilman <khilman@kernel.org>,
	Nicolas Boichat <drinkcat@google.com>
Cc: Fan Chen <fan.chen@mediatek.com>,
	Roger Lu <roger.lu@mediatek.com>,
	Jia-wei Chang <jia-wei.chang@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>
Subject: [PATCH v3 12/14] soc: mediatek: mtk-svs: restore default voltages when svs_init02() fail
Date: Tue, 3 Jan 2023 19:29:23 +0800	[thread overview]
Message-ID: <20230103112925.16554-13-roger.lu@mediatek.com> (raw)
In-Reply-To: <20230103112925.16554-1-roger.lu@mediatek.com>

If svs init02 fail, it means we cannot rely on svs bank voltages anymore.
We need to disable svs function and restore DVFS opp voltages back to the
default voltages for making sure we have enough DVFS voltages.

Signed-off-by: Roger Lu <roger.lu@mediatek.com>
---
 drivers/soc/mediatek/mtk-svs.c | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/drivers/soc/mediatek/mtk-svs.c b/drivers/soc/mediatek/mtk-svs.c
index f4382def9736..1b4798a9101c 100644
--- a/drivers/soc/mediatek/mtk-svs.c
+++ b/drivers/soc/mediatek/mtk-svs.c
@@ -1495,6 +1495,7 @@ static int svs_init02(struct svs_platform *svsp)
 {
 	struct svs_bank *svsb;
 	unsigned long flags, time_left;
+	int ret;
 	u32 idx;
 
 	for (idx = 0; idx < svsp->bank_max; idx++) {
@@ -1513,7 +1514,8 @@ static int svs_init02(struct svs_platform *svsp)
 							msecs_to_jiffies(5000));
 		if (!time_left) {
 			dev_err(svsb->dev, "init02 completion timeout\n");
-			return -EBUSY;
+			ret = -EBUSY;
+			goto out_of_init02;
 		}
 	}
 
@@ -1531,12 +1533,21 @@ static int svs_init02(struct svs_platform *svsp)
 		if (svsb->type == SVSB_HIGH || svsb->type == SVSB_LOW) {
 			if (svs_sync_bank_volts_from_opp(svsb)) {
 				dev_err(svsb->dev, "sync volt fail\n");
-				return -EPERM;
+				ret = -EPERM;
+				goto out_of_init02;
 			}
 		}
 	}
 
 	return 0;
+
+out_of_init02:
+	for (idx = 0; idx < svsp->bank_max; idx++) {
+		svsb = &svsp->banks[idx];
+		svs_bank_disable_and_restore_default_volts(svsp, svsb);
+	}
+
+	return ret;
 }
 
 static void svs_mon_mode(struct svs_platform *svsp)
-- 
2.18.0


  parent reply	other threads:[~2023-01-03 11:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 11:29 [PATCH v3 0/14] Enhance SVS's robustness Roger Lu
2023-01-03 11:29 ` [PATCH v3 01/14] soc: mediatek: mtk-svs: enable the IRQ later Roger Lu
2023-01-03 11:29 ` [PATCH v3 02/14] soc: mediatek: mtk-svs: Use pm_runtime_resume_and_get() in svs_init01() Roger Lu
2023-01-03 11:29 ` [PATCH v3 03/14] soc: mediatek: mtk-svs: clean up platform probing Roger Lu
2023-01-03 11:29 ` [PATCH v3 04/14] soc: mediatek: mtk-svs: improve readability of platform_probe Roger Lu
2023-01-03 11:29 ` [PATCH v3 05/14] soc: mediatek: mtk-svs: move svs_platform_probe into probe Roger Lu
2023-01-03 11:29 ` [PATCH v3 06/14] soc: mediatek: mtk-svs: delete superfluous platform data entries Roger Lu
2023-01-03 11:29 ` [PATCH v3 07/14] soc: mtk-svs: mt8183: refactor o_slope calculation Roger Lu
2023-01-03 11:29 ` [PATCH v3 08/14] soc: mediatek: mtk-svs: use svs get efuse common function Roger Lu
2023-01-03 11:29 ` [PATCH v3 09/14] soc: mediatek: mtk-svs: use svs clk control APIs Roger Lu
2023-01-03 11:29 ` [PATCH v3 10/14] soc: mediatek: mtk-svs: reset svs when svs_resume() fail Roger Lu
2023-01-03 11:29 ` [PATCH v3 11/14] soc: mediatek: mtk-svs: use common function to disable restore voltages Roger Lu
2023-01-03 11:29 ` Roger Lu [this message]
2023-01-03 11:29 ` [PATCH v3 13/14] soc: mediatek: mtk-svs: add thermal voltage compensation if needed Roger Lu
2023-01-03 11:29 ` [PATCH v3 14/14] soc: mediatek: mtk-svs: keep svs alive even though debug cmd create fail 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=20230103112925.16554-13-roger.lu@mediatek.com \
    --to=roger.lu@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@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=matthias.bgg@gmail.com \
    /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