Home
last modified time | relevance | path

Searched full:t_ifs (Results 1 – 4 of 4) sorted by relevance

/nrf52832-nimble/packages/NimBLE-latest/nimble/drivers/nrf52/
H A Dsyscfg.yml27 This defines additional margin for T_IFS tolerance while in
29 controllers that exceed proper T_IFS (150 usecs) by more
/nrf52832-nimble/packages/NimBLE-latest/nimble/drivers/nrf52/src/
H A Dble_phy.c644 /* RX shall start exactly T_IFS after TX end captured in CC[2] */ in ble_phy_wfr_enable()
661 * Some controllers exceed T_IFS when transmitting on coded phy in ble_phy_wfr_enable()
895 /* Schedule RX exactly T_IFS after TX end captured in CC[2] */ in ble_phy_tx_end_isr()
1021 /* Schedule TX exactly T_IFS after RX end captured in CC[2] */ in ble_phy_rx_end_isr()
/nrf52832-nimble/packages/NimBLE-latest/nimble/controller/src/
H A Dble_ll_sched.c389 * the earliest after "T_IFS + AUX_CONNECT_REQ + transmitWindowDelay". in ble_ll_sched_master_new()
619 * the earliest after "T_IFS + AUX_CONNECT_REQ + transmitWindowDelay". in ble_ll_sched_master_new()
H A Dble_ll_adv.c2879 * we need to send a scan response and that needs to be acted on within T_IFS.