From: Nicolas Boichat <drinkcat@chromium.org> To: Rob Herring <robh@kernel.org>, Steven Price <steven.price@arm.com>, Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>, fshao@chromium.org, boris.brezillon@collabora.com, hsinyi@chromium.org, hoegsberg@chromium.org, Nicolas Boichat <drinkcat@chromium.org>, Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: [PATCH v10 3/4] drm/panfrost: devfreq: Disable devfreq when num_supplies > 1 Date: Wed, 13 Jan 2021 14:07:02 +0800 [thread overview] Message-ID: <20210113140546.v10.3.I3af068abe30c9c85cabc4486385c52e56527a509@changeid> (raw) In-Reply-To: <20210113060703.3122661-1-drinkcat@chromium.org> GPUs with more than a single regulator (e.g. G72 on MT8183) will require platform-specific handling for devfreq, for 2 reasons: 1. The opp core (drivers/opp/core.c:_generic_set_opp_regulator) does not support multiple regulators, so we'll need custom handlers. 2. Generally, platforms with 2 regulators have platform-specific constraints on how the voltages should be set (e.g. minimum/maximum voltage difference between them), so we should not just create generic handlers that simply change the voltages without taking care of those constraints. Disable devfreq for now on those GPUs. Signed-off-by: Nicolas Boichat <drinkcat@chromium.org> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> --- (no changes since v9) Changes in v9: - Explain why devfreq needs to be disabled for GPUs with >1 regulators. Changes in v8: - Use DRM_DEV_INFO instead of ERROR Changes in v7: - Fix GPU ID in commit message Changes in v6: - New change drivers/gpu/drm/panfrost/panfrost_devfreq.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/drivers/gpu/drm/panfrost/panfrost_devfreq.c b/drivers/gpu/drm/panfrost/panfrost_devfreq.c index f44d28fad085..812cfecdee3b 100644 --- a/drivers/gpu/drm/panfrost/panfrost_devfreq.c +++ b/drivers/gpu/drm/panfrost/panfrost_devfreq.c @@ -92,6 +92,15 @@ int panfrost_devfreq_init(struct panfrost_device *pfdev) struct thermal_cooling_device *cooling; struct panfrost_devfreq *pfdevfreq = &pfdev->pfdevfreq; + if (pfdev->comp->num_supplies > 1) { + /* + * GPUs with more than 1 supply require platform-specific handling: + * continue without devfreq + */ + DRM_DEV_INFO(dev, "More than 1 supply is not supported yet\n"); + return 0; + } + opp_table = dev_pm_opp_set_regulators(dev, pfdev->comp->supply_names, pfdev->comp->num_supplies); if (IS_ERR(opp_table)) { -- 2.30.0.284.gd98b1dd5eaa7-goog
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Boichat <drinkcat@chromium.org> To: Rob Herring <robh@kernel.org>, Steven Price <steven.price@arm.com>, Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Cc: Nicolas Boichat <drinkcat@chromium.org>, Tomeu Vizoso <tomeu.vizoso@collabora.com>, fshao@chromium.org, David Airlie <airlied@linux.ie>, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, boris.brezillon@collabora.com, hsinyi@chromium.org, hoegsberg@chromium.org Subject: [PATCH v10 3/4] drm/panfrost: devfreq: Disable devfreq when num_supplies > 1 Date: Wed, 13 Jan 2021 14:07:02 +0800 [thread overview] Message-ID: <20210113140546.v10.3.I3af068abe30c9c85cabc4486385c52e56527a509@changeid> (raw) In-Reply-To: <20210113060703.3122661-1-drinkcat@chromium.org> GPUs with more than a single regulator (e.g. G72 on MT8183) will require platform-specific handling for devfreq, for 2 reasons: 1. The opp core (drivers/opp/core.c:_generic_set_opp_regulator) does not support multiple regulators, so we'll need custom handlers. 2. Generally, platforms with 2 regulators have platform-specific constraints on how the voltages should be set (e.g. minimum/maximum voltage difference between them), so we should not just create generic handlers that simply change the voltages without taking care of those constraints. Disable devfreq for now on those GPUs. Signed-off-by: Nicolas Boichat <drinkcat@chromium.org> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> --- (no changes since v9) Changes in v9: - Explain why devfreq needs to be disabled for GPUs with >1 regulators. Changes in v8: - Use DRM_DEV_INFO instead of ERROR Changes in v7: - Fix GPU ID in commit message Changes in v6: - New change drivers/gpu/drm/panfrost/panfrost_devfreq.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/drivers/gpu/drm/panfrost/panfrost_devfreq.c b/drivers/gpu/drm/panfrost/panfrost_devfreq.c index f44d28fad085..812cfecdee3b 100644 --- a/drivers/gpu/drm/panfrost/panfrost_devfreq.c +++ b/drivers/gpu/drm/panfrost/panfrost_devfreq.c @@ -92,6 +92,15 @@ int panfrost_devfreq_init(struct panfrost_device *pfdev) struct thermal_cooling_device *cooling; struct panfrost_devfreq *pfdevfreq = &pfdev->pfdevfreq; + if (pfdev->comp->num_supplies > 1) { + /* + * GPUs with more than 1 supply require platform-specific handling: + * continue without devfreq + */ + DRM_DEV_INFO(dev, "More than 1 supply is not supported yet\n"); + return 0; + } + opp_table = dev_pm_opp_set_regulators(dev, pfdev->comp->supply_names, pfdev->comp->num_supplies); if (IS_ERR(opp_table)) { -- 2.30.0.284.gd98b1dd5eaa7-goog _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-01-13 6:09 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-13 6:06 [PATCH v10 0/4] drm/panfrost: Add support for mt8183 GPU Nicolas Boichat 2021-01-13 6:06 ` Nicolas Boichat 2021-01-13 6:06 ` Nicolas Boichat 2021-01-13 6:06 ` Nicolas Boichat 2021-01-13 6:07 ` [PATCH v10 1/4] dt-bindings: gpu: mali-bifrost: Add Mediatek MT8183 Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat 2021-01-25 19:27 ` Rob Herring 2021-01-25 19:27 ` Rob Herring 2021-01-25 19:27 ` Rob Herring 2021-01-25 19:27 ` Rob Herring 2021-01-13 6:07 ` [PATCH v10 2/4] arm64: dts: mt8183: Add node for the Mali GPU Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat 2021-01-25 19:26 ` Rob Herring 2021-01-25 19:26 ` Rob Herring 2021-01-25 19:26 ` Rob Herring 2021-01-26 1:03 ` Nicolas Boichat 2021-01-26 1:03 ` Nicolas Boichat 2021-01-26 1:03 ` Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat [this message] 2021-01-13 6:07 ` [PATCH v10 3/4] drm/panfrost: devfreq: Disable devfreq when num_supplies > 1 Nicolas Boichat 2021-01-14 15:10 ` Steven Price 2021-01-14 15:10 ` Steven Price 2021-01-13 6:07 ` [PATCH v10 4/4] drm/panfrost: Add mt8183-mali compatible string Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat 2021-01-13 6:07 ` Nicolas Boichat 2021-01-14 15:10 ` Steven Price 2021-01-14 15:10 ` Steven Price 2021-01-14 15:10 ` Steven Price 2021-01-14 15:10 ` Steven Price 2021-01-13 7:17 ` [PATCH v10 0/4] drm/panfrost: Add support for mt8183 GPU Tomeu Vizoso 2021-01-13 7:17 ` Tomeu Vizoso 2021-01-13 7:17 ` Tomeu Vizoso 2021-01-13 7:17 ` Tomeu Vizoso
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=20210113140546.v10.3.I3af068abe30c9c85cabc4486385c52e56527a509@changeid \ --to=drinkcat@chromium.org \ --cc=airlied@linux.ie \ --cc=alyssa.rosenzweig@collabora.com \ --cc=boris.brezillon@collabora.com \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=fshao@chromium.org \ --cc=hoegsberg@chromium.org \ --cc=hsinyi@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robh@kernel.org \ --cc=steven.price@arm.com \ --cc=tomeu.vizoso@collabora.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: linkBe 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.