Searched full:still (Results 1 – 25 of 701) sorted by relevance
12345678910>>...29
| /Documentation/devicetree/bindings/power/reset/ |
| D | regulator-poweroff.yaml | 14 calling regulator_force_disable(). If the power is still on and the
15 CPU still running after a 3000ms delay, a warning is emitted.
|
| /Documentation/gpu/rfc/ |
| D | i915_gem_lmem.rst | 10 * Merge basic HW enabling of DG1(still without pciid)
12 * At this point we can still make changes, but importantly this lets us
|
| /Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 29 This is so, since the pages are still mapped to physical memory, and thus all
34 there is still a scenario when we can lose soft dirty bits -- a task
|
| /Documentation/virt/kvm/arm/ |
| D | pkvm.rst | 12 without relying on whizz-bang features in hardware, but still allowing room for
30 in either protected or non-protected state, although the hypervisor is still
41 If you're still keen, then here is an incomplete list of caveats that apply
|
| D | hyp-abi.rst | 15 here is still valid though, as it allows the kernel to kexec when
20 mode, but still needs to interact with it, allowing a built-in
|
| /Documentation/admin-guide/ |
| D | abi-obsolete.rst | 4 Documents interfaces that are still remaining in the kernel, but are
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-intro.rst | 16 data can still be stored and retrieved in the proprietary format. For
18 Applications can still capture and save the data in the compressed
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-reqbufs.rst | 15 .. warning:: this API is still experimental
63 buffers, however this cannot succeed when any buffers are still mapped.
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 24 need to use volatile as well. If volatile is still necessary, there is
45 If shared_data were declared volatile, the locking would still be
73 There are still a few rare situations where volatile makes sense in the
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 53 But the fundamental HZ-sensitive property for nice+19 still remained,
55 terms of CPU utilization, we only got complaints about it (still) being
62 The second (less frequent but still periodically occurring) complaint
|
| /Documentation/driver-api/tty/ |
| D | tty_driver.rst | 50 tty_port part in `Registering Devices`_ is still relevant there.
95 If that is not possible, the driver still can link the tty_port to a specific
96 index *before* the actual registration by tty_port_link_device(). If it still
|
| /Documentation/fb/ |
| D | aty128fb.rst | 21 * still experimental.
72 - This driver is still experimental and is not finished. Too many
|
| /Documentation/networking/ |
| D | segmentation-offloads.rst | 61 still receive them from tuntap and similar devices. Offload of UDP-based
62 tunnel protocols is still supported.
141 offloads or tunnel offloads with checksum to still make use of segmentation.
154 SCTP - despite the lack of hardware support - can still take advantage of
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 81 - but still the ability to do busy polling for new data to achieve the
165 successfully advance producer counter. At that point, data is still not yet
168 record is still being worked on, and discard bit, which might be set at commit
190 last data page would be first data page again, and thus the sample will still
198 the record being committed. If not, consumer still has to catch up and thus
|
| D | index.rst | 8 This kernel side documentation is still work in progress.
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-swap | 14 still used for tmpfs etc. other users. If set to
|
| /Documentation/admin-guide/media/ |
| D | ipu3.rst | 241 - "VIDEO" or "STILL", "VIDEO" mode is commonly used for video frames capture,
242 and "STILL" is used for still frame capture. However, you can also select
243 "VIDEO" to capture still frames if you want to capture images with less system
244 load and power. For "STILL" mode, ImgU will try to use smaller BDS factor and
246 high quality images. Besides, "STILL" mode need XNR3 to do noise reduction,
247 hence "STILL" mode will need more power and memory bandwidth than "VIDEO" mode.
248 TNR will be enabled in "VIDEO" mode and bypassed by "STILL" mode. ImgU is
253 "VIDEO" and "STILL" mode, mandatory input and main output node should be
261 "if_to_osys_primary_striped" is selected for "STILL".
284 (e.g 0 for video mode or 1 for still mode) through the control id 0x009819a1 as
|
| /Documentation/admin-guide/RAS/ |
| D | error-decoding.rst | 13 errors. If not, one can still decode such errors by supplying the
|
| /Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 54 may still be written to 'ndbusX/firmware/activate' as an override to
83 Runtime firmware activation failed, but the firmware can still be
|
| /Documentation/driver-api/usb/ |
| D | persist.rst | 23 device is still attached or perhaps it was removed and a different
35 system woke up, who cares? It'll still work the same when you type on
124 with it, unplug the flash device, plug it back in later, and still
143 device is still plugged into the port as before. But the checks
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | eeti.txt | 9 - attn-gpios: A handle to a GPIO to check whether interrupt is still
|
| /Documentation/devicetree/bindings/pci/ |
| D | fsl,pci.txt | 5 all mezzanines to be PCI-X Agents, but one per system may still
|
| /Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 26 still be processed unmodified by existing Non-secure software (and in
29 Note that it is still valid for bindings intended for purely Secure
|
| /Documentation/admin-guide/LSM/ |
| D | Yama.rst | 33 parent to a child process (i.e. direct "gdb EXE" and "strace EXE" still
35 still work as root).
|
| /Documentation/arch/x86/ |
| D | kernel-stacks.rst | 75 in many cases to still output an oops.
129 still print it, but we print a '?'. It can mean two things:
147 we still print out the real call chain as well - just with more question
|
12345678910>>...29