From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: Requesting different interrupt triggers for the same device type
Date: Thu, 4 Dec 2014 14:06:29 +0200 [thread overview]
Message-ID: <54804E45.7090808@ti.com> (raw)
In-Reply-To: <1646345.4akWfRNnkY@ws-stein>
On 12/04/2014 10:27 AM, Alexander Stein wrote:
> 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?
Hm. I think yes, in general. But problem is compatibility with non-DT builds and it
should be solved somehow in per-driver specific way.
probably simplest way would be smth. like this:
unsigned long irqflags = 0;
if (!dev->of_node)
irqflags = IRQF_TRIGGER_LOW;
devm_request_threaded_irq(.., irqflags | IRQF_ONESHOT | IRQF_SHARED, ..);
regards,
-grygorii
prev parent reply other threads:[~2014-12-04 12:06 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
2014-12-04 12:06 ` Grygorii Strashko [this message]
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=54804E45.7090808@ti.com \
--to=grygorii.strashko@ti.com \
--cc=alexander.stein@systec-electronic.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 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.