Handling GETMXDS CCC With Defining Byte

Target supports GETMXDS CCC with an optional defining byte and returns other capabilities based on the value of the defining byte. The length of data returned depends on the defining byte and its associated capabilities. Table 24-22 describes the specifics associated with possible defining bytes.

Table 24-22. GETMXDS Defining Byte Values
ValueEncodingDescription

0x00

WRRDTURN

Describes standard (Target) write/read speed parameters and the optional maximum read turnaround time. Equivalent to the GETMXDS CCC without a defining byte.

0x01 – 0x90

Reserved

These defining bytes are unsupported and are NACKed.

0x91

CRHDLY

Describes delay parameters for a Controller-capable (Secondary Controller) device and its expected activity state during the Controller handoff.

0x92 – 0xBF

Reserved

These defining bytes are unsupported and are NACKed.

0xC0 – 0xDF

Reserved

These defining bytes are unsupported and are NACKed.

0xE0 – 0xFE

Vendor extensions

Target treats the GETMXDS CCC as a directed vendor CCC.

0xFF

Reserved

This defining byte is unsupported and is NACK'd.

The byte format for defining byte ‘91’ is described in Table 24-23.

Table 24-23. CRHDLY Byte Format
BitFieldValue

7:3

Reserved

Returns 0, as this field is Reserved.

2

Set Bus Activity State

The value is returned from the I3CxCLTDATSPD [SETACTSTATE] register field, which can be programmed by the application.

1:0

Controller Handoff Activity State

The value is returned from the I3CxCLTDATSPD [ACTSTATE] register field, which can be programmed by the application.