On Mon, Apr 20, 2015 at 4:05 PM, Paul Thomas <pthomas8589@xxxxxxxxx> wrote: > On Sat, Apr 18, 2015 at 3:14 PM, Daniel Baluta <daniel.baluta@xxxxxxxxx> wrote: >> On Fri, Apr 17, 2015 at 11:57 PM, Paul Thomas <pthomas8589@xxxxxxxxx> wrote: >>> Hello, I would like to setup an iio_interrupt_trigger. I see the the >>> actual request_irq happens in iio_interrupt_trigger_probe. What is a >>> good example of a driver using this? >>> >> >> Good question. AFAIK there is no driver directly using iio_interrupt_trigger. >> >>> I take it that, if I have a GPIO pin setup as an interrupt from >>> userspace, there is no way to add the trigger from userspace in a way >>> similar to 'iio_sysfs_trigger/add_trigger'? >> >> You could use this trigger from user space by writing: >> >> echo irqtrigX > /sys/bus/iio/iio:device0/trigger/current_trigger > You mean after I've loaded an iio_interrupt_trigger and can see > irqtrigX in /sys/bus/iio/devices right? (I tried it just now without > that, and current_trigger is just blank after 'echo irqtrigX') Which > means I need a proper struct platform_device setup? Looking through > Documentation/driver-model/platform.txt I see a platform_device is > normally loaded with platform_device_register. Yes. -- 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
