From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: Requesting different interrupt triggers for the same device type
Date: Thu, 04 Dec 2014 09:27:19 +0100 [thread overview]
Message-ID: <1646345.4akWfRNnkY@ws-stein> (raw)
In-Reply-To: <547EEEAA.4040605@ti.com>
Hello Grygorii,
On Wednesday 03 December 2014 13:06:18, Grygorii Strashko wrote:
> On 12/02/2014 06:45 PM, Alexander Stein wrote:
> > Hi,
> >
> > I have a board which has two PCA9555 attached. Due to hardware wirings each has a different interrupt trigger. One is active low and one is active high and each has a different interrupt parent.
> > How can I specify this in the device tree? Do I need to set IRQ_TYPE_LEVEL_LOW and IRQ_TYPE_LEVEL_HIGH approriately? How can this work, when the driver requests the interrupt like this?
> >> ret = devm_request_threaded_irq(&client->dev,
> >> client->irq,
> >> NULL,
> >> pca953x_irq_handler,
> >> IRQF_TRIGGER_LOW | IRQF_ONESHOT |
> >> IRQF_SHARED,
> >> dev_name(&client->dev), chip);
> >
> > The interrupt flags seem rather fixed. Any comments/hints?
>
> See, http://www.spinics.net/lists/linux-gpio/msg02731.html
> It may help.
Well, removing that trigger here (and in another driver where INT line is shared) it "works". It seems that each (DT-) driver should remove those explicit flags, no?
Best regards,
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund
Tel.: 03765 38600-1156
Fax: 03765 38600-4100
Email: alexander.stein@systec-electronic.com
Website: www.systec-electronic.com
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 28082
next prev parent reply other threads:[~2014-12-04 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 16:45 Requesting different interrupt triggers for the same device type Alexander Stein
2014-12-03 11:06 ` Grygorii Strashko
2014-12-04 8:27 ` Alexander Stein [this message]
2014-12-04 12:06 ` Grygorii Strashko
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=1646345.4akWfRNnkY@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-gpio@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