template <>class WireSyncClientImpl
Defined at line 2803 of file fidling/gen/sdk/fidl/fuchsia.hardware.bluetooth/fuchsia.hardware.bluetooth/cpp/fidl/fuchsia.hardware.bluetooth/cpp/wire_messaging.h
Methods to make a sync FIDL call directly on an unowned handle or a
const reference to a |::fidl::ClientEnd
<
::fuchsia_hardware_bluetooth::Emulator>|,
avoiding setting up a client.
Public Methods
::fidl::WireResult< ::fuchsia_hardware_bluetooth::Emulator::Publish> Publish (::fuchsia_hardware_bluetooth::wire::EmulatorSettings EmulatorSettings)Publish a bt-hci device using the provided `settings`. Each Emulator instance can only
manage a single bt-hci device. Returns Emulator.`HCI_ALREADY_PUBLISHED` if the device has
already been published.
Allocates 176 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_hardware_bluetooth::Emulator::AddLowEnergyPeer> AddLowEnergyPeer (::fuchsia_hardware_bluetooth::wire::PeerParameters PeerParameters)Inserts a new LE peer device to be emulated by this controller. Once registered, the state
of the fake peer can be driven and observed using the `peer` handle.
A reply will be sent to acknowledge the creation of the fake peer. If a peer cannot be
initialized (e.g. due to a missing required field in `parameters` or for containing an
address that is already emulated) the `peer` handle will be closed and an error reply will
be sent.
The peer will appear in advertising reports and respond to requests according to its
configuration as long as the `peer` channel is open. The emulator stops emulating this peer
when the channel gets closed, which makes it no longer discoverable and not respond to any
requests.
Allocates 96 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_hardware_bluetooth::Emulator::AddBredrPeer> AddBredrPeer (::fuchsia_hardware_bluetooth::wire::PeerParameters PeerParameters)Inserts a new BR/EDR peer device to be emulated by this controller. Once registered, the state
of the fake peer can be driven and observed using the `peer` handle.
A reply will be sent to acknowledge the creation of the fake peer. If a peer cannot be
initialized (e.g. due to a missing required field in `parameters` or for containing an
address that is already emulated) the `peer` handle will be closed and an error reply will
be sent.
The peer will appear in inquiry results and respond to requests according to its
configuration as long as the `peer` channel is open. The emulator stops emulating this peer
when the channel gets closed, which makes it no longer discoverable and not respond to any
requests.
Allocates 96 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_hardware_bluetooth::Emulator::WatchControllerParameters> WatchControllerParameters ()Hanging get pattern for the controller parameter state will not resolve until the state has
changed from the last response.
Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.
::fidl::WireResult< ::fuchsia_hardware_bluetooth::Emulator::WatchLeScanStates> WatchLeScanStates ()Returns a vector of the least to most recent states for the link layer LE scan procedure.
This method returns when there has been at least one state change since the last invocation
of this method by this client.
Multiple calls to this method can be outstanding at a given time. All calls will resolve in
a response as soon as there is a change to the scan state.
Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.
::fidl::WireResult< ::fuchsia_hardware_bluetooth::Emulator::WatchLegacyAdvertisingStates> WatchLegacyAdvertisingStates ()Returns a vector of the least to most recent states for the link layer LE legacy
advertising procedure. This method returns when there has been at least one state change
since the last invocation of this method by this client.
Multiple calls to this method can be outstanding at a given time. All calls will resolve in
a response as soon as there is a change to the scan state.
Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.