On Fri, 2015-08-28 at 12:00 +0300, Mika Westerberg wrote: > On Thu, Aug 27, 2015 at 03:56:14PM +0100, Mark Brown wrote: > > On Thu, Aug 27, 2015 at 02:59:14PM +0300, Mika Westerberg wrote: > > > On Thu, Aug 27, 2015 at 01:44:45PM +0200, Christian Hartmann wrote: > > > > > > drivers/gpio/gpio-arizona.c > > > > and drivers/extcon/extcon-arizona.c > > > > > > I have already CONFIG_GPIO_ARIZONA=y, but it does not be used at all. > > > > Is it save to ignore ?? Or should I use them as well ?? > > > > > If the SPI device interrupt is connected to arizona GPIO pin, then you > > > probably need that. > > > > I can't see how that would work, the interrupt output isn't a GPIO. > > I mean that if the SPI device (codec) interrupt pin is connected to a GPIO > pin of arizona instead of GPIO pin of the SoC itself. It makes no sense to connect the codec interrupt pin back to one of its own GPIOs. If you did that the GPIO could only generate another interrupt to itself and you'd have a circular interrupt storm that went nowhere. > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@xxxxxxxxxxxxxxxx > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html