From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Javier Martinez Canillas <martinez.javier@gmail.com>,
Stephen Warren <swarren@nvidia.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Grant Likely <grant.likely@secretlab.ca>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: omap: IORESOURCE_IRQ flags not set when defining a GPIO-IRQ from DT
Date: Sat, 2 Mar 2013 00:00:17 +0000 [thread overview]
Message-ID: <20130302000017.GD30923@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <51312EA1.8000600@ti.com>
On Fri, Mar 01, 2013 at 04:41:37PM -0600, Jon Hunter wrote:
> Thanks for the history. For OMAP I see SMC_IRQ_FLAGS getting defined as
> follows in smc91x.h ...
>
> #ifndef SMC_IRQ_FLAGS
> #define SMC_IRQ_FLAGS IRQF_TRIGGER_RISING
> #endif
>
> And so for OMAP devices using smc91x, it is always being configured as
> rising-edge. So it would be good to move OMAP to use a dynamic
> configuration too.
Yep. I think that was requested back when I did the work from those
which remained...
prev parent reply other threads:[~2013-03-02 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 16:17 omap: IORESOURCE_IRQ flags not set when defining a GPIO-IRQ from DT Javier Martinez Canillas
2013-03-01 17:30 ` Russell King - ARM Linux
2013-03-01 22:41 ` Jon Hunter
2013-03-02 0:00 ` Russell King - ARM Linux [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=20130302000017.GD30923@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jon-hunter@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).