GETCAPS Without Defining Byte

The target returns three bytes of data. Table 24-18 details the data format for GETCAPS CCC without the defining byte.

Table 24-18. Data Bytes Format for GETCAPS CCC without Defining Byte
ByteBit

Field

Field Value

BYTE 1

0

HDR mode 0

1

1

HDR mode 1

0

2

HDR mode 2

0

3

HDR mode 3

0

7:4

Reserved

Reserved

BYTE 2

3:0

I3C 1.x Specification Version

Minor version number of the MIPI I3C Specification with which this I3C v1.x device complies. Returns 4’b0001 v1.1.1 compliant device.

5:4

Group address capabilities

3: Can be assigned three or more group addresses

6

HDR-DDR Write Abort

Returns 0, as this feature is not supported.

7

HDR-DDR Abort CRC

Returns 0, as this feature is not supported.

BYTE 3

0

Multi-Lane (ML) Data Transfer Support

Returns 0, as the Multi-Lane feature is not supported.

1

Device to Device Transfer (D2DXFER) Support

Returns 0, as D2DXFER is not supported in Target mode.

2

Device to Device Transfer (D2DXFER) IBI Capable

Returns 0, as D2DXFER is not supported in Target mode.

3

Defining Byte Support in GETCAPS

Returns 1, as defining byte is supported for v1.1.1 compliant devices.

4

Defining Byte Support in GETSTATUS

Returns 1, as defining byte is supported for v1.1.1 compliant devices.

5

HDR-BT CRC-32 Support

Returns 0, as this feature is not supported.

6

IBI MDB Support for Pending Read Notification

Returns 0, as this feature is not supported.

7

Reserved