Searched full:feature (Results 1 – 25 of 698) sorted by relevance
12345678910>>...28
| /Documentation/ABI/testing/ |
| D | sysfs-block-device | 34 - If the device does not support the unload heads feature,
41 ATA standard, but support the unload feature nonetheless.
44 does support the unload feature, then you can tell the kernel
59 command queueing) priority support. By default this feature is
61 priority feature, writing "1" to this file results in an error
72 (HBA) implementing support for the SATA NCQ priority feature.
74 support for the SATA NCQ priority feature, regardless of the
75 device support for this feature (see sas_ncq_prio_supported).
84 command queueing) priority feature.
94 (HBA) implementing support for the SATA NCQ priority feature.
[all …]
|
| D | sysfs-devices-mmc | 5 Enhanced area is a new feature defined in eMMC4.4 standard.
6 eMMC4.4 or later card can support such feature. This kind of
7 area can help to improve the card performance. If the feature
16 Enhanced area is a new feature defined in eMMC4.4 standard.
17 eMMC4.4 or later card can support such feature. This kind of
18 area can help to improve the card performance. If the feature
|
| D | sysfs-devices-platform-soc-ipa | 20 What: .../XXXXXXX.ipa/feature/
25 The .../XXXXXXX.ipa/feature/ directory contains a set of
29 What: .../XXXXXXX.ipa/feature/rx_offload
34 The .../XXXXXXX.ipa/feature/rx_offload file contains a
39 What: .../XXXXXXX.ipa/feature/tx_offload
44 The .../XXXXXXX.ipa/feature/tx_offload file contains a
88 header (see .../XXXXXXX.ipa/feature/monitor, above).
|
| /Documentation/arch/x86/ |
| D | cpuinfo.rst | 4 x86 Feature Flags
10 The list of feature flags in /proc/cpuinfo is not complete and
11 represents an ill-fated attempt from long time ago to put feature flags
14 However, the amount of feature flags is growing by the CPU generation,
17 What is more, those feature flags do not even need to be in that file
21 And even if it doesn't show a particular feature flag - although the CPU
24 feature and figure out if it is supported or not, regardless of whether
32 kernel has *enabled* and *supports*. As in: the CPUID feature flag is
38 So, if users want to know if a feature is available on a given system,
42 * the kernel knows about the feature enough to have an X86_FEATURE bit
[all …]
|
| D | shstk.rst | 48 properties: x86 feature: SHSTK
61 feature is enabled on the first thread, it will propagate to all the thread's
64 arch_prctl(ARCH_SHSTK_ENABLE, unsigned long feature)
65 Enable a single feature specified in 'feature'. Can only operate on
66 one feature at a time.
68 arch_prctl(ARCH_SHSTK_DISABLE, unsigned long feature)
69 Disable a single feature specified in 'feature'. Can only operate on
70 one feature at a time.
75 are ignored. The mask is ORed with the existing value. So any feature bits
90 -EPERM if any of the passed feature are locked.
[all …]
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,powerpc-cpu-features.txt | 24 Description: Container of CPU feature nodes.
51 compatibility, less the individual feature nodes. For example, an ISA v3.0
66 /cpus/ibm,powerpc-cpu-features/example-feature node bindings
69 Each child node of cpu-features represents a CPU feature / capability.
71 Node: A string describing an architected CPU feature, e.g., "floating-point".
73 Description: A feature or capability supported by the CPUs.
79 Presence of the node indicates the feature is available.
88 First level of the Power ISA that the feature appears in.
105 that can use the feature.
119 feature to lesser privilege levels. If the property does not exist then no
[all …]
|
| /Documentation/hid/ |
| D | hid-sensor.rst | 70 functions, which get and set each input/feature/output report.
121 Set Feature report::
126 This interface is used to set a value for a field in feature report. For example
177 │ │ ├── feature-0-200316
178 │ │ │ ├── feature-0-200316-maximum
179 │ │ │ ├── feature-0-200316-minimum
180 │ │ │ ├── feature-0-200316-name
181 │ │ │ ├── feature-0-200316-size
182 │ │ │ ├── feature-0-200316-unit-expo
183 │ │ │ ├── feature-0-200316-units
[all …]
|
| /Documentation/features/ |
| D | arch-support.txt | 3 arch-support.txt file in each feature directory shows the arch
8 | ok | # feature supported by the architecture
9 |TODO| # feature not yet supported by the architecture
10 | .. | # feature cannot be supported by the hardware
11 | N/A| # feature doesn't apply to the architecture
|
| /Documentation/driver-api/mei/ |
| D | mei.rst | 9 The actual feature set depends on the Intel chipset SKU.
17 Each Intel ME feature, or Intel ME Client is addressed by a unique GUID and
27 An application maintains communication with an Intel ME feature while
28 /dev/meiX is open. The binding to a specific feature is performed by calling
30 The number of instances of an Intel ME feature that can be opened
31 at the same time depends on the Intel ME feature, but most of the
34 The driver is transparent to data that are passed between firmware feature
47 virtual channels with an Intel ME feature. Not all features support
84 Connect to firmware Feature/Client.
99 in_client_uuid - GUID of the FW Feature that needs
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-firmware-zynqmp | 132 The supported config ids are for the feature configuration is,
134 disable the over temperature feature.
138 the external watchdog feature.
140 external watchdog feature.
144 Select over temperature config ID to enable/disable feature
158 Select external watchdog config ID to enable/disable feature
196 The supported config ids are for the feature configuration is,
198 disable the over temperature feature.
202 the external watchdog feature.
204 external watchdog feature.
[all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-config.rst | 32 A feature is a named set of programming for a CoreSight device. The programming
36 The feature is defined using a descriptor. This descriptor is used to load onto
37 a matching device, either when the feature is loaded into the system, or when the
43 and efficient for the feature to be programmed onto the device when required.
45 The feature will not be active on the device until the feature is enabled, and
49 A feature is enabled as part of a configuration being enabled on the system.
56 feature being enabled that can adjust the behaviour of the operation programmed
57 by the feature.
60 at a given rate. When the feature is enabled then the current value of the
63 The feature descriptor defines a default value for a parameter, which is used
[all …]
|
| /Documentation/driver-api/mmc/ |
| D | mmc-tools.rst | 25 - Enable the eMMC BKOPS feature.
26 - Permanently enable the eMMC H/W Reset feature.
27 - Permanently disable the eMMC H/W Reset feature.
33 - Enable the eMMC cache feature.
34 - Disable the eMMC cache feature.
|
| /Documentation/fpga/ |
| D | dfl.rst | 2 FPGA Device Feature List (DFL) Framework Overview
12 The Device Feature List (DFL) FPGA framework (and drivers according to
20 Device Feature List (DFL) Overview
22 Device Feature List (DFL) defines a linked list of feature headers within the
32 +----------+ | | Feature | | | Feature | | | Feature |
38 +----------+ | | Feature | | Feature | | Feature |
66 Feature Header (Next_DFH) pointer.
68 Each FIU, AFU and Private Feature could implement its own functional registers.
70 e.g. FME Header Register Set, and the one for Private Feature, is named as
71 Feature Register Set, e.g. FME Partial Reconfiguration Feature Register Set.
[all …]
|
| /Documentation/virt/kvm/x86/ |
| D | cpuid.rst | 65 KVM_FEATURE_PV_UNHALT 7 guest checks this feature bit
69 KVM_FEATURE_PV_TLB_FLUSH 9 guest checks this feature bit
77 KVM_FEATURE_PV_SEND_IPI 11 guest checks this feature bit
85 KVM_FEATURE_PV_SCHED_YIELD 13 guest checks this feature bit
89 KVM_FEATURE_ASYNC_PF_INT 14 guest checks this feature bit
95 KVM_FEATURE_MSI_EXT_DEST_ID 15 guest checks this feature bit
99 KVM_FEATURE_HC_MAP_GPA_RANGE 16 guest checks this feature bit before
103 KVM_FEATURE_MIGRATION_CONTROL 17 guest checks this feature bit before
120 KVM_HINTS_REALTIME 0 guest checks this feature bit to
|
| /Documentation/arch/powerpc/ |
| D | elf_hwcaps.rst | 32 Where software relies on a feature described by a HWCAP, it should check the
33 relevant HWCAP flag to verify that the feature is present before attempting to
34 make use of the feature.
36 HWCAP is the preferred method to test for the presence of a feature rather
61 context, e.g., the presence of the BOOKE feature implies that the server
148 supporting later architectures DO NOT set this feature.
161 supporting later architectures also set this feature.
183 supporting later architectures also set this feature.
186 Transactional Memory feature is available.
210 supporting later architectures also set this feature.
[all …]
|
| /Documentation/kbuild/ |
| D | gcc-plugins.rst | 40 their utility is proven, the goal is to upstream the feature into GCC
42 feature is available in all supported versions of GCC.
47 When a feature exists in Clang but not GCC, effort should be made to
48 bring the feature to upstream GCC (rather than just as a kernel-specific
51 Similarly, even if a feature provided by a GCC plugin does *not* exist
52 in Clang, but the feature is proven to be useful, effort should be spent
53 to upstream the feature to GCC (and Clang).
55 After a feature is available in upstream GCC, the plugin will be made
57 kernel-supported versions of GCC provide the feature, the plugin will
|
| /Documentation/arch/s390/ |
| D | s390dbf.rst | 2 S390 Debug Feature
11 The goal of this feature is to provide a kernel debug logging API
21 The debug feature may also very useful for kernel and driver development.
26 feature with the function call :c:func:`debug_register()`.
64 ``/sys/kernel/debug`` therefore the debug feature can be accessed under
89 It is also possible to deactivate the debug feature globally for every
93 There are currently 2 possible triggers, which stop the debug feature
95 set to 1 the debug feature is running. If ``debug_active`` is set to 0 the
96 debug feature is turned off.
98 The second trigger which stops the debug feature is a kernel oops.
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-get-linehandle-ioctl.rst | 89 - emulate the feature in software
90 - treat the feature as best effort
92 The approach applied depends on whether the feature can reasonably be emulated
93 in software, and the impact on the hardware and userspace if the feature is not
95 The approach applied for each feature is as follows:
98 Feature Approach
115 Userspace cannot determine if a feature is supported in hardware, is
|
| /Documentation/filesystems/ext4/ |
| D | orphan.rst | 19 in heavy creation of orphan inodes. When orphan file feature
36 When a filesystem with orphan file feature is writeably mounted, we set
37 RO_COMPAT_ORPHAN_PRESENT feature in the superblock to indicate there may
38 be valid orphan entries. In case we see this feature when mounting the
41 RO_COMPAT_ORPHAN_PRESENT feature to avoid unnecessary scanning of the orphan
|
| D | group_descr.rst | 10 the block group descriptor table unless the sparse_super feature flag
21 If the meta_bg feature flag is set, then several block groups are
29 In ext2, ext3, and ext4 (when the 64bit feature is not enabled), the
31 bg_checksum. On an ext4 filesystem with the 64bit feature enabled, the
103 RO_COMPAT_GDT_CSUM feature is set, or
105 RO_COMPAT_METADATA_CSUM feature is set. The bg_checksum
111 - These fields only exist if the 64bit feature is enabled and s_desc_size
|
| D | super.rst | 10 If the sparse_super feature flag is set, redundant copies of the
137 Note: the difference between the compatible feature set and the
138 incompatible feature set is that if there is a bit set in the
139 incompatible feature set that the kernel doesn't know about, it should
143 about a feature in either the compatible or incompatible feature set, it
160 - Compatible feature set flags. Kernel can still read/write this fs even
166 - Incompatible feature set. If the kernel or fsck doesn't understand one
172 - Readonly-compatible feature set. If the kernel doesn't understand one of
226 - Device number of journal file, if the external journal feature flag is
250 - Size of group descriptors, in bytes, if the 64bit incompat feature flag
[all …]
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 21 ATA/ATAPI-7 specifies the IDLE IMMEDIATE command with unload feature.
23 unload disk heads. This feature is being used in modern laptops in
27 situations are anticipated. The desire to have such a feature
42 -EOPNOTSUPP if the device does not support the unload feature.
94 since this feature is supposed to be used on laptops and does not seem
110 feature nonetheless. Unfortunately, there is no safe way Linux can
113 support the unload feature (for instance, because the vendor of your
115 kernel to enable the usage of this feature for that drive by writing
120 will enable the feature for /dev/sda, and giving -2 instead of -1 will
149 to develop an implementation of this feature that is fit to be merged
|
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 173 The temporary debug_layer used when the tracing feature is enabled.
179 The temporary debug_level used when the tracing feature is enabled.
185 The status of the tracing feature.
187 Users can enable/disable this debug tracing feature by executing
195 Disable the method tracing feature.
198 Enable the method tracing feature.
204 Enable the method tracing feature.
210 Enable the method tracing feature.
216 Enable the method tracing feature.
222 Enable the method tracing feature.
[all …]
|
| /Documentation/nvme/ |
| D | feature-and-quirk-policy.rst | 4 Linux NVMe feature and quirk policy
33 does not aim to implement every feature in the specification. Every additional
34 feature implemented introduces more code, more maintenance and potentially more
38 Any feature implemented in the Linux NVMe host driver must support the
41 1. The feature is specified in a release version of an official NVMe
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | 101 Enables or disables the audio deviation limiter feature. The limiter
106 Sets the audio deviation limiter feature release time. Unit is in
114 Enables or disables the audio compression feature. This feature
120 Sets the gain for audio compression feature. It is a dB value. The
128 Sets the attack time for audio compression feature. It is a useconds
132 Sets the release time for audio compression feature. It is a
136 Enables or disables the pilot tone generation feature.
|
12345678910>>...28