Home
last modified time | relevance | path

Searched full:flag (Results 1 – 25 of 807) sorted by relevance

12345678910>>...33

/Documentation/litmus-tests/locking/
DDCL-broken.litmus11 int flag;
15 P0(int *flag, int *data, spinlock_t *lck)
21 r0 = READ_ONCE(*flag);
24 r1 = READ_ONCE(*flag);
27 WRITE_ONCE(*flag, 1);
34 P1(int *flag, int *data, spinlock_t *lck)
40 r0 = READ_ONCE(*flag);
43 r1 = READ_ONCE(*flag);
46 WRITE_ONCE(*flag, 1);
53 locations [flag;data;0:r0;0:r1;1:r0;1:r1]
DDCL-fixed.litmus12 int flag;
16 P0(int *flag, int *data, spinlock_t *lck)
22 r0 = smp_load_acquire(flag);
25 r1 = READ_ONCE(*flag);
28 smp_store_release(flag, 1);
35 P1(int *flag, int *data, spinlock_t *lck)
41 r0 = smp_load_acquire(flag);
44 r1 = READ_ONCE(*flag);
47 smp_store_release(flag, 1);
54 locations [flag;data;0:r0;0:r1;1:r0;1:r1]
/Documentation/devicetree/bindings/mmc/
Dmmc-controller.yaml38 $ref: /schemas/types.yaml#/definitions/flag
48 $ref: /schemas/types.yaml#/definitions/flag
64 # using the GPIO_ACTIVE_LOW flag. This creates an ambiguity in the
67 # example leaving the GPIO_ACTIVE_LOW flag clear and specifying the
72 $ref: /schemas/types.yaml#/definitions/flag
77 $ref: /schemas/types.yaml#/definitions/flag
105 $ref: /schemas/types.yaml#/definitions/flag
125 $ref: /schemas/types.yaml#/definitions/flag
131 $ref: /schemas/types.yaml#/definitions/flag
136 $ref: /schemas/types.yaml#/definitions/flag
[all …]
/Documentation/userspace-api/media/v4l/
Dvidioc-enum-fmt.rst166 This flag can only be used in combination with the
167 ``V4L2_FMT_FLAG_COMPRESSED`` flag, since this applies to compressed
168 formats only. This flag is valid for stateful decoders only.
176 This flag can only be used in combination with the
177 ``V4L2_FMT_FLAG_COMPRESSED`` flag, since this applies to
178 compressed formats only. This flag is valid for stateful codecs only.
185 If this flag is set, then the ``CAPTURE`` coded frame interval can be
192 This flag can only be used in combination with the
193 ``V4L2_FMT_FLAG_COMPRESSED`` flag, since this applies to
194 compressed formats only. This flag is valid for stateful encoders only.
[all …]
Dbuffer.rst52 ``V4L2_CTRL_FLAG_MODIFY_LAYOUT`` flag.
58 ``V4L2_CTRL_FLAG_GRABBED`` flag when calling
76 allocation and the ``V4L2_CTRL_FLAG_GRABBED`` flag is cleared once the
85 allocated. After freeing all buffers the ``V4L2_CTRL_FLAG_GRABBED`` flag
216 - When the ``V4L2_BUF_FLAG_TIMECODE`` flag is set in ``flags``, this
293 - The file descriptor of the request to queue the buffer to. If the flag
295 queued to this request. If the flag is not set, then this field will
298 The ``V4L2_BUF_FLAG_REQUEST_FD`` flag and this field are only used by
461 * .. _`V4L2-BUF-FLAG-MAPPED`:
467 Drivers set or clear this flag when the
[all …]
Ddev-meta.rst24 ``V4L2_CAP_META_CAPTURE`` flag in the ``device_caps`` field of the
26 ioctl. That flag means the device can capture metadata to memory. Similarly,
28 ``V4L2_CAP_META_OUTPUT`` flag in the ``device_caps`` field of
29 :c:type:`v4l2_capability` structure. That flag means the device can read
51 ``V4L2_FMT_FLAG_META_LINE_BASED`` flag set for :c:func:`VIDIOC_ENUM_FMT`. Such
77 :c:type`v4l2_fmtdesc` flag ``V4L2_FMT_FLAG_META_LINE_BASED`` is set,
81 - Number of rows of metadata. Valid when :c:type`v4l2_fmtdesc` flag
87 when :c:type`v4l2_fmtdesc` flag ``V4L2_FMT_FLAG_META_LINE_BASED`` is
Dvidioc-g-dv-timings.rst63 ``V4L2_IN_CAP_DV_TIMINGS`` flag), then ``ENODATA`` error code is returned.
162 ``V4L2_DV_FL_HAS_PICTURE_ASPECT`` flag is set.
166 Only valid if the ``V4L2_DV_FL_HAS_CEA861_VIC`` flag is set.
170 Only valid if the ``V4L2_DV_FL_HAS_HDMI_VIC`` flag is set.
253 * - Flag
259 resolution over the same bandwidth. This is a read-only flag,
266 the transmitter can't generate such frequencies, then the flag
267 will also be cleared. This is a read-only flag, applications must
272 set. This flag is cleared otherwise. It is also only valid for
273 formats with the ``V4L2_DV_FL_CAN_REDUCE_FPS`` flag set, for other
[all …]
Dv4l2-selection-flags.rst19 .. flat-table:: Selection flag definitions
23 * - Flag name
33 flag (and ``V4L2_SEL_FLAG_LE``) the behaviour is to choose the
47 steps. If this flag is not given, the configuration is propagated
Ddev-rds.rst36 ``V4L2_CAP_RDS_CAPTURE`` flag in the ``capabilities`` field of struct
39 supports RDS will set the ``V4L2_TUNER_CAP_RDS`` flag in the
42 ``V4L2_TUNER_CAP_RDS_BLOCK_IO`` flag has to be set, see
43 :ref:`Reading RDS data <reading-rds-data>`. For future use the flag
55 flag in the ``capabilities`` field of struct
58 supports RDS will set the ``V4L2_TUNER_CAP_RDS`` flag in the
65 flag has to be set. If the tuner is capable of handling RDS entities
66 like program identification codes and radio text, the flag
/Documentation/devicetree/bindings/usb/
Dgeneric-ehci.yaml112 $ref: /schemas/types.yaml#/definitions/flag
114 Set this flag for HCDs with big endian descriptors and big
118 $ref: /schemas/types.yaml#/definitions/flag
120 Set this flag for HCDs with big endian descriptors.
123 $ref: /schemas/types.yaml#/definitions/flag
125 Set this flag for HCDs with big endian registers.
128 $ref: /schemas/types.yaml#/definitions/flag
130 Set this flag if EHCI has a Transaction Translator built into
134 $ref: /schemas/types.yaml#/definitions/flag
136 Set this flag to force EHCI reset after resume.
[all …]
Dusb251xb.yaml38 $ref: /schemas/types.yaml#/definitions/flag
81 $ref: /schemas/types.yaml#/definitions/flag
87 $ref: /schemas/types.yaml#/definitions/flag
93 $ref: /schemas/types.yaml#/definitions/flag
98 $ref: /schemas/types.yaml#/definitions/flag
104 $ref: /schemas/types.yaml#/definitions/flag
110 $ref: /schemas/types.yaml#/definitions/flag
115 $ref: /schemas/types.yaml#/definitions/flag
121 $ref: /schemas/types.yaml#/definitions/flag
127 $ref: /schemas/types.yaml#/definitions/flag
[all …]
Dgeneric-ohci.yaml85 $ref: /schemas/types.yaml#/definitions/flag
87 Set this flag for HCDs with big endian descriptors and big
91 $ref: /schemas/types.yaml#/definitions/flag
93 Set this flag for HCDs with big endian descriptors.
96 $ref: /schemas/types.yaml#/definitions/flag
98 Set this flag for HCDs with big endian registers.
101 $ref: /schemas/types.yaml#/definitions/flag
106 $ref: /schemas/types.yaml#/definitions/flag
/Documentation/devicetree/bindings/iio/frequency/
Dadi,adf4350.yaml58 $ref: /schemas/types.yaml#/definitions/flag
62 $ref: /schemas/types.yaml#/definitions/flag
66 $ref: /schemas/types.yaml#/definitions/flag
70 $ref: /schemas/types.yaml#/definitions/flag
74 $ref: /schemas/types.yaml#/definitions/flag
98 $ref: /schemas/types.yaml#/definitions/flag
102 $ref: /schemas/types.yaml#/definitions/flag
106 $ref: /schemas/types.yaml#/definitions/flag
111 $ref: /schemas/types.yaml#/definitions/flag
116 $ref: /schemas/types.yaml#/definitions/flag
[all …]
/Documentation/arch/x86/
Dcpuinfo.rst21 And even if it doesn't show a particular feature flag - although the CPU
27 Furthermore, those flag strings become an ABI the moment they appear
32 kernel has *enabled* and *supports*. As in: the CPUID feature flag is
39 they try to find the flag in /proc/cpuinfo. If a given flag is present,
47 * if the flag represents a hardware feature the hardware supports it.
49 The absence of a flag in /proc/cpuinfo by itself means almost nothing to
89 displayed accordingly in /proc/cpuinfo. For example, the flag "avx2"
114 "split_lock_detect" will be displayed. The flag "ring3mwait" will be
121 Isolation is purely software feature and its feature flag X86_FEATURE_PTI is
133 a: The name of the flag is from the string in X86_FEATURE_<name> by default.
[all …]
/Documentation/filesystems/
Ddax.rst43 1. There exists an in-kernel file access mode flag `S_DAX` that corresponds to
44 the statx flag `STATX_ATTR_DAX`. See the manpage for statx(2) for details
47 2. There exists a persistent flag `FS_XFLAG_DAX` that can be applied to regular
48 files and directories. This advisory flag can be set or cleared at any
51 3. If the persistent `FS_XFLAG_DAX` flag is set on a directory, this flag will
54 this flag is set or cleared on the parent directory are not modified by
58 setting of the `S_DAX` flag. Given underlying storage which supports `DAX` the
88 c) Changing the `FS_XFLAG_DAX` flag on existing regular files and
93 flag, the change to existing regular files won't take effect until the
101 and the other is a volatile flag indicating the active state of the feature
[all …]
Dfuse-io.rst14 The direct-io mode can be selected with the FOPEN_DIRECT_IO flag in the
19 mmap, the FUSE_DIRECT_IO_ALLOW_MMAP flag may be enabled in the FUSE_INIT reply.
27 writeback-cache mode may be selected by the FUSE_WRITEBACK_CACHE flag in the
35 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to
/Documentation/admin-guide/mm/
Didle_page_tracking.rst42 For huge pages the idle flag is set only on the head page, so one has to read
69 their idle flag cleared in the interim.
98 The idle memory tracking feature adds a new page flag, the Idle flag. This flag
108 more page flag is introduced, the Young flag. When the PTE Accessed bit is
109 cleared as a result of setting or updating a page's Idle flag, the Young flag
110 is set on the page. The reclaimer treats the Young flag as an extra PTE
/Documentation/block/
Dwriteback_cache_control.rst17 a forced cache flush, and the Force Unit Access (FUA) flag for requests.
23 The REQ_PREFLUSH flag can be OR ed into the r/w flags of a bio submitted from
27 storage before the flagged bio starts. In addition the REQ_PREFLUSH flag can be
36 The REQ_FUA flag can be OR ed into the r/w flags of a bio submitted from the
62 flag in the queue_limits feature field. For devices that also support the FUA
68 flag in the features field of the queue_limits structure.
74 the driver if the driver sets the BLK_FEAT_WRITE_CACHE flag and the driver
88 When the BLK_FEAT_WRITE_CACHE flag is set, REQ_OP_WRITE | REQ_PREFLUSH requests
/Documentation/devicetree/bindings/serial/
Drs485.yaml33 $ref: /schemas/types.yaml#/definitions/flag
37 $ref: /schemas/types.yaml#/definitions/flag
42 $ref: /schemas/types.yaml#/definitions/flag
47 $ref: /schemas/types.yaml#/definitions/flag
51 $ref: /schemas/types.yaml#/definitions/flag
/Documentation/ABI/testing/
Dconfigfs-usb-gadget-mass-storage25 ro Flag specifying access to the LUN shall be
29 removable Flag specifying that LUN shall be indicated as
31 cdrom Flag specifying that LUN shall be reported as
33 nofua Flag specifying that FUA flag
/Documentation/i2c/
Dsmbus-protocol.rst27 Each transaction type corresponds to a functionality flag. Before calling a
29 the corresponding functionality flag to ensure that the underlying I2C
64 Functionality flag: I2C_FUNC_SMBUS_QUICK
79 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE
94 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE
107 Functionality flag: I2C_FUNC_SMBUS_READ_BYTE_DATA
121 Functionality flag: I2C_FUNC_SMBUS_READ_WORD_DATA
141 Functionality flag: I2C_FUNC_SMBUS_WRITE_BYTE_DATA
155 Functionality flag: I2C_FUNC_SMBUS_WRITE_WORD_DATA
171 Functionality flag: I2C_FUNC_SMBUS_PROC_CALL
[all …]
/Documentation/devicetree/bindings/sound/
Dawinic,aw88395.yaml41 awinic,sync-flag:
43 Flag bit used to keep the phase synchronized in the case of multiple PA
44 $ref: /schemas/types.yaml#/definitions/flag
78 awinic,sync-flag;
/Documentation/devicetree/bindings/net/
Dethernet-phy.yaml90 $ref: /schemas/types.yaml#/definitions/flag
97 $ref: /schemas/types.yaml#/definitions/flag
111 $ref: /schemas/types.yaml#/definitions/flag
118 $ref: /schemas/types.yaml#/definitions/flag
126 $ref: /schemas/types.yaml#/definitions/flag
132 $ref: /schemas/types.yaml#/definitions/flag
138 $ref: /schemas/types.yaml#/definitions/flag
144 $ref: /schemas/types.yaml#/definitions/flag
150 $ref: /schemas/types.yaml#/definitions/flag
156 $ref: /schemas/types.yaml#/definitions/flag
[all …]
/Documentation/networking/
Dmsg_zerocopy.rst9 The MSG_ZEROCOPY flag enables copy avoidance for socket send calls.
19 such as sendfile and splice. The MSG_ZEROCOPY flag extends the
36 trivial as just passing the flag, then.
60 Passing the MSG_ZEROCOPY flag is the most obvious step to enable copy
69 this flag, a process must first signal intent by setting a socket option:
80 Pass the new flag.
96 feature is implemented as a flag. It is safe to mix calls with the flag
123 POLLERR in its output flags. That flag does not have to be set in the
211 Passing flag MSG_ZEROCOPY is a hint to the kernel to apply copy
230 setting flag SO_EE_CODE_ZEROCOPY_COPIED in field ee_code on return.
[all …]
/Documentation/devicetree/bindings/spi/
Dspi-controller.yaml45 The second flag of a gpio descriptor can be GPIO_ACTIVE_HIGH (0)
48 There is a special rule set for combining the second flag of an
49 cs-gpio with the optional spi-cs-high flag for SPI slaves.
93 $ref: /schemas/types.yaml#/definitions/flag
116 $ref: /schemas/types.yaml#/definitions/flag
121 $ref: /schemas/types.yaml#/definitions/flag
126 $ref: /schemas/types.yaml#/definitions/flag

12345678910>>...33