Bluetooth: Fix use of uint32_t in nRF5 radio timings abstractions

We have conflicting types between the decleration and implementation of
several radio functions.  We should be using u32_t everywhere.  This
shows up when we try and build with newlib enabled.

Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
This commit is contained in:
Kumar Gala 2017-06-22 12:00:24 -05:00 committed by Kumar Gala
commit 7572203f54

View file

@ -22,10 +22,10 @@ void radio_aa_set(u8_t *aa);
void radio_pkt_configure(u8_t bits_len, u8_t max_len, u8_t flags);
void radio_pkt_rx_set(void *rx_packet);
void radio_pkt_tx_set(void *tx_packet);
uint32_t radio_tx_ready_delay_get(u8_t phy, u8_t flags);
uint32_t radio_tx_chain_delay_get(u8_t phy, u8_t flags);
uint32_t radio_rx_ready_delay_get(u8_t phy);
uint32_t radio_rx_chain_delay_get(u8_t phy, u8_t flags);
u32_t radio_tx_ready_delay_get(u8_t phy, u8_t flags);
u32_t radio_tx_chain_delay_get(u8_t phy, u8_t flags);
u32_t radio_rx_ready_delay_get(u8_t phy);
u32_t radio_rx_chain_delay_get(u8_t phy, u8_t flags);
void radio_rx_enable(void);
void radio_tx_enable(void);
void radio_disable(void);