Home
last modified time | relevance | path

Searched refs:enough (Results 1 – 25 of 456) sorted by relevance

12345678910>>...19

/linux/drivers/mtd/ubi/
A Dfastmap-wl.c190 int enough; in ubi_refill_pools_and_lock() local
221 enough = 0; in ubi_refill_pools_and_lock()
233 enough++; in ubi_refill_pools_and_lock()
250 enough++; in ubi_refill_pools_and_lock()
252 if (enough == 2) in ubi_refill_pools_and_lock()
/linux/Documentation/devicetree/bindings/opp/
A Dopp-v2-base.yaml78 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
/linux/Documentation/fb/
A Dsa1100fb.rst18 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/Documentation/devicetree/bindings/dma/
A Ddma-common.yaml22 # Should be enough
37 # Should be enough
/linux/Documentation/devicetree/bindings/mfd/
A Dsyscon-common.yaml11 of miscellaneous registers. The registers are not cohesive enough to
36 maxItems: 5 # Should be enough
A Dti,nspire-misc.yaml15 of miscellaneous registers. The registers are not cohesive enough to
/linux/Documentation/devicetree/bindings/dma/ti/
A Dk3-pktdma.yaml79 # Should be enough
90 # Should be enough
101 # Should be enough
112 # Should be enough
A Dk3-udma.yaml103 # Should be enough
112 # Should be enough
121 # Should be enough
/linux/Documentation/mm/damon/
A Dindex.rst11 - *accurate* (the monitoring output is useful enough for DRAM level memory
13 - *light-weight* (the monitoring overhead is low enough to be applied online),
/linux/Documentation/arch/arm64/
A Dmemory.rst124 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
/linux/Documentation/watchdog/
A Dwatchdog-pm.rst18 userspace enough time to resume. [1] [2]
/linux/Documentation/userspace-api/media/dvb/
A Ddvb-frontend-parameters.rst14 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/Documentation/devicetree/bindings/hwmon/
A Diio-hwmon.yaml22 maxItems: 51 # Should be enough
/linux/Documentation/driver-api/gpio/
A Dusing-gpio.rst17 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/tools/memory-model/litmus-tests/
A DLB+fencembonceonce+ctrlonceonce.litmus9 * combination of a control dependency and a full memory barrier are enough
/linux/drivers/staging/olpc_dcon/
A DTODO9 - see if vx855 gpio API can be made similar enough to cs5535 so we can
/linux/tools/testing/selftests/net/packetdrill/
A Dtcp_slow_start_slow-start-ack-per-2pkt-send-5pkt.pkt3 // less than the current cwnd, and not big enough to bump up cwnd.
A Dtcp_slow_start_slow-start-ack-per-2pkt-send-6pkt.pkt3 // less than the current cwnd, but still big enough that in slow
/linux/Documentation/userspace-api/media/mediactl/
A Dmedia-ioc-enum-links.rst43 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/Documentation/userspace-api/media/rc/
A Dlirc-get-features.rst61 as long as the kernel is recent enough. Use the
153 transmit, as long as the kernel is recent enough. Use the
/linux/Documentation/devicetree/bindings/fsi/
A Dfsi-master-gpio.txt16 GPIO block is running at a low enough
/linux/arch/arm/boot/compressed/
A Dhead-xscale.S23 add r3, r2, #0x10000 @ 64 kb is quite enough...
/linux/arch/parisc/math-emu/
A DREADME5 enough to update our copies with later changes from HP-UX -- it'll
/linux/Documentation/scheduler/
A Dsched-nice-design.rst83 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/Documentation/devicetree/bindings/
A D.yamllint10 # 80 chars should be enough, but don't fail if a line is longer

Completed in 25 milliseconds

12345678910>>...19