| /linux-5.10/Documentation/driver-api/media/ |
| D | v4l2-videobuf.rst | 80 along with a list_head for the queue of available buffers. There will also
103 parameter will be a suggested number of buffers to use; the driver should
110 Each buffer (in the form of a struct videobuf_buffer pointer) will be
120 Among other things, this call will usually allocate memory for the buffer.
127 held; if it tries to acquire it as well things will come to a screeching
201 device (cameras will use V4L2_BUF_TYPE_VIDEO_CAPTURE, for example), field
225 Either one of these functions will read frame data into data, returning the
226 amount actually read; the difference is that videobuf_read_one() will only
227 read a single frame, while videobuf_read_stream() will read multiple frames
229 typical driver read() implementation will start the capture engine, call
[all …]
|
| /linux-5.10/Documentation/core-api/ |
| D | cachetlb.rst | 28 Therefore when software page table changes occur, the kernel will
35 any previous page table modification whatsoever will be
46 'mm' will be visible to the cpu. That is, after running,
47 there will be no entries in the TLB for 'mm'.
60 'start' to 'end-1' will be visible to the cpu. That is, after
61 running, there will be no entries in the TLB for 'mm' for
85 user virtual address 'addr' will be visible to the cpu. That
86 is, after running, there will be no entries in the TLB for
106 the sequence will be in one of the following forms::
120 The cache level flush will always be first, because this allows
[all …]
|
| /linux-5.10/drivers/platform/x86/ |
| D | Kconfig | 15 If you say N, all options in this submenu will be skipped and disabled.
49 To compile this driver as a module, choose M here: the module will
79 will be called huawei-wmi.
88 To compile this driver as a module, choose M here: the module will
100 To compile this driver as a module, choose M here: the module will
124 To compile this driver as a module, choose M here: the module will
140 in the same node directory will tell you if it is "acerhdf".
159 If you choose to compile this driver as a module the module will be
233 If you choose to compile this driver as a module the module will be
253 To compile this driver as a module, choose M here: the module will
[all …]
|
| /linux-5.10/Documentation/driver-api/usb/ |
| D | power-management.rst | 41 document will not discuss those other forms.)
77 LAN"; we will refer to it generically as "remote wakeup". When a
111 kernel will automatically resume the device (autoresume). For the
112 same reason, an autosuspended device will usually have remote wakeup
142 ``control`` file. In 2.6.38 the ``autosuspend`` file will be deprecated
154 whether or not remote wakeup will be enabled when the
181 before the kernel will autosuspend it (the idle-delay
233 then each new USB device will have its autosuspend idle-delay
235 will not be affected.)
237 Setting the initial default idle-delay to -1 will prevent any
[all …]
|
| /linux-5.10/Documentation/filesystems/ |
| D | overlayfs.rst | 21 In many cases, an object accessed in the union will be indistinguishable
25 While directories will report an st_dev from the overlay-filesystem,
27 upper filesystem that is providing the object. Similarly st_ino will
30 tools ignore these values and will not be affected.
33 filesystem, all objects will report an st_dev from the overlay
34 filesystem and st_ino from the underlying filesystem. This will
36 overlay objects will be distinguishable from the corresponding
46 will use the high inode number bits for fsid. Even when the underlying
52 filesystem will fall back to the non xino behavior for that inode.
102 overlayfs. The upper filesystem will normally be writable and if it
[all …]
|
| D | autofs.rst | 21 in that data base at the time of access will be used to provide
32 and mounts filesystems. This will often be the "automount" program,
93 "`stat`" will (normally) cause the `d_op->d_automount()` dentry operation
102 everything is ready. It will then return "`NULL`" indicating that the
121 directory, d_manage() will be called with the `rcu_walk` parameter set
168 will be set.
175 RCU-walk will never call `->d_automount`; the filesystems must already
189 mounted, it *will* fall back to REF-walk. `d_manage()` cannot make the
197 autofs will return `-ECHILD` if an expiry of the filesystem has been
214 the `umount` system call. Unmounting with MNT_EXPIRE will fail unless
[all …]
|
| /linux-5.10/Documentation/powerpc/ |
| D | firmware-assisted-dump.rst | 49 - When system crashes, the Power firmware will copy the registered
51 It will also save hardware PTE's.
57 size will be the larger of 5% of system RAM or 256MB.
59 through boot parameter 'crashkernel=' which will override
64 offset is provided in crashkernel= parameter, it will be
69 firmware will reset PCI and other hardware state. It will
70 *not* clear the RAM. It will then launch the bootloader, as
73 - The freshly booted kernel will notice that there is a new node
77 the early boot OS will reserve rest of the memory above
79 size. This will make sure that this kernel (also, referred
[all …]
|
| /linux-5.10/include/misc/ |
| D | cxl.h | 45 * used as a default kernel context. cxl_get_context() will get this
46 * context. This context will be released by PCI hot unplug, so doesn't need to
59 * The AFU can be reset (cxl_afu_reset()). This will cause the PSL/AFU
65 * On pci_enabled_device(), the cxl driver will init a single cxl context for
66 * use by the driver. It doesn't start this context (as that will likely
70 * doesn't need to be released as this will be done by the PCI subsystem on hot
92 * Allocate AFU interrupts for this context. num=0 will allocate the default
104 * is private data is that will be provided to the interrupt handler.
113 * task. task == NULL will make it a kernel context.
166 * ops to that file descriptor. If the file ops are blank, the cxl driver will
[all …]
|
| /linux-5.10/tools/testing/ktest/examples/include/ |
| D | bisect.conf | 7 # variable that will tell this config what test to run.
35 # set to 1 will check both that the good commit works and the bad
48 # build or boot fails, ktest.pl will do a 'git bisect skip'.
54 # Set BISECT_REPLAY to /tmp/replay and ktest.pl will run the
59 # By setting BISECT_START to a new commit. ktest.pl will checkout
65 # set BISECT_MANUAL to 1. This will cause ktest.pl not to decide
66 # if the commit was good or bad. Instead, it will ask you to tell
70 # ktest if you think it was good or not and ktest.pl will continue
76 # Currently (which hopefully will be fixed soon), the bad config
80 # fails because of a lack of a config, then it will not find
|
| /linux-5.10/Documentation/virt/uml/ |
| D | user_mode_linux_howto_v2.rst | 46 QEMU which we will cover later in this document.
110 This will create a 16G disk image. The OS will initially allocate only one
111 block and will allocate more as they are written by UML. As of kernel
114 or by running ``tune2fs -o discard /dev/ubdXX`` will request UML to
122 jfs, etc will work too.
142 will be empty and it needs an entry for the root file system::
146 The image hostname will be set to the same as the host on which you
156 Depending on which one is in use, ``/etc/network/interfaces`` will
282 amount of packets UML will attempt to read or write in a single
291 which is being configured. In most cases it will enable TCP segmentation and
[all …]
|
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-edac | 4 Description: This write-only control file will zero all the statistical
6 Zeroing the counters will also reset the timer indicating how
36 panic_on_ue is set, this counter will not have a chance to
37 increment, since EDAC will panic the system
72 The rate will be translated to an internal value that gives at
74 Reading the file will return the actual scrubbing rate employed.
76 the value of the attribute file will be -1.
90 Description: This attribute file will display the size of dimm or rank.
101 Description: This attribute file will display what type of DRAM device is
108 Description: This attribute file will display what type of Error detection
[all …]
|
| /linux-5.10/drivers/net/ethernet/amd/ |
| D | Kconfig | 17 the kernel: saying N will just cause the configurator to skip all
18 the questions regarding AMD chipsets. If you say Y, you will be asked
32 will be called a2065.
44 will be called amd8111e.
54 will be called lance. This is recommended.
66 will be called pcnet32.
76 will be called ariadne.
137 To compile this driver as a module, choose M here: the module will be
147 will be called ni65.
173 will be called sunlance.
[all …]
|
| /linux-5.10/arch/mips/include/asm/octeon/ |
| D | cvmx-fau.h | 13 * This file is distributed in the hope that it will be useful, but
57 * bit will be set. Otherwise the value of the register before
58 * the update will be returned.
67 * bit will be set. Otherwise the value of the register before
68 * the update will be returned.
77 * bit will be set. Otherwise the value of the register before
78 * the update will be returned.
87 * bit will be set. Otherwise the value of the register before
88 * the update will be returned.
97 * the error bit will be set. Otherwise the value of the
[all …]
|
| /linux-5.10/Documentation/networking/ |
| D | rds.rst | 11 and will hopefully help you find your way around the code.
49 socket. The next section will cover the details. At any rate,
58 does not change. RDS will tolerate IPs moving around (eg in
87 This is a soft limit rather than a hard limit - RDS will
89 takes the queue length over the limit. However, it will also
100 Sends a message to the indicated recipient. The kernel will
104 An attempt to send a message that exceeds SO_SNDSIZE will
108 of queued bytes over the SO_SNDSIZE threshold will return
112 as "congested" will return ENOBUFS.
136 to any destination, RDS will always signal POLLOUT as long as
[all …]
|
| /linux-5.10/drivers/net/ |
| D | Kconfig | 57 will be called bonding.
72 will be called dummy.
110 This will write log messages for handshake and other events
111 that occur for a WireGuard interface. It will also perform some
134 will be called eql. If unsure, say N.
157 will be called ifb. If you want to use more than one ifb
159 Instead of 'ifb', the devices will then be called 'ifb0',
177 will be called macvlan.
191 will be called macvtap.
205 and packets will be delivered based on the dest L3 (IPv6/IPv4 addr)
[all …]
|
| /linux-5.10/kernel/power/ |
| D | Kconfig | 58 ACPI will be used for the final steps when it is available. One
68 Note, however, that fsck will be run on your filesystems and you will
79 will get corrupted in a nasty way.
101 to-disk implementation will look for a suspended disk image.
103 The partition specified here will be different for almost every user.
111 which will set the resume partition to the device specified.
114 suspended image to. It will simply pick the first available swap
137 will allow nohz_full mask to include CPU0.
199 This option will let you suspend your machine during bootup, and
238 dependent, x86 will print the information during a
[all …]
|
| /linux-5.10/Documentation/process/ |
| D | 7.AdvancedTopics.rst | 7 works. There is still more to learn, however! This section will cover a
26 still being civilized by its developers. This document will not attempt to
28 long document in its own right. Instead, the focus here will be on how git
30 wish to come up to speed with git will find more information at:
53 will, of course, need a server that can be pulled from. Setting up such a
81 Rewriting history will rewrite the changes contained in that history,
85 have pulled into their repositories, you will make life much more difficult
91 changes should not be rewritten. Git will attempt to enforce this rule if
144 your tree is, what branch to pull, and what changes will result from the
145 pull. The git request-pull command can be helpful in this regard; it will
[all …]
|
| /linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-encoder.rst | 90 * The full set of supported formats will be returned, regardless of the
97 will be returned.
108 format will include all possible coded resolutions supported by the
112 will include all possible frame buffer resolutions supported by the
123 format and coded resolution will include all possible frame intervals
127 format and resolution will include all possible frame intervals supported
228 * Setting the ``OUTPUT`` format will reset the selection rectangles to their
257 to 1/24 (or 24 frames per second) will produce a coded video stream
435 restarts it again, the encoder will begin generating a stream independent
493 will have their ``timestamp`` field set to the same value when dequeued.
[all …]
|
| /linux-5.10/drivers/misc/ |
| D | Kconfig | 31 will be called ad525x_dpot.
40 module will be called ad525x_dpot-i2c.
51 module will be called ad525x_dpot-spi.
102 module will be called ibmvmc.
112 If you choose to build module, its name will be phantom. If unsure,
137 You will also have to select some flash card format drivers. MMC/SD
141 To compile this driver as a module, choose M here: the module will
151 To make actual use of the device, you will have to select some
154 To compile this driver as a module, choose M here: the module will
165 will be called ics932s401.
[all …]
|
| /linux-5.10/Documentation/block/ |
| D | inline-encryption.rst | 16 the inline encryption hardware will en/decrypt the data in the request with the
40 device will en/decrypt the data using the encryption context programmed into
68 to support IE will construct a KSM and set it up in its struct request_queue.
80 one. If no idle keyslots are available, then the caller will sleep until there
88 struct request. These will be referred to as the ``crypto fields``
96 support the encryption context specified with the bio, the block layer will
100 is encrypted stored in the bounce bio - blk-mq will then proceed to process the
110 ``bio_crypto_fallback_decrypt_bio`` will decrypt the bio, restore the original
115 on-disk format of data) will be the same (assuming the hardware's implementation
119 encryption context specified with a bio, then it will not be handled by the
[all …]
|
| /linux-5.10/drivers/input/tablet/ |
| D | Kconfig | 8 Say Y here, and a list of supported tablets will be displayed.
26 module will be called acecad.
39 module will be called aiptek.
51 module will be called gtco.
62 module will be called hanwang.
75 module will be called kbtab.
90 module will be called pegasus_notetaker.
100 module will be called wacom_serial4.
|
| /linux-5.10/drivers/iio/humidity/ |
| D | Kconfig | 16 This driver can also be built as a module. If so, the module will
39 will be called hdc100x.
49 will be called hdc2010.
63 will be called hid-sensor-humidity.
77 will be called hts221.
99 This driver can also be built as a module. If so, the module will
110 will be called si7005. This driver also
122 will be called si7020.
|
| /linux-5.10/drivers/pci/hotplug/ |
| D | Kconfig | 26 module will be called cpqphp.
35 controller. This will allow the PCI Hotplug driver to store the PCI
48 module will be called ibmphp.
69 module will be called acpiphp_ibm.
89 module will be called cpcihp_zt5550.
102 module will be called cpcihp_generic.
123 module will be called pnv-php.
134 module will be called rpaphp.
146 module will be called rpadlpar_io.
|
| /linux-5.10/include/media/ |
| D | v4l2-ctrls.h | 18 * This will move to the public headers once this API is fully stable.
107 * If not set, then the currently cached value will be returned.
168 * will not be added to any other handlers. Drivers can set
209 * then this will have to be extended to a u64 or a bit array.
399 * then this will have to be extended to a bit array.
407 * will not be added to any other handlers.
442 * For non-standard controls it will only fill in the given arguments
443 * and @name content will be set to %NULL.
445 * This function will overwrite the contents of @name, @type and @flags.
453 * control framework this function will no longer be exported.
[all …]
|
| /linux-5.10/include/linux/ |
| D | xarray.h | 178 * The normal API will return NULL as the contents of a slot containing
192 * If an XArray operation cannot complete an operation, it will return
209 * If an XArray operation cannot complete an operation, it will return
427 * During the iteration, @entry will have the value of the entry stored
430 * during the iteration. At the end of the iteration, @entry will be set
431 * to NULL and @index will have a value less than or equal to max.
435 * after each iteration, it will also end up being O(n.log(n)).
436 * xa_for_each_range() will spin if it hits a retry entry; if you intend to
438 * The xas_for_each() iterator will expand into more inline code than
456 * During the iteration, @entry will have the value of the entry stored
[all …]
|