From: Hans Verkuil <hverkuil@xs4all.nl>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/3] media: i2c: Add ADV761X support
Date: Tue, 24 Sep 2013 17:37:42 +0000 [thread overview]
Message-ID: <5241CDE6.9010706@xs4all.nl> (raw)
In-Reply-To: <1380029916-10331-2-git-send-email-valentine.barshak@cogentembedded.com>
On 09/24/2013 06:19 PM, Guennadi Liakhovetski wrote:
> Hi Hans
>
> On Tue, 24 Sep 2013, Hans Verkuil wrote:
>
>> Shouldn't the interrupt_service_routine() op be implemented as well?
>> Usually these drivers will generate interrupts if e.g. the format changes.
>
> Should it? AFAIU, .interrupt_service_routine() is a subde operation to be
> called by a bridge driver, when it gets an interrupt for the respective
> subdevice:
>
> interrupt_service_routine: Called by the bridge chip's interrupt service
> handler, when an interrupt status has be raised due to this subdev,
> typo ^^
>
> so that this subdev can handle the details. It may schedule work to be
> performed later. It must not sleep. *Called from an IRQ context*.
Hmm, I have serious doubts whether the "It must not sleep. *Called from an IRQ context*."
part is correct. I have to check that. I think it is actually the opposite,
especially since most i2c drivers will have to do i2c accesses which can always
sleep.
>
> In this case the device does indeed have 2 interrupt output lines, but I
> don't think they would be connected to dedicated bridge inputs, rather to
> GPIOs, so, the driver can implement an ISR itself, when it decides to
> implement support for those interrupts.
That's another option. But this driver implements neither option, which is
unusual.
Regards,
Hans
next prev parent reply other threads:[~2013-09-24 17:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 13:38 [PATCH 1/3] media: i2c: Add ADV761X support Valentine Barshak
2013-09-24 14:17 ` Hans Verkuil
2013-09-24 15:54 ` Guennadi Liakhovetski
2013-09-24 16:19 ` Guennadi Liakhovetski
2013-09-24 17:37 ` Hans Verkuil [this message]
2013-09-24 18:09 ` Andy Walls
2013-09-25 9:57 ` Laurent Pinchart
2013-09-25 10:21 ` Laurent Pinchart
2013-09-25 12:33 ` Valentine
2013-09-25 13:02 ` Valentine
2013-09-25 14:08 ` Guennadi Liakhovetski
2013-09-25 15:16 ` Valentine
2013-09-25 16:31 ` Guennadi Liakhovetski
2013-09-25 17:19 ` Valentine
2013-09-25 18:33 ` Guennadi Liakhovetski
2013-09-25 20:36 ` Valentine
2013-09-25 22:04 ` Laurent Pinchart
2013-09-25 22:57 ` Laurent Pinchart
2013-09-26 6:31 ` Hans Verkuil
2013-09-26 6:45 ` Hans Verkuil
2013-09-26 6:57 ` Hans Verkuil
2013-09-26 9:36 ` Laurent Pinchart
2013-09-26 9:39 ` 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=5241CDE6.9010706@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-sh@vger.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