PocketBeagle 2 interrupts

General Discussion
, ,
1

are there known issues with the interrupts on PB2?
getting the same failure mode for mma8652 and wiz850io devices. when registering interrupts in the dts file
genirq: Setting trigger mode 8 for irq 429 failed (gpio_irq_type)
mma8452 2-001d: probe with driver mma8452 failed with error -22

so far i’ve traced it to manage.c file
still trying to find the exact function call that fails, painfully slow process.

update:
in manage.c, this is the call that returns the -22 failure
however, irq_set_type is a pointer to some function, which i have not been able to identify
ret = chip->irq_set_type(&desc->irq_data, flags);

so my debugging has come to a road block.

lets say i get a TagConnect connector
how would i go about debugging this??
could i use eclipse or do i need to use CCS ??

1 Like
2

I have no issues with using interrupts on the PB2 in combination with an I2C gpio expander. It just seems to work.

    gpio@22 {
        compatible = "nxp,pca9675";
        reg = <0x22>;
        gpio-controller;
        #gpio-cells = <2>;
        gpio-line-names = "PixOk-5", "PixOk-6", "PixOk-7", "PixOk-8", "PixOk-21", "PixOk-22", "PixOk-23", "PixOk-24", "PixOk-17", "PixOk-18", "PixOk-19", "PixOk-20", "PixOk-1", "PixOk-2", "PixOk-3", "PixOk-4";
        
        #interrupt-cells = <2>;
        interrupt-parent = <&main_gpio1>;
        interrupts = <18 8>;
        interrupt-controller;
    };
1 Like
3

i don’t have this in my dtso, i’ll add it and see if that helps.
thanks,

did not help

mma8652: accel@1d {
	compatible = "fsl,mma8652";
	reg = <0x1D>;
    clock-frequency = <400000>;
            
    #interrupt-cells = <2>;
    
interrupt-parent = <&main_gpio1>;
    //interrupts = <2 IRQ_TYPE_EDGE_FALLING>;    // P1.34
    interrupts = <2 8>;    // P1.34
    // 8 == IRQ_TYPE_LEVEL_LOW
    interrupt-names = "INT1";
};

mma8452 2-001d: registering mma8652 accelerometer; ID 0x4a
mma8452 2-001d: probe with driver mma8452 failed with error -22