Searched refs:these (Results 1 – 25 of 1392) sorted by relevance
12345678910>>...56
/Linux-v4.19/fs/jffs2/ |
D | LICENCE | 21 macros or inline functions from these files, or you compile these 22 files and link them with other works to produce a work based on these 23 files, these files do not by themselves cause the resulting work to be 25 these files must still be made available in accordance with section (3)
|
/Linux-v4.19/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
|
/Linux-v4.19/drivers/scsi/arm/ |
D | Kconfig | 10 Acorn system with one of these, say Y. If unsure, say N. 50 Acorn system with one of these, say Y. If unsure, say N. 57 system with one of these, say Y, otherwise say N. 64 you have one of these, say Y. If unsure, say N. 75 Acorn system with one of these, say Y. If unsure, say N. 83 system with one of these, say Y. If unsure, say N.
|
/Linux-v4.19/Documentation/ |
D | Intel-IOMMU.txt | 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.
|
/Linux-v4.19/Documentation/media/uapi/v4l/ |
D | vidioc-dbg-g-register.rst | 43 For driver debugging purposes these ioctls allow test applications to 50 with the ``CONFIG_VIDEO_ADV_DEBUG`` option to enable these ioctls. 75 when a driver supports these ioctls it must also support 77 it may support ``VIDIOC_DBG_G_CHIP_INFO`` but not these ioctls. 83 We recommended the v4l2-dbg utility over calling these ioctls directly. 164 these ioctls.
|
/Linux-v4.19/Documentation/arm/OMAP/ |
D | omap_pm | 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 66 As the 'pdata' in the above examples indicates, these functions are 72 not support these functions should leave these function pointers set 78 The most common usage of these functions will probably be to specify 114 frequency. The OMAP PM interface contains functions for these 141 in these cases, the board file needs to do additional steps as follows:
|
/Linux-v4.19/Documentation/sysctl/ |
D | user.txt | 13 The primary purpose of these limits is to stop programs that 16 intention that the defaults of these limits are set high enough that 17 no program in normal operation should run into these limits. 31 Currently, these files are in /proc/sys/user:
|
/Linux-v4.19/fs/nls/ |
D | Kconfig | 45 codepage if you want to be able to read/write these filenames on 57 codepage if you want to be able to read/write these filenames on 69 codepage if you want to be able to read/write these filenames on 82 codepage if you want to be able to read/write these filenames on 98 codepage if you want to be able to read/write these filenames on 103 characters for these languages: Albanian, Croatian, Czech, English, 113 codepage if you want to be able to read/write these filenames on 124 codepage if you want to be able to read/write these filenames on 135 codepage if you want to be able to read/write these filenames on 146 codepage if you want to be able to read/write these filenames on [all …]
|
/Linux-v4.19/arch/mips/jazz/ |
D | Kconfig | 9 kernel that runs on these, say Y here. For details about Linux on 21 kernel that runs on these, say Y here. For details about Linux on 32 kernel that runs on these, say Y here. For details about Linux on
|
/Linux-v4.19/Documentation/perf/ |
D | qcom_l3_pmu.txt | 5 Centriq SoCs. The L3 cache on these SOCs is composed of multiple slices, shared 11 options in sysfs, see /sys/devices/l3cache*. Given that these are uncore PMUs 24 Given that these are uncore PMUs the driver does not support sampling, therefore
|
/Linux-v4.19/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.
|
/Linux-v4.19/Documentation/devicetree/bindings/memory-controllers/ |
D | renesas-memory-controllers.txt | 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
|
/Linux-v4.19/Documentation/hwmon/ |
D | ucd9000 | 32 interrupts, cascading, or other system functions. Twelve of these pins offer PWM 33 functionality. Using these pins, the UCD90124 offers support for fan control, 40 functions. Twelve of these pins offer PWM functionality. Using these pins, the 47 functions. Ten of these pins offer PWM functionality. Using these pins, the
|
D | asb100 | 17 supply a datasheet for these chips. Thanks go to many people who helped 26 these, the ASB100-A also implements a single PWM controller for fans 2 and 64 (2) The min and max registers for these values appear to
|
D | abituguru | 27 this does not always work. For these uGuru's the autodetection can 31 You may also need to specify the fan_sensors option for these boards 33 2) There is a separate abituguru3 driver for these motherboards, 34 the abituguru (without the 3 !) driver will not work on these
|
/Linux-v4.19/drivers/staging/android/ion/ |
D | Kconfig | 27 know your system has these regions, you should say N here. 36 Unless you know your system has these regions, you should say N here. 43 by the Contiguous Memory Allocator (CMA). If your system has these
|
/Linux-v4.19/arch/m68k/ifpsp060/src/ |
D | README-SRC | 9 You don't need to actually assemble these files in order to compile a 11 are sufficient and were generated from these source files by
|
/Linux-v4.19/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 131 given even to these.) For example, loading a filesystem module via an 171 hole at the bottom of the stack to catch these overflows. [all …]
|
/Linux-v4.19/Documentation/RCU/ |
D | rcu.txt | 22 barriers. The fact that these operations are quite expensive 32 Therefore, as soon as a CPU is seen passing through any of these 45 by sampling these counters. 76 Of these, one was allowed to lapse by the assignee, and the 91 o What are all these files in this directory?
|
/Linux-v4.19/Documentation/devicetree/bindings/mfd/ |
D | tps6507x.txt | 8 given device need to be present. The definition for each of these nodes 17 Missing of these properties can cause the regulator registration 20 supply then also it is require to have these parameters with proper
|
D | qcom,spmi-pmic.txt | 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.
|
/Linux-v4.19/Documentation/arm/Samsung/ |
D | GPIO.txt | 15 about these devices. Their implementation has been brought into line 40 on these functions.
|
/Linux-v4.19/Documentation/devicetree/bindings/regulator/ |
D | sprd,sc2731-regulator.txt | 6 ceramic capacitors are recommended to use with these LDOs. 13 of these nodes is defined using the standard binding for regulators at
|
/Linux-v4.19/Documentation/i2c/busses/ |
D | i2c-sis96x | 7 Any combination of these host bridges: 9 and these south bridges: 24 The command "lspci" as root should produce something like these lines:
|
/Linux-v4.19/Documentation/vm/ |
D | page_frags.rst | 31 main difference between these two calls is the context in which they may be 32 called. The "netdev" prefixed functions are usable in any context as these 38 level. In order to enable these cases it is necessary to provide a generic
|
12345678910>>...56