template <>class WireWeakOnewayClientImpl
Defined at line 16674 of file fidling/gen/sdk/fidl/fuchsia.hardware.audio/fuchsia.hardware.audio/cpp/fidl/fuchsia.hardware.audio/cpp/wire_messaging.h
Public Methods
::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::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.