Searched full:will (Results 326 – 350 of 20877) sorted by relevance
1...<<11121314151617181920>>...836
| /linux-6.8/drivers/staging/media/deprecated/atmel/ |
| D | TODO | 12 inside the driver that will query the subdev at probe time and make a list
14 Basically the user has nothing to configure, as the isc will handle
19 this will not be achievable, as controller 1 and controller 2 might be
20 media-controller configurable, and will not propagate the formats down to
26 media-controller paradigm will continue to be happy and use the old config
31 of the driver will be able to use all the new features.
|
| /linux-6.8/drivers/usb/host/ |
| D | Kconfig | 18 module will be called c67x00.
28 module will be called xhci-hcd.
132 modules will be called ohci-platform.ko, ehci-brcm.ko and
135 Disabling this will keep the controllers and corresponding
144 If your USB host controller supports USB 2.0, you will likely want to
149 will connect to EHCI if the device is high speed, otherwise they
158 module will be called ehci-hcd.
179 (TT) in USB 2.0 hubs. Without this, only one transfer will be
185 Controller, and some of those devices will not work correctly
313 Note that this driver will not work on Marvell's other EHCI
[all …]
|
| /linux-6.8/tools/perf/pmu-events/arch/x86/snowridgex/ |
| D | uncore-memory.json | 224 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
233 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
242 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
251 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
260 … ranks are selected and are being throttled at the same time, the counter will only increment by 1…
269 … ranks are selected and are being throttled at the same time, the counter will only increment by 1…
288 … ranks are selected and are being throttled at the same time, the counter will only increment by 1…
297 … ranks are selected and are being throttled at the same time, the counter will only increment by 1…
379 …cycles when the Read Pending Queue is full. When the RPQ is full, the HA will not be able to issu…
387 …cycles when the Read Pending Queue is full. When the RPQ is full, the HA will not be able to issu…
[all …]
|
| /linux-6.8/Documentation/filesystems/caching/ |
| D | cachefiles.rst | 59 placed on the same medium as a live set of data, and will expand to make use of
151 Do not mount other things within the cache as this will cause problems. The
162 cache as this will cause the cache state management to get confused.
207 started as soon as space is made in the table. Objects will be skipped if
214 The CacheFiles module will create two directories in the directory it was
222 to the graveyard from which the daemon will actually delete them.
224 The daemon uses dnotify to monitor the graveyard directory, and will delete
233 directory, data objects will have a file in the directory called "data" that
240 If an object has children, then it will be represented as a directory.
243 this directory, if possible, will be placed the representations of the child
[all …]
|
| /linux-6.8/Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 87 interface, which will be removed at some time in the future. The other
92 interface is mostly frozen, and will change very little if at all: it
93 will not be extended to add any new functionality in the driver, instead
94 all new functionality will be implemented on the sysfs interface.
98 yet ready or stabilized, it is expected that this interface will change,
106 to the sysfs interfaces will be enforced, as will correctness in the
110 thinkpad-acpi's implementation of the sysfs interfaces will be fixed for
194 firmware will behave in many situations.
199 The driver will report HKEY events in the following format::
205 The driver will generate events over the input layer for hot keys and
[all …]
|
| /linux-6.8/drivers/usb/dwc2/ |
| D | Kconfig | 14 linked modules, the core module will be called dwc2.ko, the PCI
15 bus interface module (if you have a PCI bus system) will be
17 controllers directly connected to the CPU) will be called
19 will be an additional module named dwc2.ko.
54 the role will be determined by the cable that gets plugged-in. This
77 WARNING: Enabling this will quickly fill your message log.
94 non-periodic transfers, but of course the debug logs will be
|
| /linux-6.8/include/linux/ |
| D | power_supply.h | 31 * space. Unused/unknown fields will not appear in sysfs.
263 * property_is_writeable() will be called during registration
369 * time in minutes. We will only use maintenance charging in this setting
370 * for a certain amount of time, then we will first move to the next
378 * Ordinary CC/CV charging will stop charging when the charge current goes
383 * charger: instead they will at all times dissipate the battery a little, like
384 * the power used in standby mode. This will over time give a charge graph
409 * CC/CV charging. The maintenance charging will for safety reasons not go on
431 * the expected stand-by current. Also overvoltage protection will be applied
451 * level the battery will need precharging when using CC/CV charging.
[all …]
|
| /linux-6.8/include/uapi/linux/ |
| D | wireguard.h | 23 * The kernel will then return several messages (NLM_F_MULTI) containing the
56 * It is possible that all of the allowed IPs of a single peer will not
57 * fit within a single netlink message. In that case, the same peer will
58 * be written in the following message, except it will only contain
61 * coalesce adjacent peers. Likewise, it is possible that all peers will
62 * not fit within a single message. So, subsequent peers will be sent
63 * in following messages, except those will only contain WGDEVICE_A_IFNAME
67 * Since this is an NLA_F_DUMP command, the final message will always be
111 * most recent protocol will be used when
128 * If an error occurs, NLMSG_ERROR will reply containing an errno.
|
| /linux-6.8/Documentation/filesystems/nfs/ |
| D | reexport.rst | 9 recommend some careful research to determine whether it will work for
20 The "crossmnt" export does not propagate "fsid=", so it will not allow
29 case when the reexport server reboots. Clients will lose any locks
30 they held before the reboot, and further IO will result in errors.
37 reexport server's filehandle for the reexported object will be X+22
50 So, for example, you will only be able to reexport a filesystem over
72 All will therefore fit in an NFSv3 or NFSv4 filehandle after reexport,
92 over NFSv3 may be dicier, and reexporting over NFSv2 will probably
111 filesystem locally. A reexport server will also not pass them along to
112 the original server, so they will not be enforced between clients of
|
| /linux-6.8/Documentation/ABI/testing/ |
| D | sysfs-class-rnbd-client | 50 The connection will be established to this server from any client IP address.
59 will be established and data will be sent according to
71 will be created.
77 will try to open: /run/rnbd-devs/blya/sda.
90 the block-layer will send the IO via the poll-mode queue.
103 If the device is already mapped it will fail with EEXIST. If the input
104 has an invalid format it will return EINVAL. If the device path cannot
105 be found on the server, it will fail with ENOENT.
132 <device_id>. Otherwise, the <device_id> will be the same as the
|
| D | sysfs-class-devlink | 15 This file indicates if the device link will ever be
19 This will be one of the following strings:
25 'consumer unbind' means the device link will be removed when
28 'supplier unbind' means the device link will be removed when
31 'never' means the device link will not be automatically removed
50 This will be one of the following strings:
71 This will be one of the following strings:
117 This will be one of the following strings:
128 '1' means the device link will only affect the syncing of
|
| D | sysfs-bus-usb | 7 If a deauthorized interface will be authorized
35 Writing a device ID to this file will attempt to
45 Upon successfully adding an ID, the driver will probe
55 Reading from this file will list all dynamically added
64 The list will be truncated at PAGE_SIZE bytes due to
80 Writing a device ID to this file will remove an ID
84 removing an ID, the driver will no longer support the
89 Reading from this file will list the dynamically added
98 in to a xHCI host which support link PM, it will perform a LPM
100 (xHCI 1.0 feature), USB2 hardware LPM will be enabled for the
[all …]
|
| /linux-6.8/Documentation/userspace-api/media/v4l/ |
| D | vidioc-encoder-cmd.rst | 51 After a STOP command, :c:func:`read()` calls will read
53 :c:func:`read()` will return zero and the next :c:func:`read()`
54 call will restart the encoder.
109 invoke the command while the drain sequence is in progress will trigger
114 is set, encoding will continue until the end of the current *Group
115 Of Pictures*, otherwise encoding will stop immediately. When the
118 For a device implementing the :ref:`encoder`, the command will initiate
121 again before the sequence completes will trigger an ``EBUSY`` error
126 driver will return an ``EPERM`` error code. When the encoder is
132 been started yet, the driver will return an ``EPERM`` error code. When
|
| /linux-6.8/Documentation/driver-api/gpio/ |
| D | board.rst | 26 <function>-gpios, where <function> is the function the driver will request
43 This property will make GPIOs 15, 16 and 17 available to the driver under the
54 The led GPIOs will be active high, while the power GPIO will be active low (i.e.
55 gpiod_is_active_low(power) will be true).
123 can be NULL, in which case it will match any function.
139 match found will be used.
143 end. The 'dev_id' field of the table is the identifier of the device that will
144 make use of these GPIOs. It can be NULL, in which case it will be matched for
164 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows::
174 Since the "led" GPIOs are mapped as active-high, this example will switch their
[all …]
|
| /linux-6.8/Documentation/ABI/stable/ |
| D | sysfs-block | 183 will exist at this location. It will contain a hexadecimal
195 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
196 will contain "0x1200".
224 device. Otherwise the discard_granularity will be set to match
236 value lower will make Linux issue smaller discards and
259 [RO] Will always return 0. Don't rely on any specific behavior
297 will have an independent_access_ranges directory if the device
305 the range. For example, a dual-actuator hard-disk will have the
330 or disabled (0). Writing '0' to this file will disable polling
331 for this device. Writing any non-zero value will enable this
[all …]
|
| /linux-6.8/fs/debugfs/ |
| D | inode.c | 323 * This function will return a pointer to a dentry if it succeeds. If the file
324 * doesn't exist or an error occurs, %NULL will be returned. The returned
327 * If debugfs is not enabled in the kernel, the value -%ENODEV will be
463 * file will be created in the root of the debugfs filesystem.
464 * @data: a pointer to something that the caller will want to get to later
465 * on. The inode.i_private pointer will point to this value on
475 * This function will return a pointer to a dentry if it succeeds. This
478 * you are responsible here.) If an error occurs, ERR_PTR(-ERROR) will be
481 * If debugfs is not enabled in the kernel, the value -%ENODEV will be
507 * file will be created in the root of the debugfs filesystem.
[all …]
|
| /linux-6.8/Documentation/mm/ |
| D | unevictable-lru.rst | 34 main memory will have over 32 million 4k pages in a single node. When a large
36 will spend a lot of time scanning the LRU lists looking for the small fraction
107 When a memory control group comes under memory pressure, the controller will
171 list. Instead, vmscan will do this if and when it encounters the folios during
189 list at mlock() or mmap() time, vmscan will not encounter the folios until they
194 folios in all of the shrink_{active|inactive|page}_list() functions and will
199 but the folio does not have the mlocked flag set. Such folios will make
201 will be detected when vmscan walks the reverse map in folio_referenced()
209 is unlocked, __pagevec_lru_add_fn() will recheck the unevictable state
259 A PG_mlocked page will be placed on the unevictable list when it is added to
[all …]
|
| /linux-6.8/drivers/hwtracing/coresight/ |
| D | coresight-trace-id.h | 16 * The system will allocate Ids on a demand basis, and allow them to be
20 * throughout a perf cs_etm event session - a session in progress flag will
25 * Trace ID maps will be created and initialised to prevent architecturally
69 * Function will read the current trace ID for the associated CPU,
84 * This will release the CoreSight trace ID associated with the CPU,
87 * If a perf session is in operation then the ID will be marked as pending
100 * Used in perf context where it is known that the value for the CPU will not
110 * return: current value, will be 0 if unallocated.
152 * release, will be released.
|
| /linux-6.8/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 26 functions. Every EPC device present in the system will have an entry in
28 will have an entry in the *functions* directory.
38 Every registered EPF driver will be listed in controllers directory. The
39 entries corresponding to EPF driver will be created by the EPF core.
94 Every registered EPC device will be listed in controllers directory. The
95 entries corresponding to EPC device will be created by the EPC core.
108 The <EPC Device> directory will have a list of symbolic links to
113 The <EPC Device> directory will also have a *start* field. Once
114 "1" is written to this field, the endpoint device will be ready to
|
| /linux-6.8/drivers/platform/x86/siemens/ |
| D | Kconfig | 11 classes will take care of driving specifics of those machines.
15 will be called simatic-ipc.
27 will be called simatic-ipc-batt.
39 will be called simatic-ipc-batt-apollolake.
51 will be called simatic-ipc-batt-elkhartlake.
64 will be called simatic-ipc-batt-f7188x.
|
| /linux-6.8/Documentation/userspace-api/media/cec/ |
| D | cec-pin-error-inj.rst | 9 has low-level support for the CEC bus. Most hardware today will have
100 (the default) which will trigger the error injection only once for the next
105 So '``any rx-nack``' will NACK the next received CEC message,
106 '``any,always rx-nack``' will NACK all received CEC messages and
107 '``0x82,toggle rx-nack``' will only NACK if an Active Source message was
121 All four error injection commands will be active simultaneously.
129 Then the second will overwrite the first.
157 Every byte of the message will be NACKed in case the transmitter
182 As soon as a start bit has been received the CEC adapter will switch
183 to transmit mode and it will transmit a POLL message. By default this is
[all …]
|
| /linux-6.8/drivers/scsi/isci/ |
| D | remote_node_table.c | 13 * This program is distributed in the hope that it will be useful, but
66 * selection will be made.
70 * This routine will find the bit position in absolute bit terms of the next 32
102 * @group_table_index: This is the remote node selector in which the change will be
106 * This method will clear the group index entry in the specified group index
133 * will be made.
136 * This method will set the group index bit entry in the specified gropu index
165 * This method will set the remote to available in the remote node allocation
226 * @remote_node_table: The remote node table from which the slot will be
285 * This method will return the group value for the specified group index. The
[all …]
|
| /linux-6.8/arch/sparc/ |
| D | Kconfig | 163 If you say N here, the kernel will run on uni- and multiprocessor
164 machines, but will use only one CPU of a multiprocessor machine. If
165 you say Y here, the kernel will run on many, but not all,
167 will run faster if you say N here.
171 Management" code will be disabled if you say Y here.
320 the kernel. This will be overridden by the bootloader, if you
325 NOTE: This option WILL override the PROM bootargs setting!
348 If you say Y here, it will be possible to use a serial port as the
355 (/dev/tty0) will still be used as the system console by default, but
362 kernel will automatically use the first serial line, /dev/ttyS0, as
[all …]
|
| /linux-6.8/Documentation/usb/ |
| D | mass-storage.rst | 21 a single memory/DMA buffer will be usable for bulk-in and bulk-out
29 (which is no longer included in Linux). It will talk only briefly
42 FSG_MAX_LUNS (8) LUNs set. If more files are specified, they will
51 The size of the logical unit will be rounded down to a full
62 If this option is set for a logical unit, gadget will accept an
64 backing file will be closed to simulate ejection and the logical
65 unit will not be mountable by the host until a new backing file is
95 reported as read only. This will prevent host from modifying the
100 will fall back to read only mode anyway.
125 This parameter specifies number of logical units the gadget will
[all …]
|
| /linux-6.8/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 …]
|
1...<<11121314151617181920>>...836