Home
last modified time | relevance | path

Searched refs:ID (Results 1 – 25 of 644) sorted by relevance

12345678910>>...26

/linux/rust/kernel/
H A Dlist.rs263 pub struct List<T: ?Sized + ListItem<ID>, const ID: u64 = 0> {
265 _ty: PhantomData<ListArc<T, ID>>,
270 unsafe impl<T, const ID: u64> Send for List<T, ID>
272 ListArc<T, ID>: Send,
273 T: ?Sized + ListItem<ID>,
278 unsafe impl<T, const ID: u64> Sync for List<T, ID>
280 ListArc<T, ID>: Sync,
281 T: ?Sized + ListItem<ID>,
293 pub unsafe trait ListItem<const ID: u64 = 0>: ListArcSafe<ID> {
307 unsafe fn view_links(me: *const Self) -> *mut ListLinks<ID>; in view_links() argument
[all …]
/linux/drivers/scsi/aic7xxx/
H A Daic7xxx_osm_pci.c47 #define ID(x) ID_C(x, PCI_CLASS_STORAGE_SCSI) macro
51 ID(ID_AHA_2902_04_10_15_20C_30C),
53 ID(ID_AHA_2930CU),
54 ID(ID_AHA_1480A & ID_DEV_VENDOR_MASK),
55 ID(ID_AHA_2940AU_0 & ID_DEV_VENDOR_MASK),
56 ID(ID_AHA_2940AU_CN & ID_DEV_VENDOR_MASK),
57 ID(ID_AHA_2930C_VAR & ID_DEV_VENDOR_MASK),
59 ID(ID_AHA_2940),
60 ID(ID_AHA_3940),
61 ID(ID_AHA_398X),
[all …]
H A Daiclib.h163 ID(x), \
164 ID((x) | 0x0001000000000000ull), \
165 ID((x) | 0x0002000000000000ull), \
166 ID((x) | 0x0003000000000000ull), \
167 ID((x) | 0x0004000000000000ull), \
168 ID((x) | 0x0005000000000000ull), \
169 ID((x) | 0x0006000000000000ull), \
170 ID((x) | 0x0007000000000000ull), \
171 ID((x) | 0x0008000000000000ull), \
172 ID((x) | 0x0009000000000000ull), \
[all …]
H A Daic79xx_osm_pci.c48 #define ID(x) \ macro
54 ID(ID_AHA_29320A),
55 ID(ID_AHA_29320ALP),
56 ID(ID_AHA_29320LPE),
58 ID(ID_AHA_29320),
59 ID(ID_AHA_29320B),
60 ID(ID_AHA_29320LP),
61 ID(ID_AHA_39320),
62 ID(ID_AHA_39320_B),
63 ID(ID_AHA_39320A),
[all …]
/linux/rust/kernel/list/
H A Darc.rs33 pub trait ListArcSafe<const ID: u64 = 0> {
57 pub unsafe trait TryNewListArc<const ID: u64 = 0>: ListArcSafe<ID> {
163 pub struct ListArc<T, const ID: u64 = 0>
165 T: ListArcSafe<ID> + ?Sized,
170 impl<T: ListArcSafe<ID>, const ID: u64> ListArc<T, ID> {
202 impl<T, const ID: u64> From<UniqueArc<T>> for ListArc<T, ID>
204 T: ListArcSafe<ID> + ?Sized,
213 impl<T, const ID: u64> From<Pin<UniqueArc<T>>> for ListArc<T, ID>
215 T: ListArcSafe<ID> + ?Sized,
229 impl<T, const ID: u64> ListArc<T, ID>
[all …]
/linux/drivers/gpu/drm/i915/
H A Dintel_device_info.c127 #define ID(id) (id) macro
130 INTEL_HSW_ULT_GT1_IDS(ID),
131 INTEL_HSW_ULT_GT2_IDS(ID),
132 INTEL_HSW_ULT_GT3_IDS(ID),
133 INTEL_BDW_ULT_GT1_IDS(ID),
134 INTEL_BDW_ULT_GT2_IDS(ID),
135 INTEL_BDW_ULT_GT3_IDS(ID),
136 INTEL_BDW_ULT_RSVD_IDS(ID),
137 INTEL_SKL_ULT_GT1_IDS(ID),
138 INTEL_SKL_ULT_GT2_IDS(ID),
[all …]
/linux/drivers/pinctrl/cirrus/
H A Dpinctrl-lochnagar.c53 #define LN_PIN_GPIO(REV, ID, NAME, REG, SHIFT, INVERT) \ argument
54 static const struct lochnagar_pin lochnagar##REV##_##ID##_pin = { \
59 #define LN_PIN_SAIF(REV, ID, NAME) \ argument
60 static const struct lochnagar_pin lochnagar##REV##_##ID##_pin = \
63 #define LN_PIN_AIF(REV, ID) \ argument
64 LN_PIN_SAIF(REV, ID##_BCLK, LN_##ID##_STR"-bclk"); \
65 LN_PIN_SAIF(REV, ID##_LRCLK, LN_##ID##_STR"-lrclk"); \
66 LN_PIN_SAIF(REV, ID##_RXDAT, LN_##ID##_STR"-rxdat"); \
67 LN_PIN_SAIF(REV, ID##_TXDAT, LN_##ID##_STR"-txdat")
69 #define LN1_PIN_GPIO(ID, NAME, REG, SHIFT, INVERT) \ argument
[all …]
/linux/Documentation/translations/zh_CN/core-api/
H A Didr.rst18 ID分配
27 符、进程ID、网络协议中的数据包标识符、SCSI标记和设备实例编号。IDR和IDA为这个问题
28 提供了一个合理的解决方案，以避免每个人都自创。IDR提供将ID映射到指针的能力，而IDA
29 仅提供ID分配，因此内存效率更高。
39 您可以调用idr_alloc()来分配一个未使用的ID。通过调用idr_find()查询与该ID相关的指针，
40 并通过调用idr_remove()释放该ID。
42 如果需要更改与一个ID相关联的指针，可以调用idr_replace()。这样做的一个常见原因是通
43 过将 ``NULL`` 指针传递给分配函数来保留ID；用保留的ID初始化对象，最后将初始化的对
46 一些用户需要分配大于 ``INT_MAX`` 的ID。到目前为止，所有这些用户都满足 ``UINT_MAX``
47 的限制，他们使用idr_alloc_u32()。如果您需要超出u32的ID，我们将与您合作以满足您的
[all …]
/linux/drivers/char/agp/
H A Dvia-agp.c506 #define ID(x) \ macro
515 ID(PCI_DEVICE_ID_VIA_82C597_0),
516 ID(PCI_DEVICE_ID_VIA_82C598_0),
517 ID(PCI_DEVICE_ID_VIA_8501_0),
518 ID(PCI_DEVICE_ID_VIA_8601_0),
519 ID(PCI_DEVICE_ID_VIA_82C691_0),
520 ID(PCI_DEVICE_ID_VIA_8371_0),
521 ID(PCI_DEVICE_ID_VIA_8633_0),
522 ID(PCI_DEVICE_ID_VIA_XN266),
523 ID(PCI_DEVICE_ID_VIA_8361),
[all …]
H A Dintel-agp.c831 #define ID(x) \ macro
840 ID(PCI_DEVICE_ID_INTEL_82441), /* for HAS2 support */
841 ID(PCI_DEVICE_ID_INTEL_82443LX_0),
842 ID(PCI_DEVICE_ID_INTEL_82443BX_0),
843 ID(PCI_DEVICE_ID_INTEL_82443GX_0),
844 ID(PCI_DEVICE_ID_INTEL_82810_MC1),
845 ID(PCI_DEVICE_ID_INTEL_82810_MC3),
846 ID(PCI_DEVICE_ID_INTEL_82810E_MC),
847 ID(PCI_DEVICE_ID_INTEL_82815_MC),
848 ID(PCI_DEVICE_ID_INTEL_82820_HB),
[all …]
/linux/drivers/perf/
H A Dfsl_imx9_ddr_perf.c193 #define ID(counter, id) ((counter << COUNTER_OFFSET_IN_EVENT) | id) macro
237 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_riq_0, ID(1, 64)),
238 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_riq_1, ID(1, 65)),
239 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_riq_2, ID(1, 66)),
240 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_riq_3, ID(1, 67)),
241 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_riq_4, ID(1, 68)),
242 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_riq_5, ID(1, 69)),
243 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_riq_6, ID(1, 70)),
244 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_riq_7, ID(1, 71)),
247 IMX9_DDR_PMU_EVENT_ATTR(ddrc_ld_wiq_0, ID(2, 64)),
[all …]
/linux/tools/testing/selftests/net/can/
H A Dtest_raw_filter.c24 #define ID 0x123 macro
35 frame.can_id = ID; in send_can_frames()
39 frame.can_id = (ID | CAN_RTR_FLAG); in send_can_frames()
43 frame.can_id = (ID | CAN_EFF_FLAG); in send_can_frames()
47 frame.can_id = (ID | CAN_EFF_FLAG | CAN_RTR_FLAG); in send_can_frames()
107 .id = ID, in FIXTURE_VARIANT_ADD()
121 .id = ID | CAN_EFF_FLAG, in FIXTURE_VARIANT_ADD()
135 .id = ID | CAN_RTR_FLAG, in FIXTURE_VARIANT_ADD()
149 .id = ID | CAN_EFF_FLAG | CAN_RTR_FLAG, in FIXTURE_VARIANT_ADD()
163 .id = ID, in FIXTURE_VARIANT_ADD()
[all …]
/linux/drivers/staging/media/atomisp/pci/hive_isp_css_include/host/
H A Dcsi_rx_public.h23 const csi_rx_frontend_ID_t ID,
33 const csi_rx_frontend_ID_t ID,
44 const csi_rx_frontend_ID_t ID,
55 const csi_rx_backend_ID_t ID,
65 const csi_rx_backend_ID_t ID,
84 const csi_rx_frontend_ID_t ID,
96 const csi_rx_frontend_ID_t ID,
109 const csi_rx_backend_ID_t ID,
121 const csi_rx_backend_ID_t ID,
/linux/Documentation/virt/kvm/arm/
H A Dvcpu-features.rst19 ID registers.
21 The ID Registers
24 The Arm architecture specifies a range of *ID Registers* that describe the set
26 the guest's ID registers to the maximum set of CPU features supported by the
27 system. The ID register values may be VM-scoped in KVM, meaning that the
30 KVM allows userspace to *opt-out* of certain CPU features described by the ID
31 registers by writing values to them via the ``KVM_SET_ONE_REG`` ioctl. The ID
34 are mutable in the ID registers using the ``KVM_ARM_GET_REG_WRITABLE_MASKS``.
39 outlined by the architecture in DDI0487J.a D19.1.3 'Principles of the ID
40 scheme for fields in ID register'. KVM does not allow ID register values that
[all …]
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-cdx18 Vendor ID for this CDX device, in hexadecimal. Vendor ID is
20 Combination of Vendor ID and Device ID identifies a device.
26 Device ID for this CDX device, in hexadecimal. Device ID is
29 Combination of Vendor ID and Device ID identifies a device.
35 Subsystem Vendor ID for this CDX device, in hexadecimal.
36 Subsystem Vendor ID is 16 bit identifier specific to the
43 Subsystem Device ID for this CDX device, in hexadecimal
44 Subsystem Device ID is 16 bit identifier specific to the
112 This attribute indicates the CDX ID of the device.
117 - vXXXX contains the vendor ID;
[all …]
H A Dsysfs-class-rapidio7 subdirectories named as "rapidioN" where N = mport ID registered
10 NOTE: An mport ID is not a RapidIO destination ID assigned to a
21 0 = small (8-bit destination ID, max. 256 devices),
23 1 = large (16-bit destination ID, max. 65536 devices).
32 (RO) reports RapidIO destination ID assigned to the given
34 that no valid destination ID have been assigned to the mport
36 only fabric enumerating mports have a valid destination ID
H A Dsysfs-bus-event_source-devices-iommu17 event = "config:0-27" - event ID
18 event_group = "config:28-31" - event group ID
20 filter_requester_en = "config1:0" - Enable Requester ID filter
21 filter_domain_en = "config1:1" - Enable Domain ID filter
25 filter_requester_id = "config1:16-31" - Requester ID filter
26 filter_domain = "config1:32-47" - Domain ID filter
/linux/Documentation/pcmcia/
H A Ddevicetable.rst8 - manufactor ID
9 - card ID
10 - product ID strings _and_ hashes of these strings
11 - function ID
17 If you want to match product ID strings, you also need to pass the crc32
18 hashes of the string to the macro, e.g. if you want to match the product ID
26 You can determine the hash of the product ID strings by catting the file
31 The hex value after "pa" is the hash of product ID string 1, after "pb" for
/linux/Documentation/hwmon/
H A Docc.rst32 The OCC sensor ID is an integer that represents the unique identifier of the
34 DIMM slot in the system may have a sensor ID of 7. This mapping is unavailable
35 to the device driver, which must therefore export the sensor ID as-is.
42 OCC sensor ID.
74 OCC sensor ID.
89 OCC sensor ID.
94 OCC sensor ID + function ID + channel in the form
96 Both the function ID and channel are integers that
102 OCC sensor ID + sensor type in the form of a string,
105 For this sensor version, OCC sensor ID will be the same
[all …]
/linux/Documentation/driver-api/surface_aggregator/
H A Dssh.rst31 and defined in ACPI as device with ID ``MSHW0084``. On these devices,
72 - Sequence ID (see explanation below).
101 same sequence ID (|SEQ|), stored inside the frame (more on this in the next
102 section). The sequence ID is a wrapping counter.
145 the same sequence ID of the |DATA| frame. In other words, the sequence ID of
148 containing an |NAK|-type frame. As the sequence ID of the previous data
150 upon, the sequence ID of the |NAK| frame should not be used and is set to
156 corresponding to a single exchange thus relies on the sequence ID as well as
157 the type of the message, and the context. Specifically, the sequence ID is
168 where both frames have the same sequence ID (``SEQ``). Here, ``FRAME(D)``
[all …]
/linux/Documentation/arch/x86/
H A Dtopology.rst64 The physical ID of the die.
68 The physical ID of the package. This information is retrieved via CPUID
76 The logical ID of the package. As we do not trust BIOSes to enumerate the
78 ID so we can sanely calculate the number of maximum possible packages in
88 - On Intel, the first APIC ID of the list of CPUs sharing the Last Level
91 - On AMD, the Node ID or Core Complex ID containing the Last Level
127 The logical package ID to which a thread belongs.
131 The physical package ID to which a thread belongs.
135 The ID of the core to which a thread belongs. It is also printed in /proc/cpuinfo
140 The logical core ID to which a thread belongs.
[all …]
/linux/Documentation/wmi/devices/
H A Dalienware-wmi.rst81 ID 0xA0, the argument you would pass to the method is 0xA001.
93 | 0x01 | Get the number of temperature | - Byte 1: Fan ID |
94 | | sensors related with a fan ID | |
96 | 0x02 | Get the temperature sensor IDs | - Byte 1: Fan ID |
97 | | related to a fan sensor ID | - Byte 2: Index |
118 | 0x03 | List an ID or resource at a given | - Byte 1: Index |
128 | | **Returns:** ID at a given index | |
131 | | given temperature sensor. | ID |
133 | 0x05 | Get the current RPM for a given | - Byte 1: Fan ID |
136 | 0x06 | Get fan speed percentage. (not | - Byte 1: Fan ID |
[all …]
/linux/Documentation/core-api/
H A Didr.rst4 ID Allocation
17 provides the ability to map an ID to a pointer, while the IDA provides
18 only ID allocation, and as a result is much more memory-efficient.
30 You can call idr_alloc() to allocate an unused ID. Look up
31 the pointer you associated with the ID by calling idr_find()
32 and free the ID by calling idr_remove().
34 If you need to change the pointer associated with an ID, you can call
36 ID by passing a ``NULL`` pointer to the allocation function; initialise the
37 object with the reserved ID and finally insert the initialised object
63 If you need to take a lock while allocating a new ID from the IDR,
/linux/Documentation/wmi/
H A Dacpi-interface.rst15 Discovery of WMI objects is handled by defining ACPI devices with a PNP ID
32 0x10 2 2 character method ID or single byte notification ID.
37 The WMI object flags control whether the method or notification ID is used:
42 - 0x8: Data block describes a WMI event, use notification ID instead
43 of method ID.
46 The method/notification ID is used to construct the ACPI method names used for
54 are the method ID of the data block to query. Their single parameter is an
69 characters of the ACPI method name are the method ID of the data block
72 describing the WMI method ID to execute, and the third parameter is a buffer
81 the ACPI method are the notification ID of the data block describing the WMI
[all …]
/linux/arch/arm/boot/compressed/
H A Dhead-sharpsl.S36 mrc p15, 0, r4, c0, c0 @ Get Processor ID
54 ldr r6, [r1, #0] @ Load Chip ID
97 .word 0x69052d00 @ PXA255 Processor ID
99 .word 0x69054100 @ PXA270 Processor ID
101 .word 0x57411002 @ w100 Chip ID
103 .word 0x08010000 @ w100 Chip ID Reg Address
147 ldrb r2, [r1, #20] @ NAND Manufacturer ID
148 ldrb r3, [r1, #20] @ NAND Chip ID

12345678910>>...26