From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH REPOST] gpio: omap: use raw locks for locking Date: Wed, 1 Jul 2015 04:29:29 -0700 Message-ID: <20150701112928.GW4156@atomide.com> References: <20150619170654.GA4937@linutronix.de> <5584547B.9040203@oracle.com> <20150622070821.GB4156@atomide.com> <559275B9.3040909@ti.com> <5592C5A2.5050809@linutronix.de> <20150701073205.GT4156@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20150701073205.GT4156@atomide.com> Sender: linux-gpio-owner@vger.kernel.org To: Sebastian Andrzej Siewior Cc: Grygorii Strashko , Santosh Shilimkar , Kevin Hilman , Javier Martinez Canillas , santosh shilimkar , Linus Walleij , Alexandre Courbot , "linux-omap@vger.kernel.org" , Linux GPIO List , Felipe Balbi , Sekhar Nori List-Id: linux-omap@vger.kernel.org * Tony Lindgren [150701 00:34]: > > This should be OK for most cases as the GPIO interrupt devices are > typically on some external bus like I2C or GPMC. The hurting case > would be bitbanging GPIO devices, like the CBUS I2C driver. Thinking about it the CBUS I2C driver does not need interrupts for the bitbanging part either :) So I think we can just make it threaded IRQ for GPIO. Tony