Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753084Ab1DOWj6 (ORCPT ); Fri, 15 Apr 2011 18:39:58 -0400 Received: from www.linutronix.de ([62.245.132.108]:60922 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751584Ab1DOWj4 (ORCPT ); Fri, 15 Apr 2011 18:39:56 -0400 Date: Sat, 16 Apr 2011 00:39:47 +0200 (CEST) From: Thomas Gleixner To: Abhijeet Dharmapurikar cc: mathieu.desnoyers@efficios.com, Ingo Molnar , Peter Zijlstra , linux-kernel@vger.kernel.org, dwalker@fifo99.com, linux-arm-msm-owner@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Greg Kroah-Hartman Subject: Re: [RFC PATCH] genirq: implement read_irq_line for interrupt lines In-Reply-To: <4DA8C1E2.3020205@codeaurora.org> Message-ID: References: <1302892952-7090-1-git-send-email-adharmap@codeaurora.org> <4DA8C1E2.3020205@codeaurora.org> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1535 Lines: 37 On Fri, 15 Apr 2011, Abhijeet Dharmapurikar wrote: > Thomas Gleixner wrote: > > On Fri, 15 Apr 2011, Abhijeet Dharmapurikar wrote: > > > > > Some drivers need to know what the status of the interrupt line is. > > > This is especially true for drivers that register a handler with > > > IRQF_TRIGGER_RISING | IRQF_TRIGGER_FALLING and in the handler they > > > need to know which edge transition it was invoked for. > > > > What's the purpose of this? How is that going to be used? > > The main purpose is to know in the handler if it was invoked becuase of a > rising edge or the falling edge. Come on. That's not an explanation. I know that already and it does not answer my question how this is going to be used. IOW: What does the driver do aside of knowing that it was a rising falling edge? > Now one could say that the driver should maintain some state and toggle it > upon each invocation of this handler. That scheme quickly goes out of sync > because we might ignore interrupts while suspended. Suspend is a totaly different issue. I have the impression that you are trying to solve some basic issue at the driver level again - just this time you add some core helper to get it solved. Can you please show _AND_ explain the code which is going to use this? Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/