SPRUJ52C june 2022 – july 2023 AM69 , AM69A , TDA4AH-Q1 , TDA4AP-Q1 , TDA4VH-Q1 , TDA4VP-Q1
For this particular case of UFS, as application layer, the connections are setup statically by having reset values for the UFS host controller and a UFS device predefined at reset. The predefined reset values are given in Table 12-302.
Note that these reset values are different from the default reset values given by the MIPI UniPro Specification but are in line with the reset values given by the JEDEC UFS Specification. Furthermore, the reset values for the device are only assumed reset values.
UniPro Attribute | Reset Value of the UFS Host Controller | Expected UFS Device Reset Value |
---|---|---|
N_DeviceID | 0 | 1 |
N_DeviceID_valid | TRUE | TRUE |
T_PeerDeviceID | 1 | 0 |
T_PeerCPortID | 0 | 0 |
T_TrafficClass | 0 | 0 |
T_CPortFlags | 6 (E2E_FC off, CSD off, CSV off) | 6 (E2E_FC off, CSD off, CSV off) |
T_ConnectionState | 1 (CONNECTED) | 1 (CONNECTED) |
At link startup and after exiting from the Auto-Hibernate state the UFS host controller will set the UniPro CPort attributes as shown in the following sequence:
CPort 0 Configuration:
Additionally, if the value of the UFS_XCNF[17-16] PCPCONFEX bit field is set to 3h, the UFS host controller will configure also the CPorts of the PEER device as follows:
If the value of the UFS_XCNF[17-16] PCPCONFEX bit field is set to 2h, the UFS host controller will poll the T_ConnectionState attribute of CPort0 of the PEER device. Only CPort0 will be polled.