Searched full:requiring (Results 1 – 25 of 324) sorted by relevance
12345678910>>...13
| /kernel/linux/linux-5.10/drivers/gpu/drm/msm/disp/mdp5/ |
| D | mdp5_mixer.c | 87 * without requiring a full modeset if we had already in mdp5_mixer_assign()
91 * result in the CRTC requiring a full modeset, even in mdp5_mixer_assign()
94 * so easily. For now, ignore the possibility of requiring in mdp5_mixer_assign()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | crc32.h | 25 * requiring only crc1, crc2, and len2. Note: If seq_full denotes
52 * requiring only crc1, crc2, and len2. Note: If seq_full denotes
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/arch/arm/include/asm/ |
| D | idmap.h | 8 /* Tag a function as requiring to be executed via an identity mapping. */
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | mmu.h | 21 /* wait queue for threads requiring an emuframe */
|
| D | pm-cps.h | 13 * enter or exit states requiring CM or CPC assistance in unison.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/drivers/media/pci/ddbridge/ |
| D | Kconfig | 41 with certain SATA controllers, requiring a reload of the ddbridge
|
| /kernel/linux/linux-5.10/kernel/ |
| D | Kconfig.hz | 47 systems requiring fast interactive responses to events.
|
| /kernel/linux/linux-5.10/arch/x86/kernel/ |
| D | resource.c | 44 * cards requiring a memory range, e.g. the i82365 PCMCIA controller. in arch_remove_reservations()
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | sa1100fb.rst | 25 For active displays or displays requiring additional configuration
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwmon/ |
| D | maxim,max20730.yaml | 16 with PMBus for applications operating from 4.5V to 16V and requiring
|
| /kernel/linux/linux-5.10/fs/nfsd/ |
| D | lockd.c | 5 * requiring the nfs client to be compiled in/loaded, and vice versa.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | cirrus,cs4234.yaml | 23 nondelayed path into the DAC outputs for input signals requiring a
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/ |
| D | arm-pl330.txt | 35 Client drivers (device nodes requiring dma transfers from dev-to-mem or
|
| /kernel/linux/linux-5.10/tools/testing/selftests/powerpc/tm/ |
| D | tm-sigreturn.c | 11 * restoring the potential TM SPRS from the signal frame is requiring to not be
|
| /kernel/linux/linux-5.10/Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 49 calls requiring the non-uevent therefore need to implement their own firmware
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | programming-language.rst | 17 requiring third-party patches.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/gpio/ |
| D | using-gpio.rst | 25 of specialized equipment that is not produced by the numbers, requiring
|
12345678910>>...13