From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
rafael@kernel.org
Cc: viresh.kumar@linaro.org, rex-bc.chen@mediatek.com,
jia-wei.chang@mediatek.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] cpufreq: Add MT8186 to cpufreq-dt-platdev blocklist
Date: Fri, 17 Jun 2022 12:16:53 +0200 [thread overview]
Message-ID: <71bf73f9-fa60-e4ba-a339-64d876514af2@gmail.com> (raw)
In-Reply-To: <20220617090652.56247-1-angelogioacchino.delregno@collabora.com>
On 17/06/2022 11:06, AngeloGioacchino Del Regno wrote:
> This SoC shall use the mediatek-cpufreq driver, or the system will
> crash upon any clock scaling request: add it to the cpufreq-dt-platdev
> blocklist.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Fixes: 39b360102f3a ("cpufreq: mediatek: Add support for MT8186")
Fixes tag should be before any Rb, SoB etc tags.
With that:
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 96de1536e1cb..2c96de3f2d83 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -127,6 +127,7 @@ static const struct of_device_id blocklist[] __initconst = {
> { .compatible = "mediatek,mt8173", },
> { .compatible = "mediatek,mt8176", },
> { .compatible = "mediatek,mt8183", },
> + { .compatible = "mediatek,mt8186", },
> { .compatible = "mediatek,mt8365", },
> { .compatible = "mediatek,mt8516", },
>
WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
rafael@kernel.org
Cc: viresh.kumar@linaro.org, rex-bc.chen@mediatek.com,
jia-wei.chang@mediatek.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] cpufreq: Add MT8186 to cpufreq-dt-platdev blocklist
Date: Fri, 17 Jun 2022 12:16:53 +0200 [thread overview]
Message-ID: <71bf73f9-fa60-e4ba-a339-64d876514af2@gmail.com> (raw)
In-Reply-To: <20220617090652.56247-1-angelogioacchino.delregno@collabora.com>
On 17/06/2022 11:06, AngeloGioacchino Del Regno wrote:
> This SoC shall use the mediatek-cpufreq driver, or the system will
> crash upon any clock scaling request: add it to the cpufreq-dt-platdev
> blocklist.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Fixes: 39b360102f3a ("cpufreq: mediatek: Add support for MT8186")
Fixes tag should be before any Rb, SoB etc tags.
With that:
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 96de1536e1cb..2c96de3f2d83 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -127,6 +127,7 @@ static const struct of_device_id blocklist[] __initconst = {
> { .compatible = "mediatek,mt8173", },
> { .compatible = "mediatek,mt8176", },
> { .compatible = "mediatek,mt8183", },
> + { .compatible = "mediatek,mt8186", },
> { .compatible = "mediatek,mt8365", },
> { .compatible = "mediatek,mt8516", },
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-17 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 9:06 [PATCH] cpufreq: Add MT8186 to cpufreq-dt-platdev blocklist AngeloGioacchino Del Regno
2022-06-17 9:06 ` AngeloGioacchino Del Regno
2022-06-17 10:16 ` Matthias Brugger [this message]
2022-06-17 10:16 ` Matthias Brugger
2022-06-17 10:48 ` AngeloGioacchino Del Regno
2022-06-17 10:48 ` 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=71bf73f9-fa60-e4ba-a339-64d876514af2@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=jia-wei.chang@mediatek.com \
--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=rafael@kernel.org \
--cc=rex-bc.chen@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.