Home
last modified time | relevance | path

Searched full:_dsd (Results 1 – 25 of 37) sorted by relevance

12

/linux/Documentation/firmware-guide/acpi/
H A DDSD-properties-rules.rst4 _DSD Device Properties Usage Rules
10 The _DSD (Device Specific Data) configuration object, introduced in ACPI 5.1,
14 _DSD output. However, there are generic UUIDs defined for _DSD recognized by
22 In the ACPI _DSD context it is an element of the sub-package following the
23 generic Device Properties UUID in the _DSD return package as specified in the
24 section titled "Well-Known _DSD UUIDs and Data Structure Formats" sub-section
25 "Device Properties UUID" in _DSD (Device Specific Data) Implementation Guide
29 that can be returned by _DSD in the Device Properties UUID sub-package for a
33 like a device. In the ACPI _DSD context it is the set of all properties that
41 section titled "Well-Known _DSD UUIDs and Data Structure Formats" sub-section
[all …]
H A Dgpio-properties.rst4 _DSD Device Properties Related to GPIO
7 With the release of ACPI 5.1, the _DSD configuration object finally
13 With _DSD we can now query GPIOs using a name instead of an integer
29 Name (_DSD, Package ()
58 Note, active_low in _DSD does not make sense for GpioInt() resource and
82 | **Up** | x (no _DSD) | |
88 | **Down** | x (no _DSD) | |
96 _DSD is present, both GPIOs will be treated as active with a high
118 Active High. Even for the cases when _DSD() is involved (see the example
125 _DSD device properties for GPIO controllers:
[all …]
H A Denumeration.rst194 The interrupt name can be listed in _DSD as 'interrupt-names'. The names
210 Name (_DSD, Package () {
269 eeprom, etc. This information can be passed via _DSD method like::
274 Name (_DSD, Package ()
340 Name (_DSD, Package ()
368 the device to the driver. ACPI 5.1 extended this with _DSD (Device
391 // ACPI 5.1 _DSD used for naming the GPIOs
392 Name (_DSD, Package ()
433 about the _DSD binding related to GPIOs.
438 ACPI _DSD (Device Specific Data) can be used to describe RS-485 capability
[all …]
H A Dintel-pmc-mux.rst67 Mux-agent specific _DSD Device Properties
75 connector. The driver extracts the correct port numbers by reading specific _DSD
82 Name (_DSD, Package () {
103 Name (_DSD, Package () {
127 Name (_DSD, Package () {
142 Name (_DSD, Package () {
/linux/Documentation/firmware-guide/acpi/dsd/
H A Dgraph.rst7 _DSD chapter
10 _DSD (Device Specific Data) [dsd-guide] is a predefined ACPI device
13 specification [acpi]. There are two _DSD extensions that are relevant
26 the firmware type. In ACPI, fwnodes are _DSD hierarchical data
27 extensions objects. A device's _DSD object is represented by an
43 All port nodes are located under the device's "_DSD" node in the hierarchical
85 Name (_DSD, Package () {
119 Name (_DSD, Package () {
165 [dsd-rules] _DSD Device Properties Usage Rules.
H A Ddata-node-references.rst15 A reference to a _DSD hierarchical data node is a string consisting of a
26 or postfixes). The same ACPI object shall include the _DSD property extension
31 "reg" property shall be omitted from the ACPI object's _DSD properties and the
39 In the ASL snippet below, the "reference" _DSD property contains a string
46 Name (_DSD, Package () {
77 Name (_DSD, Package () {
H A Dphy.rst13 This document introduces two _DSD properties that are to be used
17 Properties UUID For _DSD" [dsd-guide] document and the
50 The "phy-mode" _DSD property is used to describe the connection to
61 MAC port, which is linked in the _DSD package via
63 in accordance with [dsd-guide] "_DSD Implementation Guide" document).
126 Name (_DSD, Package () {
137 Name (_DSD, Package () {
153 Name (_DSD, Package () {
169 Name (_DSD, Package () {
H A Dleds.rst38 Name (_DSD, Package () {
67 Name (_DSD, Package () {
/linux/drivers/hwtracing/coresight/
H A Dcoresight-platform.c348 /* ACPI Graph _DSD UUID : "ab02a46b-74c7-45a2-bd68-f7d344ef2153" */
405 * acpi_validate_dsd_graph - Make sure the given _DSD graph conforms
406 * to the ACPI _DSD Graph specification.
445 * Name (_DSD, Package() {
516 /* acpi_get_dsd_graph - Find the _DSD Graph property for the given device. */
524 status = acpi_evaluate_object_typed(adev->handle, "_DSD", NULL, in acpi_get_dsd_graph()
532 * _DSD property consists tuples { Prop_UUID, Package() } in acpi_get_dsd_graph()
541 /* All _DSD elements must have a UUID and a Package */ in acpi_get_dsd_graph()
544 /* Skip the non-Graph _DSD packages */ in acpi_get_dsd_graph()
550 dev_warn(&adev->dev, "Invalid Graph _DSD property\n"); in acpi_get_dsd_graph()
[all …]
/linux/Documentation/arch/arm64/
H A Darm-acpi.rst299 and provided to a driver via the _DSD object.
312 compatibility as new hardware comes out? The _DSD method was created
314 use the _DSD method for device properties and nothing else.
318 be used if _DSD cannot represent the data required, and there is no way
319 to create a new UUID for the _DSD object. Note that there is even less
320 regulation of the use of _DSM than there is of _DSD. Drivers that depend
325 Drivers should look for device properties in the _DSD object ONLY; the _DSD
327 describes how to define the structure of an object returned via _DSD, and
329 only use the _DSD Device Properties UUID [4]:
561 [4] _DSD (Device Specific Data) Implementation Guide
H A Dacpi_object_usage.rst546 _DSD 6.2.5 To be used with caution. If this object is used, try
549 should it be necessary to create a new _DSD UUID.
551 In either case, submit the _DSD definition along with
554 considered complete without a corresponding _DSD
603 using _DSD MUST be used to create an _OSC definition;
/linux/sound/hda/codecs/side-codecs/
H A Dcs35l41_hda_property.c42 * Device 103C89C6 does have _DSD, however it is setup to use the wrong boost type.
43 * We can override the _DSD to correct the boost type here.
45 * in the ACPI. The Reset GPIO is also valid, so we can use the Reset defined in _DSD.
217 /* only one GPIO CS is supported without using _DSD, obtained using index 0 */ in cs35l41_add_gpios()
257 dev_err(cs35l41->dev, "ACPI Device does not match, cannot override _DSD.\n"); in generic_dsd_config()
275 "_DSD already exists.\n"); in generic_dsd_config()
298 "Cannot update SPI CS, _DSD already exists.\n"); in generic_dsd_config()
376 /* If _DSD exists for this laptop, we cannot support it through here */ in hp_i2c_int_2amp_dual_spkid()
404 * Device CLSA010(0/1) doesn't have _DSD so a gpiod_get by the label reset won't work.
/linux/drivers/acpi/
H A Dproperty.c41 /* ACPI _DSD device properties GUID [1]: daffd814-6eba-4d8c-8a91-bc9bbf4aa301 */
61 /* ACPI _DSD data subnodes GUID [1]: dbb8e3e6-5886-4ba6-8795-1319f52a966b */
66 /* ACPI _DSD data buffer GUID [1]: edb12dd0-363d-4085-a3d2-49522ca160c4 */
112 * Extract properties from the _DSD-equivalent package pointed to by in acpi_nondev_subnode_extract()
120 * Look for subnodes in the _DSD-equivalent package pointed to by desc in acpi_nondev_subnode_extract()
134 * _DSD-equivalent package and its scope cannot be determined. in acpi_nondev_subnode_extract()
153 * If the scope is unknown, the _DSD-equivalent package being parsed in acpi_nondev_subnode_ok()
154 * was embedded in an outer _DSD-equivalent package as a result of in acpi_nondev_subnode_ok()
211 * a package that contains _DSD-equivalent information. in acpi_add_nondev_subnodes()
225 * The target package is expected to contain _DSD- in acpi_add_nondev_subnodes()
[all …]
/linux/Documentation/driver-api/
H A Dntb.rst260 * xeon\_b2b\_dsd\_bar2\_addr64 - See *xeon\_b2b\_bar2\_addr64*.
261 * xeon\_b2b\_dsd\_bar4\_addr64 - See *xeon\_b2b\_bar2\_addr64*.
262 * xeon\_b2b\_dsd\_bar4\_addr32 - See *xeon\_b2b\_bar2\_addr64*.
263 * xeon\_b2b\_dsd\_bar5\_addr32 - See *xeon\_b2b\_bar2\_addr64*.
/linux/drivers/input/misc/
H A Dsoc_button_array.c262 /* Parse a single ACPI0011 _DSD button descriptor */
333 /* ACPI0011 _DSD btns descriptors UUID: fa6bd625-9ce8-470d-a2c7-b3ca36c4282e */
339 /* Parse ACPI0011 _DSD button descriptors */
348 status = acpi_evaluate_object_typed(ACPI_HANDLE(dev), "_DSD", NULL, in soc_button_get_button_info()
351 dev_err(dev, "ACPI _DSD object not found\n"); in soc_button_get_button_info()
/linux/drivers/acpi/x86/
H A Dapple.c24 * alternating key/value elements, unlike _DSD which stores them as a package
25 * of 2-element packages. Convert to _DSD format and make them available under
/linux/include/sound/
H A Dsdca.h40 * @interface_revision: Value read from _DSD property, mainly to check
/linux/include/acpi/
H A Dacnames.h29 #define METHOD_NAME__DSD "_DSD"
/linux/drivers/hid/intel-thc-hid/intel-thc/
H A Dintel-thc-wot.c16 * _DSD to map this GPIO resource, so this function first registers wake GPIO
/linux/drivers/platform/x86/amd/hsmp/
H A Dacpi.c116 status = acpi_evaluate_object_typed(ACPI_HANDLE(sock->dev), "_DSD", NULL, in hsmp_read_acpi_dsd()
126 /* HSMP _DSD property should contain 2 objects. in hsmp_read_acpi_dsd()
142 dev_err(sock->dev, "Invalid hsmp _DSD table data\n"); in hsmp_read_acpi_dsd()
/linux/Documentation/trace/coresight/
H A Dultrasoc-smb.rst62 Name(_DSD, Package() { \
/linux/samples/rust/
H A Drust_debugfs.rs19 //! Name (_DSD, Package () { // Sample attribute
/linux/Documentation/arch/x86/
H A Damd_hsmp.rst125 Name(_DSD, Package(2)
/linux/Documentation/driver-api/gpio/
H A Dconsumer.rst442 Systems compliant with ACPI 5.1 or newer may provide a _DSD configuration object
446 _DSD is not present, the mappings between GpioIo()/GpioInt() resources and GPIO
/linux/drivers/gpio/
H A Dgpiolib-acpi-core.c842 dev_dbg(&adev->dev, "GPIO: _DSD returned %s %u %u %u\n", in acpi_get_gpiod_by_index()
915 /* Try first from _DSD */ in __acpi_find_gpio()
1392 /* Try first from _DSD */ in acpi_gpio_count()

12