Skip to content

Commit

Permalink
Specify hardware description mechanisms instead of specific ones
Browse files Browse the repository at this point in the history
Signed-off-by: Rahul Pathak <rpathak@ventanamicro.com>
  • Loading branch information
pathakraul committed Apr 18, 2024
1 parent c0648f2 commit 1999d3b
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion src/srvgrp-clock.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ clock source affects the entire domain which may contain multiple devices.

The topology of the devices and the clock source is dependent on how the system
is designed and implementation specific. The OS can discover this topology
through firmware tables (DT cite:[DT] / ACPI cite:[ACPI]).
through supported hardware description mechanisms.

*Clock Rate Format*::
Each clock rate is a tuple of two `32 bits` values `(uint32, uint32)` represented
Expand Down
8 changes: 4 additions & 4 deletions src/srvgrp-device-power.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,10 @@ Each domain must support ON and OFF states along with custom power states which
are discoverable. Domains may also have power states which may preserve the
context. The level of context preserved will depends on the level of power state.

Power states for domains will be discovered via DT cite:[DT] or ACPI cite:[ACPI],
where the values for ON and OFF are already fixed and known. The power state encodes
both the power state value and the context preserved or lost information
corresponding to that state.
Power states for domains will be discovered via supported hardware description
mechanisms where the values for ON and OFF are already fixed and known.
The power state encodes both the power state value and the context preserved or
lost information corresponding to that state.

[#table_devpower_powerstate_data]
.Power States Encoding
Expand Down

0 comments on commit 1999d3b

Please sign in to comment.