/Documentation/userspace-api/media/ |
D | videodev2.h.rst.exceptions | 201 # V4L2 pix flags 203 replace define V4L2_PIX_FMT_FLAG_PREMUL_ALPHA format-flags 207 # V4L2 format flags 208 replace define V4L2_FMT_FLAG_COMPRESSED fmtdesc-flags 209 replace define V4L2_FMT_FLAG_EMULATED fmtdesc-flags 210 replace define V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM fmtdesc-flags 211 replace define V4L2_FMT_FLAG_DYN_RESOLUTION fmtdesc-flags 212 replace define V4L2_FMT_FLAG_ENC_CAP_FRAME_INTERVAL fmtdesc-flags 213 replace define V4L2_FMT_FLAG_CSC_COLORSPACE fmtdesc-flags 214 replace define V4L2_FMT_FLAG_CSC_XFER_FUNC fmtdesc-flags [all …]
|
/Documentation/translations/zh_CN/core-api/irq/ |
D | irqflags-tracing.rst | 17 “irq-flags tracing”(中断标志追踪)功能可以 “追踪” hardirq和softirq的状态,它让 26 架构对这一点的支持当然不属于“微不足道”的范畴,因为很多低级的汇编代码都要处理irq-flags 27 的状态变化。但是一个架构可以以一种相当直接且无风险的方式启用irq-flags-tracing。 33 然后还需要做一些功能上的改变来实现对irq-flags-tracing的支持: 36 函数的调用。锁验证器会密切关注 “real”的irq-flags是否与 “virtual”的irq-flags 38 irq-flags-track的大部分时间都是在这种状态下度过的:看看lockdep的警告,试着 45 一般来说,在一个架构中,不完整的irq-flags-tracing实现是没有风险的:lockdep
|
/Documentation/core-api/irq/ |
D | irqflags-tracing.rst | 2 IRQ-flags state tracing 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in 20 category, because lots of lowlevel assembly code deal with irq-flags 21 state changes. But an architecture can be irq-flags-tracing enabled in a 30 irq-flags-tracing support: 34 closely guards whether the 'real' irq-flags matches the 'virtual' 35 irq-flags state, and complains loudly (and turns itself off) if the 37 irq-flags-tracing is spent in this state: look at the lockdep 40 lockdep complaint in the irq-flags-tracing functions arch support is 46 In general there is no risk from having an incomplete irq-flags-tracing
|
/Documentation/netlink/specs/ |
D | rt_addr.yaml | 22 name: ifa-flags 24 enum: ifa-flags 25 enum-as-flags: true 50 name: ifa-flags 51 type: flags 108 name: ifa-flags 110 enum: ifa-flags 111 enum-as-flags: true 136 - ifa-flags 153 - ifa-flags
|
/Documentation/translations/zh_CN/driver-api/ |
D | io_ordering.rst | 28 CPU A: spin_lock_irqsave(&dev_lock, flags) 32 CPU A: spin_unlock_irqrestore(&dev_lock, flags) 34 CPU B: spin_lock_irqsave(&dev_lock, flags) 38 CPU B: spin_unlock_irqrestore(&dev_lock, flags) 45 CPU A: spin_lock_irqsave(&dev_lock, flags) 50 CPU A: spin_unlock_irqrestore(&dev_lock, flags) 52 CPU B: spin_lock_irqsave(&dev_lock, flags) 57 CPU B: spin_unlock_irqrestore(&dev_lock, flags)
|
/Documentation/filesystems/ |
D | fiemap.rst | 22 __u32 fm_flags; /* FIEMAP_FLAG_* flags for request (in/out) */ 37 Certain flags to modify the way in which mappings are looked up can be 39 flags, it will return EBADR and the contents of fm_flags will contain 40 the set of flags which caused the error. If the kernel is compatible 41 with all flags passed, the contents of fm_flags will be unmodified. 54 The following flags can be set in fm_flags: 77 flag set (see the next section on extent flags). 89 __u32 fe_flags; /* FIEMAP_EXTENT_* flags for this extent */ 100 The fe_flags field contains flags which describe the extent returned. 105 Some flags are intentionally vague and will always be set in the [all …]
|
/Documentation/driver-api/ |
D | io_ordering.rst | 18 CPU A: spin_lock_irqsave(&dev_lock, flags) 22 CPU A: spin_unlock_irqrestore(&dev_lock, flags) 24 CPU B: spin_lock_irqsave(&dev_lock, flags) 28 CPU B: spin_unlock_irqrestore(&dev_lock, flags) 35 CPU A: spin_lock_irqsave(&dev_lock, flags) 40 CPU A: spin_unlock_irqrestore(&dev_lock, flags) 42 CPU B: spin_lock_irqsave(&dev_lock, flags) 47 CPU B: spin_unlock_irqrestore(&dev_lock, flags)
|
/Documentation/translations/zh_TW/ |
D | io_ordering.txt | 35 CPU A: spin_lock_irqsave(&dev_lock, flags) 39 CPU A: spin_unlock_irqrestore(&dev_lock, flags) 41 CPU B: spin_lock_irqsave(&dev_lock, flags) 45 CPU B: spin_unlock_irqrestore(&dev_lock, flags) 52 CPU A: spin_lock_irqsave(&dev_lock, flags) 57 CPU A: spin_unlock_irqrestore(&dev_lock, flags) 59 CPU B: spin_lock_irqsave(&dev_lock, flags) 64 CPU B: spin_unlock_irqrestore(&dev_lock, flags)
|
/Documentation/translations/zh_CN/locking/ |
D | spinlocks.rst | 21 unsigned long flags; 23 spin_lock_irqsave(&xxx_lock, flags); 25 spin_unlock_irqrestore(&xxx_lock, flags); 67 unsigned long flags; 69 read_lock_irqsave(&xxx_lock, flags); 71 read_unlock_irqrestore(&xxx_lock, flags); 73 write_lock_irqsave(&xxx_lock, flags); 75 write_unlock_irqrestore(&xxx_lock, flags);
|
/Documentation/userspace-api/media/v4l/ |
D | vidioc-g-selection.rst | 46 additional targets. The ``flags`` and ``reserved`` fields of struct 70 ``flags`` field must be set to one of the following: 94 :c:type:`v4l2_selection` ``flags``. 111 constraints flags have to be violated at then ``ERANGE`` is returned. The 115 Selection targets and flags are documented in 124 Size adjustments with constraint flags. 126 Behaviour of rectangle adjustment for different constraint flags. 148 - ``flags`` 149 - Flags controlling the selection rectangle adjustments, refer to 150 :ref:`selection flags <v4l2-selection-flags>`. [all …]
|
D | vidioc-encoder-cmd.rst | 49 ``flags`` field for additional information. 82 - ``flags`` 83 - Flags to go with the command, see :ref:`encoder-flags`. If no 84 flags are defined for this command, drivers and applications must 104 this command does nothing. No flags are defined for this command. 119 the drain sequence as documented in :ref:`encoder`. No flags or other 127 already paused, this command does nothing. No flags are defined 134 flags are defined for this command. 138 .. _encoder-flags: 140 .. flat-table:: Encoder Command Flags
|
/Documentation/userspace-api/media/dvb/ |
D | fe-set-frontend-tune-mode.rst | 13 FE_SET_FRONTEND_TUNE_MODE - Allow setting tuner mode flags to the frontend. 20 ``int ioctl(int fd, FE_SET_FRONTEND_TUNE_MODE, unsigned int flags)`` 28 ``flags`` 29 Valid flags: 43 Allow setting tuner mode flags to the frontend, between 0 (normal) or
|
D | dmx-mmap.rst | 25 .. c:function:: void *mmap( void *start, size_t length, int prot, int flags, int fd, off_t offset ) 46 this combination of flags. 48 ``flags`` 49 The ``flags`` parameter specifies the type of the mapped object, 60 One of the ``MAP_SHARED`` or ``MAP_PRIVATE`` flags must be set. 68 flags. 108 The ``flags`` or ``prot`` value is not supported.
|
/Documentation/devicetree/bindings/thermal/ |
D | spear-thermal.txt | 6 - st,thermal-flags: flags used to enable thermal sensor 13 st,thermal-flags = <0x7000>;
|
/Documentation/arch/x86/ |
D | cpuinfo.rst | 4 x86 Feature Flags 10 On x86, flags appearing in /proc/cpuinfo have an X86_FEATURE definition 13 an X86_FEATURE_* defined. These flags represent hardware features as 25 can explain missing flags: the expected feature failed to enable, the feature 29 shows features which the kernel supports. For a full list of CPUID flags 32 How are feature flags created? 35 a: Feature flags can be derived from the contents of CPUID leaves. 41 cpufeatures.h, and if it is detected at run time, the flags will be 45 b: Flags can be from scattered CPUID-based features. 60 c: Flags can be created synthetically under certain conditions for hardware features. [all …]
|
/Documentation/netlink/ |
D | genetlink.yaml | 41 description: List of type and constant definitions (enums, flags, defines). 54 enum: [ const, enum, flags ] 61 # For enum and flags 63 description: For enum or flags the literal initializer for the first value. 66 description: For enum or flags array of values. 147 enum-as-flags: 149 Treat the enum as flags. In most cases enum is either used as flags or as values. 158 flags-mask: 159 … description: Name of the flags constant on which to base mask (unsigned scalar types only). 237 flags: &cmd_flags [all …]
|
D | netlink-raw.yaml | 60 description: List of type and constant definitions (enums, flags, defines). 73 enum: [ const, enum, flags, struct ] # Trim 80 # For enum and flags 82 description: For enum or flags the literal initializer for the first value. 85 description: For enum or flags array of values. 135 enum-as-flags: 137 Treat the enum as flags. In most cases enum is either used as flags or as values. 220 enum-as-flags: 222 Treat the enum as flags. In most cases enum is either used as flags or as values. 231 flags-mask: [all …]
|
D | genetlink-c.yaml | 52 description: List of type and constant definitions (enums, flags, defines). 65 enum: [ const, enum, flags ] 72 # For enum and flags 74 description: For enum or flags the literal initializer for the first value. 77 description: For enum or flags array of values. 174 enum-as-flags: 176 Treat the enum as flags. In most cases enum is either used as flags or as values. 185 flags-mask: 186 … description: Name of the flags constant on which to base mask (unsigned scalar types only). 268 flags: &cmd_flags [all …]
|
/Documentation/userspace-api/ |
D | unshare.rst | 110 since flags in clone(int flags, void \*stack) specifies what should 111 be shared, similar flags in unshare(int flags) should specify 113 the meaning of the flags from the way they are used in clone(2). 118 new context flags without requiring a rebuild of old applications. 119 If and when new context flags are added, unshare() design should allow 131 int unshare(int flags); 145 The flags argument specifies one or bitwise-or'ed of several of 187 Depending on the flags argument, the unshare() system call allocates 218 1) Check flags to force missing, but implied, flags 222 structure, if the appropriate bit is set in the flags argument. [all …]
|
D | iommu.rst | 56 method. The IOMMU driver processes the data based on flags which 91 headers. Backward compatibility is supported per feature flags. 94 on an older kernel if new feature flags are not supported by older 96 not be an issue in that only existing flags are used. 131 __u32 flags; 136 freedom to bundle the data as well as parse data size based on its own flags. 139 and flags (or the equivalent) are also embedded in the IOMMU UAPI data 165 VFIO is responsible for checking its own argsz and flags. It then 174 reserved bits in flags, padding fields, and unsupported version. 176 fields or flags are used. [all …]
|
/Documentation/devicetree/bindings/rtc/ |
D | moxa,moxart-rtc.txt | 6 - rtc-sclk-gpios : RTC sclk gpio, with zero flags 7 - rtc-data-gpios : RTC data gpio, with zero flags 8 - rtc-reset-gpios : RTC reset gpio, with zero flags
|
/Documentation/gpu/rfc/ |
D | i915_vm_bind.h | 33 * See struct drm_i915_gem_vm_control flags. 63 * @flags: Supported flags are: 71 __u32 flags; member 128 * @flags: Supported flags are: 133 * Note that @fence carries its own flags. 135 __u64 flags; member 190 * @flags: Currently reserved, MBZ. 192 * Note that @fence carries its own flags. 194 __u64 flags; member 251 /** @flags: Currently reserved, MBZ */ [all …]
|
/Documentation/core-api/ |
D | memory-allocation.rst | 14 Most of the memory allocation APIs use GFP flags to express how that 18 Diversity of the allocation APIs combined with the numerous GFP flags 27 flags must be used. 29 Get Free Page flags 32 The GFP flags control the allocators behavior. They tell what memory 35 :ref:`Documentation/core-api/mm-api.rst <mm-api-gfp-flags>` provides 36 reference documentation for the GFP flags and their combinations and 57 ``GFP_HIGHUSER`` or ``GFP_HIGHUSER_MOVABLE`` flags. The longer 80 Other legacy GFP flags are ``GFP_DMA`` and ``GFP_DMA32``. They are 83 driver for a device with such restrictions, avoid using these flags. [all …]
|
/Documentation/userspace-api/media/mediactl/ |
D | media-func-open.rst | 22 .. c:function:: int open( const char *device_name, int flags ) 30 ``flags`` 31 Open flags. Access mode must be either ``O_RDONLY`` or ``O_RDWR``. 32 Other flags have no effect.
|
/Documentation/translations/zh_CN/userspace-api/ |
D | futex2.rst | 31 unsigned int flags, struct timespec *timeout, clockid_t clockid) 36 __u32 flags; 41 地址, ``val`` 为期望值, ``flags`` 为指定的类型(如private)和futex的大小。 50 系统调用的 ``flags`` 参数需要置0,但可用作未来扩展。
|