Searched full:will (Results 426 – 450 of 18589) sorted by relevance
1...<<11121314151617181920>>...744
| /linux-5.10/drivers/cpufreq/ |
| D | Kconfig | 83 driver. Fallback governor will be the performance governor.
96 driver. Fallback governor will be the performance governor.
106 governor will be 'performance'.
117 module will be called cpufreq_performance.
128 module will be called cpufreq_powersave.
141 module will be called cpufreq_userspace.
159 module will be called cpufreq_ondemand.
180 transitions in the CPU) you will probably want to use this governor.
183 module will be called cpufreq_conservative.
316 driver. While it will make the kernel slightly larger, this is
[all …]
|
| /linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-ext-ctrls.rst | 61 relevant for pointer-type controls like strings), then the driver will
78 the :ref:`VIDIOC_S_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>` ioctl. The controls will only be set if *all*
95 control), then this will also result in an ``EINVAL`` error code error.
102 If the device does not support requests, then ``EACCES`` will be returned.
104 then ``EINVAL`` will be returned.
107 request that has already been queued will result in an ``EBUSY`` error.
111 :ref:`VIDIOC_G_EXT_CTRLS <VIDIOC_G_EXT_CTRLS>`, then it will return the
113 If the request is not yet completed, then this will result in an
116 The driver will only set/get these controls if all control values are
139 size of the memory containing the payload, or that will receive
[all …]
|
| /linux-5.10/drivers/net/ethernet/intel/fm10k/ |
| D | fm10k_mbx.c | 211 * This function will return the length of the message currently being
232 * This function will take a message and copy it into a section of the
261 * contained in the first DWORD of the message and will place at the tail
262 * of the FIFO. It will return 0 on success, or a negative value on error.
293 * This function analyzes the frame and will return a non-zero value when
326 * This function will take a section of the Tx FIFO and copy it into the
377 * This function will push the tail index forward based on the remote
378 * head index. It will then pull up to mbmem_len DWORDs off of the
379 * head of the FIFO and will place it in the MBMEM registers
419 * This function will take a section of the mailbox memory and copy it
[all …]
|
| /linux-5.10/Documentation/vm/ |
| D | slub.rst | 15 to the kernel command line. That will enable full debugging for
27 be enabled on the command line. F.e. no tracking information will be
92 of options. This will enable red zoning for dentry and user tracking for
93 kmalloc. All other slabs will not get any debugging enabled::
138 which will test all objects. Output will be generated to the syslog.
160 general slub will be able to perform this number of
222 to be booted with slub_debug) then the following output will be dumped
227 This will be a message in the system log starting with::
301 This will be generally be enough to enable the resiliency features of slub
302 which will keep the system running even if a bad kernel component will
[all …]
|
| /linux-5.10/tools/bpf/bpftool/Documentation/ |
| D | bpftool-prog.rst | 65 programs which will all be shown.
67 Output will start with program ID followed by program type and
80 programs. On such kernels bpftool will automatically emit this
85 default, eBPF will be disassembled and printed to standard
90 programs which will all be dumped. However, if **file** or
93 If **file** is specified, the binary image will instead be
96 If **visual** is specified, control flow graph (CFG) will be
97 built instead, and eBPF instructions will be presented with
100 If the programs have line_info available, the source line will
102 the filename, line number and line column will also be
[all …]
|
| /linux-5.10/Documentation/driver-api/media/ |
| D | v4l2-dev.rst | 67 file operation is called this lock will be taken by the core and released
84 If left to ``NULL``, then it will use the struct v4l2_prio_state
134 A reference to the entity will be automatically acquired/released when the
142 If you set this pointer, then that will be used by unlocked_ioctl to
147 set, then this lock will be used instead of :c:type:`video_device`->lock
162 function: if videobuf has to wait for a frame to arrive, then it will
168 In the case of :ref:`videobuf2 <vb2_framework>` you will need to implement the
184 This will create the character device for you.
195 the video device entity will be automatically registered with the media
215 device node number used (i.e. the X in ``videoX``). Normally you will pass -1
[all …]
|
| /linux-5.10/drivers/media/platform/davinci/ |
| D | Kconfig | 15 To compile this driver as a module, choose M here. There will
30 To compile this driver as a module, choose M here. There will
46 To compile this driver as a module, choose M here. There will
62 To compile this driver as a module, choose M here. There will
76 To compile this driver as a module, choose M here. There will
90 To compile this driver as a module, choose M here. There will
|
| /linux-5.10/Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 88 is 0x15 and the full version number is 0x234, this file will contain
99 file will contain the value 564 = 0x234.
122 This is the pid which will be signalled on reboot (notably, by
124 correspond to a running process will result in ``-ESRCH``.
148 and ``core_uses_pid`` is set, then .PID will be appended to
174 * If the first character of the pattern is a '|', the kernel will treat
175 the rest of the pattern as a command to run. The core dump will be
200 captured in parallel, but that no waiting will take place (i.e. the
212 and ``core_uses_pid`` is set, then .PID will be appended to
222 Nerve Pinch (tm) will be an immediate reboot, without even
[all …]
|
| /linux-5.10/Documentation/x86/ |
| D | resctrl_ui.rst | 53 only those files and directories supported by the system will be created.
104 "shareable_bits" but no resource group will
153 If RDT monitoring is available there will be an "L3_MON" directory
173 control files). If the command was successful, it will read as "ok".
174 If the command failed, it will provide more information that can be
202 Removing a directory will move all tasks and cpus owned by the group it
204 will automatically remove all MON groups below it.
210 this group. Writing a task id to the file will add a task to the
220 this group. Writing a mask to this file will add and remove
224 When the resource group is in pseudo-locked mode this file will
[all …]
|
| /linux-5.10/Documentation/kbuild/ |
| D | modules.rst | 50 easily accomplished, and a complete example will be presented in
60 using a distribution kernel, there will be a package for the kernel you
63 An alternative is to use the "make" target "modules_prepare." This will
68 NOTE: "modules_prepare" will not build Module.symvers even if
100 "make" will actually change to the specified directory
101 when executing and will change back when finished.
117 The default will build the module(s) located in the current
119 output files will also be generated in this directory. No
160 build file is required. Contained in this file will be the name of
166 The kbuild system will build <module_name>.o from <module_name>.c,
[all …]
|
| /linux-5.10/drivers/net/wireless/ralink/rt2x00/ |
| D | rt2x00queue.h | 340 * while transferring the data to the hardware. No TX status report will
386 * @Q_INDEX_DMA_DONE: Index pointer for the next entry which will have been
388 * @Q_INDEX_DONE: Index pointer to the next entry which will be completed by
405 * device might be DMA'ing skbuffers. TX queues will accept skbuffers to
406 * be transmitted and beacon queues will start beaconing the configured
490 * this macro will return the address of 1 position beyond the end of the
501 * queues, this macro will return the address of 1 position beyond
522 * @__entry: Pointer where the current queue entry will be stored in.
526 * This macro will loop through all queues between &__start and &__end.
536 * @__entry: Pointer where the current queue entry will be stored in.
[all …]
|
| /linux-5.10/include/linux/decompress/ |
| D | generic.h | 17 *posp - if non-null, input position (number of bytes read) will be
22 *If len = 0, inbuf can be NULL, in which case the decompressor will allocate
24 *fill will be called (repeatedly...) to read data, at most XXX_IOBUF_SIZE
29 *output. If flush != NULL, the output buffer will be allocated by the
30 *decompressor (outbuf = NULL), and the flush function will be called to
|
| /linux-5.10/net/tipc/ |
| D | Kconfig | 20 want). The module will be called tipc. If you want to compile it
29 Saying Y here will enable support for running TIPC on
36 Saying Y here will enable support for running TIPC over IP/UDP
46 Saying Y here will enable support for TIPC encryption.
47 All TIPC messages will be encrypted/decrypted by using the currently most
|
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-memory-page-offline | 8 physical address of the page. The kernel will then attempt
10 dropping it if possible. The kernel will then be placed
18 kernel will never kill anything for this, but rather
31 kernel will then attempt to hard-offline the page, by
34 any processes owning the page. The kernel will avoid
|
| /linux-5.10/drivers/staging/sm750fb/ |
| D | readme | 19 it will create fb0 and fb1 (or fb1,fb2 if fb0 already exist) under /dev
24 you edited in the grub config file will be also the
33 refresh rate, kernel driver will defaulty use 16bpp and 60hz
36 if you have vesafb enabled in your config then /dev/fb0 will be created by vesafb
37 and this driver will use fb1, fb2. In that case, you need to configure your X-server
|
| /linux-5.10/Documentation/arm/samsung-s3c24xx/ |
| D | suspend.rst | 58 and will end up initialising all compiled machines' pm init!
87 1) The uart drivers will disable the clocks to the UART blocks when
89 access to the UARTs will cause the debug to stop.
91 2) While the pm code itself will attempt to re-enable the UART clocks,
130 will mean that the CRC data block will take more memory, but will
|
| /linux-5.10/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | sta.h | 17 * This program is distributed in the hope that it will be useful, but
110 * queue will be allocated from the DATA pool instead. Since QoS NDPs can create
111 * a problem for aggregations, they too will use a MGMT queue.
114 * it. If no such free queue exists for reserving, the STA addition will fail.
116 * If the DATA queue pool gets exhausted, no new STA will be accepted, and if a
117 * new RA/TID comes in for an existing STA, one of the STA's queues will become
118 * shared and will serve more than the single TID (but always for the same RA!).
137 * In STA/P2P client mode, the driver will hold one station for the AP/ GO.
138 * In GO/AP mode, the driver will have as many stations as associated clients.
178 * then the reclaim flow will notice that there is no station in the map for
[all …]
|
| /linux-5.10/include/linux/ |
| D | zlib.h | 6 warranty. In no event will the authors be held liable for any damages
56 (deflation) but other algorithms will be added later and will have the same
112 The opaque value provided by the application will be passed as the first
122 exactly 65536 bytes, but will not be required to allocate more than this
140 #define Z_PARTIAL_FLUSH 1 /* will be removed, use Z_SYNC_FLUSH instead */
219 perform any compression: this will be done by deflate().
236 processing will resume at this point for the next call of deflate().
330 accordingly; otherwise the allocation will be deferred to the first call of
338 the zlib header if present: this will be done by inflate(). (So next_in and
356 will resume at this point for the next call of inflate().
[all …]
|
| /linux-5.10/Documentation/driver-api/usb/ |
| D | callbacks.rst | 4 What callbacks will usbcore do?
7 Usbcore will call into a driver through callbacks defined in the driver
88 particular interface. The device will not be suspended and you may do IO
104 If you are called due to a physical disconnection, all your URBs will be
105 killed by usbcore. Note that in this case disconnect will be called some
144 No callbacks other than probe will be invoked for an interface
147 Probe will never be called for an interface bound to a driver.
148 Hence following a successful probe, disconnect will be called
|
| /linux-5.10/arch/sh/mm/ |
| D | Kconfig | 13 turning this off will boot the kernel on these machines with the
52 The physical memory (RAM) start address will be automatically
58 value on any of the known systems will only lead to disaster.
86 If you say Y here, physical addressing will be extended to
88 29-bit physical addressing will be used.
99 This will enable support for the kernel mapping a vDSO page
248 Selecting this option will configure the caches in write-through
251 Since there's sill some aliasing issues on SH-4, this option will
|
| /linux-5.10/scripts/coccinelle/api/ |
| D | platform_no_drv_owner.cocci | 127 msg = "No need to set .owner here. The core will do it."
134 msg = "No need to set .owner here. The core will do it."
141 msg = "No need to set .owner here. The core will do it."
148 msg = "No need to set .owner here. The core will do it."
157 msg = "No need to set .owner here. The core will do it."
164 msg = "No need to set .owner here. The core will do it."
171 msg = "No need to set .owner here. The core will do it."
178 msg = "No need to set .owner here. The core will do it."
|
| /linux-5.10/include/sound/ |
| D | dmaengine_pcm.h | 64 * @filter_data: Custom DMA channel filter data, this will usually be used when
111 * PCM substream. Will be called from the PCM drivers hwparams callback.
116 * @compat_filter_fn: Will be used as the filter function when requesting a
118 * will be the DAI's DMA data.
121 * @chan_names: If set, these custom DMA channel names will be requested at
127 * compat_request_channel will be used to request the channel and
128 * compat_filter_fn will be ignored. Otherwise the channel will be requested
|
| /linux-5.10/Documentation/admin-guide/ |
| D | ras.rst | 14 is the probability that a system will produce correct outputs.
99 will translate the error message to the silkscreen or component label for
232 CE events only, the system can and will continue to operate as no data
284 and one MC driver will be loaded. Both the CORE and the MC driver (or
347 controllers. The following example will assume 2 channels:
386 ranked DIMMs are placed in slots DIMM_A0 and DIMM_B0, then they will
387 have just one csrow (csrow0) and csrow1 will be empty. The pattern
394 ``/sys/devices/system/edac/mc``, each memory controller will be
503 this counter will not have a chance to increment, since EDAC
504 will panic the system.
[all …]
|
| /linux-5.10/Documentation/networking/ |
| D | xfrm_sync.rst | 49 A XFRM_MSG_NEWAE will have at least two TLVs (as is
79 The pid will be set appropriately in netlink to recognize direction
116 Programs installing SAs will need to specify the two thresholds, however,
140 The response will always have XFRMA_LTIME_VAL and XFRMA_REPLAY_VAL TLVs.
160 The response will always have XFRMA_LTIME_VAL and XFRMA_REPLAY_VAL TLVs.
162 The threshold TLVs will be included if explicitly requested in
169 The message will always have XFRMA_LTIME_VAL and XFRMA_REPLAY_VAL TLVs.
177 The message will always have XFRMA_LTIME_VAL and XFRMA_REPLAY_VAL TLVs.
185 The first packet arrival after a timer expiry will trigger a timeout
|
| /linux-5.10/Documentation/driver-api/early-userspace/ |
| D | early_userspace_support.rst | 34 will be used directly. Only a single cpio file may be specified in
50 A source directory will have it and all of its contents packaged. The
51 specified directory name will be mapped to '/'. When packaging a
59 file format). The directives in the file will be passed directly to
63 initramfs image will be an aggregate of all of them. In this way a user
110 Eventually, several more chunks of kernel functionality will hopefully
133 initrd. init/main.c:init() will call prepare_namespace() to mount the
149 To maintain backwards compatibility, the /init binary will only run if it
151 init/main.c:init() will run prepare_namespace() to mount the final root
|
1...<<11121314151617181920>>...744