-/**\r
- Enables a driver to access memory-mapped registers in the EFI system memory space.\r
- Or, Enables a driver to access registers in the EFI CPU I/O space.\r
-\r
- @param This A pointer to the EFI_CPU_IO_PROTOCOL instance.\r
- @param Width Signifies the width of the I/O or Memory operation.\r
- @param Address The base address of the I/O or Memoryoperation.\r
- @param Count The number of I/O or Memory operations to perform.\r
- The number of bytes moved is Width size * Count, starting at Address.\r
- @param Buffer For read operations, the destination buffer to store the results.\r
- For write operations, the source buffer from which to write data.\r
-\r
- @retval EFI_SUCCESS The data was read from or written to the EFI system.\r
- @retval EFI_INVALID_PARAMETER Width is invalid for this EFI system.Or Buffer is NULL.\r
- @retval EFI_UNSUPPORTED The Buffer is not aligned for the given Width.\r
- Or,The address range specified by Address, Width, and Count is not valid for this EFI system.\r
-\r
-**/\r
-typedef\r
-EFI_STATUS\r
-(EFIAPI *EFI_CPU_IO_PROTOCOL_IO_MEM)(\r
- IN EFI_CPU_IO_PROTOCOL *This,\r
- IN EFI_CPU_IO_PROTOCOL_WIDTH Width,\r
- IN UINT64 Address,\r
- IN UINTN Count,\r
- IN OUT VOID *Buffer\r
- );\r
-\r
+// Framework CPU IO protocol structure is the same as CPU IO 2 protocol defined in PI 1.2 spec.\r
+// However, there is a significant different between the Framework CPU I/O\r
+// Protocol and the PI 1.2 CPU I/O 2 Protocol. The Framework one is a runtime\r
+// protocol, which means it can be used by runtime drivers after ExitBootServices().\r
+// The PI one is not runtime safe, so it is a boot services only protocol and may\r
+// not be used by runtime drivers after ExitBootServices().\r