Home
last modified time | relevance | path

Searched full:object (Results 1 – 25 of 1188) sorted by relevance

12345678910>>...48

/Documentation/core-api/
Ddebug-objects.rst2 The object-lifetime debugging infrastructure
21 debugobjects is not changing the data structure of the real object so it
29 object type and add calls into the debug code at appropriate places. The
30 data structure to describe the object type needs at minimum the name of
31 the object type. Optional functions can and should be provided to fixup
53 Each of these functions takes the address of the real object and a
54 pointer to the object type specific debug description structure.
71 object is called.
73 When the real object is already tracked by debugobjects it is checked,
74 whether the object can be initialized. Initializing is not allowed for
[all …]
Dassoc_array.rst8 This associative array implementation is an object container with the following
19 permits an object to be located in multiple arrays simultaneously.
24 4. Index keys must be unique. Inserting an object with the same key as one
25 already in the array will replace the old object.
52 pack leaf object pointers into spare space in the node rather than making an
53 extra branch until as such time an object needs to be added to a full node.
105 this was for insertion, the new object is _not_ released by this function,
132 2. Get a chunk of an object's index key::
134 unsigned long (*get_object_key_chunk)(const void *object, int level);
136 As the previous function, but gets its data from an object in the array
[all …]
/Documentation/devicetree/bindings/nvmem/layouts/
Donie,tlv-layout.yaml29 type: object
33 type: object
37 type: object
41 type: object
53 type: object
57 type: object
61 type: object
65 type: object
69 type: object
73 type: object
[all …]
/Documentation/devicetree/bindings/mfd/
Dstericsson,ab8500.yaml53 type: object
66 type: object
82 type: object
102 type: object
128 type: object
159 type: object
182 type: object
187 type: object
192 type: object
197 type: object
[all …]
Dstericsson,db8500-prcmu.yaml64 type: object
73 type: object
79 type: object
85 type: object
91 type: object
98 type: object
105 type: object
112 type: object
118 type: object
126 type: object
[all …]
Dcirrus,lochnagar.yaml43 type: object
47 type: object
70 type: object
74 type: object
81 type: object
88 type: object
95 type: object
102 type: object
109 type: object
116 type: object
[all …]
Dqcom-pm8xxx.yaml48 type: object
52 type: object
56 type: object
60 type: object
64 type: object
68 type: object
72 type: object
76 type: object
Dqcom,spmi-pmic.yaml113 type: object
117 type: object
121 type: object
126 type: object
133 type: object
137 type: object
141 type: object
146 type: object
154 type: object
158 type: object
[all …]
/Documentation/devicetree/bindings/phy/
Dnvidia,tegra124-xusb-padctl.yaml90 type: object
94 type: object
106 type: object
110 type: object
122 type: object
134 type: object
146 type: object
150 type: object
154 type: object
166 type: object
[all …]
Dnvidia,tegra210-xusb-padctl.yaml88 type: object
92 type: object
104 type: object
108 type: object
120 type: object
132 type: object
144 type: object
156 type: object
168 type: object
172 type: object
[all …]
Dnvidia,tegra186-xusb-padctl.yaml93 type: object
97 type: object
109 type: object
113 type: object
125 type: object
137 type: object
149 type: object
161 type: object
165 type: object
177 type: object
[all …]
Dnvidia,tegra194-xusb-padctl.yaml88 type: object
92 type: object
104 type: object
108 type: object
120 type: object
132 type: object
144 type: object
156 type: object
160 type: object
164 type: object
[all …]
/Documentation/devicetree/bindings/iio/temperature/
Dmelexis,mlx90632.yaml17 measured object temperature is in range between -20 to 200 degrees
19 object temperature range for industrial applications. Since it can
27 Since measured object emissivity effects Infra Red energy emitted,
28 emissivity should be set before requesting the object temperature.
33 measured object temperature is in range between -20 to 100 degrees
35 object temperature range for industrial applications, while just 0.2
40 Since measured object emissivity effects Infra Red energy emitted,
41 emissivity should be set before requesting the object temperature.
/Documentation/gpu/
Ddrm-mm.rst37 TTM device object reference
52 TTM resource object reference
61 TTM TT object reference
108 Buffer object allocation is relatively straightforward and largely
110 object.
123 DRM Memory Manager object which provides an address space pool for
124 object allocation.
132 its own DRM MM object.
143 driver-specific GEM object structure type that embeds an instance of
146 To create a GEM object, a driver allocates memory for an instance of its
[all …]
Ddrm-vm-bind-locking.rst10 external / shared object mappings that is needed in the simplest
34 a GEM object or anonymous or page-cache pages mapped also into the CPU
36 * ``gpu_vm_bo``: Abstracts the association of a GEM object and
37 a VM. The GEM object maintains a list of gpu_vm_bos, where each gpu_vm_bo
48 * ``dma_resv``: A struct dma_resv (a.k.a reservation object) that is used
50 gpu_vm or a GEM object. The dma_resv contains an array / list
63 * ``local object``: A GEM object which is only mapped within a
65 * ``external object``: a.k.a shared object: A GEM object which may be shared
73 dma_resv object and hence the dma_resv lock. So, even with a huge
104 * The ``gem_object->gpuva_lock`` This lock protects the GEM object's
[all …]
/Documentation/ABI/testing/
Dsysfs-kernel-livepatch17 object (vmlinux or a module) in which it patched functions.
58 What: /sys/kernel/livepatch/<patch>/<object>
63 The object directory contains subdirectories for each function
64 that is patched within the object.
66 What: /sys/kernel/livepatch/<patch>/<object>/patched
71 An attribute which indicates whether the object is currently
74 What: /sys/kernel/livepatch/<patch>/<object>/<function,sympos>
84 name in kallsyms for the patched object.
Dsysfs-bus-acpi6 object associated with the device object. For example,
17 This attribute indicates the PNP IDs of the device object.
19 CCCCCCCC contains device object's PNPID (_HID or _CID).
26 device object. For example, PNP0103.
34 This attribute contains the output of the device object's
41 This attribute contains the output of the device object's
50 This attribute contains the output of the device object's
58 this device object. This file exists for every device
59 object that has _EJ0 method.
Dsysfs-firmware-sgi_uv56 a UV Hub visible to the BIOS. Each hub object's name is appended by a
59 Each hub object directory contains a number of read-only attributes::
94 Each hub object directory also contains a number of port objects,
96 A port object's name is appended by a unique ordinal value
99 Each port object directory contains a number of read-only attributes::
125 Each PCI bus object's name is appended by its PCI bus address.
128 Each pcibus object has a number of possible read-only attributes::
156 object type is 'PPB'.
159 number that the corresponding PCI bus object is connected to.
Dsysfs-class-devfreq-event7 The name of devfreq-event object denoted as 'event<x>' which
8 includes the unique number of 'x' for each devfreq-event object.
15 the name of the devfreq-event object. This attribute is
24 object. If the device is enabled, the value of attribute is
/Documentation/gpu/rfc/
Di915_small_bar.h98 * is immutable. Previously we would have two ioctls, one to create the object
105 * @size: Requested size for the object.
107 * The (page-aligned) allocated size for the object will be returned.
113 * extension to place the object in device local-memory. The kernel will
120 * @handle: Returned handle for the object.
122 * Object handles are nonzero.
132 * the object will need to be accessed via the CPU.
145 * if the object can't be allocated in the mappable part of
154 * I915_MEMORY_CLASS_DEVICE is preferred for this object. Note that the
155 * kernel can still migrate the object to the mappable part, as a last
[all …]
/Documentation/devicetree/bindings/sound/
Dnvidia,tegra210-ahub.yaml75 type: object
78 type: object
82 type: object
86 type: object
90 type: object
94 type: object
98 type: object
102 type: object
106 type: object
110 type: object
[all …]
/Documentation/RCU/
Drculist_nulls.rst26 struct object {
46 * Because a writer could delete object, and a writer could
47 * reuse these object before the RCU grace period, we
48 * must check key after getting the reference on object
50 if (obj->key != key) { // not the object we expected
88 "If the object is moved from one list to another list in-between the
90 object has moved to the end of a new list, the traversal will not
91 complete properly on the list it should have, since the object will
124 But thanks to SLAB_TYPESAFE_BY_RCU, beware a deleted object can be reused
147 a race (some writer did a delete and/or a move of an object
[all …]
/Documentation/devicetree/bindings/pinctrl/
Damlogic,meson-pinctrl-common.yaml33 type: object
46 type: object
59 type: object
61 type: object
/Documentation/firmware-guide/acpi/
Dnamespace.rst19 receiving ACPI hotplug notification events. For each device object
85 The following naming conventions apply to object names in the ACPI
200 ACPI namespace representation of the given object and 'instance' is used
201 for distinguishing different object of the same 'bus_id' (it is
204 The value of 'bus_id' depends on the type of the object whose name it is
208 | | Object/Feature | Table | bus_id |
241 The object's source is an ACPI namespace node (as indicated by the
242 named object's type in the second column). In that case the object's
246 The struct acpi_device object is created for a fixed hardware
251 The struct acpi_device object is created for an ACPI namespace node
[all …]
/Documentation/devicetree/bindings/arm/
Dvexpress-config.yaml28 type: object
46 type: object
64 type: object
82 type: object
107 type: object
162 type: object
183 type: object
204 type: object
222 type: object
243 type: object

12345678910>>...48