All of lore.kernel.org
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
	rafael@kernel.org, viresh.kumar@linaro.org, robh+dt@kernel.org,
	krzk+dt@kernel.org, matthias.bgg@gmail.com
Cc: jia-wei.chang@mediatek.com, roger.lu@mediatek.com,
	hsinyi@google.com, khilman@baylibre.com,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH V3 11/15] cpufreq: mediatek: Link CCI device to CPU
Date: Fri, 15 Apr 2022 14:24:08 +0200	[thread overview]
Message-ID: <9fccbb92-1832-bf5d-7804-80dd481663fc@collabora.com> (raw)
In-Reply-To: <20220415055916.28350-12-rex-bc.chen@mediatek.com>

Il 15/04/22 07:59, Rex-BC Chen ha scritto:
> From: Jia-Wei Chang <jia-wei.chang@mediatek.com>
> 
> In some MediaTek SoCs, like MT8183, CPU and CCI share the same power
> supplies. Cpufreq needs to check if CCI devfreq exists and wait until
> CCI devfreq ready before scaling frequency.
> 
> Before CCI devfreq is ready, we record the voltage when booting to
> kernel and use the max(cpu target voltage, booting voltage) to
> prevent cpufreq adjust to the lower voltage which will cause the CCI
> crash because of high frequency and low voltage.
> 
> - Add is_ccifreq_ready() to link CCI device to CPI, and CPU will start
>    DVFS when CCI is ready.
> - Add platform data for MT8183.
> 
> Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
> Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com>

I am enthusiast to see that the solution that I've proposed was welcome!

I only have one nit on this patch, check below:

> ---
>   drivers/cpufreq/mediatek-cpufreq.c | 80 +++++++++++++++++++++++++++++-
>   1 file changed, 79 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/cpufreq/mediatek-cpufreq.c b/drivers/cpufreq/mediatek-cpufreq.c
> index d4c00237e862..dd3f739fede1 100644
> --- a/drivers/cpufreq/mediatek-cpufreq.c
> +++ b/drivers/cpufreq/mediatek-cpufreq.c

..snip..

