Handling GETSTATUS CCC With Defining Byte
Target mode supports GETSTATUS CCC with an optional defining byte. The length of data returned depends on the defining byte. Table 24-24 describes the specifics associated with possible defining bytes.
| Value | Encoding | Description |
|---|---|---|
0x00 | TGTSTAT | Returns Target status (standard format). Equivalent to GETSTATUS Format 1 (without a defining byte). |
0x01 – 0x90 | Reserved | These defining bytes are unsupported and are NACKed. |
0x91 | PRECR | Returns an alternate status format describing a Controller-capable device (Secondary Controller). |
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 GETSTATUS CCC as a directed vendor CCC. |
0xFF | Reserved | This defining byte is unsupported and is NACKed. |
The byte format for defining byte ‘91’ is described in Table 24-25.
| Byte | Bit | Field | Field Value |
|---|---|---|---|
BYTE 1 | 0 | Deep Sleep Detected | Returns 0 as Deep Sleep Detection Capability is not supported. |
1 | Handoff Delay NACK | The value of the I3CxCNTRLEXT [REQACKCTRL] register field can be programmed by the application. | |
7:2 | Reserved | 0 is returned as this field is Reserved. | |
BYTE 2 | 15:8 | Vendor Reserved | 0 is returned as this field is Reserved. |
