From: Matthias Brugger <matthias.bgg@gmail.com>
To: Roger Lu <roger.lu@mediatek.com>,
Enric Balletbo Serra <eballetbo@gmail.com>,
Kevin Hilman <khilman@kernel.org>,
Nicolas Boichat <drinkcat@google.com>
Cc: Fan Chen <fan.chen@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: Re: [PATCH v5 2/3] soc: mediatek: mtk-svs: use common function to disable restore voltages
Date: Thu, 2 Feb 2023 13:46:28 +0100 [thread overview]
Message-ID: <2e616aea-0a38-b33e-20d5-0c6254cdd616@gmail.com> (raw)
In-Reply-To: <20230202124104.16504-3-roger.lu@mediatek.com>
On 02/02/2023 13:41, Roger Lu wrote:
> The timing of disabling SVS bank and restore default voltage is more
> than one place. Therefore, add a common function to use for removing
> the superfluous codes.
>
> Signed-off-by: Roger Lu <roger.lu@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Queued for the next merge window.
Thanks!
> ---
> drivers/soc/mediatek/mtk-svs.c | 54 ++++++++++++++--------------------
> 1 file changed, 22 insertions(+), 32 deletions(-)
>
> diff --git a/drivers/soc/mediatek/mtk-svs.c b/drivers/soc/mediatek/mtk-svs.c
> index c9899f5df60a..299f580847bd 100644
> --- a/drivers/soc/mediatek/mtk-svs.c
> +++ b/drivers/soc/mediatek/mtk-svs.c
> @@ -624,6 +624,25 @@ static int svs_adjust_pm_opp_volts(struct svs_bank *svsb)
> return ret;
> }
>
> +static void svs_bank_disable_and_restore_default_volts(struct svs_platform *svsp,
> + struct svs_bank *svsb)
> +{
> + unsigned long flags;
> +
> + if (svsb->mode_support == SVSB_MODE_ALL_DISABLE)
> + return;
> +
> + spin_lock_irqsave(&svs_lock, flags);
> + svsp->pbank = svsb;
> + svs_switch_bank(svsp);
> + svs_writel_relaxed(svsp, SVSB_PTPEN_OFF, SVSEN);
> + svs_writel_relaxed(svsp, SVSB_INTSTS_VAL_CLEAN, INTSTS);
> + spin_unlock_irqrestore(&svs_lock, flags);
> +
> + svsb->phase = SVSB_PHASE_ERROR;
> + svs_adjust_pm_opp_volts(svsb);
> +}
> +
> #ifdef CONFIG_DEBUG_FS
> static int svs_dump_debug_show(struct seq_file *m, void *p)
> {
> @@ -700,7 +719,6 @@ static ssize_t svs_enable_debug_write(struct file *filp,
> {
> struct svs_bank *svsb = file_inode(filp)->i_private;
> struct svs_platform *svsp = dev_get_drvdata(svsb->dev);
> - unsigned long flags;
> int enabled, ret;
> char *buf = NULL;
>
> @@ -716,16 +734,8 @@ static ssize_t svs_enable_debug_write(struct file *filp,
> return ret;
>
> if (!enabled) {
> - spin_lock_irqsave(&svs_lock, flags);
> - svsp->pbank = svsb;
> + svs_bank_disable_and_restore_default_volts(svsp, svsb);
> svsb->mode_support = SVSB_MODE_ALL_DISABLE;
> - svs_switch_bank(svsp);
> - svs_writel_relaxed(svsp, SVSB_PTPEN_OFF, SVSEN);
> - svs_writel_relaxed(svsp, SVSB_INTSTS_VAL_CLEAN, INTSTS);
> - spin_unlock_irqrestore(&svs_lock, flags);
> -
> - svsb->phase = SVSB_PHASE_ERROR;
> - svs_adjust_pm_opp_volts(svsb);
> }
>
> kfree(buf);
> @@ -1508,16 +1518,7 @@ static int svs_init02(struct svs_platform *svsp)
> out_of_init02:
> for (idx = 0; idx < svsp->bank_max; idx++) {
> svsb = &svsp->banks[idx];
> -
> - spin_lock_irqsave(&svs_lock, flags);
> - svsp->pbank = svsb;
> - svs_switch_bank(svsp);
> - svs_writel_relaxed(svsp, SVSB_PTPEN_OFF, SVSEN);
> - svs_writel_relaxed(svsp, SVSB_INTSTS_VAL_CLEAN, INTSTS);
> - spin_unlock_irqrestore(&svs_lock, flags);
> -
> - svsb->phase = SVSB_PHASE_ERROR;
> - svs_adjust_pm_opp_volts(svsb);
> + svs_bank_disable_and_restore_default_volts(svsp, svsb);
> }
>
> return ret;
> @@ -1563,23 +1564,12 @@ static int svs_suspend(struct device *dev)
> {
> struct svs_platform *svsp = dev_get_drvdata(dev);
> struct svs_bank *svsb;
> - unsigned long flags;
> int ret;
> u32 idx;
>
> for (idx = 0; idx < svsp->bank_max; idx++) {
> svsb = &svsp->banks[idx];
> -
> - /* This might wait for svs_isr() process */
> - spin_lock_irqsave(&svs_lock, flags);
> - svsp->pbank = svsb;
> - svs_switch_bank(svsp);
> - svs_writel_relaxed(svsp, SVSB_PTPEN_OFF, SVSEN);
> - svs_writel_relaxed(svsp, SVSB_INTSTS_VAL_CLEAN, INTSTS);
> - spin_unlock_irqrestore(&svs_lock, flags);
> -
> - svsb->phase = SVSB_PHASE_ERROR;
> - svs_adjust_pm_opp_volts(svsb);
> + svs_bank_disable_and_restore_default_volts(svsp, svsb);
> }
>
> ret = reset_control_assert(svsp->rst);
next prev parent reply other threads:[~2023-02-02 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 12:41 [PATCH v5 0/3] Enhance SVS's robustness Roger Lu
2023-02-02 12:41 ` [PATCH v5 1/3] soc: mediatek: mtk-svs: use svs get efuse common function Roger Lu
2023-02-02 12:46 ` Matthias Brugger
2023-02-02 12:41 ` [PATCH v5 2/3] soc: mediatek: mtk-svs: use common function to disable restore voltages Roger Lu
2023-02-02 12:46 ` Matthias Brugger [this message]
2023-02-02 12:41 ` [PATCH v5 3/3] soc: mediatek: mtk-svs: add thermal voltage compensation if needed Roger Lu
2023-02-02 12:58 ` Matthias Brugger
2023-02-11 11:12 ` Roger Lu (陸瑞傑)
2023-03-30 9:31 ` Matthias Brugger
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=2e616aea-0a38-b33e-20d5-0c6254cdd616@gmail.com \
--to=matthias.bgg@gmail.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=roger.lu@mediatek.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