From: Akhil P Oommen <akhilpo@codeaurora.org>
To: mka@chromium.org
Cc: freedreno@lists.freedesktop.org, robh@kernel.org,
robdclark@gmail.com, linux-arm-msm@vger.kernel.org,
dri-devel@freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [2/2] drm/msm: Add support for GPU cooling
Date: Mon, 12 Oct 2020 19:03:51 +0530 [thread overview]
Message-ID: <cab2105e-7a8c-988f-dcc1-056692a94e8b@codeaurora.org> (raw)
In-Reply-To: <20201009183640.GB1292413@google.com>
On 10/10/2020 12:06 AM, mka@chromium.org wrote:
> Hi Akhil,
>
> On Thu, Oct 08, 2020 at 10:39:07PM +0530, Akhil P Oommen wrote:
>> Register GPU as a devfreq cooling device so that it can be passively
>> cooled by the thermal framework.
>>
>> Signed-off-by: Akhil P Oommen <akhilpo@codeaurora.org>
>> ---
>> drivers/gpu/drm/msm/msm_gpu.c | 13 ++++++++++++-
>> drivers/gpu/drm/msm/msm_gpu.h | 2 ++
>> 2 files changed, 14 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/msm/msm_gpu.c b/drivers/gpu/drm/msm/msm_gpu.c
>> index 55d1648..93ffd66 100644
>> --- a/drivers/gpu/drm/msm/msm_gpu.c
>> +++ b/drivers/gpu/drm/msm/msm_gpu.c
>> @@ -14,6 +14,7 @@
>> #include <generated/utsrelease.h>
>> #include <linux/string_helpers.h>
>> #include <linux/devfreq.h>
>> +#include <linux/devfreq_cooling.h>
>> #include <linux/devcoredump.h>
>> #include <linux/sched/task.h>
>>
>> @@ -107,9 +108,18 @@ static void msm_devfreq_init(struct msm_gpu *gpu)
>> if (IS_ERR(gpu->devfreq.devfreq)) {
>> DRM_DEV_ERROR(&gpu->pdev->dev, "Couldn't initialize GPU devfreq\n");
>> gpu->devfreq.devfreq = NULL;
>> + return;
>> }
>>
>> devfreq_suspend_device(gpu->devfreq.devfreq);
>> +
>> + gpu->cooling = of_devfreq_cooling_register(gpu->pdev->dev.of_node,
>> + gpu->devfreq.devfreq);
>> + if (IS_ERR(gpu->cooling)) {
>> + DRM_DEV_ERROR(&gpu->pdev->dev,
>> + "Couldn't register GPU cooling device\n");
>> + gpu->cooling = NULL;
>> + }
>> }
>>
>> static int enable_pwrrail(struct msm_gpu *gpu)
>> @@ -926,7 +936,6 @@ int msm_gpu_init(struct drm_device *drm, struct platform_device *pdev,
>>
>> msm_devfreq_init(gpu);
>>
>> -
>> gpu->aspace = gpu->funcs->create_address_space(gpu, pdev);
>>
>> if (gpu->aspace == NULL)
>> @@ -1005,4 +1014,6 @@ void msm_gpu_cleanup(struct msm_gpu *gpu)
>> gpu->aspace->mmu->funcs->detach(gpu->aspace->mmu);
>> msm_gem_address_space_put(gpu->aspace);
>> }
>> +
>> + devfreq_cooling_unregister(gpu->cooling);
>
> Resources should be released in reverse order, otherwise the cooling device
> could use resources that have already been freed.
> Why do you think this is not the correct order? If you are thinking
about devfreq struct, it is managed device resource.
-Akhil
next prev parent reply other threads:[~2020-10-12 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 17:09 [PATCH 1/2] arm64: dts: qcom: sc7180: Add gpu cooling support Akhil P Oommen
2020-10-08 17:09 ` [PATCH 2/2] drm/msm: Add support for GPU cooling Akhil P Oommen
2020-10-09 18:36 ` [2/2] " mka
2020-10-12 13:33 ` Akhil P Oommen [this message]
2020-10-12 17:40 ` mka
2020-10-13 13:53 ` Akhil P Oommen
2020-10-13 17:40 ` mka
2020-10-13 19:21 ` Akhil P Oommen
2020-10-14 1:09 ` mka
2020-10-09 15:05 ` [PATCH 1/2] arm64: dts: qcom: sc7180: Add gpu cooling support Doug Anderson
2020-10-09 16:57 ` Matthias Kaehlcke
2020-10-14 13:29 ` Akhil P Oommen
2020-10-14 18:37 ` manafm
2020-10-15 22:19 ` Matthias Kaehlcke
2020-10-16 13:46 ` Akhil P Oommen
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=cab2105e-7a8c-988f-dcc1-056692a94e8b@codeaurora.org \
--to=akhilpo@codeaurora.org \
--cc=dri-devel@freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robdclark@gmail.com \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).