public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Hans Verkuil <hansverk@cisco.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Valentine <valentine.barshak@cogentembedded.com>,
	linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <m.chehab@samsung.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH V2] media: i2c: Add ADV761X support
Date: Wed, 27 Nov 2013 17:29:47 +0100	[thread overview]
Message-ID: <3727129.B5lM1JXKsv@avalon> (raw)
In-Reply-To: <529606AA.7050209@metafoo.de>

On Wednesday 27 November 2013 15:50:18 Lars-Peter Clausen wrote:
> On 11/27/2013 01:14 PM, Hans Verkuil wrote:
> [...]
> 
> >>> For our systems the adv7604 interrupts is not always hooked up to a gpio
> >>> irq, instead a register has to be read to figure out which device
> >>> actually produced the irq.
> >> 
> >> Where is that register located ? Shouldn't it be modeled as an interrupt
> >> controller ?
> > 
> > It's a PCIe interrupt whose handler needs to read several FPGA registers
> > in order to figure out which interrupt was actually triggered. I don't
> > know enough about interrupt controller to understand whether it can be
> > modeled as a 'standard' interrupt.
> 
> This sounds as if it should be implemented as a irq_chip driver. There are a
> couple of examples in drivers/irqchip/

Exactly, that was my point. A piece of hardware that takes several interrupt 
inputs, includes mask and flag registers and generate a single interrupt 
towards the system is an interrupt controller and should have be handled by 
the Linux irqchip infrastructure.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-11-27 17:22 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 12:54 [PATCH V2] media: i2c: Add ADV761X support Valentine Barshak
2013-11-19  9:50 ` Hans Verkuil
2013-11-20 10:14   ` Valentine
2013-11-20 11:19     ` Hans Verkuil
2013-11-20 12:24       ` Valentine
2013-11-20 15:42         ` Hans Verkuil
2013-11-20 15:53           ` Valentine
2013-11-26 21:28             ` Valentine
2013-11-26 21:43               ` Lars-Peter Clausen
2013-11-26 21:57                 ` Valentine
2013-11-26 22:02                   ` Lars-Peter Clausen
2013-11-26 22:00                 ` Laurent Pinchart
2013-11-26 22:03                   ` Lars-Peter Clausen
2013-11-26 22:03                     ` Laurent Pinchart
2013-11-26 22:06                       ` Lars-Peter Clausen
2013-11-29 20:07                         ` Lars-Peter Clausen
2013-11-27  8:21               ` Hans Verkuil
2013-11-27  9:59                 ` Lars-Peter Clausen
2013-11-27 11:26                   ` Hans Verkuil
2013-11-27 10:29                 ` Valentine
2013-11-27 11:18                   ` Hans Verkuil
2013-11-27 11:39                 ` Laurent Pinchart
2013-11-27 12:14                   ` Hans Verkuil
2013-11-27 12:32                     ` Valentine
2013-11-27 13:07                       ` Lars-Peter Clausen
2013-11-27 13:46                         ` Valentine
2013-11-27 16:40                       ` Laurent Pinchart
2013-11-27 16:48                         ` Lars-Peter Clausen
2013-11-29 10:37                         ` Linus Walleij
2013-11-29 10:45                           ` Lars-Peter Clausen
2013-11-29 12:14                             ` Valentine
2013-11-29 13:46                               ` Linus Walleij
2013-11-29 13:42                             ` Linus Walleij
2013-11-29 13:48                               ` Lars-Peter Clausen
2013-11-29 19:52                                 ` Linus Walleij
2013-11-29 20:03                                   ` Laurent Pinchart
2013-11-29 20:05                                   ` Lars-Peter Clausen
2013-11-29 20:09                                     ` Linus Walleij
2013-11-27 14:50                     ` Lars-Peter Clausen
2013-11-27 16:29                       ` Laurent Pinchart [this message]
2013-11-27 16:32                     ` 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=3727129.B5lM1JXKsv@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=hans.verkuil@cisco.com \
    --cc=hansverk@cisco.com \
    --cc=horms@verge.net.au \
    --cc=hverkuil@xs4all.nl \
    --cc=lars@metafoo.de \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=valentine.barshak@cogentembedded.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