From: Boris Brezillon <boris.brezillon@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: "Liviu Dudau" <liviu.dudau@arm.com>,
"Adrián Larumbe" <adrian.larumbe@collabora.com>,
dri-devel@lists.freedesktop.org, kernel@collabora.com
Subject: Re: [PATCH v2 4/5] drm/panthor: Let IRQ handlers clear the interrupts themselves
Date: Wed, 2 Apr 2025 12:58:20 +0200 [thread overview]
Message-ID: <20250402125820.49c5a450@collabora.com> (raw)
In-Reply-To: <2e565589-4845-4007-80be-adb6b370e911@arm.com>
On Wed, 2 Apr 2025 11:20:17 +0100
Steven Price <steven.price@arm.com> wrote:
> > static void panthor_mmu_irq_handler(struct panthor_device *ptdev, u32 status)
> > {
> > bool has_unhandled_faults = false;
> >
> > status = panthor_mmu_fault_mask(ptdev, status);
> > while (status) {
> > u32 as = ffs(status | (status >> 16)) - 1;
>
> panthor_mmu_fault_mask() masks status with GENMASK(15, 0), so AFAICT
> (status >> 16) is always 0.
>
> Which isn't a big issue, other than you are now only clearing IRQs which
> are recognised by the loop.
Quick note on that: I think it's been written when I was trying to add
support for CSF in panfrost, and panthor_mmu_fault_mask() (at the time
it was panfrost_mmu_fault_mask()) was a way to have a different
fault_mask for JM and CSF. Now that JM support in panthor is being
considered [1], I'd prefer to keep this logic, even if it seems silly
right now.
[1]https://gitlab.freedesktop.org/panfrost/linux/-/merge_requests/16
next prev parent reply other threads:[~2025-04-02 10:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 18:23 [PATCH v2 0/5] drm/panthor: Misc fixes Boris Brezillon
2025-04-01 18:23 ` [PATCH v2 1/5] drm/panthor: Fix GPU_COHERENCY_ACE[_LITE] definitions Boris Brezillon
2025-04-02 10:19 ` Steven Price
2025-04-01 18:23 ` [PATCH v2 2/5] drm/panthor: Call panthor_gpu_coherency_init() after PM resume() Boris Brezillon
2025-04-02 10:20 ` Steven Price
2025-04-01 18:23 ` [PATCH v2 3/5] drm/panthor: Update panthor_mmu::irq::mask when needed Boris Brezillon
2025-04-02 10:20 ` Steven Price
2025-04-01 18:23 ` [PATCH v2 4/5] drm/panthor: Let IRQ handlers clear the interrupts themselves Boris Brezillon
2025-04-01 20:36 ` Liviu Dudau
2025-04-02 10:20 ` Steven Price
2025-04-02 10:52 ` Boris Brezillon
2025-04-02 10:58 ` Boris Brezillon [this message]
2025-04-02 11:03 ` Steven Price
2025-04-01 18:23 ` [PATCH v2 5/5] drm/panthor: Don't update MMU_INT_MASK in panthor_mmu_irq_handler() Boris Brezillon
2025-04-01 20:38 ` Liviu Dudau
2025-04-02 10:20 ` Steven Price
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=20250402125820.49c5a450@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=liviu.dudau@arm.com \
--cc=steven.price@arm.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 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.