Searched full:could (Results 1 – 25 of 736) sorted by relevance
12345678910>>...30
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-query-dv-timings.rst | 57 If the timings could not be detected because there was no signal, then
59 the receiver could not lock to the signal, then ``ENOLCK`` is returned. If
60 the receiver could lock to the signal, but the format is unsupported
62 capabilities), then the driver fills in whatever timings it could find
79 No timings could be detected because no signal was found.
82 The signal was unstable and the hardware could not lock on to it.
|
| D | selection-api-vs-crop-api.rst | 19 image inside a memory buffer. The application could configure a
23 Introducing an image offsets could be done by modifying field
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 21 the descriptor could be found at UFS specifications 2.1.
31 the descriptor could be found at UFS specifications 2.1.
41 about the descriptor could be found at UFS specifications 2.1.
51 The full information about the descriptor could be found
62 about the descriptor could be found at UFS specifications 2.1.
72 The full information about the descriptor could be found
83 parameters. The full information about the descriptor could
93 descriptor could be read after partial initialization phase
95 parameters. The full information about the descriptor could
107 about the descriptor could be found at UFS specifications 2.1.
[all …]
|
| D | sysfs-bus-iio-adc-hi8435 | 7 Could be either "GND-Open" or "Supply-Open" mode. Y is a
20 Channels 0..31 have common low threshold values, but could have different
40 Channels 0..31 have common high threshold values, but could have different
|
| D | sysfs-block-zram | 48 "0". Otherwise, you could see -EINVAL.
57 The limit could be changed in run time and "0" means disable
66 it could free fragment space.
138 amount of writeback ZRAM can do. The limit could be changed
|
| D | sysfs-class-fpga-manager | 15 fails, that could be due to not being able to find the firmware
43 If FPGA programming operation fails, it could be caused by crc
|
| /Documentation/sound/ |
| D | utimers.rst | 13 which could be created and controlled by userspace applications using
14 IOCTL calls. Such timers could be useful when synchronizing audio
24 The userspace-driven timers could be enabled in the kernel using the
51 applications. There could be up to 128 userspace-driven timers in the
93 More detailed example of creating and ticking the timer could be found
99 Userspace-driven timers could be easily used with ``snd-aloop`` module
107 timers could be used to achieve this.
|
| /Documentation/networking/devlink/ |
| D | index.rst | 23 first, only after that RTNL lock could be taken.
28 Some objects, like linecards or port functions, could have another
35 instance lock of the nested instance could be taken.
40 devlink relationship (could be user for multiple nested instances.
|
| /Documentation/mm/damon/ |
| D | design.rst | 16 called ``kdamond``. Multiple kdamonds could run in parallel, for different
99 mapping is not strictly required but could even incur a high overhead in some
131 bit(s) set again after one sampling period. This could disturb other kernel
238 access pattern of a region has maintained. That could be used for good
240 utilizing both the frequency and the recency could be implemented using that.
251 The monitoring target address range could dynamically changed. For example,
252 virtual memory could be dynamically mapped and unmapped. Physical memory could
255 As the changes could be quite frequent in some cases, DAMON allows the
286 operation changes for the regions. The changes could be made by modifying or
288 reconfiguring the hardware. Both offline and online approaches could be
[all …]
|
| /Documentation/devicetree/bindings/display/hisilicon/ |
| D | hisi-ade.txt | 23 The rate of "clk_ade_core" could be "360000000" or "180000000";
24 The rate of "clk_codec_jpeg" could be or less than "1440000000".
25 These rate values could be configured according to performance and power
|
| /Documentation/driver-api/ |
| D | isa.rst | 13 ISA bus might be best; Russell King agreed and suggested this bus could
59 ALSA would want to keep the old non-load behaviour, it could stick all
63 changeover to platform devices, it could just not provide a .match() and
68 could conceivably succeed, it could use .match() for the prerequisites
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 9 careful to prevent the parent from doing anything that could subvert the
26 promises not to grant the privilege to do anything that could not have
59 In the future, other potentially dangerous kernel features could become
|
| /Documentation/trace/ |
| D | events-kmem.rst | 65 is triggered. Significant amounts of activity here could indicate that the
70 freed in batch with a page list. Significant amounts of activity here could
96 refills and drains could imply an imbalance between CPUs where too much work
97 is being concentrated in one place. It could also indicate that the per-CPU
99 and drains on another could be a factor in causing large amounts of cache
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | mc-peripheral-props.yaml | 11 They could be common properties like reg or they could be controller
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 125 siblings could be forced to select a lower priority task if the highest
167 core. But there could be small window of time during which untrusted tasks run
168 concurrently or kernel could be running concurrently with a task not trusted by
174 the siblings to switch to the new task. But there could be hardware delays in
201 Or it could be a system admin policy which considers guest to guest attacks as
205 system to not trust every other untrusted task. While this could reduce
220 with SMT enabled. There are other use cases where this feature could be used:
225 together could also be realized using core scheduling. One example is vCPUs of
|
| /Documentation/admin-guide/mm/damon/ |
| D | lru_sort.rst | 15 As page-granularity access checking overhead could be significant on huge
25 DAMON_LRU_SORT could be helpful for making LRU lists more trustworthy access
43 conservatively chosen. That is, the module under its default parameters could
67 Setting it as ``N`` disables DAMON_LRU_SORT. Note that DAMON_LRU_SORT could do
89 it could not be reclaimed under memory pressure. 50% by default.
98 that it could be reclaimed first under memory pressure. 120 seconds by
183 But, setting this too high could result in increased monitoring overhead.
194 However, setting this too low could result in bad monitoring quality. Please
|
| D | reclaim.rst | 24 guests could be not so memory-frugal, mainly because some kernel subsystems and
26 guests could report only small amount of memory as free to host, results in
28 guests could mitigate this problem.
59 Setting it as ``N`` disables DAMON_RECLAIM. Note that DAMON_RECLAIM could do
204 But, setting this too high could result in increased monitoring overhead.
214 However, setting this too low could result in bad monitoring quality. Please
|
| /Documentation/i2c/ |
| D | ten-bit-addresses.rst | 8 address 0x10 (though a single device could respond to both of them).
32 listed above could stay for a long time, maybe even forever if nobody
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 38 * lock the source (exclusive; probably could be weakened to shared)
125 on a filesystem could trigger directory operations only on higher-ranked
216 Which pair could it be?
220 children must be involved and thus neither of them could be a descendent
254 the only operation that could introduce loops is cross-directory rename.
260 Since the operation has succeeded, neither source nor target could have
262 in the parent of source could not have passed through the target and
263 vice versa. On the other hand, the chain of ancestors of any node could
|
| /Documentation/netlink/specs/ |
| D | binder.yaml | 41 if the target could not be determined.
47 if the target could not be determined.
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 43 In many cases there could be overlap between these three types (i.e.,
59 one could imagine slight tweaks to this that would allow for the same
61 memory behind it, its driver could add support as a P2P provider and
62 then the NVMe Target could use the RNIC's memory instead of the CMB
|
| /Documentation/devicetree/bindings/net/ |
| D | brcm,mdio-mux-iproc.yaml | 13 This MDIO bus multiplexer defines buses that could be internal as well as
14 external to SoCs and could accept MDIO transaction compatible to C-22 or
|
| /Documentation/networking/ |
| D | x25.rst | 23 which could allow X.25 to be run over an Ethernet (or Token Ring) and
28 Just when you thought that it could not become more confusing, another
|
| /Documentation/arch/arm/nwfpe/ |
| D | todo.rst | 35 so such a method could be promising, but requires more research to
49 bits describing the rounding mode. The emulator could be altered to
69 Hence, the answer is yes, you could do this, but then you will run a high
|
| /Documentation/admin-guide/media/ |
| D | faq.rst | 85 this could also work for terrestrial transmissions.
153 That could be due to a lot of problems. On my personal experience,
156 cabling. Yet, it could also be some hardware or driver issue.
162 Please see the FAQ page at linuxtv.org, as it could contain some
174 linux-media ML and see if someone else could shed some light.
|
12345678910>>...30