iMX6SL GPIO Interrupt latency (Yocto Project)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

iMX6SL GPIO Interrupt latency (Yocto Project)

1,220 Views
indukkim
Contributor I

Hi All,

I want to use the GPIO Interrupt, but the interrupt response time is too long (20us more)

How do you feel about the following statements?

iMX6SL, Yocto Project, linux kenel 3.10.17

Please help me......

gpio_request(97,"test1"); //GPIO4 1 Intertup source

gpio_request(26,"test2"); //GPIO0 26 Out Control

gpio_direction_input(97);

gpio_direction_output(26,0);

int irq = gpio_to_irq(97);

int ret = request_irq(irq,test_isr,IRQF_TRIGGER_FALLING|IRQF_TRIGGER_RISING, "gpiodev", NULL);

irqreturn_t test_isr(int irq, void *dev_id)

{

  gpio_set_value(26,1);

  gpio_set_value(26,0);

  gpio_set_value(26,1);

  gpio_set_value(26,0);

  return IRQ_HANDLED;

}

scope_5.bmp

Labels (3)
0 Kudos
1 Reply

465 Views
igorpadykov
NXP Employee
NXP Employee

Hi Induk

since linux is not real time OS such time is normal,

you can refer to below context latencies (interrupts use

this context switching)

Context switching - times in microseconds

LMbench Benchmarks on i.MX

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------