Solved: Hi, I'm coding a continuous measurement sequence which starts to pull data when IRQ(data ready) triggers. After the trigger, I read FSTAT
/* * Universal device tree overlay for SPI devices */ /dts-v1/; /plugin/; /* #include <include/dt-bindings/interrupt-controller/irq.h> */ / { compatible = "brcm,bcm2711"; fragment@0 { target = <&spidev0>; __overlay__ { status = "disabled"; }; }; fragment@1 { target = ...
Convert the following case: struct irq_data *irq_data = irq_get_irq_data(irq); if (irq_data && irqd_get_trigger_type(irq_data) ... ) { ... } to the simpler: if (irq_get_trigger_type(irq) ... ) { ... } by using the irq_get_trigger_type() function. Suggested-by: Andy...
改成这样: request_irq(gpio_keys_100ask[i].irq, gpio_key_isr, IRQF_TRIGGER_RISING |IRQF_TRIGGER_RISING, "100ask_gpio_key", &gpio_keys_100ask[i]);
ret = request_irq (data->pen_irq, tsc2007_handle_penirq, IRQF_TRIGGER_FALLING, DRIVER_NAME, data); if (ret < 0) { printk(KERN_INFO "Unable to grab IRQ\n"); goto err_exit; } return 0; err_exit: return -ENODEV; } i also tried set_irq_type(irq_num, IRQT_FALLING); like set...
I'm coding a continuous measurement sequence which starts to pull data when IRQ(data ready) triggers. After the trigger, I read FSTAT register. But EMPTY is high and I have to wait for ~25us before CREF is high. Could you explain why is IRQ triggered 25us before the threshold is reac...
Interrupt line can be configured on different hardware in different way, The driver should not enforce specific trigger type - but instead rely on Devicetree to configure it. Further, if the device tree specified the different irq trigger type with the driver, the second device of 88W9098 will...