Searched full:requiring (Results 1 – 25 of 90) sorted by relevance
1234
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | andestech,ativic32.txt | 4 suitable for a simpler SoC platform not requiring a more sophisticated and
|
| D | qcom,pdc.txt | 10 controller PDC is next in hierarchy, followed by others. Drivers requiring
|
| /Documentation/userspace-api/media/v4l/ |
| D | app-pri.rst | 23 V4L2 and drivers not supporting these ioctls. Applications requiring a
|
| D | rw.rst | 22 However this is also the simplest I/O method, requiring little or no
|
| /Documentation/filesystems/ |
| D | inotify.rst | 36 can use epoll, but requiring both is a silly and extraneous requirement.
39 want: Users initialize inotify, once, and add n watches, requiring but one
|
| D | path-lookup.txt | 106 However when a dentry is renamed, its hash value can change, requiring it to be
342 drop rcu that fail due to d_seq failure and requiring the entire path lookup
345 routine requiring rcu drop, permission for permission check requiring drop,
346 and link for symlink traversal requiring drop.
|
| /Documentation/admin-guide/kdump/ |
| D | vmcoreinfo.rst | 227 user-space tools to view the kernel log buffer without requiring the
241 requiring the declaration of the structure.
253 user-space tools to be able to read descriptors without requiring
268 requiring the declaration of the structure.
280 user-space tools to be able to read the information without requiring
294 requiring the declaration of the structure.
307 user-space tools to access the long value without requiring the
|
| /Documentation/fb/ |
| D | sa1100fb.rst | 25 For active displays or displays requiring additional configuration
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | maxim,max20730.yaml | 16 with PMBus for applications operating from 4.5V to 16V and requiring
|
| /Documentation/devicetree/bindings/sound/ |
| D | cirrus,cs4234.yaml | 23 nondelayed path into the DAC outputs for input signals requiring a
|
| /Documentation/devicetree/bindings/dma/ |
| D | arm-pl330.txt | 35 Client drivers (device nodes requiring dma transfers from dev-to-mem or
|
| /Documentation/driver-api/ |
| D | regulator.rst | 43 may either be static, requiring only a fixed supply, or dynamic,
44 requiring active management of the regulator at runtime.
|
| /Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 49 calls requiring the non-uevent therefore need to implement their own firmware
|
| /Documentation/powerpc/ |
| D | cpu_features.rst | 9 PPC Linux kernel to support a variety of PowerPC CPUs without requiring
|
| /Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 25 of specialized equipment that is not produced by the numbers, requiring
|
| /Documentation/process/ |
| D | programming-language.rst | 17 requiring third-party patches.
|
| D | 3.Early-stage.rst | 99 requiring months or years of effort before the code can be brought up to
222 without requiring public disclosure of the project.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-pxa-pci-ce4100.txt | 27 requiring custom device driver code.
|
| /Documentation/accounting/ |
| D | delay-accounting.rst | 56 are sent to userspace without requiring a command. If it is the last exiting
|
| /Documentation/core-api/ |
| D | protection-keys.rst | 17 protections, but without requiring modification of the page tables
|
| /Documentation/devicetree/bindings/iommu/ |
| D | qcom,iommu.txt | 5 and optionally requiring additional configuration to route context irqs
|
| /Documentation/devicetree/bindings/arm/ |
| D | vexpress-sysreg.txt | 22 by subnodes, each of them requiring the following properties:
|
| /Documentation/driver-api/usb/ |
| D | anchors.rst | 7 A USB driver needs to support some callbacks requiring
|
| /Documentation/dev-tools/kunit/ |
| D | index.rst | 36 without requiring a virtual machine or separate hardware.
|
| /Documentation/admin-guide/laptops/ |
| D | toshiba_haps.rst | 47 given the fact that such drives have no movable parts, and thus, not requiring
|
1234