Update preprocessor macro names indicating CCI-P encodings available.
// after the initial release, allowing RTL to work with multiple versions.
//
-// Speculative loads: eREQ_RDLSPEC and the error flag in t_ccip_c0_RspMemHdr
+// The fields required to encode speculative loads are available when
+// CCIP_ENCODING_HAS_RDLSPEC is defined.
+//
+// Speculative loads may be useful for emitting a load prefetch with virtual
+// addresses when it is possible that the virtual address is invalid (has no
+// translation). Speculative reads return a flag indicating failure and
+// don't trigger a hard failure. The MPF BBB can be configured to honor
+// eREQ_RDLSPEC. FIM's that take only physical addresses do not support
+// speculative reads.
+`define CCIP_ENCODING_HAS_RDLSPEC 1
+// CCIP_RDLSPEC_AVAIL is maintained for legacy code support. In new code
+// use the new name, CCIP_ENCODING_HAS_RDLSPEC. They are equivalent.
`define CCIP_RDLSPEC_AVAIL 1
-// Byte enable, controlling which bytes in a line are updated.
+// The fields required to encode partial-line writes are present when
+// CCIP_ENCODING_HAS_BYTE_WR is defined.
+//
// Be careful! This flag only indicates whether the CCI-P data structures
// can encode byte enable. The flag does not indicate whether the platform
// actually honors the encoding. For that, AFUs must check the value of
// ccip_cfg_pkg::BYTE_EN_SUPPORTED.
-`define CCIP_BYTE_EN_AVAIL 1
+`define CCIP_ENCODING_HAS_BYTE_WR 1
import ccip_if_pkg::*;
