Searched refs:enough (Results 1 – 25 of 420) sorted by relevance
12345678910>>...17
| /linux-6.1.9/drivers/mtd/ubi/ |
| D | fastmap-wl.c | 136 int enough; in ubi_refill_pools() local
158 enough = 0; in ubi_refill_pools()
170 enough++; in ubi_refill_pools()
184 enough++; in ubi_refill_pools()
186 if (enough == 2) in ubi_refill_pools()
|
| /linux-6.1.9/Documentation/mm/damon/ |
| D | index.rst | 10 - *accurate* (the monitoring output is useful enough for DRAM level memory
12 - *light-weight* (the monitoring overhead is low enough to be applied online),
|
| /linux-6.1.9/Documentation/devicetree/bindings/dma/ti/ |
| D | k3-pktdma.yaml | 65 # Should be enough
76 # Should be enough
87 # Should be enough
98 # Should be enough
|
| D | k3-bcdma.yaml | 91 # Should be enough
102 # Should be enough
113 # Should be enough
|
| D | k3-udma.yaml | 99 # Should be enough
108 # Should be enough
117 # Should be enough
|
| /linux-6.1.9/Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 80 maxItems: 8 # Should be enough regulators
104 maxItems: 8 # Should be enough regulators
119 maxItems: 8 # Should be enough regulators
133 maxItems: 32 # Should be enough
143 maxItems: 32 # Should be enough
220 maxItems: 8 # Should be enough regulators
231 maxItems: 8 # Should be enough regulators
239 maxItems: 8 # Should be enough regulators
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/devicetree/bindings/dma/ |
| D | dma-common.yaml | 22 # Should be enough
37 # Should be enough
|
| /linux-6.1.9/Documentation/devicetree/bindings/mfd/ |
| D | syscon.yaml | 11 of miscellaneous registers. The registers are not cohesive enough to
78 maxItems: 5 # Should be enough
|
| /linux-6.1.9/Documentation/arm64/ |
| D | memory.rst | 126 spaces, the VMEMMAP must be sized large enough for 52-bit VAs and
127 also must be sized large enough to accommodate a fixed PAGE_OFFSET.
141 sized large enough or that addresses are positioned close enough for
|
| /linux-6.1.9/Documentation/watchdog/ |
| D | watchdog-pm.rst | 18 userspace enough time to resume. [1] [2]
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/devicetree/bindings/hwmon/ |
| D | iio-hwmon.yaml | 22 maxItems: 8 # Should be enough
|
| /linux-6.1.9/tools/testing/memblock/ |
| D | TODO | 8 likely that the current MEM_SIZE won't be enough for these
|
| /linux-6.1.9/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
|
| /linux-6.1.9/tools/memory-model/litmus-tests/ |
| D | LB+fencembonceonce+ctrlonceonce.litmus | 9 * combination of a control dependency and a full memory barrier are enough
|
| /linux-6.1.9/drivers/staging/olpc_dcon/ |
| D | TODO | 9 - see if vx855 gpio API can be made similar enough to cs5535 so we can
|
| /linux-6.1.9/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
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/devicetree/bindings/fsi/ |
| D | fsi-master-gpio.txt | 16 GPIO block is running at a low enough
|
| /linux-6.1.9/arch/parisc/math-emu/ |
| D | README | 5 enough to update our copies with later changes from HP-UX -- it'll
|
| /linux-6.1.9/arch/arm/boot/compressed/ |
| D | head-xscale.S | 23 add r3, r2, #0x10000 @ 64 kb is quite enough...
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/devicetree/bindings/ |
| D | .yamllint | 5 # 80 chars should be enough, but don't fail if a line is longer
|
| /linux-6.1.9/arch/arm64/boot/dts/qcom/ |
| D | msm8996-v3.0.dtsi | 16 * the GPU. Funnily enough, it's simpler to make it an
|
12345678910>>...17