Home
last modified time | relevance | path

Searched full:requiring (Results 1 – 25 of 392) sorted by relevance

12345678910>>...16

/linux/drivers/gpu/drm/msm/disp/mdp5/
H A Dmdp5_mixer.c87 * 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()
/linux/Documentation/admin-guide/kdump/
H A Dvmcoreinfo.rst233 user-space tools to view the kernel log buffer without requiring the
247 requiring the declaration of the structure.
259 user-space tools to be able to read descriptors without requiring
274 requiring the declaration of the structure.
286 user-space tools to be able to read the information without requiring
300 requiring the declaration of the structure.
313 user-space tools to access the long value without requiring the
/linux/include/linux/
H A Dcrc32.h27 * requiring only crc1, crc2, and len2. Note: If seq_full denotes
55 * requiring only crc1, crc2, and len2. Note: If seq_full denotes
H A Dlibnvdimm.h39 * dimm contents have changed requiring invalidation of CPU caches prior
73 /* mark newly adjusted resources as requiring a label update */
/linux/Documentation/filesystems/
H A Dinotify.rst36 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
H A Dpath-lookup.txt106 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.
/linux/arch/arm/include/asm/
H A Didmap.h8 /* Tag a function as requiring to be executed via an identity mapping. */
/linux/arch/mips/include/asm/
H A Dmmu.h21 /* wait queue for threads requiring an emuframe */
H A Dpm-cps.h13 * enter or exit states requiring CM or CPC assistance in unison.
/linux/Documentation/driver-api/
H A Dregulator.rst43 may either be static, requiring only a fixed supply, or dynamic,
44 requiring active management of the regulator at runtime.
H A Dvfio-pci-device-specific-driver-acceptance.rst15 requiring device specific knowledge, ex. saving and loading device
/linux/Documentation/ABI/testing/
H A Dima_policy165 Example of a 'measure' rule requiring fs-verity's digests
171 Example of 'measure' and 'appraise' rules requiring fs-verity
/linux/Documentation/userspace-api/media/v4l/
H A Dapp-pri.rst23 V4L2 and drivers not supporting these ioctls. Applications requiring a
H A Drw.rst22 However this is also the simplest I/O method, requiring little or no
/linux/drivers/mtd/nand/
H A DKconfig46 ECC codes. They are used with NAND devices requiring more than 1 bit
/linux/drivers/media/pci/ddbridge/
H A DKconfig41 with certain SATA controllers, requiring a reload of the ddbridge
/linux/kernel/
H A DKconfig.hz47 systems requiring fast interactive responses to events.
/linux/Documentation/fb/
H A Dsa1100fb.rst25 For active displays or displays requiring additional configuration
/linux/drivers/firmware/
H A DKconfig87 requiring any access to /dev/mem at all. Tables are found
236 active, requiring some core operations to be performed by the secure
/linux/Documentation/devicetree/bindings/hwmon/
H A Dmaxim,max20730.yaml16 with PMBus for applications operating from 4.5V to 16V and requiring
/linux/fs/nfsd/
H A Dlockd.c5 * requiring the nfs client to be compiled in/loaded, and vice versa.
/linux/Documentation/devicetree/bindings/sound/
H A Dcirrus,cs4234.yaml23 nondelayed path into the DAC outputs for input signals requiring a
/linux/tools/testing/selftests/powerpc/tm/
H A Dtm-sigreturn.c11 * restoring the potential TM SPRS from the signal frame is requiring to not be
/linux/Documentation/userspace-api/gpio/
H A Derror-codes.rst68 - Typically returned when a feature requiring interrupt support was
/linux/Documentation/driver-api/firmware/
H A Dfirmware_cache.rst49 calls requiring the non-uevent therefore need to implement their own firmware

12345678910>>...16