This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DRA821U: USB irq pin

Part Number: DRA821U

Dear Team,

we are woking on DRA821U2 custom board . 

we have connected (D5)WKUP_GPIO0_31 pin as irq pin to FUSB302MPX typeC controller, we observed that sometimes the irq is not clearing, beacuse of this typeC is not functioning properly, is there any option to clear the irq or give pullup internally

Regards,

Ashwini A

  • Hi Ashwini

    Assigned expert is on leave and will be back by 28-May-2026 .Allow us sometime tt respond on this.

    Regards
    Diwakar

  • HI Ashwini,

    I will loop in the hardware expert to have a look into this query.

    In the meantime, can you share the USB hardware schematics for the custom board.

    Best Regards

    Gokul Praveen

  • Hi Ashwini,

    Yes, this pin has the capability of having internal pullup or pulldown when it is setup during the pin mux.

  • Hii ShreyasRao,

    Thank you for your reply.

    Please find below the schematic related to the USB Type-C interface.


    The IRQ pin is configured in the pinmux as shown below:


            wkup_typec_irq_pins_default: wkup_typec_irq_pins {
                    pinctrl-single,pins = <
                            J721E_WKUP_IOPAD(0x4, PIN_INPUT, 7) /* (D5) MAIN_OSPI0_CSn3.WKUP_GPIO0_31*/
                    >;
            };

    However, we are observing that the IRQ is not getting cleared.

    Could you please let us know if there are any additional configurations that need to be checked

    Regards,

    Ashwini A

  • Are the FUSB302 device from TI? I am not sure to how the other device might behave. 

    All the interrupts in the ISR may need to serviced before the IRQ is cleared. 

    Another suggestion is to have the IRQ as level triggered instead of edge-triggered. 

  • Dear ShreyasRao,

    Thank you for your response.

    Another suggestion is to have the IRQ as level triggered instead of edge-triggered. 

    whether drivers/gpio/gpio-davinci.c this driver support level triggered.(Linux 6.12.57).

    Regards,

    Ashwini

  • whether drivers/gpio/gpio-davinci.c this driver support level triggered.(Linux 6.12.57).

    Yes, it accepts level low and level high irq. 

    but more importantly need to ensure that the interrupt / inta / intb registers are all cleared in the ISR and the int_n actually go low b/w the interrupts.