From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Anatoliy Klymenko <anatoliy.klymenko@amd.com>,
laurent.pinchart@ideasonboard.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
michal.simek@amd.com, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] drm: xlnx: zynqmp_dpsub: Don't generate vblank in live mode
Date: Wed, 17 Jan 2024 16:20:10 +0200 [thread overview]
Message-ID: <beb551c7-bb7e-4cd0-b166-e9aad90c4620@ideasonboard.com> (raw)
In-Reply-To: <20240112234222.913138-4-anatoliy.klymenko@amd.com>
On 13/01/2024 01:42, Anatoliy Klymenko wrote:
> Filter out status register against interrupts' mask.
> Some events are being reported via DP status register, even if
> corresponding interrupts have been disabled. Avoid processing
> of such events in interrupt handler context.
The subject talks about vblank and live mode, the the description
doesn't. Can you elaborate in the desc a bit about when this is an issue
and why it wasn't before?
> Signed-off-by: Anatoliy Klymenko <anatoliy.klymenko@amd.com>
> ---
> drivers/gpu/drm/xlnx/zynqmp_dp.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xlnx/zynqmp_dp.c b/drivers/gpu/drm/xlnx/zynqmp_dp.c
> index d60b7431603f..571c5dbc97e5 100644
> --- a/drivers/gpu/drm/xlnx/zynqmp_dp.c
> +++ b/drivers/gpu/drm/xlnx/zynqmp_dp.c
> @@ -1624,8 +1624,16 @@ static irqreturn_t zynqmp_dp_irq_handler(int irq, void *data)
> u32 status, mask;
>
> status = zynqmp_dp_read(dp, ZYNQMP_DP_INT_STATUS);
> + zynqmp_dp_write(dp, ZYNQMP_DP_INT_STATUS, status);
> mask = zynqmp_dp_read(dp, ZYNQMP_DP_INT_MASK);
> - if (!(status & ~mask))
> +
> + /*
> + * Status register may report some events, which corresponding interrupts
> + * have been disabled. Filter out those events against interrupts' mask.
> + */
> + status &= ~mask;
> +
> + if (!status)
> return IRQ_NONE;
>
> /* dbg for diagnostic, but not much that the driver can do */
> @@ -1634,7 +1642,6 @@ static irqreturn_t zynqmp_dp_irq_handler(int irq, void *data)
> if (status & ZYNQMP_DP_INT_CHBUF_OVERFLW_MASK)
> dev_dbg_ratelimited(dp->dev, "overflow interrupt\n");
>
> - zynqmp_dp_write(dp, ZYNQMP_DP_INT_STATUS, status);
>
> if (status & ZYNQMP_DP_INT_VBLANK_START)
> zynqmp_dpsub_drm_handle_vblank(dp->dpsub);
Moving the zynqmp_dp_write() is not related to this fix, is it? I think
it should be in a separate patch.
Tomi
next prev parent reply other threads:[~2024-01-17 14:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 23:42 [PATCH 0/4] Fixing live video input in ZynqMP DPSUB Anatoliy Klymenko
2024-01-12 23:42 ` [PATCH 1/4] drm: xlnx: zynqmp_dpsub: Make drm bridge discoverable Anatoliy Klymenko
2024-01-17 14:06 ` Tomi Valkeinen
2024-01-17 14:24 ` Laurent Pinchart
2024-01-12 23:42 ` [PATCH 2/4] drm: xlnx: zynqmp_dpsub: Fix timing for live mode Anatoliy Klymenko
2024-01-17 14:11 ` Tomi Valkeinen
2024-01-12 23:42 ` [PATCH 3/4] drm: xlnx: zynqmp_dpsub: Don't generate vblank in " Anatoliy Klymenko
2024-01-17 14:20 ` Tomi Valkeinen [this message]
2024-01-12 23:42 ` [PATCH 4/4] drm: xlnx: zynqmp_dpsub: Set live video in format Anatoliy Klymenko
2024-01-17 15:32 ` Tomi Valkeinen
2024-01-15 8:28 ` [PATCH 0/4] Fixing live video input in ZynqMP DPSUB Maxime Ripard
2024-01-17 14:23 ` Laurent Pinchart
2024-01-26 12:26 ` Maxime Ripard
2024-01-26 23:18 ` Klymenko, Anatoliy
2024-02-01 17:01 ` Maxime Ripard
2024-02-04 9:56 ` Laurent Pinchart
2024-02-09 15:41 ` Maxime Ripard
[not found] <mailman.1660.1705501214.2415.dri-devel@lists.freedesktop.org>
2024-01-19 5:53 ` [PATCH 3/4] drm: xlnx: zynqmp_dpsub: Don't generate vblank in live mode Klymenko, Anatoliy
2024-01-19 12:29 ` Laurent Pinchart
2024-01-19 21:54 ` Klymenko, Anatoliy
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=beb551c7-bb7e-4cd0-b166-e9aad90c4620@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=anatoliy.klymenko@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michal.simek@amd.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®