Package: android.hardware.wifi@1.0

IWifiChipEventCallback

interface IWifiChipEventCallback

Methods

onChipReconfigured

oneway onChipReconfigured (ChipModeId modeId)

Callback indicating that the chip has been reconfigured successfully.At this point the interfaces available in the mode must be able to be configured.When this is called any previous iface objects must be considered invalid.

Details
RPC mode
oneway
Parameters
modeId
The mode that the chip switched to, corresponding to the id property of the target ChipMode.

onChipReconfigureFailure

oneway onChipReconfigureFailure (WifiStatus status)

Callback indicating that a chip reconfiguration failed.This is a fatal error and any iface objects available previously must be considered invalid.The client can attempt to recover by trying to reconfigure the chip again using |IWifiChip.configureChip|.

Details
RPC mode
oneway
Parameters
status
Failure reason code.

onIfaceAdded

oneway onIfaceAdded (IfaceType type, string name)

Callback indicating that a new iface has been added to the chip.

Details
RPC mode
oneway
Parameters
type
Type of iface added.
name
Name of iface added.

onIfaceRemoved

oneway onIfaceRemoved (IfaceType type, string name)

Callback indicating that an existing iface has been removed from the chip.

Details
RPC mode
oneway
Parameters
type
Type of iface removed.
name
Name of iface removed.

onDebugRingBufferDataAvailable

oneway onDebugRingBufferDataAvailable (WifiDebugRingBufferStatus status, vec<uint8_t> data)

Callbacks for reporting debug ring buffer data.

The ring buffer data collection is event based:- Driver calls this callback when new records are available, the |WifiDebugRingBufferStatus| passed up to framework in the callback indicates to framework if more data is available in the ring buffer.It is not expected that driver will necessarily always empty the ring immediately as data is available, instead driver will report data every X seconds or if N bytes are available based on the parameters set via |startLoggingToDebugRingBuffer|.- In the case where a bug report has to be captured, framework will require driver to upload all data immediately.This is indicated to driver when framework calls |forceDumpToDebugRingBuffer|.The driver will start sending all available data in the indicated ring by repeatedly invoking this callback.

Details
RPC mode
oneway
Parameters
status
Status of the corresponding ring buffer.This should contain the name of the ring buffer on which the data is available.
data
Raw bytes of data sent by the driver.Must be dumped out to a bugreport and post processed.

onDebugErrorAlert

oneway onDebugErrorAlert (int32_t errorCode, vec<uint8_t> debugData)

Callback indicating that the chip has encountered a fatal error.Client must not attempt to parse either the errorCode or debugData.Must only be captured in a bugreport.

Details
RPC mode
oneway
Parameters
errorCode
Vendor defined error code.
debugData
Vendor defined data used for debugging.