From: Anton Vorontsov <cbouatmailru@gmail.com>
To: "André Schwarz" <andre.schwarz@matrix-vision.de>
Cc: LinuxPPC List <linuxppc-dev@ozlabs.org>,
DevTreeDiscuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: How to define an I2C-to-SPI bridge device ?
Date: Fri, 10 Sep 2010 22:27:35 +0400 [thread overview]
Message-ID: <20100910182735.GA28479@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1284142484.2152.18.camel@swa-e6500>
On Fri, Sep 10, 2010 at 08:14:44PM +0200, André Schwarz wrote:
[...]
> > Does the device actually generate edge interrupts? Or is it a level
> > irq device? If it is a level irq device, then the correct way to
> > handle this is to disable the irq line so that the event can be
> > handled at non-irq context, and then reenable it when finished.
>
> The irq is level-low active.
> Will do it via disable/re-enable then.
FYI, In newer kernels you don't have to do it manually, there's
request_threaded_irq() for this.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
WARNING: multiple messages have this Message-ID (diff)
From: Anton Vorontsov <cbouatmailru-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "André Schwarz" <andre.schwarz-P0pTl12WyEgpBod+wgzj8A@public.gmane.org>
Cc: LinuxPPC List
<linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
DevTreeDiscuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: How to define an I2C-to-SPI bridge device ?
Date: Fri, 10 Sep 2010 22:27:35 +0400 [thread overview]
Message-ID: <20100910182735.GA28479@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1284142484.2152.18.camel@swa-e6500>
On Fri, Sep 10, 2010 at 08:14:44PM +0200, André Schwarz wrote:
[...]
> > Does the device actually generate edge interrupts? Or is it a level
> > irq device? If it is a level irq device, then the correct way to
> > handle this is to disable the irq line so that the event can be
> > handled at non-irq context, and then reenable it when finished.
>
> The irq is level-low active.
> Will do it via disable/re-enable then.
FYI, In newer kernels you don't have to do it manually, there's
request_threaded_irq() for this.
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
next prev parent reply other threads:[~2010-09-10 18:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 8:36 How to define an I2C-to-SPI bridge device ? André Schwarz
2010-09-03 12:08 ` Anton Vorontsov
2010-09-03 12:08 ` Anton Vorontsov
2010-09-06 11:40 ` Andre Schwarz
2010-09-06 11:40 ` Andre Schwarz
2010-09-06 14:37 ` André Schwarz
2010-09-06 14:37 ` André Schwarz
2010-09-09 18:23 ` Grant Likely
2010-09-09 18:23 ` Grant Likely
2010-09-10 8:11 ` André Schwarz
2010-09-10 17:37 ` Grant Likely
2010-09-10 17:37 ` Grant Likely
2010-09-10 18:14 ` André Schwarz
2010-09-10 18:14 ` André Schwarz
2010-09-10 18:27 ` Anton Vorontsov [this message]
2010-09-10 18:27 ` Anton Vorontsov
2010-09-10 18:28 ` Grant Likely
2010-09-10 18:28 ` Grant Likely
2010-09-12 15:10 ` André Schwarz
2010-09-12 15:10 ` André Schwarz
2010-09-13 4:39 ` Grant Likely
2010-09-13 4:39 ` Grant Likely
2011-03-25 9:28 ` Andre Schwarz
2011-03-29 16:21 ` Andre Schwarz
2011-03-31 3:43 ` Grant Likely
2010-09-09 17:06 ` Grant Likely
2010-09-09 17:06 ` Grant Likely
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=20100910182735.GA28479@oksana.dev.rtsoft.ru \
--to=cbouatmailru@gmail.com \
--cc=andre.schwarz@matrix-vision.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.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.