Searched full:these (Results 1 – 25 of 1617) sorted by relevance
12345678910>>...65
| /Documentation/ABI/testing/ |
| D | sysfs-tty | 29 These sysfs values expose the TIOCGSERIAL interface via
38 These sysfs values expose the TIOCGSERIAL interface via
47 These sysfs values expose the TIOCGSERIAL interface via
56 These sysfs values expose the TIOCGSERIAL interface via
65 These sysfs values expose the TIOCGSERIAL interface via
74 These sysfs values expose the TIOCGSERIAL interface via
83 These sysfs values expose the TIOCGSERIAL interface via
92 These sysfs values expose the TIOCGSERIAL interface via
101 These sysfs values expose the TIOCGSERIAL interface via
110 These sysfs values expose the TIOCGSERIAL interface via
[all …]
|
| /Documentation/ABI/ |
| D | README | 2 userspace, and the relative stability of these interfaces. Due to the
3 everchanging nature of Linux, and the differing maturity levels, these
14 defined to be stable. Userspace programs are free to use these
26 programs can start to rely on these interfaces, but they must be
27 aware of changes that can occur before these interfaces move to
28 be marked stable. Programs that use these interfaces are
30 these interfaces, so that the kernel developers can easily
44 Every file in these directories will contain the following information:
56 important to get feedback for these interfaces to make
|
| /Documentation/devicetree/bindings/sifive/ |
| D | sifive-blocks-ip-versioning.txt | 4 strings for open-source SiFive IP blocks. HDL for these IP blocks
16 Until these IP blocks (or IP integration) support version
17 auto-discovery, the maintainers of these IP blocks intend to increment
19 interface to these IP blocks changes, or when the functionality of the
26 match on these IP block-specific compatible strings.
|
| /Documentation/arm64/ |
| D | pointer-authentication.rst | 30 A subset of these instructions have been allocated from the HINT
32 these instructions behave as NOPs. Applications and libraries using
33 these instructions operate correctly regardless of the presence of the
85 user_pac_address_keys and struct user_pac_generic_keys). These can be
94 requesting these two separate cpu features to be enabled. The current KVM
96 these userspace flags are checked before enabling pointer authentication.
98 if support is added in the future to allow these two features to be
105 Additionally, when these vcpu feature flags are not set then KVM will
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra194-pinmux.txt | 14 subnodes. Each of these subnodes represents some desired configuration for a
25 group. Valid values for these names are listed below.
60 These correspond to Tegra PADCTL_* (pinmux) registers.
64 These correspond to Tegra PADCTL_* (pinmux) registers. Any property
71 These registers controls a single pin for which a mux group exists.
83 these pins here.
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas,dbsc.txt | 5 These memory controllers differ from one SoC variant to another, and are called
10 domains, and prevent these PM domains from being powered down, which would
13 As there exist no actual drivers for these controllers yet, these bindings
|
| /Documentation/x86/ |
| D | intel-iommu.rst | 30 PS2 emulation. The regions of memory used for these devices are marked
32 regions will fail. Hence BIOS uses RMRR to specify these regions along with
33 devices that need to access these regions. OS is expected to setup
34 unity mappings for these regions for these devices to access these regions.
49 but these are not global address spaces, but separate for each domain.
|
| /Documentation/RCU/ |
| D | rcu.rst | 25 barriers. The fact that these operations are quite expensive
35 Therefore, as soon as a CPU is seen passing through any of these
44 counters. These counters allow limited types of blocking within
47 critical sections. These variants of RCU detect grace periods
48 by sampling these counters.
79 Of these, one was allowed to lapse by the assignee, and the
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-dbg-g-register.rst | 50 For driver debugging purposes these ioctls allow test applications to
57 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls.
81 These ioctls are optional, not all drivers may support them. However
82 when a driver supports these ioctls it must also support
84 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls.
90 We recommended the v4l2-dbg utility over calling these ioctls directly.
171 these ioctls.
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 21 In short, your I2C driver code may need to know these codes in order
28 These are returned as negative numbers from most calls, with zero or
30 numbers associated with these symbols differ between architectures,
34 codes that may be returned, and other cases where these codes should
35 be returned. However, drivers should not return other codes for these
58 on these as the only way to detect incorrect data transfers.
109 transaction it can't. (These limitations can't be seen in
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qcom,spmi-pmic.txt | 4 PMICs. These PMICs use a QPNP scheme through SPMI interface.
7 locations/definitions within these regions, with some of these regions
14 each. A function can consume one or more of these fixed-size register regions.
|
| D | tps6507x.txt | 8 given device need to be present. The definition for each of these nodes
16 These entries are required if regulators are enabled for a device.
17 Missing of these properties can cause the regulator registration
20 supply then also it is require to have these parameters with proper
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-mlxreg-io | 16 Description: These files show with which CPLD versions have been burned
37 Description: These files show with which CPLD versions have been burned
47 Description: These files enable and disable the access to the JTAG domain.
70 Description: These files allow asserting system power cycling, switching
97 Description: These files show the system reset cause, as following: power
115 Description: These files show the system reset cause, as following: ComEx
128 Description: These files show with which CPLD versions have been burned
136 Description: These files show the system reset cause, as following:
|
| /Documentation/arm/omap/ |
| D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
71 As the 'pdata' in the above examples indicates, these functions are
78 not support these functions should leave these function pointers set
84 The most common usage of these functions will probably be to specify
120 frequency. The OMAP PM interface contains functions for these
148 in these cases, the board file needs to do additional steps as follows:
|
| /Documentation/arm/nwfpe/ |
| D | netwinder-fpe.rst | 28 These instructions are fully implemented.
40 These instructions are fully implemented. They store/load three words
73 These are fully implemented.
87 These are fully implemented.
93 These are fully implemented as well. They use the same algorithm as the
96 to the ARM manual. The manual notes these are defined only for single
110 These are fully implemented.
116 These are fully implemented.
121 These are implemented. URD is implemented using the same code as the RND
141 These are not implemented. They are not currently issued by the compiler,
[all …]
|
| D | todo.rst | 20 These are not implemented. They are not currently issued by the compiler,
21 and are handled by routines in libc. These are not implemented by the FPA11
25 There are a couple of ways to approach the implementation of these. One
26 method would be to use accurate table methods for these routines. I have
29 These methods are used in GLIBC for some of the transcendental functions.
|
| /Documentation/hwmon/ |
| D | asb100.rst | 20 These are custom ASICs available only on Asus mainboards. Asus refuses to
21 supply a datasheet for these chips. Thanks go to many people who helped
30 these, the ASB100-A also implements a single PWM controller for fans 2 and
66 .. [2] The min and max registers for these values appear to
|
| /Documentation/security/ |
| D | self-protection.rst | 26 is uncommon that all these goals can be met, but it is worth explicitly
27 mentioning them, since these aspects need to be explored, dealt with,
44 to redirect execution flow. To reduce the availability of these targets
54 alternatives, breakpoints, kprobes, etc. If these must exist in a
64 Most architectures have these options on by default and not user selectable.
65 For some architectures like arm that wish to have these be selectable,
75 tables, file/network/etc operation structures, etc). The number of these
83 For variables that are initialized once at ``__init`` time, these can
87 What remains are variables that are updated rarely (e.g. GDT). These
98 access userspace memory without explicit expectation to do so. These
[all …]
|
| /Documentation/sh/ |
| D | register-banks.txt | 18 in mind when writing code that utilizes these banked registers, for obvious
19 reasons. Userspace is also not able to poke at the bank1 values, so these can
22 Presently the kernel uses several of these registers.
|
| /Documentation/devicetree/bindings/timer/ |
| D | stericsson-u300-apptimer.txt | 7 - interrupts : A list of 4 interrupts; one for each subtimer. These
9 adopted for EPOC/Symbian with two specific IRQs for these tasks,
|
| /Documentation/driver-api/80211/ |
| D | introduction.rst | 9 These books attempt to give a description of the various subsystems
10 that play a role in 802.11 wireless networking in Linux. Since these
|
| /Documentation/admin-guide/sysctl/ |
| D | user.rst | 18 The primary purpose of these limits is to stop programs that
21 intention that the defaults of these limits are set high enough that
22 no program in normal operation should run into these limits.
36 Currently, these files are in /proc/sys/user:
|
| /Documentation/core-api/ |
| D | timekeeping.rst | 117 These are quicker than the non-coarse versions, but less accurate,
124 reading the 'jiffies' variable. These are only useful when called
137 These variants are safe to call from any context, including from
151 architectures. These are the recommended replacements:
171 These are replaced by ktime_get_coarse_real_ts64() and
175 these days.
184 These are replaced by ktime_get_raw()/ktime_get_raw_ts64(),
|
| D | tracepoint.rst | 18 provide a framework for using 'probes'. These tools include Systemtap,
28 ``trace_tracepointname(function parameters)``. These are the tracepoints
30 unregistering probes with these callback sites is covered in the
|
| /Documentation/admin-guide/perf/ |
| D | qcom_l3_pmu.rst | 6 Centriq SoCs. The L3 cache on these SOCs is composed of multiple slices, shared
12 options in sysfs, see /sys/devices/l3cache*. Given that these are uncore PMUs
25 Given that these are uncore PMUs the driver does not support sampling, therefore
|
12345678910>>...65