DECT PHY events callback context

[kirill.neznamov]

Hi All,

I have a question regarding modem DECT phy API.

There is a function nrf_modem_dect_phy_event_handler_set(nrf_modem_dect_phy_event_handler_t handler).
I'd like to know more information about handler:

1. Is this function callback called inside ISR context or inside zephyr thread context? 
2. Are there any strict limitations for the time processing inside that event callback handler?

Thanks in advance!

[Øyvind]

Hello, 

There are some API changes introduced with the latest DECT modem FW. I have forwarded internally to get some feedback on your questions. What modem FW are you currently working with? Note that with the latest modem FW, the latest version of NCS v3.0.x must be used due to these changes.

I hope to have an answer by end of tomorrow. 

Kind regards,
Øyvind

[Øyvind]

Hello, our DECT NR+ team confirms that event handler is called from the same context as the prior callbacks. No specific processing time constraints are defined; however, for Physical Control Channel (PCC) notification events, rapid processing is essential should a Hybrid Automatic Repeat Request (HARQ) transmission be issued consequently.

They noted that documentation improvements is needed, so thanks for pointing this out to us.

Kind regards,
Øyvind

[kirill.neznamov]

Thank you for the information, the answer on my question 2 now is clear. But I still does not understand if events callback is called inside ISR context or inside zephyr thread context? You said that event handler is called from the same context as prior callbacks so the question - is it ISR or some zephyr thread? 

[Øyvind]

kirill.neznamov said:

events callback is called inside ISR context or inside zephyr thread context?

The callbacks are in ISR context.

[kirill.neznamov]

thanks! That's helped me a lot!

[Øyvind]

You're welcome!