Home
last modified time | relevance | path

Searched refs:GUID (Results 1 – 25 of 29) sorted by relevance

12

/Linux-v5.4/drivers/platform/x86/
Dtc1100-wmi.c21 #define GUID "C364AC71-36DB-495A-8494-B439D472A505" macro
59 status = wmi_query_block(GUID, instance, &result); in get_state()
111 status = wmi_set_block(GUID, instance, &input); in set_state()
233 if (!wmi_has_guid(GUID)) in tc1100_init()
/Linux-v5.4/Documentation/ABI/stable/
Dsysfs-firmware-efi-vars12 GUID. They also have an arbitrary binary value
36 guid: The vendor GUID of the variable. This
37 should always match the GUID in the
74 variable that has a matching vendor GUID
Dsysfs-bus-vmbus12 Description: The VMBus interface type GUID of the device
19 Description: The VMBus interface instance GUID of the device
Dsysfs-driver-ib_srp14 byte I/O controller GUID portion of the 16-byte target port
129 Description: Eight-byte I/O controller GUID portion of the 16-byte target
Dsysfs-class-infiniband14 node_guid: (RO) Node GUID
16 sys_image_guid: (RO) System image GUID
379 administrative state of a given GUID
/Linux-v5.4/fs/ntfs/
Dlayout.h1105 } __attribute__ ((__packed__)) GUID; typedef
1123 GUID birth_volume_id;
1124 GUID birth_object_id;
1125 GUID domain_id;
1137 GUID object_id; /* Unique id assigned to the
1145 GUID birth_volume_id; /* Unique id of volume on which
1147 GUID birth_object_id; /* Unique id of file when it was
1149 GUID domain_id; /* Reserved, zero. */
1596 /* 12*/ GUID object_type;
1597 /* 28*/ GUID inherited_object_type;
[all …]
/Linux-v5.4/Documentation/driver-api/mei/
Dmei.rst17 Each Intel ME feature, or Intel ME Client is addressed by a unique GUID and
29 :c:macro:`MEI_CONNECT_CLIENT_IOCTL`, which passes the desired GUID.
94 in_client_uuid - GUID of the FW Feature that needs
101 ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
Diamt.rst56 firmware feature using a defined GUID and then communicates with the feature
/Linux-v5.4/drivers/staging/fwserial/
DTODO9 GUID-to-port matching/whitelist/blacklist.
/Linux-v5.4/Documentation/admin-guide/acpi/
Dssdt-overlays.rst120 "Name-GUID" and that the first 4 bytes in the file (little-endian format)
155 # try to pick up an existing GUID
158 # use a randomly generated GUID
/Linux-v5.4/drivers/staging/unisys/Documentation/
Doverview.txt77 visorbus:<device type GUID>
100 * the GUID(s) of the channel type(s) that are handled by this driver, as
105 device/channel with the appropriate channel-type GUID(s) appears or
205 typeguid a GUID identifying the channel type, in
215 zoneguid a GUID identifying the channel zone, in
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-devices-platform-ipmi96 (RO) A GUID (Globally Unique ID), also referred to as a UUID
98 as described in section 20.8 'Get Device GUID Command' of the
Dsysfs-firmware-efi-esrt30 Description: Each ESRT entry is identified by a GUID, and each gets a
/Linux-v5.4/drivers/usb/dwc2/
Dcore.c810 addr = hsotg->regs + GUID; in dwc2_dump_global_registers()
812 (unsigned long)addr, dwc2_readl(hsotg, GUID)); in dwc2_dump_global_registers()
Dhw.h231 #define GUID HSOTG_REG(0x003c) macro
Ddebugfs.c354 dump_register(GUID),
/Linux-v5.4/Documentation/fpga/
Ddfl.rst48 | GUID |
149 Read Accelerator GUID (afu_id)
/Linux-v5.4/Documentation/
Ddebugging-via-ohci1394.txt118 firewire_core 0000:15:00.1: created device fw1: GUID 00061b0020105917, S400
/Linux-v5.4/Documentation/core-api/
Dkernel-api.rst171 UUID/GUID
Dprintk-formats.rst329 UUID/GUID addresses
/Linux-v5.4/Documentation/media/v4l-drivers/
Duvcvideo.rst158 __u8 entity[16] UVC extension unit GUID
/Linux-v5.4/Documentation/driver-api/
Duio-howto.rst674 Since the driver does not declare any device GUID's, it will not get
677 the network device class GUID::
685 the hardware specific driver and bind the generic driver, using the device specific GUID
/Linux-v5.4/block/partitions/
DKconfig249 bool "EFI GUID Partition support" if PARTITION_ADVANCED
/Linux-v5.4/drivers/usb/dwc3/
Ddebugfs.c70 dump_register(GUID),
/Linux-v5.4/drivers/message/fusion/lsi/
Dmpi_cnfg.h2347 U8 GUID[24]; /* 08h */ member

12