#[repr(C)]pub struct ble_hs_cfg {Show 14 fields
pub gatts_register_cb: ble_gatt_register_fn,
pub gatts_register_arg: *mut c_void,
pub sm_io_cap: u8,
pub _bitfield_align_1: [u8; 0],
pub _bitfield_1: __BindgenBitfieldUnit<[u8; 1]>,
pub sm_our_key_dist: u8,
pub sm_their_key_dist: u8,
pub reset_cb: ble_hs_reset_fn,
pub sync_cb: ble_hs_sync_fn,
pub store_read_cb: ble_store_read_fn,
pub store_write_cb: ble_store_write_fn,
pub store_delete_cb: ble_store_delete_fn,
pub store_status_cb: ble_store_status_fn,
pub store_status_arg: *mut c_void,
}
Expand description
@brief Bluetooth Host main configuration structure
Those can be used by application to configure stack.
The only reason Security Manager (sm_ members) is configurable at runtime is to simplify security testing. Defaults for those are configured by selecting proper options in application’s syscfg.
Fields§
§gatts_register_cb: ble_gatt_register_fn
An optional callback that gets executed upon registration of each GATT resource (service, characteristic, or descriptor).
gatts_register_arg: *mut c_void
An optional argument that gets passed to the GATT registration callback.
sm_io_cap: u8
Security Manager Local Input Output Capabilities
_bitfield_align_1: [u8; 0]
§_bitfield_1: __BindgenBitfieldUnit<[u8; 1]>
§sm_our_key_dist: u8
@brief Security Manager Local Key Distribution Mask
sm_their_key_dist: u8
@brief Security Manager Remote Key Distribution Mask
reset_cb: ble_hs_reset_fn
@brief Stack reset callback
This callback is executed when the host resets itself and the controller due to fatal error.
sync_cb: ble_hs_sync_fn
@brief Stack sync callback
This callback is executed when the host and controller become synced. This happens at startup and after a reset.
store_read_cb: ble_store_read_fn
Storage Read callback handles read of security material
store_write_cb: ble_store_write_fn
Storage Write callback handles write of security material
store_delete_cb: ble_store_delete_fn
Storage Delete callback handles deletion of security material
store_status_cb: ble_store_status_fn
@brief Storage Status callback.
This callback gets executed when a persistence operation cannot be performed or a persistence failure is imminent. For example, if is insufficient storage capacity for a record to be persisted, this function gets called to give the application the opportunity to make room.
store_status_arg: *mut c_void
An optional argument that gets passed to the storage status callback.
Implementations§
source§impl ble_hs_cfg
impl ble_hs_cfg
pub fn sm_oob_data_flag(&self) -> c_uint
pub fn set_sm_oob_data_flag(&mut self, val: c_uint)
pub fn sm_bonding(&self) -> c_uint
pub fn set_sm_bonding(&mut self, val: c_uint)
pub fn sm_mitm(&self) -> c_uint
pub fn set_sm_mitm(&mut self, val: c_uint)
pub fn sm_sc(&self) -> c_uint
pub fn set_sm_sc(&mut self, val: c_uint)
pub fn sm_keypress(&self) -> c_uint
pub fn set_sm_keypress(&mut self, val: c_uint)
pub fn new_bitfield_1( sm_oob_data_flag: c_uint, sm_bonding: c_uint, sm_mitm: c_uint, sm_sc: c_uint, sm_keypress: c_uint, ) -> __BindgenBitfieldUnit<[u8; 1]>
Trait Implementations§
source§impl Clone for ble_hs_cfg
impl Clone for ble_hs_cfg
source§fn clone(&self) -> ble_hs_cfg
fn clone(&self) -> ble_hs_cfg
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for ble_hs_cfg
impl Debug for ble_hs_cfg
source§impl Default for ble_hs_cfg
impl Default for ble_hs_cfg
impl Copy for ble_hs_cfg
Auto Trait Implementations§
impl Freeze for ble_hs_cfg
impl RefUnwindSafe for ble_hs_cfg
impl !Send for ble_hs_cfg
impl !Sync for ble_hs_cfg
impl Unpin for ble_hs_cfg
impl UnwindSafe for ble_hs_cfg
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
source§unsafe fn clone_to_uninit(&self, dst: *mut T)
unsafe fn clone_to_uninit(&self, dst: *mut T)
clone_to_uninit
)Layout§
Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...)
attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.
Size: 40 bytes