external 32.768K start up question

[William.wei]

in sdk16 "examples\peripheral\usbd_hid_composite" example, i found that after those code

ret = nrf_drv_clock_init();
APP_ERROR_CHECK(ret);

nrf_drv_clock_lfclk_request(NULL);
while(!nrf_drv_clock_lfclk_is_running())
{
/* Just waiting */
}

the external 32.768 clock is not running through this register:NRF_CLOCK->LFCLKSTAT, it indicates internal RC is running ,not external RC;

my question is ,in the while loop, why "nrf_drv_clock_lfclk_is_running" doesn't judge it is internal RC or external RC?

seems like it is a bug.

[William.wei]

Thank you Berg, i understand what you said, is there any API interface for customer to use , instead of register 

[Vidar Berg]

They can register a callback when they call nrf_drv_clock_lfclk_request() which will get invoked when the clock has started. Note that the event registers are cleared inside the clock driver.