From: Rui Miguel Silva <rmfrfs@gmail.com>
To: "Isaac Scott" <isaac.scott@ideasonboard.com>,
<laurent.pinchart@ideasonboard.com>
Cc: <kieran.bingham@ideasonboard.com>, <rmfrfs@gmail.com>,
<martink@posteo.de>, <kernel@puri.sm>, <mchehab@kernel.org>,
<shawnguo@kernel.org>, <s.hauer@pengutronix.de>,
<kernel@pengutronix.de>, <festevam@gmail.com>,
<linux-media@vger.kernel.org>, <imx@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] media: Add line end IRQ to imx-mipi-csis driver
Date: Fri, 06 Jun 2025 17:17:20 +0100 [thread overview]
Message-ID: <DAFL3CTS8R5D.1FIGCAM5SXJPL@linaro.com> (raw)
In-Reply-To: <20250606154414.540290-1-isaac.scott@ideasonboard.com>
Hi Isaac,
Many thanks for the patches.
On Fri Jun 6, 2025 at 4:44 PM WEST, Isaac Scott wrote:
> Many boards, such as the NXP i.MX 8M Plus, feature multiple interrupt
> registers. This series refactors interrupt status register debug handling to make
> it more intuitive to add other registers such as LINE_END, which has an
> entire register containing only one interrupt. Previously, the
> mipi_csi_events[] list contained a debug enable field, and this replaces
> that with a status_index, which indicates which status register contains
> the mask for the interrupt.
>
> The second patch adds the user line interrupt, which is useful for
> debugging, as it allows a user to trigger an interrupt after the MIPI
> CSI receiver has counted a configurable number of lines. This can make
> it possible to discern the true resolution of the image stream reaching
> the CSI receiver. It adds an entry to debugfs which lets users choose
> how many lines are needed to trigger the interrupt, and can be disabled
> both within and outside streaming by setting the value to 0.
LGTM.
for the all series:
Reviewed-by: Rui Miguel Silva <rui.silva@linaro.org>
Cheers,
Rui
>
> ---
>
> Changes since v1:
> - Moved from magic number to enum in status_index
> - Clear INT_MSK_1 in enable_interrupts() when on == false
> - use local variable in set_params() as in the interrupt handler
> - move interrupt handling code outside of spinlock
>
> Isaac Scott (2):
> media: platform: Refactor interrupt status registers
> media: platform: Add user line interrupt to imx-mipi-csis driver
>
> drivers/media/platform/nxp/imx-mipi-csis.c | 107 ++++++++++++++-------
> 1 file changed, 74 insertions(+), 33 deletions(-)
>
> --
> 2.43.0
prev parent reply other threads:[~2025-06-06 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 15:44 [PATCH v2 0/2] media: Add line end IRQ to imx-mipi-csis driver Isaac Scott
2025-06-06 15:44 ` [PATCH v2 1/2] media: platform: Refactor interrupt status registers Isaac Scott
2025-06-07 18:38 ` Laurent Pinchart
2025-06-06 15:44 ` [PATCH v2 2/2] media: platform: Add user line interrupt to imx-mipi-csis driver Isaac Scott
2025-06-07 18:45 ` Laurent Pinchart
2025-06-06 16:17 ` Rui Miguel Silva [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=DAFL3CTS8R5D.1FIGCAM5SXJPL@linaro.com \
--to=rmfrfs@gmail.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=isaac.scott@ideasonboard.com \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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).