linux-kernel - Re: [RFC patch 0/3] Support for irq chips on slow busses (i2c, spi)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 16 Aug 2009 00:19:22 +0200
From:	Pavel Machek <pavel@....cz>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Trilok Soni <soni.trilok@...il.com>,
	Brian Swetland <swetland@...gle.com>,
	Joonyoung Shim <jy0922.shim@...sung.com>,
	m.szyprowski@...sung.com, t.fujak@...sung.com,
	kyungmin.park@...sung.com, David Brownell <david-b@...bell.net>,
	Daniel Ribeiro <drwyrm@...il.com>, arve@...roid.com,
	Barry Song <21cnbao@...il.com>
Subject: Re: [RFC patch 0/3] Support for irq chips on slow busses (i2c,
	spi) - V2

Hi!

> 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

FWIW, it looks ok to me.
					Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/