From: Maxime Ripard <mripard@redhat.com>
To: Sarah Walker <sarah.walker@imgtec.com>
Cc: matthew.brost@intel.com, dri-devel@lists.freedesktop.org,
christian.koenig@amd.com, luben.tuikov@amd.com, dakr@redhat.com,
donald.robson@imgtec.com, boris.brezillon@collabora.com,
sumit.semwal@linaro.org, faith.ekstrand@collabora.com
Subject: Re: [PATCH v3 09/17] drm/imagination: Implement power management
Date: Fri, 7 Jul 2023 14:48:06 +0200 [thread overview]
Message-ID: <twmetot6wcg5j7wnqy2gqohhrwhsgaizz5psou5etur6cavjjj@fwky6irlxubt> (raw)
In-Reply-To: <20230613144800.52657-10-sarah.walker@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 2864 bytes --]
On Tue, Jun 13, 2023 at 03:47:52PM +0100, Sarah Walker wrote:
> @@ -503,21 +506,31 @@ pvr_device_init(struct pvr_device *pvr_dev)
> if (err)
> goto err_device_clk_fini;
>
> + /* Explicitly power the GPU so we can access control registers before the FW is booted. */
> + err = pm_runtime_resume_and_get(dev);
> + if (err)
> + goto err_device_clk_fini;
> +
> /* Map the control registers into memory. */
> err = pvr_device_reg_init(pvr_dev);
> if (err)
> - goto err_device_clk_fini;
> + goto err_pm_runtime_put;
>
> /* Perform GPU-specific initialization steps. */
> err = pvr_device_gpu_init(pvr_dev);
> if (err)
> goto err_device_reg_fini;
>
> + pm_runtime_put_autosuspend(dev);
> +
You probably can use pm_runtime_put here
> @@ -532,12 +545,17 @@ pvr_device_init(struct pvr_device *pvr_dev)
> void
> pvr_device_fini(struct pvr_device *pvr_dev)
> {
> + struct drm_device *drm_dev = from_pvr_device(pvr_dev);
> + struct device *dev = drm_dev->dev;
> +
> /*
> * Deinitialization stages are performed in reverse order compared to
> * the initialization stages in pvr_device_init().
> */
> + pm_runtime_get_sync(dev);
> pvr_device_gpu_fini(pvr_dev);
> pvr_device_reg_fini(pvr_dev);
AFAIK gpu_fini releases the firmware and reg_fini drops the register
mapping address, I don't think you need the device powered up for that.
> @@ -130,6 +133,20 @@ struct pvr_device {
>
> /** @fw_dev: Firmware related data. */
> struct pvr_fw_device fw_dev;
> +
> + struct {
> + /** @work: Work item for watchdog callback. */
> + struct delayed_work work;
> +
> + /** @old_kccb_cmds_executed: KCCB command execution count at last watchdog poll. */
> + u32 old_kccb_cmds_executed;
> +
> + /** @kccb_stall_count: Number of watchdog polls KCCB has been stalled for. */
> + u32 kccb_stall_count;
> + } watchdog;
> +
> + /** @lost: %true if the device has been lost. */
> + bool lost;
The device being "lost" isn't clear to me. Does it mean it's
unresponsive or stuck somehow?
> @@ -1285,9 +1303,15 @@ pvr_probe(struct platform_device *plat_dev)
>
> platform_set_drvdata(plat_dev, drm_dev);
>
> + devm_pm_runtime_enable(&plat_dev->dev);
> +
> + pm_runtime_set_autosuspend_delay(&plat_dev->dev, 50);
> + pm_runtime_use_autosuspend(&plat_dev->dev);
> + pvr_power_init(pvr_dev);
The name threw me off a bit. It doesn't look like it's power related but
you init the watchdog timer?
I can't really tell from that patch, but if it's not done in a later
patch you'll probably need a call to sprinkle your driver with a few
_mark_last_busy calls (at least in the job submission path?)
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-07-07 12:48 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:47 [PATCH v3 00/17] Imagination Technologies PowerVR DRM driver Sarah Walker
2023-06-13 14:47 ` [PATCH v3 01/17] sizes.h: Add entries between 32G and 64T Sarah Walker
2023-06-16 12:10 ` Linus Walleij
2023-06-26 13:25 ` Frank Binns
2023-06-13 14:47 ` [PATCH v3 02/17] dt-bindings: gpu: Add Imagination Technologies PowerVR GPU Sarah Walker
2023-06-13 17:38 ` Andrew Davis
2023-06-16 11:23 ` Frank Binns
2023-06-13 18:24 ` Krzysztof Kozlowski
2023-06-14 14:34 ` Frank Binns
2023-06-15 20:50 ` Rob Herring
2023-06-16 11:27 ` Frank Binns
2023-06-16 12:48 ` Linus Walleij
2023-06-16 14:23 ` Rob Herring
2023-07-04 15:13 ` Frank Binns
2023-07-05 7:08 ` Linus Walleij
2023-06-13 14:47 ` [PATCH v3 03/17] drm/imagination/uapi: Add PowerVR driver UAPI Sarah Walker
2023-06-13 14:47 ` [PATCH v3 04/17] drm/imagination: Add skeleton PowerVR driver Sarah Walker
2023-07-07 12:46 ` Maxime Ripard
2023-07-14 13:15 ` Frank Binns
2023-06-13 14:47 ` [PATCH v3 05/17] drm/imagination: Get GPU resources Sarah Walker
2023-06-13 18:12 ` Andrew Davis
2023-06-16 11:23 ` Frank Binns
2023-07-07 12:47 ` Maxime Ripard
2023-07-14 13:39 ` Frank Binns
2023-06-13 14:47 ` [PATCH v3 06/17] drm/imagination: Add GPU register and FWIF headers Sarah Walker
2023-06-13 14:47 ` [PATCH v3 07/17] drm/imagination: Add GPU ID parsing and firmware loading Sarah Walker
2023-06-17 12:48 ` Adam Ford
2023-06-26 13:22 ` Frank Binns
2023-06-26 15:38 ` Adam Ford
2023-07-05 13:13 ` Frank Binns
2023-07-05 18:10 ` Marek Vasut
2023-06-13 14:47 ` [PATCH v3 08/17] drm/imagination: Add GEM and VM related code Sarah Walker
2023-06-13 14:47 ` [PATCH v3 09/17] drm/imagination: Implement power management Sarah Walker
2023-07-07 12:48 ` Maxime Ripard [this message]
2023-07-14 13:47 ` Frank Binns
2023-06-13 14:47 ` [PATCH v3 10/17] drm/imagination: Implement firmware infrastructure and META FW support Sarah Walker
2023-06-13 14:47 ` [PATCH v3 11/17] drm/imagination: Implement MIPS firmware processor and MMU support Sarah Walker
2023-06-13 14:47 ` [PATCH v3 12/17] drm/imagination: Implement free list and HWRT create and destroy ioctls Sarah Walker
2023-06-13 14:47 ` [PATCH v3 13/17] drm/imagination: Implement context creation/destruction ioctls Sarah Walker
2023-06-13 14:47 ` [PATCH v3 14/17] drm/imagination: Implement job submission and scheduling Sarah Walker
2023-06-13 14:47 ` [PATCH v3 15/17] drm/imagination: Add firmware trace to debugfs Sarah Walker
2023-06-13 14:47 ` [PATCH v3 16/17] drm/imagination: Add driver documentation Sarah Walker
2023-06-13 14:48 ` [PATCH v3 17/17] arm64: dts: ti: k3-am62-main: Add GPU device node [DO NOT MERGE] Sarah Walker
2023-06-13 18:26 ` [PATCH v3 00/17] Imagination Technologies PowerVR DRM driver Krzysztof Kozlowski
2023-06-16 12:29 ` Linus Walleij
2023-06-16 14:06 ` H. Nikolaus Schaller
2023-06-26 13:45 ` Frank Binns
2023-06-26 18:48 ` H. Nikolaus Schaller
2023-06-16 14:08 ` H. Nikolaus Schaller
2023-06-26 13:31 ` Frank Binns
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=twmetot6wcg5j7wnqy2gqohhrwhsgaizz5psou5etur6cavjjj@fwky6irlxubt \
--to=mripard@redhat.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=dakr@redhat.com \
--cc=donald.robson@imgtec.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith.ekstrand@collabora.com \
--cc=luben.tuikov@amd.com \
--cc=matthew.brost@intel.com \
--cc=sarah.walker@imgtec.com \
--cc=sumit.semwal@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 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).