template <>
class WireSyncClientImpl
Defined at line 5467 of file fidling/gen/sdk/fidl/fuchsia.hardware.audio/fuchsia.hardware.audio/cpp/fidl/fuchsia.hardware.audio/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_audio::Dai>|,
avoiding setting up a client.
Public Methods
::fidl::WireResult< ::fuchsia_hardware_audio::Dai::GetHealthState> GetHealthState ()
Retrieves top level health state.
A driver not responding promptly can be used as an indication of an unhealthy driver.
Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.
::fidl::OneWayStatus SignalProcessingConnect (::fidl::ServerEnd< ::fuchsia_hardware_audio_signalprocessing::SignalProcessing> && protocol)
Connect to a `SignalProcessing` protocol.
Multiple connections may be supported, if a new connection request is not supported, i.e.
the maximum number of connections have already been created, for instance one, then the
`protocol` channel (not the channel upon which `SignalProcessingConnect` is being called)
will be closed with a `ZX_ERR_ALREADY_BOUND` epitaph.
If signal processing is not supported at all, then the `protocol` channel (again, not the
channel upon which `SignalProcessingConnect` is being called) will be closed with a
`ZX_ERR_NOT_SUPPORTED` epitaph.
This method is named `SignalProcessingConnect` instead of `Connect` because this protocol
is intended to be composed, and hence the more verbose name allows differentiation and
improved clarity.
Allocates 40 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_hardware_audio::Dai::Reset> Reset ()
Resets the DAI HW. The `ring_buffer` channel obtained via `CreateRingBuffer` may be closed
by the driver, in this case the client needs to obtain a new `ring_buffer`.
`Reset` returns when the reset is completed. If the driver can't successfully reset the HW,
it will close the DAI protocol channel, in this case the client may obtain a new DAI
protocol channel and retry.
Allocates 32 bytes of message buffer on the stack. No heap allocation necessary.
::fidl::WireResult< ::fuchsia_hardware_audio::Dai::GetProperties> GetProperties ()
Retrieves top level static properties.
Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.
::fidl::WireResult< ::fuchsia_hardware_audio::Dai::GetDaiFormats> GetDaiFormats ()
Retrieves the DAI formats supported by the DAI, if not available at the time the DAI
may reply with an error status and the client may retry at a later time.
Retrieving multiple `DaiSupportedFormats` allows for cases where exclusive combinations of
the parameters in SupportedFormats may be supported.
Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.
::fidl::WireResult< ::fuchsia_hardware_audio::Dai::GetRingBufferFormats> GetRingBufferFormats ()
Retrieves the ring buffer formats supported by the DAI, if not available at the time the DAI
may reply with an error status and the client may retry at a later time.
Retrieving multiple `SupportedFormats` allows for cases where exclusive combinations of
the parameters in `SupportedFormats` may be supported.
Allocates 16 bytes of request buffer on the stack. Response is heap-allocated.
::fidl::OneWayStatus CreateRingBuffer (const ::fuchsia_hardware_audio::wire::DaiFormat & dai_format, ::fuchsia_hardware_audio::wire::Format ring_buffer_format, ::fidl::ServerEnd< ::fuchsia_hardware_audio::RingBuffer> && ring_buffer)
`CreateRingBuffer` is sent by clients to select both a DAI format and a ring buffer format
based on information that the driver provides in `GetDaiFormats` and `GetRingBufferFormats`,
what is supported by the client, and any other requirement. The `ring_buffer` channel is
used to control the audio buffer, if a previous ring buffer channel had been established and
was still active, the driver must close that (ring buffer) channel and make every attempt to
gracefully quiesce any on-going streaming operations in the process.
Allocates 120 bytes of message buffer on the stack. No heap allocation necessary.