From: Naushir Patuck <naush@raspberrypi.com>
To: Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-media@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, jacopo.mondi@ideasonboard.com,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Naushir Patuck <naush@raspberrypi.com>
Subject: [PATCH v1 5/5] drivers: media: bcm2835-unicam: Correctly handle FS + FE ISR condition
Date: Fri, 22 Nov 2024 08:41:52 +0000 [thread overview]
Message-ID: <20241122084152.1841419-6-naush@raspberrypi.com> (raw)
In-Reply-To: <20241122084152.1841419-1-naush@raspberrypi.com>
This change aligns the FS/FE interrupt handling with the Raspberry Pi
kernel downstream Unicam driver.
If we get a simultaneous FS + FE interrupt for the same frame, it cannot
be marked as completed and returned to userland as the framebuffer will
be refilled by Unicam on the next sensor frame. Additionally, the
timestamp will be set to 0 as the FS interrupt handling code will not
have run yet.
To avoid these problems, the frame is considered dropped in the FE
handler, and will be returned to userland on the subsequent sensor frame.
Signed-off-by: Naushir Patuck <naush@raspberrypi.com>
---
.../media/platform/broadcom/bcm2835-unicam.c | 39 +++++++++++++++++--
1 file changed, 35 insertions(+), 4 deletions(-)
diff --git a/drivers/media/platform/broadcom/bcm2835-unicam.c b/drivers/media/platform/broadcom/bcm2835-unicam.c
index f10064107d54..0d2aa25d483f 100644
--- a/drivers/media/platform/broadcom/bcm2835-unicam.c
+++ b/drivers/media/platform/broadcom/bcm2835-unicam.c
@@ -773,10 +773,26 @@ static irqreturn_t unicam_isr(int irq, void *dev)
* as complete, as the HW will reuse that buffer.
*/
if (node->cur_frm && node->cur_frm != node->next_frm) {
+ /*
+ * This condition checks if FE + FS for the same
+ * frame has occurred. In such cases, we cannot
+ * return out the frame, as no buffer handling
+ * or timestamping has yet been done as part of
+ * the FS handler.
+ */
+ if (!node->cur_frm->vb.vb2_buf.timestamp) {
+ dev_dbg(unicam->v4l2_dev.dev,
+ "ISR: FE without FS, dropping frame\n");
+ continue;
+ }
+
unicam_process_buffer_complete(node, sequence);
+ node->cur_frm = node->next_frm;
+ node->next_frm = NULL;
inc_seq = true;
+ } else {
+ node->cur_frm = node->next_frm;
}
- node->cur_frm = node->next_frm;
}
/*
@@ -812,10 +828,25 @@ static irqreturn_t unicam_isr(int irq, void *dev)
i);
/*
* Set the next frame output to go to a dummy frame
- * if we have not managed to obtain another frame
- * from the queue.
+ * if no buffer currently queued.
*/
- unicam_schedule_dummy_buffer(node);
+ if (!node->next_frm ||
+ node->next_frm == node->cur_frm) {
+ unicam_schedule_dummy_buffer(node);
+ } else if (unicam->node[i].cur_frm) {
+ /*
+ * Repeated FS without FE. Hardware will have
+ * swapped buffers, but the cur_frm doesn't
+ * contain valid data. Return cur_frm to the
+ * queue.
+ */
+ spin_lock(&node->dma_queue_lock);
+ list_add_tail(&node->cur_frm->list,
+ &node->dma_queue);
+ spin_unlock(&node->dma_queue_lock);
+ node->cur_frm = node->next_frm;
+ node->next_frm = NULL;
+ }
}
unicam_queue_event_sof(unicam);
--
2.34.1
next prev parent reply other threads:[~2024-11-22 8:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 8:41 [PATCH v1 0/5] media: bcm2835-unicam: Upstreaming various improvements Naushir Patuck
2024-11-22 8:41 ` [PATCH v1 1/5] drivers: media: bcm2835-unicam: Improve frame sequence count handling Naushir Patuck
2024-11-22 14:45 ` Jacopo Mondi
2024-11-22 8:41 ` [PATCH v1 2/5] drivers: media: bcm2835-unicam: Allow setting of unpacked formats Naushir Patuck
2024-11-22 11:16 ` Jacopo Mondi
2024-11-22 8:41 ` [PATCH v1 3/5] drivers: media: bcm2835-unicam: Disable trigger mode operation Naushir Patuck
2024-11-22 11:18 ` Jacopo Mondi
2024-11-22 8:41 ` [PATCH v1 4/5] drivers: media: bcm2835-unicam: Fix for possible dummy buffer overrun Naushir Patuck
2024-11-22 11:20 ` Jacopo Mondi
2024-11-22 11:35 ` Naushir Patuck
2024-11-22 14:42 ` Jacopo Mondi
2024-11-22 8:41 ` Naushir Patuck [this message]
2024-11-22 11:16 ` [PATCH v1 5/5] drivers: media: bcm2835-unicam: Correctly handle FS + FE ISR condition Jacopo Mondi
2024-11-22 11:40 ` Naushir Patuck
2024-11-22 14:41 ` Jacopo Mondi
2024-11-22 14:48 ` Jacopo Mondi
2024-11-24 7:04 ` Laurent Pinchart
2024-11-25 8:37 ` Naushir Patuck
2024-11-25 9:23 ` Laurent Pinchart
2024-11-25 9:46 ` Naushir Patuck
2024-11-25 10:27 ` Laurent Pinchart
2024-11-25 10:46 ` Naushir Patuck
2024-11-25 11:00 ` Laurent Pinchart
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=20241122084152.1841419-6-naush@raspberrypi.com \
--to=naush@raspberrypi.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=florian.fainelli@broadcom.com \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel-list@raspberrypi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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