From: Tony Lindgren <tony@atomide.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [RFC PATCH] gpio/omap: Fix IRQ handling for SPARSE_IRQ
Date: Thu, 23 Feb 2012 15:08:21 -0800 [thread overview]
Message-ID: <20120223230821.GD18185@atomide.com> (raw)
In-Reply-To: <4F46C1AF.2040201@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [120223 14:14]:
> The GPIO driver is still relying on internal OMAP IRQ defines that
> are not relevant anymore if OMAP is built with SPARSE_IRQ.
Great :)
> Please note that this patch is still RFC, because I do not know
> how to fix properly the ugly cpu_class_is_omap1 and the dependency
> with IH_MPUIO_BASE to detect a MPUIO.
Sounds like gpio_to_irq() needs to be set in the
arch/arm/*omap*/gpio*.c then.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] gpio/omap: Fix IRQ handling for SPARSE_IRQ
Date: Thu, 23 Feb 2012 15:08:21 -0800 [thread overview]
Message-ID: <20120223230821.GD18185@atomide.com> (raw)
In-Reply-To: <4F46C1AF.2040201@ti.com>
* Cousson, Benoit <b-cousson@ti.com> [120223 14:14]:
> The GPIO driver is still relying on internal OMAP IRQ defines that
> are not relevant anymore if OMAP is built with SPARSE_IRQ.
Great :)
> Please note that this patch is still RFC, because I do not know
> how to fix properly the ugly cpu_class_is_omap1 and the dependency
> with IH_MPUIO_BASE to detect a MPUIO.
Sounds like gpio_to_irq() needs to be set in the
arch/arm/*omap*/gpio*.c then.
Tony
next prev parent reply other threads:[~2012-02-23 23:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 22:46 [RFC PATCH] gpio/omap: Fix IRQ handling for SPARSE_IRQ Cousson, Benoit
2012-02-23 22:46 ` Cousson, Benoit
2012-02-23 23:08 ` Tony Lindgren [this message]
2012-02-23 23:08 ` Tony Lindgren
2012-02-24 10:11 ` Cousson, Benoit
2012-02-24 10:11 ` Cousson, Benoit
2012-02-24 10:37 ` DebBarma, Tarun Kanti
2012-02-24 10:37 ` DebBarma, Tarun Kanti
2012-02-24 13:24 ` DebBarma, Tarun Kanti
2012-02-24 13:24 ` DebBarma, Tarun Kanti
2012-02-24 13:32 ` Cousson, Benoit
2012-02-24 13:32 ` Cousson, Benoit
2012-02-24 13:53 ` DebBarma, Tarun Kanti
2012-02-24 13:53 ` DebBarma, Tarun Kanti
2012-02-24 13:56 ` Cousson, Benoit
2012-02-24 13:56 ` Cousson, Benoit
2012-02-24 15:09 ` DebBarma, Tarun Kanti
2012-02-24 15:09 ` DebBarma, Tarun Kanti
2012-02-24 15:12 ` Cousson, Benoit
2012-02-24 15:12 ` Cousson, Benoit
2012-02-24 14:14 ` Rob Herring
2012-02-24 14:14 ` Rob Herring
2012-02-24 14:54 ` Cousson, Benoit
2012-02-24 14:54 ` Cousson, Benoit
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=20120223230821.GD18185@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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.