Searched full:enough (Results 1 – 25 of 300) sorted by relevance
12345678910>>...12
| /Documentation/devicetree/bindings/dma/ |
| D | dma-common.yaml | 22 # Should be enough
37 # Should be enough
|
| /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/devicetree/bindings/mfd/ |
| D | syscon.yaml | 11 of miscellaneous registers. The registers are not cohesive enough to
57 maxItems: 4 # Should be enough
|
| D | ti,j721e-system-controller.yaml | 13 of miscellaneous registers. The registers are not cohesive enough to
|
| /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/dma/ti/ |
| D | k3-udma.yaml | 97 # Should be enough
106 # Should be enough
115 # Should be enough
|
| /Documentation/devicetree/bindings/ |
| D | .yamllint | 5 # 80 chars should be enough, but don't fail if a line is longer
|
| /Documentation/watchdog/ |
| D | watchdog-pm.rst | 18 userspace enough time to resume. [1] [2]
|
| /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/arm64/ |
| D | memory.rst | 131 spaces, the VMEMMAP must be sized large enough for 52-bit VAs and
132 also must be sized large enough to accommodate a fixed PAGE_OFFSET.
146 sized large enough or that addresses are positioned close enough for
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi-master-gpio.txt | 16 GPIO block is running at a low enough
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-features.rst | 61 as long as the kernel is recent enough. Use the
171 transmit, as long as the kernel is recent enough. Use the
|
| /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/admin-guide/cgroup-v1/ |
| D | hugetlb.rst | 75 there are enough available on the machine for all the users to avoid processes
101 the HugeTLB usage of all the tasks in the system and make sure there is enough
|
| /Documentation/devicetree/bindings/iio/imu/ |
| D | inv_mpu6050.txt | 33 simple enough to be described using the i2c-gate binding. See
|
| /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 | 35 While in most cases tracking memory changes by #PF-s is more than enough
|
| D | concepts.rst | 194 until enough memory pages are reclaimed to satisfy the request.
218 kernel will be unable to reclaim enough memory to continue to operate. In
223 enough memory will be freed to continue normal operation.
|
| /Documentation/userspace-api/media/v4l/ |
| D | func-open.rst | 72 Not enough kernel memory was available to complete the request.
|
| /Documentation/input/devices/ |
| D | edt-ft5x06.rst | 50 big enough to contain num_x * num_y * 2 bytes.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-fpga-manager | 12 The intent is to provide enough detail that if something goes
|
| /Documentation/maintainer/ |
| D | modifying-patches.rst | 16 name, all enclosed in square brackets, is noticeable enough to make it obvious
|
12345678910>>...12