Home
last modified time | relevance | path

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

12345678910>>...17

/linux-6.3-rc2/drivers/mtd/ubi/
A Dfastmap-wl.c136 int enough; in ubi_refill_pools() local
160 enough = 0; in ubi_refill_pools()
172 enough++; in ubi_refill_pools()
186 enough++; in ubi_refill_pools()
188 if (enough == 2) in ubi_refill_pools()
/linux-6.3-rc2/Documentation/devicetree/bindings/dma/ti/
A Dk3-pktdma.yaml65 # Should be enough
76 # Should be enough
87 # Should be enough
98 # Should be enough
A Dk3-bcdma.yaml91 # Should be enough
102 # Should be enough
113 # Should be enough
A Dk3-udma.yaml92 # Should be enough
101 # Should be enough
110 # Should be enough
/linux-6.3-rc2/Documentation/devicetree/bindings/opp/
A Dopp-v2-base.yaml80 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.3-rc2/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-6.3-rc2/Documentation/devicetree/bindings/dma/
A Ddma-common.yaml22 # Should be enough
37 # Should be enough
/linux-6.3-rc2/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-6.3-rc2/Documentation/userspace-api/media/v4l/
A Dvidioc-subdev-g-routing.rst56 provided ``num_routes`` is not big enough to contain all the available routes
58 value of the ``num_routes`` field. Application should then reserve enough memory
136 The application provided ``num_routes`` is not big enough to contain
/linux-6.3-rc2/Documentation/devicetree/bindings/mfd/
A Dsyscon.yaml11 of miscellaneous registers. The registers are not cohesive enough to
76 maxItems: 5 # Should be enough
/linux-6.3-rc2/Documentation/arm64/
A Dmemory.rst126 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.3-rc2/Documentation/watchdog/
A Dwatchdog-pm.rst18 userspace enough time to resume. [1] [2]
/linux-6.3-rc2/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-6.3-rc2/Documentation/devicetree/bindings/hwmon/
A Diio-hwmon.yaml22 maxItems: 8 # Should be enough
/linux-6.3-rc2/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-6.3-rc2/drivers/staging/olpc_dcon/
A DTODO9 - see if vx855 gpio API can be made similar enough to cs5535 so we can
/linux-6.3-rc2/tools/memory-model/litmus-tests/
A DLB+fencembonceonce+ctrlonceonce.litmus9 * combination of a control dependency and a full memory barrier are enough
/linux-6.3-rc2/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-6.3-rc2/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-6.3-rc2/Documentation/devicetree/bindings/fsi/
A Dfsi-master-gpio.txt16 GPIO block is running at a low enough
/linux-6.3-rc2/arch/parisc/math-emu/
A DREADME5 enough to update our copies with later changes from HP-UX -- it'll
/linux-6.3-rc2/arch/arm/boot/compressed/
A Dhead-xscale.S23 add r3, r2, #0x10000 @ 64 kb is quite enough...
/linux-6.3-rc2/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-6.3-rc2/Documentation/devicetree/bindings/
A D.yamllint5 # 80 chars should be enough, but don't fail if a line is longer
/linux-6.3-rc2/arch/arm64/boot/dts/qcom/
A Dmsm8996-v3.0.dtsi16 * the GPU. Funnily enough, it's simpler to make it an

Completed in 33 milliseconds

12345678910>>...17