From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Subject: Re: [patch 2.6.24-rc5-git] add i2c_new_dummy() utility Date: Thu, 17 Jan 2008 14:24:30 -0800 Message-ID: <200801171424.30592.david-b@pacbell.net> References: <20071216052308.A0FB11668D7@adsl-69-226-248-13.dsl.pltn13.pacbell.net> <57e2b00712281645y70f6ec74s57945dc53f113ec8@mail.gmail.com> <200712291905.15160.david-b@pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200712291905.15160.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org Errors-To: i2c-bounces-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org To: Byron Bradley Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Saturday 29 December 2007, David Brownell wrote: > I still don't know why you get lockdep warnings and I don't ... Theory: my test systems were turning lockdep off because of a lockdep (usage) deficiency that triggers while booting: enable_irq_wake(GPIO_irq) holds irq_desc[GPIO_irq].lock and calls enable_irq_wake(parent_of(GPIO_irq)) which grabs irq_desc[parent_of(GPIO_irq))] Lockdep falsely detects that as a potential recursion, and then turns off all further lockdep calls. I think a genirq patch to make set_irq_chained_handler() put the parent into a different locking class may help resolve that issue. - Dave _______________________________________________ i2c mailing list i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org http://lists.lm-sensors.org/mailman/listinfo/i2c