Skip to content

Commit

Permalink
Sunil's feedback on allowing RSCV IDs to be used as either HID or CID. (
Browse files Browse the repository at this point in the history
#172)

Signed-off-by: Andrei Warkentin <[email protected]>
  • Loading branch information
andreiw committed Jun 10, 2024
1 parent 4da6020 commit 71ec69d
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion acpi-id.adoc
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[[acpi-ids]]
=== RVI-specific ACPI IDs

ACPI ID is used in the `_HID` (Hardware ID), `_CID` (Compatibility ID) or
ACPI ID is used in the `_HID` (Hardware ID), `_CID` (Compatible ID) or
`_SUB` (Subsystem ID) objects as described in the ACPI Specification for
devices, that do not have a standard enumeration mechanism. The ACPI ID
consists of two parts: a vendor identifier followed by a product identifier.
Expand Down
2 changes: 1 addition & 1 deletion acpi.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ available to an OS loader via the standard `UEFI EFI_GRAPHICS_OUTPUT_PROTOCOL` i
* Revision 4 or later of SPCR.
* For NS16550-compatible UARTs:
** Use `Interface Type` 0x12 (16550-compatible with parameters defined in Generic Address Structure).
** There MUST be a matching AML device object with compatible ID `RSCV0003`.
** There MUST be a matching AML device object with `_HID` (Hardware ID) or `_CID` (Compatible ID) `RSCV0003`.
2+| _See <<acpi-guidance-spcr, additional guidance>>_.
| [[acpi-namespace-dev]]`ACPI_080` | PLIC/APLIC namespace devices MUST
be present in the ACPI namespace whenever corresponding MADT entries are
Expand Down

0 comments on commit 71ec69d

Please sign in to comment.