Hi Manjunath,
On Friday 11 May 2012 05:32:13 Hadli, Manjunath wrote:
> On Tue, Apr 17, 2012 at 15:36:16, Laurent Pinchart wrote:
> > On Tuesday 17 April 2012 14:22:59 Manjunath Hadli wrote:
> > > As the same interrupt is shared between capture and display devices,
> > > sometimes we get isr calls where the interrupt might not genuinely
> > > belong to capture or display. Hence, add a condition in the isr to
> > > check for interrupt ownership and channel number to make sure we do
> > > not service wrong interrupts.
> > >
> > > Signed-off-by: Manjunath Hadli <manjunath.hadli@xxxxxx>
> > > ---
> > >
> > > drivers/media/video/davinci/vpif_capture.c | 5 +++++
> > > drivers/media/video/davinci/vpif_display.c | 5 +++++
> > > include/media/davinci/vpif_types.h | 2 ++
> > > 3 files changed, 12 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/drivers/media/video/davinci/vpif_capture.c
> > > b/drivers/media/video/davinci/vpif_capture.c index 6504e40..33d865d
> > > 100644
> > > --- a/drivers/media/video/davinci/vpif_capture.c
> > > +++ b/drivers/media/video/davinci/vpif_capture.c
> > > @@ -333,6 +333,7 @@ static void vpif_schedule_next_buffer(struct
> > > common_obj
> > > *common) */
> > >
> > > static irqreturn_t vpif_channel_isr(int irq, void *dev_id) {
> > >
> > > + struct vpif_capture_config *config = vpif_dev->platform_data;
> > >
> > > struct vpif_device *dev = &vpif_obj;
> > > struct common_obj *common;
> > > struct channel_obj *ch;
> > >
> > > @@ -341,6 +342,10 @@ static irqreturn_t vpif_channel_isr(int irq, void
> > > *dev_id) int fid = -1, i;
> > >
> > > channel_id = *(int *)(dev_id);
> > >
> > > + if (!config->intr_status ||
> > > + !config->intr_status(vpif_base, channel_id))
> > > + return IRQ_NONE;
> > > +
> >
> > I don't think this is the right way to handle the situation. You should
> > instead read the interrupt source register for the VPIF capture device,
> > and return IRQ_NONE if you find that no interrupt source has been flagged
> > (and similarly for the display device below).
>
> Agreed, and this is what is being done in intr_status() function, which
> is implemented in the board file. This function checks the interrupt source
> register for VPIF capture and display devices the way you mentioned.
Why do you need to do that in board code ? You can just check whether the VPIF
capture hardware has generated an interrupt here exactly the same way as you
do in your board code, and return IRQ_NONE if it hasn't. There's no need for
the VPIF capture driver to be aware of the VPIF display driver (and vice
versa).
> > > ch = dev->dev[channel_id];
> > >
> > > field = ch->common[VPIF_VIDEO_INDEX].fmt.fmt.pix.field;
--
Regards,
Laurent Pinchart
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
