From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Trilok Soni <soni.trilok@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Brian Swetland <swetland@google.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
m.szyprowski@samsung.com, t.fujak@samsung.com,
kyungmin.park@samsung.com, David Brownell <david-b@pacbell.net>,
Daniel Ribeiro <drwyrm@gmail.com>,
arve@android.com, Barry Song <21cnbao@gmail.com>
Subject: [RFC patch 0/3] Support for irq chips on slow busses (i2c, spi) - V2
Date: Sat, 15 Aug 2009 17:48:26 -0000 [thread overview]
Message-ID: <20090815174512.491425246@linutronix.de> (raw)
The support for irq chips on slow busses eg. i2c, spi has been
discussed to great length several times. Most of the details can be
found in this thread: http://lkml.org/lkml/2009/7/21/266
The following patch series is a round up of the various patch snippets
sent out during the discussion and the ideas we agreed on.
This is version 2 of the patch series. The main changes vs. V1
(http://lkml.org/lkml/2009/8/13/348)
- patch 1/3: Provide a generic primary handler function which just
returns IRQ_WAKE_THREAD as this is all what oneshot
threaded handlers need to avoid useless copies of that
all over the place.
- patch 2/3: Reverted to the initial idea of conditional locking to
allow drivers to be used for both slowbus and standard
interrupts without any magic in the driver code
- patch 3/3: To avoid different driver code for nested or separate
thread handling a new function is provided which allows
to mark the interrupt nested. request_threaded_irq()
creates a separate thread only when the flag is not set.
Please have a thorough look and hopefully a test ride on your
favourite slowbus irq chip implementation so we can get this into .32
Thanks,
tglx
next reply other threads:[~2009-08-15 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 17:48 Thomas Gleixner [this message]
2009-08-15 17:48 ` [RFC patch 1/3] genirq: Add oneshot support Thomas Gleixner
2009-08-15 19:42 ` Dmitry Torokhov
2009-08-15 20:00 ` Thomas Gleixner
2009-08-15 17:48 ` [RFC patch 2/3] genirq: Add buslock support Thomas Gleixner
2009-08-15 17:48 ` [RFC patch 3/3] genirq: Support nested threaded irq handling Thomas Gleixner
2009-08-15 22:19 ` [RFC patch 0/3] Support for irq chips on slow busses (i2c, spi) - V2 Pavel Machek
2009-08-24 19:38 ` Mark Brown
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=20090815174512.491425246@linutronix.de \
--to=tglx@linutronix.de \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=david-b@pacbell.net \
--cc=dmitry.torokhov@gmail.com \
--cc=drwyrm@gmail.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=soni.trilok@gmail.com \
--cc=swetland@google.com \
--cc=t.fujak@samsung.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.