prussdrv_pru_clear_event swap parameters

[arielfernando]

I had a problem using this function.

The function definition is:
int prussdrv_pru_clear_event (unsigned int host_interrupt, unsigned int eventnum);

and the example is
prussdrv_pru_clear_event ( PRU0_ARM_INTERRUPT, PRU_EVTOUT0 );

but this example doesn't work. To make it work I had to swap the parameters:
prussdrv_pru_clear_event(PRU_EVTOUT_0, PRU0_ARM_INTERRUPT);

Thanks

[jadonk]

Thanks for the issue report. Any chance you could provide a bug fix via a pull request as well?

[arielfernando]

Jason, I was watching the code and i suggest to do a exhaustive review
because these parameters are used in more that one place. I am starting to
work with the beaglebone PRU and I don't want to do a simple swatch.

thanks for your answer
Ariel

El jue., 6 ago. 2015 a las 12:46, Jason Kridner ([email protected])
escribió:

Thanks for the issue report. Any chance you could provide a bug fix via a
pull request as well?

—
Reply to this email directly or view it on GitHub
#41 (comment)
.

[engkan2kit]

What happened to this?
Is this the newer way prussdrv_pru_clear_event ( PRU0_ARM_INTERRUPT, PRU_EVTOUT0 );?
Or is this just a clerical error in the documetation?

[e-matteson]

I'm curious as well. I haven't been able to clear PRU->host interrupts properly, using either argument order. If I attempt to clear them, the interrupt will only be received once, even if it is sent many times. If I don't clear them, the interrupt will be received many times, even if it is only sent once. Neither of these behaviors are useful.