Searched full:enough (Results 1 – 25 of 362) sorted by relevance
12345678910>>...15
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 78 maxItems: 8 # Should be enough regulators
102 maxItems: 8 # Should be enough regulators
117 maxItems: 8 # Should be enough regulators
131 maxItems: 32 # Should be enough
141 maxItems: 32 # Should be enough
218 maxItems: 8 # Should be enough regulators
229 maxItems: 8 # Should be enough regulators
237 maxItems: 8 # Should be enough regulators
|
| /Documentation/devicetree/bindings/dma/ |
| D | dma-common.yaml | 22 # Should be enough
37 # Should be enough
|
| /Documentation/devicetree/bindings/mfd/ |
| D | syscon-common.yaml | 11 of miscellaneous registers. The registers are not cohesive enough to
36 maxItems: 5 # Should be enough
|
| D | ti,nspire-misc.yaml | 15 of miscellaneous registers. The registers are not cohesive enough to
|
| /Documentation/fb/ |
| D | sa1100fb.rst | 18 on the kernel command line should be enough to configure the
27 options may not be enough to configure the display. Adding sections to
|
| /Documentation/mm/damon/ |
| D | index.rst | 11 - *accurate* (the monitoring output is useful enough for DRAM level memory
13 - *light-weight* (the monitoring overhead is low enough to be applied online),
|
| /Documentation/devicetree/bindings/dma/ti/ |
| D | k3-pktdma.yaml | 79 # Should be enough
90 # Should be enough
101 # Should be enough
112 # Should be enough
|
| D | k3-udma.yaml | 103 # Should be enough
112 # Should be enough
121 # Should be enough
|
| D | k3-bcdma.yaml | 92 # Should be enough
103 # Should be enough
114 # Should be enough
|
| /Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 17 in the upstream Linux kernel when you feel it is mature enough and you will get
29 because of not being reusable or abstract enough, or involving a lot of non
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 83 nice levels were not 'punchy enough', so lots of people had to resort to
91 enough), the scheduler was decoupled from 'time slice' and HZ concepts
108 The third complaint (of negative nice levels not being "punchy" enough
|
| /Documentation/userspace-api/media/dvb/ |
| D | dvb-frontend-parameters.rst | 14 data, the structure size weren't enough to fit, and just extending its
18 ioctl's. The new API is flexible enough to add new parameters to
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | iio-hwmon.yaml | 22 maxItems: 51 # Should be enough
|
| /Documentation/arch/arm64/ |
| D | memory.rst | 124 spaces, the VMEMMAP must be sized large enough for 52-bit VAs and
125 also must be sized large enough to accommodate a fixed PAGE_OFFSET.
139 sized large enough or that addresses are positioned close enough for
|
| /Documentation/watchdog/ |
| D | watchdog-pm.rst | 18 userspace enough time to resume. [1] [2]
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | 61 as long as the kernel is recent enough. Use the
153 transmit, as long as the kernel is recent enough. Use the
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-enum-links.rst | 43 with information about the entity's pads. The array must have enough
49 enough room to store all the entity's outbound links. The number of
|
| /Documentation/devicetree/bindings/ |
| D | .yamllint | 10 # 80 chars should be enough, but don't fail if a line is longer
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi-master-gpio.txt | 16 GPIO block is running at a low enough
|
| /Documentation/devicetree/bindings/timer/ |
| D | riscv,timer.yaml | 29 maxItems: 4096 # Should be enough?
|
| /Documentation/hwmon/ |
| D | w83l785ts.rst | 44 there is no old value). It seems to work well enough so that you should
|
| /Documentation/admin-guide/device-mapper/ |
| D | zero.rst | 16 enough data has been written to fill up the actual storage space, the sparse
|
| /Documentation/core-api/ |
| D | workqueue.rst | 128 maintaining just enough concurrency to prevent work processing from
444 enough across the affinity scopes by the issuers. The following performance
453 Scenario 1: Enough issuers and work spread across the machine
489 With enough issuers spread across the system, there is no downside to
495 Scenario 2: Fewer issuers, enough work for saturation
505 a third of the issuers but is still enough total work to saturate the
528 This is more than enough work to saturate the system. Both "system" and
538 Scenario 3: Even fewer issuers, not enough work to saturate
548 reduced to four, there now isn't enough work to saturate the whole system
|
| /Documentation/power/ |
| D | video.rst | 10 initialized by BIOS, and kernel does not have enough information to
50 the BIOS works well enough to be able to set video mode. Use
57 a new enough X, and a plain text console (no vesafb or radeonfb). See
61 (6) other radeon systems, where vbetool is enough to bring system back
|
| /Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 33 While in most cases tracking memory changes by #PF-s is more than enough
|
12345678910>>...15