Dear Juergen Beisert, [...] > > >> But wait, you're getting interrupts on channel 0. Doesn't seem quite > > >> right. Did you happen to poke into the code and see where the issue > > >> might be? > > > > > > No yet. But if you think this is not the intended behaviour of your > > > driver I will do a deeper look. > > > > I don't know the hardware, but from what I've seen in the driver this > > behavior looks correct. When reading a physical channel the channel will > > be mapped to the first free virtual channel, afterward it is unmapped > > again. > > Makes sense. > > > So if you are only reading a single channel it will always be mapped to > > first virtual channel. If you'd be using buffered mode and read multiple > > channels at once you'll probably get multiple interrupts on different > > virtual channels. > > So, the driver's behaviour is intended. Sorry for the noise. Heh, my own driver confused me. I really better get back to this thing, I even have the touchscreen part in the works. Sorry for the confusion. > Regards, > Juergen Best regards, Marek Vasut -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
