stuck in k_sem_take

[paladahallin]

I’m working on adding a new ADC driver and running into an issue with adc_context_lock in the ADC read function. I’ve checked my code and made sure I’m not locking the context anywhere else, but I still get an error related to context locking when I try to read from the ADC.

Could someone please help me understand the correct sequence for using adc_context_lock in a custom ADC driver? Are there any common pitfalls or best practices I should follow to avoid this error?

Any guidance or example code would be greatly appreciated!

[ldomaigne]

Eh,eh,eh Aurix platform...

I’m working on adding a new ADC driver and running into an issue with adc_context_lock in the ADC read function.

What kind of issue are you facing exactly? You block in the spinlock?

Could someone please help me understand the correct sequence for using adc_context_lock in a custom ADC driver? Are there any common pitfalls or best practices I should follow to avoid this error?

AFAICS, you just lock the adc context before the read operation, and release it after completion. There are many examples of ADC drivers available under zephyr/drivers/adc

One thing that comes to mind: have you properly initialized the context? You can either call adc_context_init() in the driver's init function, or use the ADC_INIT_{LOCK,SYNC} macro when creating the driver data structure.

Example of drivers using:

• adc_context_init: adc_max11102_17.c
• ADC_INIT macro: adc_stm32.c