Searched full:will (Results 376 – 400 of 18589) sorted by relevance
1...<<11121314151617181920>>...744
| /linux-5.10/Documentation/arm/ |
| D | booting.rst | 36 kernel will use for volatile data storage in the system. It performs
78 For DT-only platforms, the machine type will be determined by device
80 necessary, but assures that it will not match any existing types.
123 the kernel decompressor nor initrd 'bootp' program will overwrite
132 The kernel will look for the dtb magic value of 0xd00dfeed at the dtb
138 placed in a region of memory where the kernel decompressor will not
139 overwrite it, while remaining within the region which will be covered
153 a region of memory where the kernel decompressor will not overwrite it
154 while also with the region which will be covered by the kernel's
157 A safe location is just above the device tree blob which itself will
[all …]
|
| /linux-5.10/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 125 directory will be used as a reference for the link and it will contain the
136 configure type of data that will travel over this channel
138 configure whether this link will be an input or output
143 configure the number of packets that will be collected from the
167 inside the most_sound's configuration directory. This adapter dir will
169 only and has no further influence, as all sound adapters will be given a static
170 name in ALSA. The sound adapter will have the following attribute:
178 Secondly, links will have to be created inside the adapter dir as described in
179 section 2.1. These links will become the PCM devices of the sound card. The
180 name of a PCM device will be inherited from the directory name. When all
[all …]
|
| /linux-5.10/include/media/ |
| D | v4l2-dv-timings.h | 69 * If a valid timing for the given index is found, it will fill in @t and
92 * On success it will fill in @t with the found timings and it returns true.
93 * On failure it will return false.
106 * On success it will fill in @t with the found timings and it returns true.
107 * On failure it will return false.
151 * This function will attempt to detect if the given values correspond to a
152 * valid CVT format. If so, then it will return true, and fmt will be filled
172 * is not filled in correctly, then 16:9 will be assumed.
175 * This function will attempt to detect if the given values correspond to a
176 * valid GTF format. If so, then it will return true, and fmt will be filled
|
| /linux-5.10/fs/ocfs2/ |
| D | reservations.h | 35 #define OCFS2_RESV_FLAG_TMP 0x02 /* Temporary reservation, will be
69 * After this function is called, the reservation will be empty, and
98 * This function will call ocfs2_trunc_resv against all existing
99 * reservations. A future version will recalculate existing
118 * Using the reservation data from resv, this function will compare
121 * this function will try to allocate a window for it.
142 * Internally, the reservations code will use this information to mark the
143 * reservations bitmap. If resv is passed, it's next allocation window will be
|
| /linux-5.10/sound/firewire/ |
| D | Kconfig | 25 will be called snd-dice.
48 will be called snd-oxfw.
58 will be called snd-isight.
74 will be called snd-fireworks.
115 will be called snd-bebob.
130 will be called snd-firewire-digi00x.
143 will be called snd-firewire-tascam.
161 will be called snd-firewire-motu.
|
| /linux-5.10/Documentation/filesystems/ |
| D | gfs2-uevents.rst | 17 The ADD event occurs at mount time. It will always be the first
19 is successful, an ONLINE uevent will follow. If it is not successful
20 then a REMOVE uevent will follow.
33 RDONLY are a relatively recent addition (2.6.32-rc+) and will not
72 or at the end of a umount of the filesystem. All REMOVE uevents will
93 on the mount command line, or via fstab. It will be either
101 assigned for spectator mounts) then this will give the
108 into the filesystem superblock. If it exists, this will
|
| D | dax.txt | 50 3. If the persistent FS_XFLAG_DAX flag is set on a directory, this flag will
72 in-core inode state (S_DAX) will be overridden until the filesystem is
92 the policy change will affect
94 b) evict the data set from kernel caches so it will be re-instantiated when
153 statx can be used to query S_DAX. NOTE that only regular files will ever have
154 S_DAX set and therefore statx will never indicate that S_DAX is set on
233 This will free the filesystem blocks that were being used by the file,
234 and the next time they're allocated, they will be zeroed first, which
235 happens through the driver, and will clear bad sectors.
254 DAX on a block device that supports DAX, they will still be copied into RAM.
[all …]
|
| /linux-5.10/drivers/staging/media/atomisp/pci/ |
| D | ia_css_control.h | 10 * This program is distributed in the hope it will be useful, but WITHOUT
63 * with the exception of ia_css_init which will re-initialize the CSS code,
77 * will be made the default and this function will be removed.
79 * when the SP is running will result in an error value being returned. }
115 * It will boot the SP hardware and start multi-threading infrastructure.
116 * All threads will be started and blocked by semaphore. This function should
126 * This function will terminate all threads and shut down SP. It should be
|
| /linux-5.10/arch/mips/include/asm/ |
| D | maar.h | 19 * the number that were used. Any further MAARs will be configured to be
20 * invalid. The default implementation of this function will simply indicate
30 * @lower: The lowest address that the MAAR pair will affect. Must be
32 * @upper: The highest address that the MAAR pair will affect. Must be
35 * MIPS_MAAR_VL/MIPS_MAAR_VH attributes will automatically be set.
88 * @lower: The lowest address that the MAAR pair will affect. Must be
90 * @upper: The highest address that the MAAR pair will affect. Must be
93 * MIPS_MAAR_VL attribute will automatically be set.
|
| /linux-5.10/Documentation/admin-guide/ |
| D | security-bugs.rst | 16 who will help verify the bug report and develop and release a fix.
19 security team will bring in extra help from area maintainers to
23 will be to diagnose and fix. Please review the procedure outlined in
25 information is helpful. Any exploit code is very helpful and will not
55 order to develop a fix, such information will not be published alongside
73 upstream fix. Distros will need some time to test the proposed patch and
74 will generally request at least a few days of embargo, and vendor update
87 assigned ahead of public disclosure, they will need to contact the private
|
| /linux-5.10/drivers/media/pci/ivtv/ |
| D | Kconfig | 30 module will be called ivtv.
58 module will be called ivtv-alsa.
73 module will be called ivtvfb.
81 For this reason, the driver will by default disable itself
89 With this setting enabled, the framebuffer will initialize on
90 PAT-enabled systems but the framebuffer memory will be uncached.
|
| /linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-module | 7 module name will always show up if the module is loaded as a
9 will only show up if it has a version or at least one
23 considered stable, only the fact that they will be
30 will contain the current reference count of the module.
34 this file will not be present.
|
| /linux-5.10/drivers/net/ethernet/ibm/ |
| D | Kconfig | 14 kernel: saying N will just cause the configurator to skip all
15 the questions about IBM devices. If you say Y, you will be asked for
27 To compile this driver as a module, choose M here. The module will
39 will be called ehea.
48 To compile this driver as a module, choose M here. The module will
|
| /linux-5.10/Documentation/filesystems/caching/ |
| D | cachefiles.rst | 58 placed on the same medium as a live set of data, and will expand to make use of
150 Do not mount other things within the cache as this will cause problems. The
161 cache as this will cause the cache state management to get confused.
206 started as soon as space is made in the table. Objects will be skipped if
213 The CacheFiles module will create two directories in the directory it was
221 to the graveyard from which the daemon will actually delete them.
223 The daemon uses dnotify to monitor the graveyard directory, and will delete
232 directory, data objects will have a file in the directory called "data" that
239 If an object has children, then it will be represented as a directory.
242 this directory, if possible, will be placed the representations of the child
[all …]
|
| /linux-5.10/drivers/regulator/ |
| D | Kconfig | 170 AS3722 PMIC. This will enable support for all the software
185 BCM590xx PMUs. This will enable support for the software
193 This will enable support for the software controllable buck
197 will be called bd70528-regulator.
205 This will enable support for the software controllable buck
209 will be called bd71828-regulator.
217 This will enable support for the software controllable buck
221 will be called bd718x7-regulator.
228 ROHM BD9571MWV PMIC. This will enable support for the software
232 will be called bd9571mwv-regulator.
[all …]
|
| /linux-5.10/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 80 will assume you have the version 2.2 of GnuPG (or later). If you are
81 using version 2.0 of GnuPG, then some of the commands in this guide will
97 The GnuPG agent is a helper tool that will start automatically whenever
103 the time-to-live expires, the countdown will reset for another period.
127 You will need to regularly refresh your keyring in order to get the
187 is what you will have. You can verify by running ``gpg --list-secret-keys``,
268 that passphrase, and if you ever change it you will not remember what it
293 disaster-level preparedness we did with ``paperkey``. You will also rely
299 will use for backup purposes. You will need to encrypt them using LUKS
343 your GnuPG directory in its entirety. What we are about to do will
[all …]
|
| /linux-5.10/Documentation/driver-api/media/ |
| D | v4l2-device.rst | 15 Registration will initialize the :c:type:`v4l2_device` struct. If the
16 dev->driver_data field is ``NULL``, it will be linked to
26 If :c:type:`v4l2_dev <v4l2_device>`\ ->name is empty then it will be set to a
28 If you set it up before calling :c:func:`v4l2_device_register` then it will
34 name and a driver-global atomic_t instance. This will generate names like
35 ``ivtv0``, ``ivtv1``, etc. If the name ends with a digit, then it will insert
55 it will be reset to ``NULL``. Unregistering will also automatically unregister
141 will never reach 0.
|
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-block-bcache | 47 For backing devices: Threshold past which sequential IO will
64 writes will be buffered in the cache. When off, caching is in
65 writethrough mode; reads and writes will be added to the
66 cache but no write buffering will take place.
72 For backing devices: when off, dirty data will not be written
73 from the cache to the backing device. The cache will still be
104 if disabled bcache will not generally wait for writes to
106 will be discarded from the cache. Should not be turned off with
135 one node tree will have a depth of 0).
|
| /linux-5.10/sound/drivers/ |
| D | Kconfig | 60 You can compile this as a module which will be called snd-pcsp.
90 will be called snd-dummy.
110 will be called snd-aloop.
127 will be called snd-virmidi.
138 will be called snd-mtpav.
151 will be called snd-mts64.
166 will be called snd-serial-u16550.
176 will be called snd-mpu401.
187 will be called snd-portman2x4.
|
| /linux-5.10/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| D | Expedited-Grace-Periods.rst | 52 will ignore it because idle and offline CPUs are already residing
54 Otherwise, the expedited grace period will use
63 invocation will provide the needed quiescent-state report.
71 When that happens, RCU will enqueue the task, which will the continue to
74 The CPU will report a quiescent state just after enqueuing the task because
134 quiescent state. Should the CPU go offline first, it will report the
142 grace periods. In addition, attempting to IPI offline CPUs will result
169 been online at least once will be considered for a given grace
171 #. Any CPU that goes offline will clear its bit in its leaf ``rcu_node``
202 | at the bottom of the tree. Those bits will never be cleared, which |
[all …]
|
| /linux-5.10/drivers/gpu/drm/ |
| D | Kconfig | 106 history of each topology reference/dereference will be printed to the
131 is 100. Typical values for double buffering will be 200,
182 GPU memory types. Will be enabled automatically if a device driver
251 If M is selected, the module will be called radeon.
270 If M is selected, the module will be called amdgpu.
284 If M is selected the module will be called vgem.
297 If M is selected the module will be called vkms.
416 graphics card. If M is selected, the module will be called tdfx.
424 is selected, the module will be called r128. AGP support for
433 selected, the module will be called i810. AGP support is required
[all …]
|
| /linux-5.10/security/ |
| D | inode.c | 83 * file will be created in the root of the securityfs filesystem.
84 * @data: a pointer to something that the caller will want to get to later
85 * on. The inode.i_private pointer will point to this value on
102 * function will return the error value (via ERR_PTR).
182 * file will be created in the root of the securityfs filesystem.
183 * @data: a pointer to something that the caller will want to get to later
184 * on. The inode.i_private pointer will point to this value on
194 * you are responsible here). If an error occurs, the function will return
215 * directory will be created in the root of the securityfs filesystem.
222 * you are responsible here). If an error occurs, the function will return
[all …]
|
| /linux-5.10/Documentation/admin-guide/pm/ |
| D | cpufreq_drivers.rst | 23 Note that the driver's will not load on the "wrong" hardware,
28 is not available in all processors. The drivers will refuse
34 Frequency transitions will be unavailable if the BIOS does
49 The powernow-k8 driver will attempt to use ACPI if so configured,
51 The powernow-k7 driver will try to use the PSB support first, and
149 When PCC mode is enabled, the platform will not expose processor performance
152 AMD) will not load.
177 ignored by OSPM. The next invocation of "Get Average Frequency" will inform
182 The PCC driver will load on any system where the platform firmware:
192 is not implemented, the PCC driver will fail to load silently.
[all …]
|
| /linux-5.10/Documentation/scheduler/ |
| D | completion.rst | 129 from the wait_on_completion*() caller function will deallocate the function
164 to wait_for_completion() then the waiting side simply will continue
165 immediately as all dependencies are satisfied; if not, it will block until
170 Calling it from IRQs-off atomic contexts will result in hard-to-detect
207 If a signal was received while waiting it will return -ERESTARTSYS; 0 otherwise::
211 The task is marked as TASK_UNINTERRUPTIBLE and will wait at most 'timeout'
224 TASK_INTERRUPTIBLE. If a signal was received it will return -ERESTARTSYS;
229 designated tasks state and will return -ERESTARTSYS if it is interrupted,
256 The signaling will work as expected even if completions are signaled before
261 If complete() is called multiple times then this will allow for that number
[all …]
|
| /linux-5.10/Documentation/block/ |
| D | data-integrity.rst | 56 The controller will interleave the buffers on write and split them on
115 will still use the automatic generation interface.
125 This also means that applications such as fsck and mkfs will need
144 calling bio_integrity_alloc(bio). This will allocate and attach the
150 bio_free() will automatically free the bip.
166 Layered block devices will need to pick a profile that's appropriate
169 will require extra work due to the application tag.
179 is capable of sending/receiving integrity metadata. The IMD will
181 in case of a WRITE. A READ request will cause the I/O integrity
229 The integrity payload will be freed at bio_free() time.
[all …]
|
1...<<11121314151617181920>>...744