From: Kevin Hilman <khilman@deeprootsystems.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [ARM][OMAP] TWL4030 IRQ
Date: Mon, 29 Jun 2009 10:58:00 -0700 [thread overview]
Message-ID: <87k52u9b2v.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20090629175250.GE9042@n2100.arm.linux.org.uk> (Russell King's message of "Mon\, 29 Jun 2009 18\:52\:50 +0100")
Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
> On Mon, Jun 29, 2009 at 10:51:09AM -0700, Kevin Hilman wrote:
>> And if you look at the OMAP's MPU irq_chip implementation, these are
>> not populated either. We rely on the default lazy enable via unmask
>> and the lazy disable.
>
> There's no lazy enable - it's immediate. There's only lazy disable.
Correct, that was a mis-edit. It should've read: "We rely on the
default enable via unmask and the lazy disable."
Kevin
next prev parent reply other threads:[~2009-06-29 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 7:46 [ARM][OMAP] TWL4030 IRQ Shilimkar, Santosh
2009-06-24 7:57 ` Russell King - ARM Linux
2009-06-29 9:30 ` Russell King - ARM Linux
2009-06-29 15:34 ` Shilimkar, Santosh
2009-06-29 15:43 ` Russell King - ARM Linux
2009-06-29 17:51 ` Kevin Hilman
2009-06-29 17:52 ` Russell King - ARM Linux
2009-06-29 17:58 ` Kevin Hilman [this message]
2009-06-30 6:31 ` Shilimkar, Santosh
2009-06-30 23:05 ` Kevin Hilman
2009-07-01 5:03 ` Shilimkar, Santosh
2009-07-01 13:51 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2009-06-24 5:07 Shilimkar, Santosh
2009-06-24 7:31 ` Russell King - ARM Linux
2009-06-20 15:24 Shilimkar, Santosh
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=87k52u9b2v.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
/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.