On Thu, Feb 06, 2014 at 09:05:05PM +0100, Christopher Heiny wrote: > On 02/04/2014 06:31 PM, Courtney Cavin wrote: > > On Wed, Feb 05, 2014 at 12:08:35AM +0100, Christopher Heiny wrote: > >> On 01/23/2014 04:00 PM, Courtney Cavin wrote: > >>> Since all the configuration needed for an irq can be provided in other > >>> ways, remove all gpio->irq functionality. This cleans up the code quite > >>> a bit. > >> > >> In certain diagnostic modes, we need to be able to release the IRQ so > >> the GPIO can be monitored from userspace. This patch removes that > >> capability. > >> > > > > Polling a GPIO from userspace is poor design regardless of the use-case, if > > you ask me. It certainly doesn't motivate the extra gpio<->IRQ code. > > Fortunately, neither the in-driver polling implementation nor the user > space diagnostic applications are implemented that way. I'm missing something here then. If the userspace diagnostic applications do not poll the GPIO, then what exactly is the purpose of them accessing the GPIO at all? -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
