From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] mx2_camera: return IRQ_NONE when doing nothing
Date: Wed, 28 Jul 2010 08:53:37 +0200 [thread overview]
Message-ID: <20100728065337.GC14113@pengutronix.de> (raw)
In-Reply-To: <49da2476310a921b19226d572503b7c04175204d.1280229966.git.baruch@tkos.co.il>
On Tue, Jul 27, 2010 at 03:06:08PM +0300, Baruch Siach wrote:
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> drivers/media/video/mx2_camera.c | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/media/video/mx2_camera.c b/drivers/media/video/mx2_camera.c
> index 1536bd4..b42ad8d 100644
> --- a/drivers/media/video/mx2_camera.c
> +++ b/drivers/media/video/mx2_camera.c
> @@ -420,15 +420,17 @@ static irqreturn_t mx25_camera_irq(int irq_csi, void *data)
> struct mx2_camera_dev *pcdev = data;
> u32 status = readl(pcdev->base_csi + CSISR);
>
> - if (status & CSISR_DMA_TSF_FB1_INT)
> + writel(status, pcdev->base_csi + CSISR);
> +
> + if (!(status & (CSISR_DMA_TSF_FB1_INT | CSISR_DMA_TSF_FB2_INT)))
> + return IRQ_NONE;
I'm not sure this is correct. When we get here, the interrupt definitely
is from the camera, it's not a shared interrupt. So this only provokes a
'nobody cared' message from the kernel (if it's still present, I don't
know).
Sascha
> + else if (status & CSISR_DMA_TSF_FB1_INT)
> mx25_camera_frame_done(pcdev, 1, VIDEOBUF_DONE);
> else if (status & CSISR_DMA_TSF_FB2_INT)
> mx25_camera_frame_done(pcdev, 2, VIDEOBUF_DONE);
>
> /* FIXME: handle CSISR_RFF_OR_INT */
>
> - writel(status, pcdev->base_csi + CSISR);
> -
> return IRQ_HANDLED;
> }
>
> --
> 1.7.1
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
WARNING: multiple messages have this Message-ID (diff)
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH 2/4] mx2_camera: return IRQ_NONE when doing nothing
Date: Wed, 28 Jul 2010 08:53:37 +0200 [thread overview]
Message-ID: <20100728065337.GC14113@pengutronix.de> (raw)
In-Reply-To: <49da2476310a921b19226d572503b7c04175204d.1280229966.git.baruch@tkos.co.il>
On Tue, Jul 27, 2010 at 03:06:08PM +0300, Baruch Siach wrote:
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> drivers/media/video/mx2_camera.c | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/media/video/mx2_camera.c b/drivers/media/video/mx2_camera.c
> index 1536bd4..b42ad8d 100644
> --- a/drivers/media/video/mx2_camera.c
> +++ b/drivers/media/video/mx2_camera.c
> @@ -420,15 +420,17 @@ static irqreturn_t mx25_camera_irq(int irq_csi, void *data)
> struct mx2_camera_dev *pcdev = data;
> u32 status = readl(pcdev->base_csi + CSISR);
>
> - if (status & CSISR_DMA_TSF_FB1_INT)
> + writel(status, pcdev->base_csi + CSISR);
> +
> + if (!(status & (CSISR_DMA_TSF_FB1_INT | CSISR_DMA_TSF_FB2_INT)))
> + return IRQ_NONE;
I'm not sure this is correct. When we get here, the interrupt definitely
is from the camera, it's not a shared interrupt. So this only provokes a
'nobody cared' message from the kernel (if it's still present, I don't
know).
Sascha
> + else if (status & CSISR_DMA_TSF_FB1_INT)
> mx25_camera_frame_done(pcdev, 1, VIDEOBUF_DONE);
> else if (status & CSISR_DMA_TSF_FB2_INT)
> mx25_camera_frame_done(pcdev, 2, VIDEOBUF_DONE);
>
> /* FIXME: handle CSISR_RFF_OR_INT */
>
> - writel(status, pcdev->base_csi + CSISR);
> -
> return IRQ_HANDLED;
> }
>
> --
> 1.7.1
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2010-07-28 6:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 12:06 [PATCH 0/4] mx2_camera: mx25 fixes and enhancements Baruch Siach
2010-07-27 12:06 ` Baruch Siach
2010-07-27 12:06 ` [PATCH 1/4] mx2_camera: fix a race causing NULL dereference Baruch Siach
2010-07-27 12:06 ` Baruch Siach
2010-07-27 12:06 ` [PATCH 2/4] mx2_camera: return IRQ_NONE when doing nothing Baruch Siach
2010-07-27 12:06 ` Baruch Siach
2010-07-28 6:53 ` Sascha Hauer [this message]
2010-07-28 6:53 ` Sascha Hauer
2010-07-28 7:27 ` Russell King - ARM Linux
2010-07-28 7:27 ` Russell King - ARM Linux
2010-07-28 11:25 ` Guennadi Liakhovetski
2010-07-28 11:25 ` Guennadi Liakhovetski
2010-08-09 11:46 ` Baruch Siach
2010-08-09 11:46 ` Baruch Siach
2010-07-27 12:06 ` [PATCH 3/4] mx2_camera: fix comment typo Baruch Siach
2010-07-27 12:06 ` Baruch Siach
2010-07-27 12:06 ` [PATCH 4/4] mx2_camera: implement forced termination of active buffer for mx25 Baruch Siach
2010-07-27 12:06 ` Baruch Siach
2010-08-27 9:07 ` Guennadi Liakhovetski
2010-08-27 9:07 ` Guennadi Liakhovetski
2010-08-29 7:56 ` Baruch Siach
2010-08-29 7:56 ` Baruch Siach
2010-08-23 4:11 ` [PATCH 0/4] mx2_camera: mx25 fixes and enhancements Baruch Siach
2010-08-23 4:11 ` Baruch Siach
2010-08-23 22:05 ` Guennadi Liakhovetski
2010-08-23 22:05 ` Guennadi Liakhovetski
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=20100728065337.GC14113@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 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.