Searched full:fields (Results 1 – 25 of 375) sorted by relevance
12345678910>>...15
| /Documentation/accounting/ |
| D | taskstats-struct.rst | 5 This document contains an explanation of the struct taskstats fields.
7 There are three different groups of fields in the struct taskstats:
9 1) Common and basic accounting fields
11 the common fields and basic accounting fields are collected for
13 2) Delay accounting fields
14 These fields are placed between::
16 /* Delay accounting fields start */
20 /* Delay accounting fields end */
23 3) Extended accounting fields
24 These fields are placed between::
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | field-order.rst | 18 Interlaced video divides an image into two fields, containing only the
21 fields a cathode ray TV displays the lines interleaved, yielding the
24 fields reduces the flicker without the necessity of doubling the frame
28 at a time, merely transmitting the frames separated into fields. The
29 fields are in fact captured at two different instances in time. An
35 interleaved, it is also important applications understand how the fields
37 even) fields, the *spatial order*: The first line of the top field is
41 However because fields were captured one after the other, arguing
43 two successive top and bottom, or bottom and top fields yield a valid
45 transferring film to video, two fields may come from the same frame,
[all …]
|
| D | pixfmt-v4l2.rst | 35 * - :cspan:`2` Applications set these fields to request an image
44 inside the stream, when fed to a stateful mem2mem decoder, the fields
59 capture or output only the top or bottom field, or both fields
62 For more details on fields see :ref:`field-order`.
117 - This field indicates whether the remaining fields of the
119 extended fields, are valid. When set to
120 ``V4L2_PIX_FMT_PRIV_MAGIC``, it indicates that the extended fields
122 indicates that the extended fields contain undefined values.
124 Applications that wish to use the pixel format extended fields
128 fields are not supported and using the extended fields will lead
[all …]
|
| D | pixfmt-meta-d4xx.rst | 37 where all fields are in little endian order:
56 version xxx. The version number will be incremented when new fields are
91 version xxx. The version number will be incremented when new fields are
114 version xxx. The version number will be incremented when new fields are
141 [2] Depth Control flags specify which fields are valid: ::
153 [3] Capture Timing flags specify which fields are valid: ::
164 [4] Configuration flags specify which fields are valid: ::
|
| D | pixfmt-meta-uvc.rst | 36 Each individual block contains the following fields:
56 - Flags, indicating presence of other standard UVC fields
58 - The rest of the header, possibly including UVC PTS and SCR fields
|
| D | dev-raw-vbi.rst | 88 fields of the struct :c:type:`v4l2_vbi_format`
176 fields, are invalid and shall not be returned by the driver.
178 To initialize the ``start`` and ``count`` fields, applications
205 between fields. Normally the VBI image stores the first field
209 fields are still in correct temporal order with the older field
218 two fields are interlaced (cf. ``V4L2_FIELD_INTERLACED``). The
223 fields for VBI capturing at the same time. For simplicity setting
267 consisting of two fields of VBI images immediately following in memory.
301 Most VBI services transmit on both fields, but some have different
|
| /Documentation/security/ |
| D | lsm.rst | 31 operations on kernel objects and a set of opaque security fields in
61 The LSM kernel patch adds security fields to kernel data structures and
63 manage the security fields and to perform access control. It also adds
68 The LSM security fields are simply ``void*`` pointers. For process and
69 program execution security information, security fields were added to
74 information, security fields were added to :c:type:`struct inode
76 network device security information, security fields were added to
79 security fields were added to :c:type:`struct kern_ipc_perm
142 categories: hooks that are used to manage the security fields and hooks
170 move the capability-related fields from the kernel data structures into
[all …]
|
| D | IMA-templates.rst | 36 by translating the format into an array of template fields structures taken
47 fields associated to the chosen template descriptor and store the result
53 method for each item of the array of template fields structures.
57 Supported Template Fields and Descriptors
60 In the following, there is the list of supported template fields
|
| /Documentation/ABI/testing/ |
| D | procfs-smaps_rollup | 10 fields from all the maps in /proc/pid/smaps.
11 Additionally, the fields Pss_Anon, Pss_File and Pss_Shmem
12 are not present in /proc/pid/smaps. These fields represent
|
| D | procfs-diskstats | 7 fields:
24 Kernel 4.18+ appends four more fields for discard
|
| /Documentation/fb/ |
| D | api.rst | 52 bits_per_pixel, grayscale, red, green, blue and transp fields.
120 information red, green, blue and transp fields.
137 information red, green, blue and transp fields.
228 fields they care about.
248 blue, green and transp fields must be set to 0 by applications and ignored by
253 red, blue, green and transp fields must be set to 0 by applications and
258 to zero, and the red, blue, green and transp fields to describe the layout of
271 length fields. Offset are computed from the right.
278 type, visual and line_length fields depending on the selected format.
300 The red, green, blue and transp fields are not used with the FOURCC-based API.
[all …]
|
| /Documentation/hid/ |
| D | hid-sensor.rst | 16 and also the individual data fields. Each sensor can have variable number of
17 data fields. The length and order is specified in the report descriptor. For
36 This accelerometer-3D has some fields. Here for example field 2 is motion intensity
38 order of fields and length of each field is important as the input event raw
46 data fields. It is difficult to have a common input event to user space applications,
76 the report and get the indexes of the fields and also can get events. This driver
88 int (*capture_sample)(..): Capture a sample for one of its data fields
90 multiple data fields.
117 so that fields can be set or get individually.
210 Here there is a custom sensors with four fields, two feature and two inputs.
[all …]
|
| /Documentation/pcmcia/ |
| D | locking.rst | 69 The "main" struct pcmcia_socket is protected as follows (read-only fields
70 or single-use fields not mentioned):
112 The "main" struct pcmcia_device is protected as follows (read-only fields
113 or single-use fields not mentioned):
|
| /Documentation/filesystems/ext4/ |
| D | about.rst | 9 and the fields will be shorter.
35 When referenced in ``preformatted text`` blocks, ``sb`` refers to fields
36 in the super block, and ``inode`` refers to fields in an inode table
|
| D | overview.rst | 15 All fields in ext4 are written to disk in little-endian order. HOWEVER,
16 all fields in jbd2 (the journal) are written to disk in big-endian
|
| /Documentation/admin-guide/ |
| D | iostats.rst | 2 I/O statistics fields
9 tools, the fields are explained here.
11 In 2.4 now, the information is found as additional fields in
46 In 2.4, the statistics fields are those after the device name. In
49 find just the eleven fields, beginning with 446216. If you look at
50 ``/proc/diskstats``, the eleven fields will be preceded by the major and
52 eleven fields of statistics, each meaning exactly the same things.
53 All fields except field 9 are cumulative since boot. Field 9 should
145 partitions from that for disks. There are only *four* fields available
|
| /Documentation/driver-api/driver-model/ |
| D | porting.rst | 21 be embedded in larger, bus-specific objects. Fields in these generic
22 objects can replace fields in the bus-specific objects.
129 things to initialize are the bus_id, parent, and bus fields.
154 fields.
247 initialize the necessary fields of the driver: the name and bus
248 fields.
311 /* initialize common driver fields */
323 Ideally, the bus should only initialize the fields if they are not
402 The generic bus, device, and driver structures provide several fields
441 - Device and driver fields.
[all …]
|
| D | driver.rst | 19 The driver must initialize at least the name and bus fields. It should
44 bus-specific fields that cannot be generalized.
60 A definition that included bus-specific fields would look like
86 no bus-specific fields (i.e. don't have a bus-specific driver
94 possible. Registration with the core initializes several fields in the
96 lock. These fields are assumed to be valid at all times and may be
105 let the bus wrapper fill in the fields. For the callbacks, the bus can
118 Once the object has been registered, it may access the common fields of
|
| D | overview.rst | 41 Common data fields have been moved out of individual bus layers into a common
42 data structure. These fields must still be accessed by the bus layers,
63 The PCI bus layer freely accesses the fields of struct device. It knows about
66 driver model generally do not and should not touch the fields of struct device,
|
| /Documentation/devicetree/bindings/ata/ |
| D | ahci-ceva.txt | 10 The fields for the above parameter must be as shown below:
18 The fields for the above parameter must be as shown below:
26 The fields for the above parameter must be as shown below:
34 The fields for the above parameter must be as shown below:
|
| /Documentation/powerpc/ |
| D | cxl.rst | 215 Indicates which optional fields in the structure are
239 reserved fields:
333 These flags indicate which optional fields are present
334 in this struct. Currently all fields are mandatory.
357 These flags indicate which optional fields are present in
358 this struct. Currently all fields are mandatory.
371 reserved fields:
387 These flags indicate which optional fields are present in
388 this struct. Currently all fields are Mandatory.
393 reserved fields:
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 135 two fields specify the major and minor number of the device and
141 two fields specify the major and minor number of the device and
148 or async. First two fields specify the major and minor number of the
155 or async. First two fields specify the major and minor number of the
168 the type of operation - read or write, sync or async. First two fields
184 read or write, sync or async. First two fields specify the major and
236 from service tree of the device. First two fields specify the major
281 or async. First two fields specify the major and minor number of the
288 or async. First two fields specify the major and minor number of the
|
| /Documentation/arm/samsung/ |
| D | clksrc-change-registers.awk | 72 splitdefine(line, fields)
73 name = fields[0]
76 dmask[name,0] = find_length(fields[1])
77 dmask[name,1] = find_shift(fields[1])
|
| /Documentation/sound/designs/ |
| D | tracepoints.rst | 155 The first three fields are common. They represent name of ALSA PCM character
157 field for rules of constraint consists of two sub-fields; index of applied rule
162 fields are different according to type of the parameter. For parameters of mask
163 type, the fields represent hexadecimal dump of content of the parameter. For
164 parameters of interval type, the fields represent values of each member of
|
| /Documentation/input/ |
| D | input-programming.rst | 196 input_register_device, you have to fill additional fields in the input_dev
229 The id* and name fields
236 The id* fields contain the bus ID (PCI, USB, ...), vendor ID and device ID
238 are defined in pci_ids.h, usb_ids.h and similar include files. These fields
244 The id and name fields can be passed to userland via the evdev interface.
246 The keycode, keycodemax, keycodesize fields
249 These three fields should be used by input devices that have dense keymaps.
256 When a device has all 3 aforementioned fields filled in, the driver may
|
12345678910>>...15