| /linux/Documentation/devicetree/bindings/iio/adc/ |
| A D | adi,ad7606.yaml | 47 input channels. As the line is active high, it should be marked
55 it should be marked GPIO_ACTIVE_HIGH.
62 Shutdown mode. As the line is active low, it should be marked
71 As the line is active high, it should be marked GPIO_ACTIVE_HIGH.
80 is ±5V for all channels. As the line is active high, it should be marked
87 mode pins. As the line is active high, it should be marked
|
| A D | adi,ad7780.yaml | 47 line is active high, it should be marked GPIO_ACTIVE_HIGH.
54 driver probe. As the line is active low, it should be marked
63 marked GPIO_ACTIVE_LOW.
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-driver-aspeed-uart-routing | 8 selected option marked by brackets "[]". The list of available options
25 will be marked by brackets "[]".
|
| /linux/lib/ |
| A D | Kconfig.kcsan | 212 writes up to word size: conflicts between marked reads and plain
218 bool "Do not instrument marked atomic accesses"
221 Never instrument marked atomic accesses. This option can be used for
222 additional filtering. Conflicting marked atomic reads and plain
224 plain reads and marked writes to result in "unknown origin" reports.
226 races where at least one access is marked atomic will never be
230 accesses, conflicting marked atomic reads and plain writes will not
|
| /linux/Documentation/filesystems/ |
| A D | ntfs3.rst | 33 this table marked with no it means default is without **no**.
76 will be marked as system immutable files.
84 - Forces the driver to mount partitions even if volume is marked dirty.
|
| A D | automount-support.rst | 89 mountpoint will not be marked for expiration or unmounted.
91 If the mountpoint was not already marked for expiry at that time, an EAGAIN
94 Otherwise if it was already marked and it wasn't referenced, unmounting will
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| A D | media-ioc-setup-link.rst | 41 enable/disable a link. Links marked with the ``IMMUTABLE`` link flag can
48 Only links marked with the ``DYNAMIC`` link flag can be enabled/disabled
|
| /linux/security/yama/ |
| A D | yama_lsm.c | 183 bool marked = false; in yama_ptracer_del() local
192 marked = true; in yama_ptracer_del()
197 if (marked) in yama_ptracer_del()
|
| /linux/Documentation/admin-guide/mm/ |
| A D | idle_page_tracking.rst | 32 A page is considered idle if it has not been accessed since it was marked idle
86 set, or marked accessed explicitly by the kernel (see mark_page_accessed()). The
99 exceeding the dirty memory limit, it is not marked referenced.
107 When a page is marked idle, the Accessed bit must be cleared in all PTEs it is
|
| /linux/drivers/staging/pi433/ |
| A D | TODO | 5 * Some missing data (marked with ###) needs to be added in the documentation
|
| /linux/Documentation/admin-guide/ |
| A D | abi-obsolete.rst | 5 marked to be removed at some later point in time.
|
| A D | abi-testing.rst | 13 be marked stable.
|
| /linux/tools/memory-model/Documentation/ |
| A D | access-marking.txt | 67 2. Data-racy reads whose values are checked against marked reload.
104 fed into some operation that checks the full value against a later marked
211 It is important to comment marked accesses so that people reading your
222 if that concurrent access is marked with READ_ONCE(). In addition,
226 write is marked with data_race() or WRITE_ONCE().
297 this function can be marked __no_kcsan and the data_race() can be dropped:
343 Because foo is read locklessly, all accesses are marked. The purpose
464 Because foo is accessed locklessly, all accesses are marked. It does
513 flag buggy concurrent writes, even if: (1) Those writes are marked or
|
| /linux/Documentation/devicetree/bindings/media/i2c/ |
| A D | ovti,ov02a10.yaml | 60 to be active, it should be marked GPIO_ACTIVE_HIGH.
68 marked GPIO_ACTIVE_LOW.
|
| /linux/net/sched/ |
| A D | sch_sfb.c | 79 u32 marked; /* ECN mark */ member
394 q->stats.marked++; in sfb_enqueue()
603 .marked = q->stats.marked, in sfb_dump_stats()
|
| /linux/Documentation/dev-tools/ |
| A D | kcsan.rst | 206 KCSAN is aware of *marked atomic operations* (``READ_ONCE``, ``WRITE_ONCE``,
264 To detect data races between plain and marked accesses, KCSAN also annotates
265 marked accesses, but only to check if a watchpoint exists; i.e. KCSAN never
266 sets up a watchpoint on marked accesses. By never setting up watchpoints for
267 marked operations, if all accesses to a variable that is accessed concurrently
268 are properly marked, KCSAN will never trigger a watchpoint and therefore never
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| A D | multihit.rst | 113 the page is broken down into 4K pages, which are then marked executable.
135 pages in the EPT are marked as non-executable.
137 broken down into 4K pages, which are then marked executable.
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| A D | i2c-pca-platform.txt | 16 is active low, it should be marked GPIO_ACTIVE_LOW.
|
| /linux/Documentation/livepatch/ |
| A D | module-elf-format.rst | 110 Livepatch relocation sections must be marked with the SHF_RELA_LIVEPATCH
113 at patch module load time. These sections must also be marked with SHF_ALLOC,
166 characteristics. Notice that they are marked SHF_ALLOC ("A") so that they will
204 Livepatch symbols must be marked with SHN_LIVEPATCH so that the module
237 Livepatch symbols must have their section index marked as SHN_LIVEPATCH, so
|
| /linux/Documentation/networking/device_drivers/ethernet/toshiba/ |
| A D | spider_net.rst | 37 buffers. These are all marked "empty", ready to receive data. This
47 flowing RX traffic, every descr behind it should be marked "full",
157 marked xa... which is "empty". Thus, from the OS point of view, there
163 The HW pointer is at descr 0. This descr is marked 0x4.. or "full".
165 halted processing. Notice that descrs 0 through 254 are all marked
|
| /linux/Documentation/driver-api/ |
| A D | mtdnand.rst | 26 struct member has a short description which is marked with an [XXX]
33 The functions are marked with [XXX] identifiers in the short comment.
67 The struct members are marked with [XXX] identifiers in the comment. The
478 AG-AND chips this is mandatory, as they have no factory marked bad
479 blocks. They have factory marked good blocks. The marker pattern is
547 marked and identified by a pattern which is stored in the spare area
564 to be marked bad due to wear. The MTD interface function
577 about the one worn out block which should be marked bad. The version
957 developer. Each struct member has a short description which is marked
980 marked with an [XXX] identifier. See the chapter "Documentation hints"
[all …]
|
| /linux/Documentation/devicetree/bindings/spi/ |
| A D | spi-clps711x.txt | 14 which is assumed to be in the same device tree, with and marked
|
| /linux/tools/include/uapi/linux/ |
| A D | pkt_sched.h | 280 __u32 marked; /* Marked packets */ member
380 __u32 marked; /* Marked packets */ member
757 __u32 marked; member
|
| /linux/Documentation/devicetree/bindings/regmap/ |
| A D | regmap.txt | 14 be marked that way in the devicetree.
|
| /linux/Documentation/devicetree/bindings/iio/dac/ |
| A D | adi,ad5766.yaml | 37 should be marked GPIO_ACTIVE_LOW.
|