Message ID | 20220422075239.16437-1-rex-bc.chen@mediatek.com (mailing list archive) |
---|---|
Headers | show |
Series | cpufreq: mediatek: Cleanup and support MT8183 and MT8186 | expand |
On 22/04/2022 09:52, Rex-BC Chen wrote: > > Reference series: > [1]: V1 of this series is present by Jia-Wei Chang. > message-id:20220307122151.11666-1-jia-wei.chang@mediatek.com > > [2]: The MediaTek CCI devfreq driver is introduced in another series. > message-id:20220408052150.22536-1-johnson.wang@mediatek.com > > [3]: The MediaTek SVS driver is introduced in another series. > message-id:20220221063939.14969-1-roger.lu@mediatek.com These are not proper links. Please use lore references. Best regards, Krzysztof
On 22-04-22, 15:52, Rex-BC Chen wrote: > From: "Andrew-sh.Cheng" <andrew-sh.cheng@mediatek.com> > > >From this opp notifier, cpufreq should listen to opp notification and do Why the extra ">" here ? > proper actions when receiving events of disable and voltage adjustment. > > One of the user for this opp notifier is MediaTek SVS. > The MediaTek Smart Voltage Scaling (SVS) is a hardware which calculates > suitable SVS bank voltages to OPP voltage table. > > Signed-off-by: Andrew-sh.Cheng <andrew-sh.cheng@mediatek.com> > Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com> > Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com> > Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> > --- > drivers/cpufreq/mediatek-cpufreq.c | 92 +++++++++++++++++++++++++++--- > 1 file changed, 84 insertions(+), 8 deletions(-) > > diff --git a/drivers/cpufreq/mediatek-cpufreq.c b/drivers/cpufreq/mediatek-cpufreq.c > +static int mtk_cpufreq_opp_notifier(struct notifier_block *nb, > + unsigned long event, void *data) > +{ > + struct dev_pm_opp *opp = data; > + struct dev_pm_opp *new_opp; > + struct mtk_cpu_dvfs_info *info; > + unsigned long freq, volt; > + struct cpufreq_policy *policy; > + int ret = 0; > + > + info = container_of(nb, struct mtk_cpu_dvfs_info, opp_nb); > + > + if (event == OPP_EVENT_ADJUST_VOLTAGE) { I don't see any call to dev_pm_opp_adjust_voltage() for your platform, how is this ever going to get called ? > + freq = dev_pm_opp_get_freq(opp); > + > + mutex_lock(&info->reg_lock); > + if (info->opp_freq == freq) { > + volt = dev_pm_opp_get_voltage(opp); > + ret = mtk_cpufreq_set_voltage(info, volt); > + if (ret) > + dev_err(info->cpu_dev, > + "failed to scale voltage: %d\n", ret); > + } > + mutex_unlock(&info->reg_lock); > + } else if (event == OPP_EVENT_DISABLE) { > + freq = dev_pm_opp_get_freq(opp); > + > + /* case of current opp item is disabled */ > + if (info->opp_freq == freq) { > + freq = 1; > + new_opp = dev_pm_opp_find_freq_ceil(info->cpu_dev, > + &freq); > + if (IS_ERR(new_opp)) { > + dev_err(info->cpu_dev, > + "all opp items are disabled\n"); > + ret = PTR_ERR(new_opp); > + return notifier_from_errno(ret); > + } > + > + dev_pm_opp_put(new_opp); > + policy = cpufreq_cpu_get(info->opp_cpu); > + if (policy) { > + cpufreq_driver_target(policy, freq / 1000, > + CPUFREQ_RELATION_L); > + cpufreq_cpu_put(policy); IIUC, then you are trying to change the frequency if a currently used OPP is getting removed ? In that case, this problem is generic enough not to be fixed in a end driver. This should be fixed in core somehow.
On Fri, 2022-04-22 at 19:23 +0200, Krzysztof Kozlowski wrote: > On 22/04/2022 09:52, Rex-BC Chen wrote: > > > > Reference series: > > [1]: V1 of this series is present by Jia-Wei Chang. > > message-id:20220307122151.11666-1-jia-wei.chang@mediatek.com > > > > [2]: The MediaTek CCI devfreq driver is introduced in another > > series. > > message-id:20220408052150.22536-1-johnson.wang@mediatek.com > > > > [3]: The MediaTek SVS driver is introduced in another series. > > message-id:20220221063939.14969-1-roger.lu@mediatek.com > > These are not proper links. Please use lore references. > > > Best regards, > Krzysztof Hello Krzysztof, I will use lore references in next version. Thanks. BRs, Rex