> @@ -225,6 +251,14 @@ static int mtk_cpufreq_set_target(struct cpufreq_policy *policy,
>   	vproc = dev_pm_opp_get_voltage(opp);
>   	dev_pm_opp_put(opp);
>   
> +	/*
> +	 * If MediaTek cci is supported but is not ready, we will use the value
> +	 * of max(target cpu voltage, booting voltage) to prevent high freqeuncy
> +	 * low voltage crash.
> +	 */
> +	if (info->soc_data->ccifreq_supported && !is_ccifreq_ready(info))
> +		vproc = max(vproc, info->vproc_on_boot);
> +
>   	/*
>   	 * If the new voltage or the intermediate voltage is higher than the
>   	 * current voltage, scale up voltage first.

..snip..

> @@ -423,6 +484,13 @@ static int mtk_cpu_dvfs_info_init(struct mtk_cpu_dvfs_info *info, int cpu)
>   	if (ret)
>   		goto out_disable_mux_clock;
>   
> +	info->vproc_on_boot = regulator_get_voltage(info->proc_reg);

This result is used only if we use ccifreq, so this should be enclosed in an if
condition: this will spare us some (yes, small) time on devices that don't use it.

	if (info->soc_data->ccifreq_supported) {
		info->vproc_on_boot = regulator_get_voltage(info->proc_reg);
		if (info->vproc_on_boot < 0) {
			dev_err(....
			goto ..
		}
	}

P.S.: While at it, since the maximum width is 100 columns, the dev_err() call fits,
so don't break that line!

After the requested change:

Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
	rafael@kernel.org, viresh.kumar@linaro.org, robh+dt@kernel.org,
	krzk+dt@kernel.org, matthias.bgg@gmail.com
Cc: jia-wei.chang@mediatek.com, roger.lu@mediatek.com,
	hsinyi@google.com, khilman@baylibre.com,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH V3 11/15] cpufreq: mediatek: Link CCI device to CPU
Date: Fri, 15 Apr 2022 14:24:08 +0200	[thread overview]
Message-ID: <9fccbb92-1832-bf5d-7804-80dd481663fc@collabora.com> (raw)
In-Reply-To: <20220415055916.28350-12-rex-bc.chen@mediatek.com>

Il 15/04/22 07:59, Rex-BC Chen ha scritto:
> From: Jia-Wei Chang <jia-wei.chang@mediatek.com>
> 
> In some MediaTek SoCs, like MT8183, CPU and CCI share the same power
> supplies. Cpufreq needs to check if CCI devfreq exists and wait until
> CCI devfreq ready before scaling frequency.
> 
> Before CCI devfreq is ready, we record the voltage when booting to
> kernel and use the max(cpu target voltage, booting voltage) to
> prevent cpufreq adjust to the lower voltage which will cause the CCI
> crash because of high frequency and low voltage.
> 
> - Add is_ccifreq_ready() to link CCI device to CPI, and CPU will start
>    DVFS when CCI is ready.
> - Add platform data for MT8183.
> 
> Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
> Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com>

I am enthusiast to see that the solution that I've proposed was welcome!

I only have one nit on this patch, check below:

> ---
>   drivers/cpufreq/mediatek-cpufreq.c | 80 +++++++++++++++++++++++++++++-
>   1 file changed, 79 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/cpufreq/mediatek-cpufreq.c b/drivers/cpufreq/mediatek-cpufreq.c
> index d4c00237e862..dd3f739fede1 100644
> --- a/drivers/cpufreq/mediatek-cpufreq.c
> +++ b/drivers/cpufreq/mediatek-cpufreq.c

..snip..

> @@ -225,6 +251,14 @@ static int mtk_cpufreq_set_target(struct cpufreq_policy *policy,
>   	vproc = dev_pm_opp_get_voltage(opp);
>   	dev_pm_opp_put(opp);
>   
> +	/*
> +	 * If MediaTek cci is supported but is not ready, we will use the value
> +	 * of max(target cpu voltage, booting voltage) to prevent high freqeuncy
> +	 * low voltage crash.
> +	 */
> +	if (info->soc_data->ccifreq_supported && !is_ccifreq_ready(info))
> +		vproc = max(vproc, info->vproc_on_boot);
> +
>   	/*
>   	 * If the new voltage or the intermediate voltage is higher than the
>   	 * current voltage, scale up voltage first.

..snip..

> @@ -423,6 +484,13 @@ static int mtk_cpu_dvfs_info_init(struct mtk_cpu_dvfs_info *info, int cpu)
>   	if (ret)
>   		goto out_disable_mux_clock;
>   
> +	info->vproc_on_boot = regulator_get_voltage(info->proc_reg);

This result is used only if we use ccifreq, so this should be enclosed in an if
condition: this will spare us some (yes, small) time on devices that don't use it.

	if (info->soc_data->ccifreq_supported) {
		info->vproc_on_boot = regulator_get_voltage(info->proc_reg);
		if (info->vproc_on_boot < 0) {
			dev_err(....
			goto ..
		}
	}

P.S.: While at it, since the maximum width is 100 columns, the dev_err() call fits,
so don't break that line!

After the requested change:

Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>

WARNING: multiple messages have this Message-ID (diff)
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
	rafael@kernel.org, viresh.kumar@linaro.org, robh+dt@kernel.org,
	krzk+dt@kernel.org, matthias.bgg@gmail.com
Cc: jia-wei.chang@mediatek.com, roger.lu@mediatek.com,
	hsinyi@google.com, khilman@baylibre.com,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH V3 11/15] cpufreq: mediatek: Link CCI device to CPU
Date: Fri, 15 Apr 2022 14:24:08 +0200	[thread overview]
Message-ID: <9fccbb92-1832-bf5d-7804-80dd481663fc@collabora.com> (raw)
In-Reply-To: <20220415055916.28350-12-rex-bc.chen@mediatek.com>

Il 15/04/22 07:59, Rex-BC Chen ha scritto:
> From: Jia-Wei Chang <jia-wei.chang@mediatek.com>
> 
> In some MediaTek SoCs, like MT8183, CPU and CCI share the same power
> supplies. Cpufreq needs to check if CCI devfreq exists and wait until
> CCI devfreq ready before scaling frequency.
> 
> Before CCI devfreq is ready, we record the voltage when booting to
> kernel and use the max(cpu target voltage, booting voltage) to
> prevent cpufreq adjust to the lower voltage which will cause the CCI
> crash because of high frequency and low voltage.
> 
> - Add is_ccifreq_ready() to link CCI device to CPI, and CPU will start
>    DVFS when CCI is ready.
> - Add platform data for MT8183.
> 
> Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
> Signed-off-by: Rex-BC Chen <rex-bc.chen@mediatek.com>

I am enthusiast to see that the solution that I've proposed was welcome!

I only have one nit on this patch, check below:

> ---
>   drivers/cpufreq/mediatek-cpufreq.c | 80 +++++++++++++++++++++++++++++-
>   1 file changed, 79 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/cpufreq/mediatek-cpufreq.c b/drivers/cpufreq/mediatek-cpufreq.c
> index d4c00237e862..dd3f739fede1 100644
> --- a/drivers/cpufreq/mediatek-cpufreq.c
> +++ b/drivers/cpufreq/mediatek-cpufreq.c

..snip..

> @@ -225,6 +251,14 @@ static int mtk_cpufreq_set_target(struct cpufreq_policy *policy,
>   	vproc = dev_pm_opp_get_voltage(opp);
>   	dev_pm_opp_put(opp);
>   
> +	/*
> +	 * If MediaTek cci is supported but is not ready, we will use the value
> +	 * of max(target cpu voltage, booting voltage) to prevent high freqeuncy
> +	 * low voltage crash.
> +	 */
> +	if (info->soc_data->ccifreq_supported && !is_ccifreq_ready(info))
> +		vproc = max(vproc, info->vproc_on_boot);
> +
>   	/*
>   	 * If the new voltage or the intermediate voltage is higher than the
>   	 * current voltage, scale up voltage first.

..snip..

> @@ -423,6 +484,13 @@ static int mtk_cpu_dvfs_info_init(struct mtk_cpu_dvfs_info *info, int cpu)
>   	if (ret)
>   		goto out_disable_mux_clock;
>   
> +	info->vproc_on_boot = regulator_get_voltage(info->proc_reg);

This result is used only if we use ccifreq, so this should be enclosed in an if
condition: this will spare us some (yes, small) time on devices that don't use it.

	if (info->soc_data->ccifreq_supported) {
		info->vproc_on_boot = regulator_get_voltage(info->proc_reg);
		if (info->vproc_on_boot < 0) {
			dev_err(....
			goto ..
		}
	}

P.S.: While at it, since the maximum width is 100 columns, the dev_err() call fits,
so don't break that line!

After the requested change:

Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-04-15 12:24 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  5:59 [PATCH V3 00/15] cpufreq: mediatek: Cleanup and support MT8183 and MT8186 Rex-BC Chen
2022-04-15  5:59 ` Rex-BC Chen
2022-04-15  5:59 ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 01/15] dt-bindings: cpufreq: mediatek: Add MediaTek CCI property Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 02/15] cpufreq: mediatek: Use device print to show logs Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15 12:24   ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15  5:59 ` [PATCH V3 03/15] cpufreq: mediatek: Replace old_* with pre_* Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15 12:24   ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15  5:59 ` [PATCH V3 04/15] cpufreq: mediatek: Record previous target vproc value Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15 12:24   ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-18  1:37     ` Rex-BC Chen
2022-04-18  1:37       ` Rex-BC Chen
2022-04-18  1:37       ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 05/15] cpufreq: mediatek: Add opp notification support Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15 12:24   ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-18  1:38     ` Rex-BC Chen
2022-04-18  1:38       ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 06/15] cpufreq: mediatek: Move voltage limits to platform data Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15 12:24   ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15  5:59 ` [PATCH V3 07/15] cpufreq: mediatek: Add .get function Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 08/15] cpufreq: mediatek: Make sram regulator optional Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 09/15] cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking() Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 10/15] cpufreq: mediatek: Add counter to prevent infinite loop when tracking voltage Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  6:14   ` Hsin-Yi Wang
2022-04-15  6:14     ` Hsin-Yi Wang
2022-04-15  6:14     ` Hsin-Yi Wang
2022-04-15  6:29     ` Rex-BC Chen
2022-04-15  6:29       ` Rex-BC Chen
2022-04-15  6:29       ` Rex-BC Chen
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15 12:24       ` AngeloGioacchino Del Regno
2022-04-15 12:24       ` AngeloGioacchino Del Regno
2022-04-18  1:40       ` Rex-BC Chen
2022-04-18  1:40         ` Rex-BC Chen
2022-04-18  1:40         ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 11/15] cpufreq: mediatek: Link CCI device to CPU Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15 12:24   ` AngeloGioacchino Del Regno [this message]
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-18  1:45     ` Rex-BC Chen
2022-04-18  1:45       ` Rex-BC Chen
2022-04-18  1:45       ` Rex-BC Chen
2022-04-20 18:09   ` Kevin Hilman
2022-04-20 18:09     ` Kevin Hilman
2022-04-20 18:09     ` Kevin Hilman
2022-04-15  5:59 ` [PATCH V3 12/15] cpufreq: mediatek: Add support for MT8186 Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 13/15] arm64: dts: mediatek: Add opp table and clock property for MT8183 cpufreq Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15 12:24   ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-15 12:24     ` AngeloGioacchino Del Regno
2022-04-18  1:46     ` Rex-BC Chen
2022-04-18  1:46       ` Rex-BC Chen
2022-04-18  1:46       ` Rex-BC Chen
2022-04-15  5:59 ` [PATCH V3 14/15] arm64: dts: mediatek: Add MediaTek CCI node for MT8183 Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  6:06   ` Hsin-Yi Wang
2022-04-15  6:06     ` Hsin-Yi Wang
2022-04-15  6:06     ` Hsin-Yi Wang
2022-04-15  6:10     ` Hsin-Yi Wang
2022-04-15  6:10       ` Hsin-Yi Wang
2022-04-15  6:10       ` Hsin-Yi Wang
2022-04-15 12:23   ` AngeloGioacchino Del Regno
2022-04-15 12:23     ` AngeloGioacchino Del Regno
2022-04-15 12:23     ` AngeloGioacchino Del Regno
2022-04-15  5:59 ` [PATCH V3 15/15] arm64: dts: mediatek: Add mediatek, cci property for MT8183 cpufreq Rex-BC Chen
2022-04-15  5:59   ` Rex-BC Chen
2022-04-15  5:59   ` [PATCH V3 15/15] arm64: dts: mediatek: Add mediatek,cci " Rex-BC Chen
2022-04-15 12:23   ` [PATCH V3 15/15] arm64: dts: mediatek: Add mediatek, cci " AngeloGioacchino Del Regno
2022-04-15 12:23     ` AngeloGioacchino Del Regno
2022-04-15 12:23     ` [PATCH V3 15/15] arm64: dts: mediatek: Add mediatek,cci " AngeloGioacchino Del Regno

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=9fccbb92-1832-bf5d-7804-80dd481663fc@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hsinyi@google.com \
    --cc=jia-wei.chang@mediatek.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@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 \
    --cc=rafael@kernel.org \
    --cc=rex-bc.chen@mediatek.com \
    --cc=robh+dt@kernel.org \
    --cc=roger.lu@mediatek.com \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.