Home
last modified time | relevance | path

Searched refs:_HID (Results 1 – 20 of 20) sorted by relevance

/linux-6.12.1/Documentation/firmware-guide/acpi/
Di2c-muxes.rst21 Name (_HID, ...)
24 Name (_HID, ...)
37 Name (_HID, ...)
52 Name (_HID, ...)
Dnamespace.rst122 | | +-| _HID | Name(_HID, "PNP0C0D"): the hardware ID
134 | +-| _HID | Name(_HID, "PNP0A08"): the hardware ID
178 | | +-| _HID | Name(_HID, "PNP0A0B"): the hardware ID
212 | N | Device | xSDT | _HID |
267 _HID:
268 _HID in the last column of the table means that the object's bus_id
269 is derived from the _HID/_CID identification objects present under
272 used to retrieve the _HID and _CIDs of that object.
279 bus_id cannot be determined from _HID/_CID of the corresponding
281 example, it may be a PCI device with _ADR defined and without _HID
Denumeration.rst510 Moreover, the specification mandates that either a _HID or an _ADR identification
512 6.0). For non-enumerable bus types that object must be _HID and its value must
518 if PRP0001 is returned by _HID, the ACPI subsystem will look for the
534 _HID and _CID depends on the position of PRP0001 in the _CID return package.
535 Specifically, the device IDs returned by _HID and preceding PRP0001 in the _CID
537 will be enumerated to depends on the device ID returned by _HID.
545 Name (_HID, "PRP0001")
565 It is valid to define device objects with a _HID returning PRP0001 and without
571 However, PRP0001 can only be returned from either _HID or _CID of a device
Dnon-d0-probe.rst66 Name (_HID, "SONY319A")
Dgpio-properties.rst19 Name (_HID, ...)
230 In those cases ACPI device identification objects, _HID, _CID, _CLS, _SUB, _HRV,
278 Name (_HID, ...)
Dintel-pmc-mux.rst121 Name (_HID, "INTC105C")
/linux-6.12.1/include/media/
Dipu-bridge.h20 #define IPU_SENSOR_CONFIG(_HID, _NR, ...) \ argument
22 .hid = _HID, \
27 #define NODE_SENSOR(_HID, _PROPS) \ argument
29 .name = _HID, \
/linux-6.12.1/Documentation/translations/zh_CN/PCI/
Dacpi-info.rst39 如果操作系统要管理一个通过ACPI描述的不可发现的设备,该设备将有一个特定的_HID/_CID,以
80 系统固件必须为每个设备提供一个_HID对象...以使OSPM能够做到这一点。
118 主板资源将出现在ACPI命名空间的根部(在_SB下),在一个节点的_HID为EISAID(PNP0C0
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-bus-acpi19 CCCCCCCC contains device object's PNPID (_HID or _CID).
25 This attribute indicates the hardware ID (_HID) of the
27 This file is present for device objects having the _HID
/linux-6.12.1/tools/arch/x86/dell-uart-backlight-emulator/
DREADME9 Name (_HID, "DELL0501")
25 4. A DSDT overlay for the desktop PC replacing the _HID of the 16550 UART
/linux-6.12.1/Documentation/driver-api/
Dipmb.rst55 Name (_HID, "<Vendor-Specific HID>") // Vendor-Specific HID
61 Name (_HID, "IPMB0001") // IPMB device interface
/linux-6.12.1/Documentation/arch/arm64/
Dacpi_object_usage.rst259 and define processor container devices (_HID ACPI0010, Section 8.4,
528 _CID 6.1.2 Use as needed, see also _HID.
530 _CLS 6.1.3 Use as needed, see also _HID.
574 _HID 6.1.5 This is the primary object to use in device probing,
581 _LPI 8.4.4.3 Recommended for use with processor definitions (_HID
634 _RDI 8.4.4.4 Recommended for use with processor definitions (_HID
655 _SUB 6.1.9 Use as needed; _HID or _CID are preferred.
685 Processors should now be defined as Device objects with _HID ACPI0007; do
688 Devices (see Section 8.4.3.1, _HID ACPI0010); do not use processor aggregator
/linux-6.12.1/Documentation/trace/coresight/
Dultrasoc-smb.rst55 Name(_HID, "HISI03A1") \
/linux-6.12.1/Documentation/PCI/
Dacpi-info.rst40 ACPI, that device will have a specific _HID/_CID that tells the OS what
103 system firmware must supply an _HID object ... for each device to
158 namespace (under \_SB) in a node with a _HID of EISAID (PNP0C02), and
/linux-6.12.1/drivers/staging/media/atomisp/pci/
Datomisp_csi2_bridge.c82 #define ATOMISP_SENSOR_CONFIG(_HID, _LANES, _VCM) \ argument
84 .id = _HID, \
/linux-6.12.1/Documentation/firmware-guide/acpi/dsd/
Dphy.rst85 Name(_HID, "NXP0006")
/linux-6.12.1/Documentation/admin-guide/acpi/
Dssdt-overlays.rst33 Name (_HID, "BMA222E")
/linux-6.12.1/Documentation/input/devices/
Dalps.rst22 We experimented with probing the ACPI interface _HID (Hardware ID)/_CID
25 In fact, it appeared to be an m:n mapping between the _HID and actual
/linux-6.12.1/Documentation/spi/
Dspidev.rst48 _HID matching one of the entries in the table.
/linux-6.12.1/Documentation/admin-guide/mm/
Dmemory-hotplug.rst103 If the firmware supports hotplug of NUMA nodes, it defines an object _HID