Home
last modified time | relevance | path

Searched refs:these (Results 1 – 200 of 1192) sorted by relevance

123456

/linux-4.4.14/fs/jffs2/
DLICENCE21 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-4.4.14/Documentation/ABI/
DREADME2 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-4.4.14/drivers/scsi/arm/
DKconfig10 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-4.4.14/Documentation/
DIntel-IOMMU.txt29 PS2 emulation. The regions of memory used for these devices are marked
31 regions will fail. Hence BIOS uses RMRR to specify these regions along with
32 devices that need to access these regions. OS is expected to setup
33 unity mappings for these regions for these devices to access these regions.
48 but these are not global address spaces, but separate for each domain.
Dsgi-ioc4.txt8 standpoint is that all these functions share a single IRQ, and
11 themselves) present in IOC4 are mixed-purpose between these several
28 by the core driver at appropriate times. The interface of these
Diostats.txt6 activity. Tools such as sar and iostat typically interpret these and do
19 Here are examples of these different formats:
47 minor device numbers, and device name. Each of these formats provides
51 overflow and wrap). Yes, these are (32-bit or 64-bit) unsigned long
88 merge, or read of these stats by the number of I/Os in progress
95 modifying these counters. This implies that minor inaccuracies may be
Dunicode.txt31 Note that although these codes are similar to ISO 2022, neither the
55 have been defined; these are used by the DEC VT graphics map. [v1.2]
63 The DEC VT220 uses a 6x10 character matrix, and these characters form
113 Unicode practice these differences are considered font variants.
171 wish to encode fictional scripts use these codes, in the interest of
Dkernel-per-CPU-kthreads.txt39 that does not require per-CPU kthreads. This will prevent these
58 1. Don't use Bluetooth, in which case these kthreads won't be
105 and also do I/O involving these drivers on other CPUs.
230 1. Build the kernel with CONFIG_PREEMPT=n. This prevents these
234 2. Build the kernel with CONFIG_RCU_BOOST=n. This prevents these
253 1. Use affinity, cgroups, or other mechanism to force these kthreads
255 2. Build with CONFIG_RCU_NOCB_CPU=n, which will prevent these
263 1. Build with CONFIG_LOCKUP_DETECTOR=n, which will prevent these
265 2. Boot with "nosoftlockup=0", which will also prevent these kthreads
Dsysfs-rules.txt14 abstractions these programs provide instead of accessing sysfs directly.
103 /sys/block, /sys/class and /sys/bus. It is planned that these will
146 directory does not contain directories for child devices, these links
148 valid use of these links; they must never appear in any path as an
149 element. Assuming the existence of these links for devices which are
153 It is planned to remove all these links when all class device
Dcachetlb.txt137 these routines must be implemented for cpus which have virtually
141 implement these interfaces since the caches are fully synchronized
220 Here in these two interfaces we are flushing a specific range
225 The first of these two routines is invoked after map_vm_area()
267 for these two pages is chosen in such a way that the kernel
276 If D-cache aliasing is not an issue, these two routines may
296 D-cache aliasing, to make sure these kernel stores are
301 sure that kernel reads of these pages will see the most recent
312 This allows these interfaces to be implemented much more
339 these two routines.
DSAK.txt47 actually want killed. This is because these applications are
86 delete these lines, but this may cause system management
Dpreempt-locking.txt16 requires protecting these situations.
32 protect these situations by disabling preemption around them.
130 these are called from the spin_lock and read/write lock macros, the right thing
DDMA-ISA-LPC.txt40 In order to allocate a piece of memory that satisfies all these
74 You allocate these in a similar fashion as all basic resources:
150 controller being in a certain state then you have to restore these
/linux-4.4.14/arch/mips/jazz/
DKconfig8 kernel that runs on these, say Y here. For details about Linux on
20 kernel that runs on these, say Y here. For details about Linux on
31 kernel that runs on these, say Y here. For details about Linux on
/linux-4.4.14/Documentation/arm/OMAP/
Domap_pm6 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-4.4.14/fs/nls/
DKconfig45 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-4.4.14/Documentation/sh/
Dregister-banks.txt18 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-4.4.14/Documentation/devicetree/bindings/memory-controllers/
Drenesas-memory-controllers.txt10 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-4.4.14/arch/m68k/ifpsp060/src/
DREADME-SRC9 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-4.4.14/Documentation/video4linux/bttv/
DREADME.quirks7 stability problems you can try if one of these options makes your box
10 drivers/pci/quirks.c knows about these issues, this way these bits are
74 compliant. To ensure compatibility when using PCs with these PCI
81 query for these non-compliant devices, and set the EN_VSFX bit only if
DSound-FAQ45 these pins. One register is the output enable register
48 you can get/set the status if these pins. They can be used for input
51 Most grabber board vendors use these pins to control an external chip
59 line for your board. The important fields are these two:
70 (BT848_GPIO_OUT_EN) will be set as these pins must be driven by the
81 card installed, you might to check out if you can read these registers
/linux-4.4.14/drivers/staging/iio/magnetometer/
DKconfig21 If so, these modules will be created:
35 If so, these modules will be created:
/linux-4.4.14/Documentation/hwmon/
Dasb10017 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
Dabituguru27 this doesnot always work. For these uGuru's the autodection 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
Ducd900031 interrupts, cascading, or other system functions. Twelve of these pins offer PWM
32 functionality. Using these pins, the UCD90124 offers support for fan control,
39 functions. Ten of these pins offer PWM functionality. Using these pins, the
Dsmsc47m19228 these features are accessed via ISA bus and are not supported by this
74 temp[2-3]_input - temperature measured by external diodes (one of these would
81 The chip adds the offsets stored in these registers to
Dw83627hf51 If you really want i2c accesses for these Super I/O chips,
59 to these pins despite their not being labeled for that purpose. Therefore,
60 the w83627thf driver interprets these as VID. If the VID on your board
Dwm835020 simple access to these major supplies.
Dpc87360121 channels). For technical reasons, these channels are held by the VLM
123 measurement) one. As a consequence, these temperatures are exported as
126 Note that these three additional channels share their pins with the
141 are likely to be divided externally. The meaning of each of these inputs as
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dqcom,spmi-pmic.txt7 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.
Dtps6507x.txt8 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
Das3711.txt22 Additionally one of these properties must be provided to select the type of
30 and one of these to select the over-voltage protection pin
Dqcom,tcsr.txt4 functions for their peripherals. This node is intended to allow access to these
Dtps65910.txt17 device need to be present. The definition for each of these nodes is defined
29 These entries are require if regulators are enabled for a device. Missing of these
32 also it is require to have these parameters with proper node handle of always
/linux-4.4.14/Documentation/devicetree/bindings/regmap/
Dregmap.txt14 - {big,little}-endian: these are boolean properties, if absent
16 these properties are for register values and all the buffers only.
/linux-4.4.14/Documentation/RCU/
Drcu.txt22 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
94 o What are all these files in this directory?
/linux-4.4.14/Documentation/arm/Samsung/
DGPIO.txt15 about these devices. Their implementation has been brought into line
40 on these functions.
/linux-4.4.14/Documentation/devicetree/bindings/leds/backlight/
Dpwm-backlight.txt6 - brightness-levels: Array of distinct brightness levels. Typically these
9 from these values. 0 means a 0% duty cycle (darkest/off), while the
/linux-4.4.14/drivers/staging/
DKconfig8 them. Please note that these drivers are under heavy
13 Using any of these drivers will taint your kernel which might
17 If you wish to work on these drivers, to help improve them, or
/linux-4.4.14/Documentation/i2c/busses/
Di2c-sis96x7 Any combination of these host bridges:
9 and these south bridges:
24 The command "lspci" as root should produce something like these lines:
Di2c-sis559517 Note: these chips contain a 0008 device which is incompatible with the
18 5595. We recognize these by the presence of the listed
Di2c-viapro47 Your lspci -n listing must show one of these :
65 If none of these show up, you should look in the BIOS for settings like
Di2c-piix464 parts of the PIIX4 needs a range of 8 of these addresses to function
65 correctly. If these addresses are already reserved by some other device,
103 Some of these machines have an RFID EEPROM (24RF08) connected to the SMBus,
Di2c-ali156316 For an overview of these chips see http://www.acerlabs.com
/linux-4.4.14/Documentation/power/regulator/
Ddesign.txt18 specific knowledge that these changes are safe to perform on this
31 => The consumer API should be structured so that these use cases are
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dhi6220-clock.txt5 for these system controllers:
51 All these identifier could be found in <dt-bindings/clock/hi6220-clock.h>.
Dst,nomadik.txt23 PLL nodes: these nodes represent the two PLLs on the system,
34 HCLK nodes: these represent the clock gates on individual
Dhi3620-clock.txt20 All these identifier could be found in <dt-bindings/clock/hi3620-clock.h>.
Dmarvell,pxa910.txt21 All these identifier could be found in <dt-bindings/clock/marvell-pxa910.h>.
Dhix5hd2-clock.txt15 All these identifier could be found in <dt-bindings/clock/hix5hd2-clock.h>.
Dmarvell,pxa168.txt21 All these identifier could be found in <dt-bindings/clock/marvell,pxa168.h>.
Dmarvell,mmp2.txt21 All these identifier could be found in <dt-bindings/clock/marvell-mmp2.h>.
Darm-integrator.txt7 core module and there is only one of these.
Dmarvell,pxa1928.txt21 All these identifiers can be found in <dt-bindings/clock/marvell,pxa1928.h>.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dcpus.txt19 by the Power ISA. For these EREF-specific categories, the existence of
31 these registers should be set if the coresponding CPU should be
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dlantiq,pinctrl-falcon.txt13 subnodes. Each of these subnodes represents some desired configuration for a
33 Valid values for these names are listed below.
51 Valid values for these names are listed below.
Dpinctrl-palmas.txt17 subnodes. Each of these subnodes represents some desired configuration for a
46 Note that many of these properties are only valid for certain specific pins.
62 There are 4 special functions: opt0, opt1, opt2 and opt3. If any of these
Dlantiq,pinctrl-xway.txt13 subnodes. Each of these subnodes represents some desired configuration for a
33 Valid values for these names are listed below.
58 Valid values for these names are listed below.
Dfsl,mxs-pinctrl.txt17 subnodes. Each of these subnodes represents some desired configuration for
36 having these pins defined in several group nodes. It also means each of
54 Valid values for these integers are listed below.
119 applied on all these pins. And config nodes mmc-cd-cfg and mmc-sck-cfg are
Dimg,tz1090-pdc-pinctrl.txt13 of subnodes. Each of these subnodes represents some desired configuration for a
32 group. Valid values for these names are listed below.
55 Note that many of these properties are only valid for certain specific pins
Dnvidia,tegra124-xusb-padctl.txt5 assigned to one out of a set of different pads. Some of these pads have an
35 they should be assigned to. The name of these subnodes is not important. All
56 Note that not all of these properties are valid for all lanes. Lanes can be
Dnvidia,tegra20-pinmux.txt13 subnodes. Each of these subnodes represents some desired configuration for a
32 group. Valid values for these names are listed below.
62 Note that many of these properties are only valid for certain specific pins
94 With some exceptions, these support nvidia,high-speed-mode,
Dpinctrl-bindings.txt54 section of this document for details of the format of these
163 where they are applicable; not all of these properties are relevant or useful
165 should state which of these generic properties, if any, are used, and the
166 structure of the DT nodes that contain these properties.
235 More in-depth documentation on these parameters can be found in
/linux-4.4.14/Documentation/video4linux/
Dcpia2_overview.txt14 mappings for the two chips. In these cases, the symbols defined in the
20 try to make note of all of these cases.
31 of these registers and the possible values for most of them.
DREADME.saa713426 these config options:
55 Cards can use either of these two crystals (xtal):
D4CCs.txt9 Existing 4CCs may not obey these guidelines.
/linux-4.4.14/Documentation/i2c/
Dfault-codes17 In short, your I2C driver code may need to know these codes in order
26 numbers associated with these symbols differ between architectures,
30 codes that may be returned, and other cases where these codes should
31 be returned. However, drivers should not return other codes for these
54 on these as the only way to detect incorrect data transfers.
/linux-4.4.14/Documentation/devicetree/bindings/arm/ux500/
Dboards.txt4 Required properties (in root node) one of these:
13 Required property of soc node, one of these:
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Darm,versatile-fpga-irq.txt4 such as the Integrator or Versatile family. The output of these different
19 the system till not make it possible for devices to request these
Dst,sti-irq-syscfg.txt20 these IRQs using bitwise logic. A number of defines have been
Dti,omap4-wugen-mpu15 - interrupt-parent : a phandle to the GIC these interrupts are routed
Dsnps,archs-idu-intc.txt39 /* upstream core irqs: downstream these are "COMMON" irq 0,1.. */
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dgpio-matrix-keypad.txt13 which these row lines are connected.
16 which these column lines are connected.
Dps2keyb-mouse-apbps2.txt6 these properties are built from information in the AMBA plug&play and from
Dmatrix-keymap.txt13 drivers will use fixed values for these.
/linux-4.4.14/arch/m68k/ifpsp060/
DTEST.DOC47 To assist in assembling and linking these modules with other modules,
50 of these packages.
61 (1) | Call-Out | - 4 bytes per entry (user fills these in)
80 to a function required by the test packages (these functions and their
160 basically, it enables each of these exceptions and forces
173 to _real_access(), _real_trace(), _real_trap(), etc. because these
Disp.doc38 isp.sa provides full emulation support for these instructions.
75 (1) | Call-Out | - 4 bytes per entry (user fills these in)
94 to a function required by the ISP (these functions and their location are
176 060ISP is installed properly, these instructions will enter through the
183 host system (see isp.s source code), then these "Call-out"s should be
/linux-4.4.14/arch/cris/arch-v32/mach-a3/
DKconfig57 LED's at the general ports, these bits are used for all kinds of
77 LED's at the general ports, these bits are used for all kinds of
97 LED's at the general ports, these bits are used for all kinds of
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfsd-admin-interfaces.txt4 Note that normally these interfaces are used only by the utilities in
21 If nfsd is started without doing any of these, then it will create one
/linux-4.4.14/Documentation/nvmem/
Dnvmem.txt22 This framework aims at solve these problems. It also introduces DT
109 The difference between these apis and cell based apis is that these apis always
124 Both these APIs are used to release a reference to the NVMEM and
/linux-4.4.14/Documentation/vm/
Dunevictable-lru.txt54 pages and to hide these pages from vmscan. This mechanism is based on a patch
61 fraction of these pages are not evictable for any reason [see below], vmscan
231 event and movement of pages onto the unevictable list should be rare, these
360 these mappings are inherently pinned, so we don't need to mark them as
362 mark the page. Because of this, get_user_pages() will fail for these VMAs,
366 neither need nor want to mlock() these pages. However, to preserve the
374 mlock_fixup() treats these VMAs the same as hugetlbfs VMAs. It calls
377 Note that for all of these special VMAs, mlock_fixup() does not set the
379 munlock(), munmap() or task exit. Neither does mlock_fixup() account these
388 lock operation indicated by an argument. So, these system calls are also
[all …]
Dzsmalloc.txt12 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
15 page boundaries. The code refers to these linked pages as a single entity
/linux-4.4.14/Documentation/usb/
Dgadget-testing.txt63 The ECM function provides these attributes in its function directory:
96 The ECM subset function provides these attributes in its function directory:
129 The EEM function provides these attributes in its function directory:
185 The HID function provides these attributes in its function directory:
231 The LOOPBACK function provides these attributes in its function directory:
251 The MASS STORAGE function provides these attributes in its directory:
304 The MIDI function provides these attributes in its function directory:
387 The NCM function provides these attributes in its function directory:
511 The RNDIS function provides these attributes in its function directory:
574 The SOURCESINK function provides these attributes in its function directory:
[all …]
Dhotplug.txt16 partitions mounted, and so on. In some cases these will
63 is the string "usb", and it passes these environment variables:
94 macros such as these, and use driver_info to store more information.
116 Most USB device drivers should pass these tables to the USB subsystem as
/linux-4.4.14/arch/cris/arch-v32/mach-fs/
DKconfig95 LED's at the general ports, these bits are used for all kinds of
117 LED's at the general ports, these bits are used for all kinds of
139 LED's at the general ports, these bits are used for all kinds of
161 LED's at the general ports, these bits are used for all kinds of
183 LED's at the general ports, these bits are used for all kinds of
/linux-4.4.14/drivers/usb/gadget/
DKconfig39 If in doubt, say "N" and don't enable these drivers; most people
54 Avoid enabling these messages, even if you're actively
58 trying to track down. Never enable these messages for a
68 Avoid enabling these messages, even if you're actively
72 trying to track down. Never enable these messages for a
81 (for a peripheral controller). The information in these
83 driver on a new board. Enable these files by choosing "Y"
92 The information in these files may help when you're
94 Enable these files by choosing "Y" here. If in doubt, or
208 systems call these "client" drivers, of which "class drivers"
/linux-4.4.14/Documentation/security/
DLSM.txt6 "module" is a bit of a misnomer since these extensions are not actually
16 specific changes to system operation when these tweaks are not available
/linux-4.4.14/Documentation/scheduler/
Dsched-domains.txt2 hierarchy is built from these base domains via the ->parent pointer. ->parent
12 explicitly set. A sched domain's span means "balance process load among these
17 pointer. The union of cpumasks of these groups MUST be the same as the
18 domain's span. The intersection of cpumasks from any two of these groups
Dsched-stats.txt23 of these will need to start with a baseline observation and then calculate
59 One of these is produced per domain for each cpu described. (Note that if
60 CONFIG_SMP is not defined, *no* domains are utilized and these lines
150 A program could be easily written to make use of these extra fields to
/linux-4.4.14/drivers/staging/panel/
DKconfig143 'standard' ASCII characters to the character sets used by these controllers.
174 1..17 : directly connected to any of these pins on the DB25 plug
189 1..17 : directly connected to any of these pins on the DB25 plug
204 1..17 : directly connected to any of these pins on the DB25 plug
219 1..17 : directly connected to any of these pins on the DB25 plug
234 1..17 : directly connected to any of these pins on the DB25 plug
249 1..17 : directly connected to any of these pins on the DB25 plug
/linux-4.4.14/arch/arm/boot/dts/
Dste-hrefv60plus.dtsi33 * Set this up using hogs, as time goes by and as seems fit, these
71 * processor firmware), mux in these image processor GPIO lines 0
99 * the "other alt C1" setting enables these pins)
Dste-hrefprev60-stuib.dts30 /* Only one of these will be used */
Dste-hrefv60plus-stuib.dts32 /* Only one of these will be used */
/linux-4.4.14/Documentation/pti/
Dpti_intel_mid.txt18 these two line disciplines can work separately from
58 // these two vars used to grab LDISC values from loaded ldisc drivers
68 // doubt you'll want to use these exact error lines of code
/linux-4.4.14/arch/cris/arch-v32/
DKconfig110 LED's at the general ports, these bits are used for all kinds of
132 LED's at the general ports, these bits are used for all kinds of
154 LED's at the general ports, these bits are used for all kinds of
176 LED's at the general ports, these bits are used for all kinds of
198 LED's at the general ports, these bits are used for all kinds of
/linux-4.4.14/Documentation/input/
Dgamepad.txt68 Legacy drivers often don't comply to these rules. As we cannot change them
71 change the mappings so you can advise users to set these.
85 No other devices, that do not look/feel like a gamepad, shall report these
117 Some of these are available as digital buttons, some as analog buttons. Some
118 may even report both. The kernel does not convert between these so
Dntrig.txt56 However not all of these devices have the same physical dimensions. Most
66 obvious that these sensors were prone to erroneous events. Users reported
104 I don't know what the optimal values are for these filters. If the defaults
108 The calibration of these devices does drift over time. If ghosts or contact
/linux-4.4.14/drivers/net/ethernet/i825xx/
DKconfig14 the questions about these devices. If you say Y, you will be asked for
23 If you have an Acorn system with one of these (AKA25) network cards,
/linux-4.4.14/Documentation/devicetree/bindings/nvmem/
Dnvmem.txt7 some data on NVMEM, for the OS to be able to retrieve these information
9 these data from, and where they are stored on the storage device.
/linux-4.4.14/Documentation/devicetree/bindings/
Dcommon-properties.txt21 If a binding supports these properties, then the binding should also
22 specify the default behavior if none of these properties are present.
/linux-4.4.14/Documentation/ABI/testing/
Ddebugfs-pktcdvd11 these files in debugfs:
Dsysfs-kernel-mm-hugepages9 Under these directories are a number of files:
Dsysfs-bus-iio-mpu605011 positions relative to the board that holds these sensors. Identity matrix
Dsysfs-firmware-dmi-tables21 The complete DMI information can be obtained using these two
/linux-4.4.14/drivers/infiniband/hw/mlx5/
DKconfig8 IP-over-IB or SRP with these devices.
/linux-4.4.14/drivers/infiniband/hw/mlx4/
DKconfig10 IP-over-IB or SRP with these devices.
/linux-4.4.14/drivers/gpu/drm/udl/
DKconfig15 Say M/Y to add support for these devices via drm/kms interfaces.
/linux-4.4.14/drivers/atm/
DKconfig229 When active, these messages can have a significant impact on the
253 here if you have one of these cards.
267 When active, these messages can have a significant impact on the
277 named horizon) here if you have one of these cards.
291 When active, these messages can have a significant impact on the
306 named iphase) here if you have one of these cards.
324 When active, these messages can have a significant impact on the
336 named fore_200e) here if you have one of these ATM adapters.
376 When active, these messages can have a significant impact on
/linux-4.4.14/drivers/media/usb/cpia2/
DKconfig7 Microscope. If you have one of these cameras, say Y here
/linux-4.4.14/drivers/media/radio/
DKconfig241 Say Y here to enable support for these ISA drivers.
253 Choose Y here if you have one of these AM/FM radio cards, and then
264 Choose Y here if you have one of these FM radio cards, and then fill
268 and are not supported by this driver. For these cards, use the
274 been reported to be used by these cards.
318 Choose Y here if you have one of these FM radio cards, and then fill
391 Choose Y here if you have one of these FM radio cards.
401 Choose Y here if you have one of these FM radio cards.
448 Choose Y here if you have one of these FM radio cards, and then fill
482 Choose Y here if you have one of these FM radio cards, and then fill
/linux-4.4.14/Documentation/timers/
DNO_HZ.txt38 periods, but where these idle periods are also quite short (tens or
39 hundreds of microseconds). For these types of workloads, scheduling
41 will frequently be multiple runnable tasks per CPU. In these cases,
76 unnecessary scheduling-clock interrupts. In these situations, there
116 by one less than the number of CPUs. In these situations, there is
192 a timer will awaken these CPUs every four jiffies in order to ensure
263 options for these workloads:
299 tasks, even though these interrupts are unnecessary.
306 Better handling of these sorts of situations is future work.
325 result in these shootdowns. For another example, page faults
[all …]
/linux-4.4.14/Documentation/infiniband/
Dsysfs.txt50 Each of these files contains the corresponding value from the port's
70 The hfi1 driver also creates these additional files:
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-firmware-efi-vars15 The efivars module enumerates these variables and
31 explanation of each of these variables.
Dsysfs-acpi-pmprofile13 Currently these values are defined by spec:
/linux-4.4.14/fs/fscache/
DKconfig23 multi-CPU system these may be on cachelines that keep bouncing
40 and on a multi-CPU system these may be on cachelines that keep
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Das3722-regulator.txt8 sd[0-6], 10 LDOs as ldo[0-7], ldo[9-11]. The input supply of these
26 description of standard properties for these sub-nodes.
Dmt6311-regulator.txt8 The definition for each of these nodes is defined using the standard binding
Dtps65023.txt13 these nodes is defined using the standard binding for regulators found at
/linux-4.4.14/arch/arm/mach-vexpress/
DKconfig36 You must boot using a Flattened Device Tree in order to use these
38 these boards with this option.
/linux-4.4.14/drivers/nvme/host/
DKconfig7 don't have one of these, it is safe to answer N.
/linux-4.4.14/drivers/media/pci/pt1/
DKconfig7 Since these cards have no MPEG decoder onboard, they transmit
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/cpm/
Dbrg.txt10 numbers are assigned to these in order.
/linux-4.4.14/Documentation/cpu-freq/
Duser-guide.txt123 On these systems, all you can do is select the lower and upper
131 On all other cpufreq implementations, these boundaries still need to
187 kHz). By echoing new values into these
188 files, you can change these limits.
Dgovernors.txt42 core must be able to tell these drivers of a "target frequency". So
43 these specific drivers will be transformed to offer a "->target/target_index"
55 governors, these can be tested extensively, and the best one can be
250 these two functions:
261 What's the difference between these two functions? When your governor
265 use __cpufreq_driver_target only in these cases. In all other cases
Dcpu-drivers.txt119 with these values.
121 For setting some of these values (cpuinfo.min[max]_freq, policy->min[max]), the
125 SMP systems normally have same clock source for a group of cpus. For these the
137 so that incompatible values can be corrected. For verifying these
152 only allow the CPU to be set to one frequency. For these, you use the
/linux-4.4.14/Documentation/console/
Dconsole.txt42 What do these files signify?
110 console drivers must follow these guidelines:
124 driver to check when it's legal to release these resources. Calling
139 and unbinding them may cause problems. With minimal fixes, these drivers can
/linux-4.4.14/Documentation/phy/
Dsamsung-usb2.txt10 create a one driver that would fit all these PHY controllers. Often
53 be modified to change the internal routing of these pins between a USB
135 After completing these steps the support for the new SoC should be ready.
/linux-4.4.14/Documentation/trace/
Dstm.txt8 these masters and channels are statically allocated to certain
25 identifiers to ranges of masters and channels. If these rules (policy)
48 channel from within these ranges.
/linux-4.4.14/drivers/staging/unisys/Documentation/ABI/
Dsysfs-platform-visorchipset59 purposes, but these acknowledgements are not required for the
78 situation by sending a message to guests using these VFs, and
97 situation by sending a message to guests using these VFs, and
/linux-4.4.14/scripts/
Dchecksyscalls.sh173 /* these can be expressed using other calls */
/linux-4.4.14/Documentation/devicetree/bindings/timer/
Dstericsson-u300-apptimer.txt9 adopted for EPOC/Symbian with two specific IRQs for these tasks,
Dallwinner,sun5i-a13-hstimer.txt8 - interrupts : The interrupts of these timers (2 for the sun5i IP, 4 for the sun7i
/linux-4.4.14/Documentation/networking/
Dtcp-thin.txt22 a set of mechanisms has been made, which address these latency issues
35 Since these mechanisms are targeted at time-dependent applications,
Dirda.txt2 of the IrDA Utilities. More detailed information about these and associated
DREADME.sb100033 along with these utilities.
38 If you don't have these installed as a standard part of your Linux
50 To make the SB1000 card work, follow these steps:
73 0x310 and IRQ 11 for my SB1000 card and these work well for me. YMMV.)
147 install the correct versions of the header files in these two directories.
175 to the "cmconfig" command (uncomment that line). If you're not receiving these
Dxfrm_sync.txt68 How these flags are used is dependent on the direction of the
77 to get notified of these events.
101 By default these events should be turned off unless there is
107 we also provide default threshold values for these different parameters
/linux-4.4.14/drivers/mmc/card/
DKconfig46 Say Y here to help these restricted hosts by bouncing
67 on your card will be overwritten by these tests.
/linux-4.4.14/drivers/media/pci/pluto2/
DKconfig10 Since these cards have no MPEG decoder onboard, they transmit
/linux-4.4.14/tools/testing/selftests/rcutorture/doc/
DTINY_RCU.txt11 combinations of these parameters.
/linux-4.4.14/Documentation/sound/oss/
DOpti9 kernel release will include these features.
31 Answer 'm' for these items:
39 options will override these values.
133 line3. This program reroutes these mixer channels to their
162 systems (which have only one IDE controller) but these systems
/linux-4.4.14/drivers/ipack/
DKconfig12 hosted on these buses. While IndustryPack modules can provide a
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dmtk-afe-pcm.txt7 - clock-names: should have these clock names:
Dwm8962.txt20 be 6 entries long. If absent, no configuration of these registers is
Dimx-audio-spdif.txt25 * Note: At least one of these two properties should be set in the DT binding.
/linux-4.4.14/Documentation/gpio/
Dconsumer.txt20 other function in the kernel should use these prefixes.
94 Device-managed variants of these functions are also defined:
129 It is strictly forbidden to use a descriptor after calling these functions.
154 is possible. You should normally issue these calls from a task context. However,
191 Also, using these calls for GPIOs that can't safely be accessed without sleeping
216 Other than the fact that these accessors might sleep, and will work on GPIOs
217 that can't be accessed from hardIRQ handlers, these calls act the same as the
239 Note that these functions should only be used with great moderation ; a driver
Ddriver.txt84 - If sleepable APIs have to be used, these can be done from the .irq_bus_lock()
85 and .irq_bus_unlock() callbacks, as these are the only slowpath callbacks
90 * CHAINED GPIO irqchips: these are usually the type that is embedded on
126 * GENERIC CHAINED GPIO irqchips: these are the same as "CHAINED GPIO irqchips",
140 * NESTED THREADED GPIO irqchips: these are off-chip GPIO expanders and any
219 When implementing an irqchip inside a GPIO driver, these two functions should
235 If sleepable APIs have to be used, these can be done from the .irq_bus_lock()
/linux-4.4.14/Documentation/devicetree/bindings/rng/
Domap_rng.txt9 Note that these two versions are incompatible.
/linux-4.4.14/fs/omfs/
DKconfig9 the opposite is true. Say Y if you have either of these devices
/linux-4.4.14/drivers/staging/sm750fb/
DTODO6 - check on hardware effects of removal of USE_HW_I2C and USE_DVICHIP (these two
/linux-4.4.14/drivers/iio/magnetometer/
DKconfig90 This driver can also be built as a module. If so, these modules
96 (*) one of these is necessary to do something.
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-memory.txt41 All of these registers are 32 bits wide.
65 3 processors on chip, Java ones, VPU, SPU, APU, maybe these are the
78 0xec-0xff - Nothing seems to be in these registers, 0xec-f4 are 0x00000000.
Dfw-calling.txt45 There are 16 parameters/results 32-bit fields. The driver populates these fields
47 these fields with result values returned by the call. The API specifics may be
/linux-4.4.14/Documentation/filesystems/
Dsquashfs.txt104 these are stored here.
184 A second index table is used to locate these. This second index table for
194 locate these. This second index table for speed of access (and because it
208 used to locate these. This second index table for speed of access (and because
246 The cache is not used for file datablocks, these are decompressed and cached in
252 which have been packed with it, these because of locality-of-reference may be
Dcramfs.txt35 No timestamps are stored in a cramfs, so these default to the epoch
42 == 4096. At least the latter of these is a bug, but it hasn't been
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dexynos5-gsc.txt20 in the form of gscN, N = 0...3. G-Scaler driver uses these aliases
/linux-4.4.14/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.txt4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
61 these LEDs. Only valid for LEDs 0 to 7, where LED signals 0 to 3 may
67 these LEDs. Only valid for LEDs 0 to 7, where LED signals 0 to 3 may
/linux-4.4.14/Documentation/hid/
Dhiddev.txt11 To support these disparate requirements, the Linux USB system provides
27 events into the input subsystem, but these have no effect on the hid
69 each one of these usages has a single signed 32 bit value.
76 the report. In its basic mode, the hiddev will make these individual
149 looked up by type (input, output or feature) and id, so these fields
/linux-4.4.14/drivers/media/pci/dm1105/
DKconfig17 Since these cards have no MPEG decoder onboard, they transmit
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dpower-controller.txt4 sometimes able to control the system power. The device driver associated with these
/linux-4.4.14/drivers/block/zram/
DKconfig9 Pages written to these disks are compressed and stored in memory
/linux-4.4.14/drivers/misc/cxl/
DKconfig30 userspace programs to access these accelerators via /dev/cxl/afuM.N
/linux-4.4.14/drivers/staging/rdma/ipath/
DKconfig7 including InfiniBand verbs support. This driver allows these
/linux-4.4.14/Documentation/sysctl/
DREADME45 In fact, there are only four things needed to use these config
49 - common sense (this is especially hard to come by these days)
/linux-4.4.14/Documentation/thermal/
Dnouveau_thermal34 WARNING: Some of these thresholds may not be used by Nouveau depending
37 The default value for these thresholds comes from the GPU's vbios. These
/linux-4.4.14/Documentation/sound/alsa/
DBt87x.txt63 sample rates are between 119466 and 448000 Hz (yes, these numbers are
69 device to control these.
Demu10k1-jack.txt36 popular belief, all emu10k1 cards are multichannel cards. Which of these
44 input, or nothing. The one exception is the SBLive! 5.1. On these devices,
/linux-4.4.14/tools/perf/Documentation/
Dandroid.txt22 perf uses some bionic enhancements that are not included in these NDK versions.
71 You need to set these before running perf on the target:
Dperf-diff.txt43 Only consider symbols in these dsos. CSV that understands
49 Only consider symbols in these comms. CSV that understands
55 Only consider these symbols. CSV that understands
/linux-4.4.14/Documentation/cdrom/
Dide-cd83 Linux names these devices as follows. The master and slave devices
169 IDE support code. Some of these items apply only to earlier versions
249 The Pioneer DR-A24X CDROM drives are fairly popular these days.
250 Unfortunately, these drives seem to become very confused when we perform
251 the standard Linux ATA disk drive probe. If you own one of these drives,
252 you can bypass the ATA probing which confuses these CDROM drives, by
262 The most notorious of these is the CMD640B chip. This problem can
300 Some early Slackware releases had these defined incorrectly. If
301 these are wrong, you can remake them by running the script
308 If you hear people talking of the devices `hd1a' and `hd1b', these
/linux-4.4.14/security/
DKconfig48 If enabled, a security module can use these hooks to
57 If enabled, a security module can use these hooks to
70 If enabled, a security module can use these hooks to
/linux-4.4.14/arch/x86/math-emu/
DREADME59 (1) Add, subtract, and multiply. Nothing remarkable in these.
107 functions and its 80486 value with these functions is likely to differ
121 If all of these apply, the emulator will set the Underflow flag but a real
126 and Unnormals. None of these will be generated by an 80486 or by the
233 these never exceeds 1/2 an lsb. The fprem and fprem1 instructions
274 consequence, the accuracy of these functions for large arguments has
306 has been considerably improved and these functions now give measured
313 accuracy in number of times per million, thus the second of these
359 results of relatively poor accuracy for these instructions when the
/linux-4.4.14/Documentation/crypto/
Ddescore-readme.txt36 71755.204@compuserve.com, sparked a number of these enhancements.
185 note that 99% of C programs make these assumptions.
203 these are just performance tweaks.
211 these optimizations are all rather persnickety, yet with them you should
225 the 6 bits of data is the low part; it helps to exchange these.
247 do the arithmetic, so i assign these to explicit `m' register variables
292 it generates the special 64k table these routines need.
307 two bits of each byte are not used. note that these two bits
344 to use these with kerberos or kerberos-compatible code put desCore.a
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DNAND.txt23 OOB layout remains the default kernel layout for these flashes.
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dmarvell,pxa2xx-lcdc.txt5 - compatible : one of these
/linux-4.4.14/Documentation/devicetree/bindings/hwlock/
Dqcom-hwspinlock.txt4 the SoC as part of the communication protocol used by these processors.
/linux-4.4.14/drivers/mcb/
DKconfig14 for these devices.
/linux-4.4.14/kernel/configs/
Dxen.config1 # global stuff - these enable us to allow some
/linux-4.4.14/Documentation/mic/
Dmic_overview.txt14 devices for networking, storage and console. We provide these devices
33 "client" driver on the MIC cards over SCIF to perform these functions.
/linux-4.4.14/drivers/media/usb/ttusb-dec/
DKconfig10 Even if these devices have a MPEG decoder built in, they transmit
/linux-4.4.14/drivers/staging/fbtft/
DREADME5 The module 'fbtft' makes writing drivers for some of these displays very easy.
/linux-4.4.14/arch/score/
DKconfig.debug14 pass arguments to the kernel. For these platforms, you can supply
/linux-4.4.14/drivers/staging/rdma/
DKconfig15 If you wish to work on these drivers, to help improve them, or
/linux-4.4.14/drivers/net/ethernet/silan/
DKconfig26 have one of these, say Y here.
/linux-4.4.14/arch/m68k/kernel/
Dsun3-head.S25 | todo: all these should be in bss!
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dnand.txt19 The interpretation of these parameters is implementation-defined, so not all
/linux-4.4.14/Documentation/scsi/
Dlpfc.txt22 Please heed these dependencies....
40 to the system. If the driver did not hide these conditions, i/o would be
/linux-4.4.14/drivers/iio/gyro/
DKconfig98 This driver can also be built as a module. If so, these modules
104 (*) one of these is necessary to do something.
/linux-4.4.14/Documentation/driver-model/
Dporting.txt20 be embedded in larger, bus-specific objects. Fields in these generic
282 core calls. Most of these operations are probably similar to
306 The generic driver should be initialized with these methods before it
334 bus driver compares these IDs to the IDs of devices registered with it.
408 The core provides an iterator to access these devices.
440 fields in the bus-specific representations of these objects. Feel free
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-grgpio.txt6 these properties are built from information in the AMBA plug&play.
/linux-4.4.14/drivers/media/usb/tm6000/
DKconfig11 Since these cards have no MPEG decoder onboard, they transmit
/linux-4.4.14/net/wimax/
DKconfig14 Please note that most of these devices require signing up
/linux-4.4.14/drivers/net/ethernet/seeq/
DKconfig23 If you have an Acorn system with one of these network cards, you
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dbroadcom-bcm87xx.txt2 have these bindings in addition to the standard PHY bindings.
/linux-4.4.14/drivers/gpu/drm/omapdrm/
DTODO6 . This is mainly theoretical since most of these devices don't actually
/linux-4.4.14/drivers/net/wireless/
DKconfig87 one of these, you will need to provide a firmware image
165 Note: You need a motherboard with DMA support to use any of these cards
212 All of these devices are based on Broadcom 4320 chip which is the
238 However, some of these cards have been replaced with other chips
/linux-4.4.14/Documentation/arm/
Dswp_emulation7 ARMv7 multiprocessing extensions introduce the ability to disable these
/linux-4.4.14/tools/testing/selftests/zram/
DREADME6 (<id> = 0, 1, ...). Pages written to these disks are compressed and stored
/linux-4.4.14/net/unix/
DKconfig11 the X Window system and syslog use these sockets even if your
/linux-4.4.14/arch/arc/boot/dts/
Dnsim_hs_idu.dts50 * upstream irqs to core intc - downstream these are
/linux-4.4.14/Documentation/devicetree/bindings/lpddr2/
Dlpddr2-timings.txt11 data-sheet of the device for a given speed-bin. All these properties are

123456