From: Steven Price <steven.price@arm.com>
To: Boris Brezillon <boris.brezillon@collabora.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Daniel Stone <daniel@fooishbar.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Karunika Choo <karunika.choo@arm.com>,
Chia-I Wu <olvaffe@gmail.com>
Subject: Re: [PATCH v2] drm/panthor: Simplify mmu_hw_do_operation_locked
Date: Thu, 28 Aug 2025 11:52:52 +0100 [thread overview]
Message-ID: <cc81e5f1-386c-4e2c-a306-a00fd9d4b754@arm.com> (raw)
In-Reply-To: <20250815134226.57703-1-steven.price@arm.com>
On 15/08/2025 14:42, Steven Price wrote:
> The only callers to mmu_hw_do_operation_locked() pass an 'op' of either
> AS_COMAND_FLUSH_MEM or AS_COMMAND_FLUSH_PT. This means the code paths
> after that are dead. Removing those paths means the
> mmu_hw_do_flush_on_gpu_ctrl() function might has well be inlined.
>
> Simplify everything by having a switch statement for the type of 'op'
> (warning if we get an unexpected value) and removing the dead cases.
>
> Suggested-by: Daniel Stone <daniel@fooishbar.org>
> Signed-off-by: Steven Price <steven.price@arm.com>
Applied to drm-misc-next.
Thanks,
Steve
> ---
> Changes from v1:
> * As well as removing dead code, inline mmu_hw_do_flush_on_gpu_ctrl
>
> drivers/gpu/drm/panthor/panthor_mmu.c | 57 ++++++++++++---------------
> 1 file changed, 26 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_mmu.c b/drivers/gpu/drm/panthor/panthor_mmu.c
> index 367c89aca558..9d77e7c16ed2 100644
> --- a/drivers/gpu/drm/panthor/panthor_mmu.c
> +++ b/drivers/gpu/drm/panthor/panthor_mmu.c
> @@ -569,15 +569,37 @@ static void lock_region(struct panthor_device *ptdev, u32 as_nr,
> write_cmd(ptdev, as_nr, AS_COMMAND_LOCK);
> }
>
> -static int mmu_hw_do_flush_on_gpu_ctrl(struct panthor_device *ptdev, int as_nr,
> - u32 op)
> +static int mmu_hw_do_operation_locked(struct panthor_device *ptdev, int as_nr,
> + u64 iova, u64 size, u32 op)
> {
> const u32 l2_flush_op = CACHE_CLEAN | CACHE_INV;
> - u32 lsc_flush_op = 0;
> + u32 lsc_flush_op;
> int ret;
>
> - if (op == AS_COMMAND_FLUSH_MEM)
> + lockdep_assert_held(&ptdev->mmu->as.slots_lock);
> +
> + switch (op) {
> + case AS_COMMAND_FLUSH_MEM:
> lsc_flush_op = CACHE_CLEAN | CACHE_INV;
> + break;
> + case AS_COMMAND_FLUSH_PT:
> + lsc_flush_op = 0;
> + break;
> + default:
> + drm_WARN(&ptdev->base, 1, "Unexpected AS_COMMAND: %d", op);
> + return -EINVAL;
> + }
> +
> + if (as_nr < 0)
> + return 0;
> +
> + /*
> + * If the AS number is greater than zero, then we can be sure
> + * the device is up and running, so we don't need to explicitly
> + * power it up
> + */
> +
> + lock_region(ptdev, as_nr, iova, size);
>
> ret = wait_ready(ptdev, as_nr);
> if (ret)
> @@ -598,33 +620,6 @@ static int mmu_hw_do_flush_on_gpu_ctrl(struct panthor_device *ptdev, int as_nr,
> return wait_ready(ptdev, as_nr);
> }
>
> -static int mmu_hw_do_operation_locked(struct panthor_device *ptdev, int as_nr,
> - u64 iova, u64 size, u32 op)
> -{
> - lockdep_assert_held(&ptdev->mmu->as.slots_lock);
> -
> - if (as_nr < 0)
> - return 0;
> -
> - /*
> - * If the AS number is greater than zero, then we can be sure
> - * the device is up and running, so we don't need to explicitly
> - * power it up
> - */
> -
> - if (op != AS_COMMAND_UNLOCK)
> - lock_region(ptdev, as_nr, iova, size);
> -
> - if (op == AS_COMMAND_FLUSH_MEM || op == AS_COMMAND_FLUSH_PT)
> - return mmu_hw_do_flush_on_gpu_ctrl(ptdev, as_nr, op);
> -
> - /* Run the MMU operation */
> - write_cmd(ptdev, as_nr, op);
> -
> - /* Wait for the flush to complete */
> - return wait_ready(ptdev, as_nr);
> -}
> -
> static int mmu_hw_do_operation(struct panthor_vm *vm,
> u64 iova, u64 size, u32 op)
> {
prev parent reply other threads:[~2025-08-28 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 13:42 [PATCH v2] drm/panthor: Simplify mmu_hw_do_operation_locked Steven Price
2025-08-15 14:01 ` Karunika Choo
2025-08-15 14:10 ` Steven Price
2025-08-15 14:53 ` Karunika Choo
2025-08-28 10:52 ` Steven Price [this message]
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=cc81e5f1-386c-4e2c-a306-a00fd9d4b754@arm.com \
--to=steven.price@arm.com \
--cc=boris.brezillon@collabora.com \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=karunika.choo@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=olvaffe@gmail.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: 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).