Complete preparations for next release

Signed-off-by: Al Stone <[email protected]>

dsd-guide.adoc

@@ -5,8 +5,8 @@
 //
 # _DSD (Device Specific Data) Implementation Guide
 :author: UEFI ACPI Specification Working Group
-:revnumber: 2.0-rc2
-:revdate: March 2021
+:revnumber: 2.0
+:revdate: 23 April 2021
 :doctype: book
 :sectnums:
 :toc: macro
@@ -102,7 +102,7 @@ UUID:: Universal Unique Identifier, a synonym for GUID.
 
 ### Conventions
 
-The following typographic connventions are used:
+The following typographic conventions are used:
 
 Computer Text:: ``monospace text`` is used to represent computer
    inputs or outputs.
@@ -115,7 +115,7 @@ Terms:: _italic text_ is used to highlight important terminology.
 - [[[ACPI]]] Advanced Configuration and Power Interface (ACPI) Specification,
   Version 6.3, January 2019.  Copyright (c) 2018, Unified Extensible
   Firmware Interface (UEFI) Forum, Inc. https://uefi.org/specifications
-- [[DCO]] Developer's Certificate of Origing. https://developercertificate.org/
+- [[DCO]] Developer's Certificate of Origin. https://developercertificate.org/
 - [[[RFC2119]]] https://www.ietf.org/rfc/rfc2119.txt
 
 
@@ -627,7 +627,7 @@ forming a graph. An example is shown below.
 image::fig1.png[Debug Trace Graph]
 
 This Debug Trace Graph includes Trace Sources (Trace 1 and Trace 2)
-that produce traces, multiplexors that combine traces from one or more
+that produce traces, multiplexers that combine traces from one or more
 sources, and multiple Sinks to which traces are fed. The Traces could
 be generated by debug logic attached to devices or logical blocks
 in a system.  Some OS drivers need to be able to process graphs such
@@ -810,11 +810,11 @@ Scope (\_SB) {
 
 #### Known Device Graph UUIDs
 
-##### Arm Coresight ACPI Specification
+##### Arm CoreSight ACPI Specification
 
 *3ECBC8B6-1D0E-4FB3-8107-E627F805C6CD*
 
-https://developer.arm.com/docs/den0067/latest/acpi-for-coresighttm-10-platform-design-document
+https://developer.arm.com/documentation/den0067/latest
 
 
 [appendix]
@@ -872,7 +872,7 @@ used instead.
     Property: max-transfer-unit
     Value:    Integer (ASL assumes hexadecimal)
     Description:
-        Specifies the MTU (IEEE defined maxium transfer unit)
+        Specifies the MTU (IEEE defined maximum transfer unit)
         supported by the device
     Example:
         Package (2) { "max-transfer-unit", 5dc } // MTU of 1500
@@ -892,6 +892,10 @@ used instead.
 The following Device Properties are part of the ``uefi-`` Device Property
 Key namespace. These should be used instead of the entries in Appendix A.
 
+When using values for device properties listed in this appendix, only
+explicitly defined values must be used. System behavior with any other
+values is undefined.
+
 Request for additional Key names in the ``uefi-`` namespace should be
 made as a github merge request to this document.
 
@@ -943,7 +947,7 @@ made as a github merge request to this document.
     Property: uefi-max-transfer-unit
     Value:    Integer (ASL assumes hexadecimal)
     Description:
-        Specifies the MTU (IEEE defined maxium transfer unit)
+        Specifies the MTU (IEEE defined maximum transfer unit)
         supported by the device
     Example:
         Package (2) { "uefi-max-transfer-unit", 5dc } // MTU of 1500
@@ -955,6 +959,18 @@ made as a github merge request to this document.
         Specifies the maximum speed in Mbits/second supported by the device
     Example:
         Package (2) { "uefi-max-speed", 3e8 } // 1000 Mbps
+---------------------------------------------------------------------------
+    Property: uefi-register-access-restriction
+    Value:    String, one of the following:
+              "32bit-access-for-64bit" => Must use 32-bit register access for 64-bit registers
+    Description:
+        Specifies the register access restrictions of a device. On platforms
+        which may have register access restrictions for some devices, this
+        property can be used to communicate to the OS the register access
+        restriction type.
+    Example:
+        // Must use 32-bit register access for 64-bit registers
+        Package (2) { "uefi-register-access-restriction", "32bit-access-for-64bit" }
 
 ....