Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
95 lines
2.8 KiB
ReStructuredText
95 lines
2.8 KiB
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0
|
|
.. include:: <isonum.txt>
|
|
|
|
===================================
|
|
Referencing hierarchical data nodes
|
|
===================================
|
|
|
|
:Copyright: |copy| 2018, 2021 Intel Corporation
|
|
:Author: Sakari Ailus <sakari.ailus@linux.intel.com>
|
|
|
|
ACPI in general allows referring to device objects in the tree only.
|
|
Hierarchical data extension nodes may not be referred to directly, hence this
|
|
document defines a scheme to implement such references.
|
|
|
|
A reference to a _DSD hierarchical data node is a string consisting of a
|
|
device object reference followed by a dot (".") and a relative path to a data
|
|
node object. Do not use non-string references as this will produce a copy of
|
|
the hierarchical data node, not a reference!
|
|
|
|
The hierarchical data extension node which is referred to shall be located
|
|
directly under its parent object i.e. either the device object or another
|
|
hierarchical data extension node [dsd-guide].
|
|
|
|
The keys in the hierarchical data nodes shall consist of the name of the node,
|
|
"@" character and the number of the node in hexadecimal notation (without pre-
|
|
or postfixes). The same ACPI object shall include the _DSD property extension
|
|
with a property "reg" that shall have the same numerical value as the number of
|
|
the node.
|
|
|
|
In case a hierarchical data extensions node has no numerical value, then the
|
|
"reg" property shall be omitted from the ACPI object's _DSD properties and the
|
|
"@" character and the number shall be omitted from the hierarchical data
|
|
extension key.
|
|
|
|
|
|
Example
|
|
=======
|
|
|
|
In the ASL snippet below, the "reference" _DSD property contains a string
|
|
reference to a hierarchical data extension node ANOD under DEV0 under the parent
|
|
of DEV1. ANOD is also the final target node of the reference.
|
|
::
|
|
|
|
Device (DEV0)
|
|
{
|
|
Name (_DSD, Package () {
|
|
ToUUID("dbb8e3e6-5886-4ba6-8795-1319f52a966b"),
|
|
Package () {
|
|
Package () { "node@0", "NOD0" },
|
|
Package () { "node@1", "NOD1" },
|
|
}
|
|
})
|
|
Name (NOD0, Package() {
|
|
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
|
|
Package () {
|
|
Package () { "reg", 0 },
|
|
Package () { "random-property", 3 },
|
|
}
|
|
})
|
|
Name (NOD1, Package() {
|
|
ToUUID("dbb8e3e6-5886-4ba6-8795-1319f52a966b"),
|
|
Package () {
|
|
Package () { "reg", 1 },
|
|
Package () { "anothernode", "ANOD" },
|
|
}
|
|
})
|
|
Name (ANOD, Package() {
|
|
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
|
|
Package () {
|
|
Package () { "random-property", 0 },
|
|
}
|
|
})
|
|
}
|
|
|
|
Device (DEV1)
|
|
{
|
|
Name (_DSD, Package () {
|
|
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
|
|
Package () {
|
|
Package () { "reference", "^DEV0.ANOD" }
|
|
},
|
|
}
|
|
})
|
|
}
|
|
|
|
Please also see a graph example in
|
|
Documentation/firmware-guide/acpi/dsd/graph.rst.
|
|
|
|
References
|
|
==========
|
|
|
|
[dsd-guide] DSD Guide.
|
|
https://github.com/UEFI/DSD-Guide/blob/main/dsd-guide.adoc, referenced
|
|
2021-11-30.
|