| /linux-4.4.14/arch/arm/boot/dts/ |
| D | sama5d3_gmac.dtsi | 2 * sama5d3_gmac.dtsi - Device Tree Include file for SAMA5D3 SoC with
20 <AT91_PIOB 0 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB0 periph A GTX0, conflicts with PWMH0 */
21 AT91_PIOB 1 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB1 periph A GTX1, conflicts with PWML0 */
22 AT91_PIOB 2 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB2 periph A GTX2, conflicts with TK1 */
23 AT91_PIOB 3 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB3 periph A GTX3, conflicts with TF1 */
24 AT91_PIOB 4 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB4 periph A GRX0, conflicts with PWMH1 */
25 AT91_PIOB 5 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB5 periph A GRX1, conflicts with PWML1 */
26 AT91_PIOB 6 AT91_PERIPH_A AT91_PINCTRL_NONE /* PB6 periph A GRX2, conflicts with TD1 */
27 AT91_PIOB 7 AT91_PERIPH_A AT91_PINCTRL_NONE>; /* PB7 periph A GRX3, conflicts with RK1 */
31 … <AT91_PIOB 19 AT91_PERIPH_B AT91_PINCTRL_NONE /* PB19 periph B GTX4, conflicts with MCI1_CDA */
[all …]
|
| D | at91sam9x5_isi.dtsi | 2 * at91sam9x5_isi.dtsi - Device Tree Include file for AT91SAM9x5 SoC with an
20 <AT91_PIOC 0 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_D0, conflicts with LCDDAT0 */
21 AT91_PIOC 1 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_D1, conflicts with LCDDAT1 */
22 AT91_PIOC 2 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_D2, conflicts with LCDDAT2 */
23 AT91_PIOC 3 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_D3, conflicts with LCDDAT3 */
24 AT91_PIOC 4 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_D4, conflicts with LCDDAT4 */
25 AT91_PIOC 5 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_D5, conflicts with LCDDAT5 */
26 AT91_PIOC 6 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_D6, conflicts with LCDDAT6 */
27 AT91_PIOC 7 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_D7, conflicts with LCDDAT7 */
28 AT91_PIOC 12 AT91_PERIPH_B AT91_PINCTRL_NONE /* ISI_PCK, conflicts with LCDDAT12 */
[all …]
|
| D | sama5d3_mci2.dtsi | 2 * sama5d3_mci2.dtsi - Device Tree Include file for SAMA5D3 SoC with
21 … <AT91_PIOC 15 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC15 periph A MCI2_CK, conflicts with PCK2 */
22 AT91_PIOC 10 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PC10 periph A MCI2_CDA with pullup */
23 AT91_PIOC 11 AT91_PERIPH_A AT91_PINCTRL_PULL_UP>; /* PC11 periph A MCI2_DA0 with pullup */
27 …2 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PC12 periph A MCI2_DA1 with pullup, conflicts with TIOA1 */
28 …3 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PC13 periph A MCI2_DA2 with pullup, conflicts with TIOB1 */
29 …AT91_PERIPH_A AT91_PINCTRL_PULL_UP>; /* PC14 periph A MCI2_DA3 with pullup, conflicts with TCLK1 */
|
| D | sama5d3_emac.dtsi | 2 * sama5d3_emac.dtsi - Device Tree Include file for SAMA5D3 SoC with
20 <AT91_PIOC 0 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC0 periph A ETX0, conflicts with TIOA3 */
21 AT91_PIOC 1 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC1 periph A ETX1, conflicts with TIOB3 */
22 AT91_PIOC 2 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC2 periph A ERX0, conflicts with TCLK3 */
23 AT91_PIOC 3 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC3 periph A ERX1, conflicts with TIOA4 */
24 AT91_PIOC 4 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC4 periph A ETXEN, conflicts with TIOB4 */
25 AT91_PIOC 5 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC5 periph A ECRSDV,conflicts with TCLK4 */
26 AT91_PIOC 6 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC6 periph A ERXER, conflicts with TIOA5 */
27 AT91_PIOC 7 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC7 periph A EREFCK, conflicts with TIOB5 */
28 AT91_PIOC 8 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC8 periph A EMDC, conflicts with TCLK5 */
|
| D | sama5d3.dtsi | 538 <AT91_PIOD 30 AT91_PERIPH_A AT91_PINCTRL_NONE>; /* PD30 periph A AD10, conflicts with PCK0 */
542 <AT91_PIOD 31 AT91_PERIPH_A AT91_PINCTRL_NONE>; /* PD31 periph A AD11, conflicts with PCK1 */
550 AT91_PIOB 31 AT91_PERIPH_A AT91_PINCTRL_PULL_UP>; /* PB31 periph A with pullup */
557 …<AT91_PIOA 30 AT91_PERIPH_A AT91_PINCTRL_NONE /* PA30 periph A TWD0 pin, conflicts with URXD1, ISI…
558 …AT91_PIOA 31 AT91_PERIPH_A AT91_PINCTRL_NONE>; /* PA31 periph A TWCK0 pin, conflicts with UTXD1, I…
565 …<AT91_PIOC 26 AT91_PERIPH_B AT91_PINCTRL_NONE /* PC26 periph B TWD1 pin, conflicts with SPI1_NPCS1…
566 …AT91_PIOC 27 AT91_PERIPH_B AT91_PINCTRL_NONE>; /* PC27 periph B TWCK1 pin, conflicts with SPI1_NPC…
573 <AT91_PIOA 18 AT91_PERIPH_B AT91_PINCTRL_NONE /* TWD2 pin, conflicts with LCDDAT18, ISI_D2 */
574 … AT91_PIOA 19 AT91_PERIPH_B AT91_PINCTRL_NONE>; /* TWCK2 pin, conflicts with LCDDAT19, ISI_D3 */
581 … <AT91_PIOA 16 AT91_PERIPH_C AT91_PINCTRL_NONE /* PA16 periph C ISI_D0, conflicts with LCDDAT16 */
[all …]
|
| D | sama5d3_uart.dtsi | 2 * sama5d3_uart.dtsi - Device Tree Include file for SAMA5D3 SoC with
26 … <AT91_PIOC 29 AT91_PERIPH_A AT91_PINCTRL_NONE /* PC29 periph A, conflicts with PWMFI2, ISI_D8 */
27 …_PIOC 30 AT91_PERIPH_A AT91_PINCTRL_PULL_UP>; /* PC30 periph A with pullup, conflicts with ISI_PCK…
34 … <AT91_PIOA 30 AT91_PERIPH_B AT91_PINCTRL_NONE /* PA30 periph B, conflicts with TWD0, ISI_VSYNC */
35 …_PIOA 31 AT91_PERIPH_B AT91_PINCTRL_PULL_UP>; /* PA31 periph B with pullup, conflicts with TWCK0, …
|
| D | at91sam9x5_can.dtsi | 2 * at91sam9x5_can.dtsi - Device Tree Include file for AT91SAM9x5 SoC with 1
56 <AT91_PIOA 9 AT91_PERIPH_B AT91_PINCTRL_NONE /* CANRX0, conflicts with DRXD */
57 AT91_PIOA 10 AT91_PERIPH_B AT91_PINCTRL_NONE>; /* CANTX0, conflicts with DTXD */
64 <AT91_PIOA 6 AT91_PERIPH_B AT91_PINCTRL_NONE /* CANRX1, conflicts with RXD1 */
65 AT91_PIOA 5 AT91_PERIPH_B AT91_PINCTRL_NONE>; /* CANTX1, conflicts with TXD1 */
|
| D | sama5d3_can.dtsi | 2 * sama5d3_can.dtsi - Device Tree Include file for SAMA5D3 SoC with
20 …<AT91_PIOD 14 AT91_PERIPH_C AT91_PINCTRL_NONE /* PD14 periph C RX, conflicts with SCK0, SPI0_NPCS1…
21 …AT91_PIOD 15 AT91_PERIPH_C AT91_PINCTRL_NONE>; /* PD15 periph C TX, conflicts with CTS0, SPI0_NPCS…
28 <AT91_PIOB 14 AT91_PERIPH_B AT91_PINCTRL_NONE /* PB14 periph B RX, conflicts with GCRS */
29 AT91_PIOB 15 AT91_PERIPH_B AT91_PINCTRL_NONE>; /* PB15 periph B TX, conflicts with GCOL */
|
| D | at91sam9263.dtsi | 416 AT91_PIOC 31 AT91_PERIPH_A AT91_PINCTRL_PULL_UP>; /* PC31 periph with pullup */
423 <AT91_PIOA 26 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PA26 periph A with pullup */
441 <AT91_PIOD 0 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PD0 periph A with pullup */
459 <AT91_PIOD 2 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PD2 periph A with pullup */
518 <AT91_PIOA 1 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PA1 periph A with pullup */
519 AT91_PIOA 0 AT91_PERIPH_A AT91_PINCTRL_PULL_UP>; /* PA0 periph A with pullup */
524 <AT91_PIOA 3 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PA3 periph A with pullup */
525 AT91_PIOA 4 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PA4 periph A with pullup */
526 AT91_PIOA 5 AT91_PERIPH_A AT91_PINCTRL_PULL_UP>; /* PA5 periph A with pullup */
531 <AT91_PIOA 16 AT91_PERIPH_A AT91_PINCTRL_PULL_UP /* PA16 periph A with pullup */
[all …]
|
| /linux-4.4.14/Documentation/ |
| D | 00-INDEX | 29 - How to do DMA with ISA (and LPC) devices.
33 - directory with DocBook templates etc. for kernel documentation.
35 - directory with info on customizing EDID for broken gfx/displays.
53 - directory with info on RCU (read-copy update).
73 - description of AoE (ATA over Ethernet) along with config examples.
77 - directory with info about Linux on the ARM architecture.
79 - directory with info about Linux on the 64 bit ARM architecture.
87 - directory with info on controlling backlights in flat panel displays
97 - directory with documentation for the Blackfin arch.
109 - directory with info on TI GPMC (General Purpose Memory Controller)
[all …]
|
| D | SubmitChecklist | 16 2: Builds cleanly with applicable or modified CONFIG options =y, =m, and
30 Documentation/CodingStyle. Check for trivial violations with the
39 8: Has been carefully reviewed with respect to relevant Kconfig
40 combinations. This is very hard to get right with testing -- brainpower
43 9: Check cleanly with sparse.
54 12: Has been tested with CONFIG_PREEMPT, CONFIG_DEBUG_PREEMPT,
59 13: Has been build- and runtime tested with and without CONFIG_SMP and
62 14: If the patch affects IO/Disk, etc: has been tested with and without
65 15: All codepaths have been exercised with all lockdep features enabled.
72 18: All new module parameters are documented with MODULE_PARM_DESC()
[all …]
|
| D | percpu-rw-semaphore.txt | 7 The problem with traditional read-write semaphores is that when multiple
17 The lock is declared with "struct percpu_rw_semaphore" type.
20 The lock must be freed with percpu_free_rwsem to avoid memory leak.
22 The lock is locked for read with percpu_down_read, percpu_up_read and
23 for write with percpu_down_write, percpu_up_write.
|
| D | flexible-arrays.txt | 7 pages with vmalloc(). This solution not ideal, though. On 32-bit systems,
29 The creation of a flexible array is done with:
43 It is also possible to define flexible arrays at compile time with:
47 This macro will result in a definition of an array with the given name; the
50 Storing data into a flexible array is accomplished with a call to:
76 Getting data back out of the array is done with:
89 Note that, if array elements are allocated with __GFP_ZERO, they will be
92 Individual elements in the array can be cleared with:
99 element does not release the storage associated with it; to reduce the
107 if the array's pages are allocated with __GFP_ZERO.
[all …]
|
| D | coccinelle.txt | 37 as a regular user, and install it with
49 use is specified by setting the MODE variable with 'MODE=<mode>'.
57 diff-like style.Lines of interest are indicated with '-'.
69 It should be used with the C option (described later)
103 Using Coccinelle with a single semantic patch
107 semantic patch. In that case, the variable must be initialized with
142 The "report" mode is the default. You can select another one with the
158 thus active by default. However, by indexing the code with
197 msg="ERR_CAST can be used with %s" % (x)
204 /home/user/linux/crypto/ctr.c:188:9-16: ERR_CAST can be used with alg
[all …]
|
| D | parport.txt | 12 The parport code is split into two parts: generic (which deals with
13 port-sharing) and architecture-dependent (which deals with actually
25 architecture-dependent code with (for example):
30 0x3bc with no IRQ, one at 0x378 using IRQ 7, and one at 0x278 with an
48 modprobe will load parport_pc (with the options "io=0x378,0x278 irq=7,auto")
61 enhanced and now lives with the IEEE 1284 support. When a parallel
143 with tabs. These values might not have any sensible
206 with no lp device associated with the second port (parport1). Note
219 * If you give PLIP the `timid' parameter, either with `plip=timid' on
220 the command line, or with `insmod plip timid=1' when using modules,
[all …]
|
| D | printk-formats.txt | 31 Raw pointer value SHOULD be printed with %p. The kernel supports
40 (with __builtin_extract_return_addr() translation)
45 result in the symbol name with ('S') or without ('s') offsets. Where
49 The 'B' specifier results in the symbol name with offsets and should be
52 when tail-call's are used and marked with the noreturn GCC attribute.
75 printed resource with ('R') or without ('r') a decoded flags member.
132 For printing a small buffers (up to 64 bytes long) as a hex string with
145 specifiers result in a printed address with ('M') or without ('m') byte
165 specifiers result in a printed address with ('i4') or without ('I4')
181 specifiers result in a printed address with ('I6') or without ('i6')
[all …]
|
| D | gcov.txt | 1 Using gcov with the Linux kernel
19 tool gcov [1] with the Linux kernel. Coverage data of a running kernel
22 directory and use gcov with the -o option as follows (requires root):
27 This will create source code files annotated with execution counts
48 Configure the kernel with:
61 Note that kernels compiled with profiling flags will be significantly
112 tool. This file is generated by gcc when compiling with
122 with the unloaded module. This data remains available through debugfs.
124 initialized with the data from its previous instantiation.
145 The gcov tool version on the test machine must be compatible with the
[all …]
|
| D | binfmt_misc.txt | 9 with which binary. Binfmt_misc recognises the binary-type by matching some bytes
10 at the beginning of the file with a magic byte sequence (masking out specified
22 - 'name' is an identifier string. A new /proc file will be created with this
38 The mask is anded with the byte sequence of the file. Note that you must
41 - 'interpreter' is the program that should be invoked with the binary as first
47 the original argv[0] with the full path to the binary. When this
51 in /usr/local/bin), then the kernel will execute /bin/foo with
54 with argv[] set to ["blah"].
60 should be used with care - the interpreter has to be trusted not to
66 This feature should be used with care as the interpreter
[all …]
|
| D | initrd.txt | 15 where the kernel comes up with a minimum set of compiled-in drivers, and
36 shell scripts; it is run with uid 0 and can do basically everything
77 with the RAM disk mounted as root.
85 disk with the desired initrd content, cd to that directory, and run (as an
117 Second, the kernel has to be compiled with RAM disk support and with
147 even without rebooting with the command
149 This is of course limited to initrds that do not interfere with the
160 For experimenting with initrd, you may want to take a rescue floppy and
167 with an older mechanism, the following boot command line parameters
197 When finished with its duties, init typically changes the root device
[all …]
|
| D | kobject.txt | 13 place. Dealing with kobjects requires understanding a few different types,
15 easier, we'll take a multi-pass approach, starting with vague terms and
17 some terms we will be working with.
51 It is rare for kernel code to create a standalone kobject, with one major
62 (As an aside, for those familiar with the kernel linked list implementation,
68 defines the memory region associated with a uio device:
76 just a matter of using the kobj member. Code that works with kobjects will
93 *containing* uio_map structure with:
109 question. That macro is subsequently invoked with:
117 of the internal fields are setup with a (mandatory) call to kobject_init():
[all …]
|
| D | padata.txt | 6 developed for use with the IPsec code, which needs to be able to perform
26 To allocate a padata instance with the cpu_possible_mask for both
51 The list of CPUs to be used can be adjusted with these functions:
62 done with great frequency.
64 It's possible to change both cpumasks of a padata instance with
87 Padata calls the notifier chain with:
113 The submission of work is done with:
122 progress. -EBUSY means that somebody, somewhere else is messing with the
129 fact that the workqueue is used to make these calls, parallel() is run with
138 outstanding, it should be prepared to be called again with a new job before
[all …]
|
| D | efi-stub.txt | 7 along with the EFI-specific entry point that the firmware loader
25 The EFI boot stub is enabled with the CONFIG_EFI_STUB kernel option.
31 System Partition (ESP) and renamed with the extension ".efi". Without
56 is an EFI-style path and directory elements must be separated with
68 to boot with the initrd-large.img file if the current working
73 Notice how bzImage.efi can be specified with a relative path. That's
82 device tree to the kernel. This is done with the "dtb=" command line option,
|
| D | numastat.txt | 12 but ended up with memory from this node.
15 but ended up with memory from another one.
26 well right now on machines with a small number of CPUs.
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | HD-Audio-Models.txt | 10 6stack-digout 6-jack with a SPDIF out
17 fujitsu-jwse Quirk for FSC S7020 with jack modes and HP mic support
30 laptop-amic Laptops with analog-mic input
31 laptop-dmic Laptops with digital-mic input
42 alc283-dac-wcaps Fixups for Chromebook with ALC283
92 3stack-automute 3-stack with automute front HP (default)
98 laptop laptop with HP jack sensing
99 mobile mobile devices with HP jack sensing
128 laptop-imic 2-channel with built-in mic
134 6stack-dig ditto with SPDIF
[all …]
|
| D | timestamping.txt | 7 estimate with a delay. In the latter two cases, the low-level driver
11 provides a refined estimate with a delay.
18 and delay, which combined with the trigger and current system
30 along with a snapshot of system time. Applications can select from
34 dynamically with sw_params
58 supported in hardware by sample counters or wallclocks (e.g. with
60 estimated (e.g. with the frame counter in USB).
74 time with dedicated hardware, possibly synchronized with system time,
82 For backwards compatibility with previous implementations that did not
83 provide timestamp selection, with a zero-valued COMPAT timestamp type
[all …]
|
| D | Audiophile-Usb.txt | 1 Guide to using M-Audio Audiophile USB with ALSA and Jack v1.5
6 This document is a guide to using the M-Audio Audiophile USB (tm) device with
82 parameter), or in an "advanced" mode with the device-specific parameter called
127 If you're happy with the default Alsa driver mode and don't experience any
128 issue with this mode, then you can skip the following chapter.
136 from the Ai interface sounds distorted (as if boosted with an excessive high
151 When initialized with "device_setup=0x00", the snd-usb-audio module has
162 - 16bits 48kHz mode with Di disabled
168 - 16bits 48kHz mode with Di enabled
190 - 24bits 48kHz mode with Di disabled
[all …]
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | PROBLEMS | 25 with his S3 868 went away when he upgraded to XFree 3.2.
28 - I still only get a black picture with my S3 card!
30 Even with XFree-3.2A some people have problems with their S3 cards
31 (mostly with Trio 64 but also with some others)
33 bttv with it. bttv seems to work with most S3 cards with Accelerated X.
39 Would be nice if somebody could get this to work with XFree since
45 - Grabbing is not switched off when changing consoles with XFree.
51 Disable backing store by starting X with the option "-bs"
59 - Some S3 cards and the Matrox Mystique will produce pixel errors with
62 - Some video cards have problems with Accelerated X 4.1
|
| D | README.freeze | 2 If the box freezes hard with bttv ...
37 other people. But in case you have problems with the 0.7.x versions you
44 Some hardware can't deal with PCI-PCI transfers (i.e. grabber => vga).
45 Sometimes problems show up with bttv just because of the high load on
54 Some mainboard have problems to deal correctly with multiple devices
56 if this is the case you likely see freezes only with video and hard disk
70 it share the IRQ with some other piece of hardware. IRQ sharing with
72 effects with bttv sharing the IRQ with the ACPI bridge (and
|
| D | README | 13 Make bttv work with your card
24 If bttv takes very long to load (happens sometimes with the cheap
51 ID and therefore can't be autodetected. There is a list with the ID's
53 with updates).
59 I do NOT have a lab with 30+ different grabber boards and a
69 If you have trouble with some specific TV card, try to ask there
70 instead of mailing me directly. The chance that someone with the
73 For problems with sound: There are a lot of different systems used
85 Have fun with bttv,
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | trivial-devices.txt | 12 abracon,abb5zes3 AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
13 ad,ad7414 SMBus/I2C Digital Temperature Sensor in 6-Pin SOT with SMBus Alert and Over Temperature …
41 dallas,ds1338 I2C RTC with 56-Byte NV RAM
42 dallas,ds1340 I2C RTC with Trickle Charger
43 dallas,ds1374 I2C, 32-Bit Binary Counter Watchdog RTC with Trickle Charger and Reset Input/Output
45 dallas,ds1682 Total-Elapsed-Time Recorder with Alarm
47 dallas,ds3232 Extremely Accurate I²C RTC with Integrated Crystal and SRAM
48 dallas,ds4510 CPU Supervisor with Nonvolatile Memory and Programmable I/O
50 dlg,da9053 DA9053: flexible system level PMIC with multicore support
59 gmt,g751 G751: Digital Temperature Sensor and Thermal Watchdog with Two-Wire Interface
[all …]
|
| D | i2c-mt6577.txt | 3 The Mediatek's I2C controller is used to interface with I2C devices.
7 (a) "mediatek,mt6577-i2c", for i2c compatible with mt6577 i2c.
8 (b) "mediatek,mt6589-i2c", for i2c compatible with mt6589 i2c.
9 (c) "mediatek,mt8127-i2c", for i2c compatible with mt8127 i2c.
10 (d) "mediatek,mt8135-i2c", for i2c compatible with mt8135 i2c.
11 (e) "mediatek,mt8173-i2c", for i2c compatible with mt8173 i2c.
|
| D | i2c-exynos5.txt | 3 The Samsung's High Speed I2C controller is used to interface with I2C devices
9 for i2c compatible with HSI2C available
11 -> "samsung,exynos5250-hsi2c", for i2c compatible with HSI2C available
13 -> "samsung,exynos5260-hsi2c", for i2c compatible with HSI2C available
15 -> "samsung,exynos7-hsi2c", for i2c compatible with HSI2C available
|
| D | nvidia,tegra20-i2c.txt | 13 controller. Driver of DVC I2C controller is only compatible with
18 only compatible with "nvidia,tegra20-i2c".
20 very much similar to Tegra20 I2C controller with additional feature:
23 compatible with "nvidia,tegra30-i2c" to enable the continue transfer
24 support. This is also compatible with "nvidia,tegra20-i2c" without
27 very much similar to Tegra30 I2C controller with some hardware
35 Due to above changes, Tegra114 I2C driver makes incompatible with
37 with "nvidia,tegra114-i2c".
|
| /linux-4.4.14/Documentation/usb/ |
| D | anchors.txt | 9 keeping track of URBs and provides methods to deal with
22 Once it has no more URBs associated with it, the anchor can be
23 freed with normal memory management operations.
25 Association and disassociation of URBs with anchors
32 all URBs associated with an anchor.
33 Furthermore, disassociation can be made with usb_unanchor_urb()
41 This function kills all URBs associated with an anchor. The URBs
48 This function unlinks all URBs associated with an anchor. The URBs
63 This function waits for all URBs associated with an anchor to finish
70 Returns true if no URBs are associated with an anchor. Locking
[all …]
|
| D | usb-serial.txt | 38 ConnectTech has been very forthcoming with information about their
39 device, including providing a unit to test with.
44 For any questions or problems with this driver, please contact
50 This driver works with all HandSpring USB, Palm USB, and Sony Clié USB
82 Devices that are not compiled into the kernel can be specified with module
88 For any questions or problems with this driver, please contact Greg
122 up with a "Connected to usbdial" window with status shown as connected.
126 with the module parameter "debug" set to 1 and examine the system log.
130 Wes Cilldhaire <billybobjoehenrybob@hotmail.com>, with the Toshiba E570,
133 is displayed), then put it in the cradle with the ipaq driver loaded, open
[all …]
|
| D | rio.txt | 26 It seems that the Rio has a problem when sending .mp3 with low batteries.
28 replace it with a fresh one. In my case, what happened is I lost two 16kb
30 know if that's normal or not; it could simply be a problem with the flash
40 On systems with OHCI controllers, the kernel OHCI code appears to have
41 power on problems with some chipsets. If you are having problems
60 re-written and Pete Ikusz along with the rest will re-design it. I would
62 with some important information regarding the communication with the Rio.
71 A host with a USB port. Ideally, either a UHCI (Intel) or OHCI
74 A Linux development kernel (2.3.x) with USB support enabled or a
78 A Linux kernel with RIO 500 support enabled.
|
| D | gadget_multi.txt | 10 with RNDIS[1] (that is Ethernet), USB CDC[2] ACM (that is serial) and
15 have two configurations -- one with RNDIS and another with CDC ECM[3].
23 without that there's no hope of achieving anything with the gadget.
33 This is also true for two configuration set-up with RNDIS
35 configuration with CDC ECM which should work better under Linux.
64 Things are harder with RDNIS and CDC ACM.
69 gadget, one needs to use the [[file:linux.inf]] file provided with this
90 This also means, that after experimenting with g_multi and changing
92 so there will be no collision with other customised gadgets or the
121 ([[mailto:mina86@mina86.com]]). INF files have been hacked with
|
| D | chipidea.txt | 4 with 2 Freescale i.MX6Q sabre SD boards.
17 1) Power up 2 Freescale i.MX6Q sabre SD boards with gadget class driver loaded
20 2) Connect 2 boards with usb cable with one end is micro A plug, the other end
23 The A-device(with micro A plug inserted) should enumrate B-device.
60 A-device should disconnect with B-device and power down the bus.
|
| /linux-4.4.14/arch/arc/include/asm/ |
| D | cmpxchg.h | 109 #define _xchg(ptr, with) ((typeof(*(ptr)))__xchg((unsigned long)(with), (ptr), \ argument
129 #define xchg(ptr, with) \ argument
135 old_val = _xchg(ptr, with); \
142 #define xchg(ptr, with) _xchg(ptr, with) argument
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | spear.txt | 4 Boards with the ST SPEAr600 SoC shall have the following properties:
8 Boards with the ST SPEAr300 SoC shall have the following properties:
12 Boards with the ST SPEAr310 SoC shall have the following properties:
16 Boards with the ST SPEAr320 SoC shall have the following properties:
20 Boards with the ST SPEAr1310 SoC shall have the following properties:
24 Boards with the ST SPEAr1340 SoC shall have the following properties:
|
| D | vt8500.txt | 4 Boards with the VIA VT8500 SoC shall have the following properties:
8 Boards with the Wondermedia WM8505 SoC shall have the following properties:
12 Boards with the Wondermedia WM8650 SoC shall have the following properties:
16 Boards with the Wondermedia WM8750 SoC shall have the following properties:
20 Boards with the Wondermedia WM8850 SoC shall have the following properties:
|
| D | sti.txt | 4 Boards with the ST STiH415 SoC shall have the following properties:
8 Boards with the ST STiH416 SoC shall have the following properties:
12 Boards with the ST STiH407 SoC shall have the following properties:
16 Boards with the ST STiH410 SoC shall have the following properties:
20 Boards with the ST STiH418 SoC shall have the following properties:
|
| D | altera.txt | 4 Boards with Cyclone 5 SoC:
8 Boards with Arria 5 SoC:
12 Boards with Arria 10 SoC:
|
| D | psci.txt | 30 IDs are not required and should be ignored by an OS with PSCI 0.2
31 support, but are permitted to be present for compatibility with
35 backward compatible with PSCI 0.2 with minor specification updates,
41 "smc" : SMC #0, with the register assignments specified
44 "hvc" : HVC #0, with the register assignments specified
92 These IDs will be ignored by kernels with PSCI 0.2 support, which will
|
| D | amlogic.txt | 4 Boards with the Amlogic Meson6 SoC shall have the following properties:
8 Boards with the Amlogic Meson8 SoC shall have the following properties:
12 Boards with the Amlogic Meson8b SoC shall have the following properties:
|
| D | arm-boards | 3 ARM's oldest Linux-supported platform with connectors for different core
15 a core-module with regs and the compatible string
18 must have an external bus interface with regs and the
27 with the compatible string
71 ARM's development hardware platform with connectors for customizable
93 a core-module with regs and the compatible strings
126 with the compatible string set to one of these tuples:
144 model = "ARM RealView PB1176 with device tree";
170 with the second iteration, Juno r1, mainly aimed at development of PCIe
175 with the motherboard part of the hardware being described in a separate file
|
| /linux-4.4.14/arch/arc/plat-axs10x/ |
| D | Kconfig | 19 The AXS10x Platforms consist of a mainboard with peripherals,
27 bool "AXS101 with AXC001 CPU Card (ARC 770D/EM6/AS221)"
32 The AXS101 Platform consists of an AXS10x mainboard with
34 with this configuration.
37 bool "AXS103 with AXC003 CPU Card (ARC HS38x)"
42 The AXS103 Platform consists of an AXS10x mainboard with
44 with this configuration.
|
| /linux-4.4.14/tools/testing/selftests/rcutorture/doc/ |
| D | TREE_RCU-kconfig.txt | 12 CONFIG_NO_HZ_FULL -- Do two, one with CONFIG_NO_HZ_FULL_SYSIDLE.
19 CONFIG_RCU_FANOUT -- Cover hierarchy, but overlap with others.
21 CONFIG_RCU_FAST_NO_HZ -- Do one, but not with CONFIG_RCU_NOCB_CPU_ALL.
29 RCU-bh: Do one with PREEMPT and one with !PREEMPT.
30 RCU-sched: Do one with PREEMPT but not BOOST.
56 Redundant with CONFIG_PREEMPT, ignore.
77 Redundant with CONFIG_NO_HZ_FULL.
|
| /linux-4.4.14/Documentation/arm64/ |
| D | memory.txt | 8 tables with a 4KB page size and up to 3 levels with a 64KB page size.
11 with the 4KB page configuration, allowing 39-bit (512GB) or 48-bit
24 AArch64 Linux memory layout with 4KB pages + 3 levels:
32 AArch64 Linux memory layout with 4KB pages + 4 levels:
40 AArch64 Linux memory layout with 64KB pages + 2 levels:
48 AArch64 Linux memory layout with 64KB pages + 3 levels:
60 Translation table lookup with 4KB pages:
75 Translation table lookup with 64KB pages:
|
| /linux-4.4.14/sound/oss/ |
| D | CHANGELOG | 39 - Disabled MIDI input with GUS PnP (Interwave). There seems to be constant
48 with GUS.
49 - Limited minimum fragment size with some audio devices (GUS=512 and
57 You can safely use this driver version with C930 if it looks to work.
58 However please don't complain if you have problems with it. C930 support
63 been causing "audio device opening" errors with RealAudio player.
76 - Fixed silent playback with ESS 688/1688.
86 - Reduced clicking with AD1848.
94 - Renamed sb16_midi.c to uart401.c. Also modified it to work also with
108 - Fixed for compatibility with Linux 1.3.70 and later.
[all …]
|
| /linux-4.4.14/sound/soc/intel/ |
| D | Kconfig | 57 tristate "ASoC Audio driver for Intel Baytrail with RT5640 codec"
65 with the RT5640 audio codec.
68 tristate "ASoC Audio driver for Intel Baytrail with MAX98090 codec"
76 with the MAX98090 audio codec.
105 tristate "ASoC Audio driver for Intel Cherrytrail & Braswell with RT5672 codec"
112 platforms with RT5672 audio codec.
117 tristate "ASoC Audio driver for Intel Cherrytrail & Braswell with RT5645/5650 codec"
124 platforms with RT5645/5650 audio codec.
128 tristate "ASoC Audio driver for Intel Cherrytrail & Braswell with MAX98090 & TI codec"
136 platforms with MAX98090 audio codec it also can support TI jack chip as aux device.
[all …]
|
| /linux-4.4.14/sound/soc/mediatek/ |
| D | Kconfig | 6 that can be used with other codecs.
11 tristate "ASoC Audio driver for MT8173 with MAX98090 codec"
16 with the MAX98090 audio codec.
21 tristate "ASoC Audio driver for MT8173 with RT5650 RT5676 codecs"
27 with the RT5650 and RT5676 codecs.
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-annotate.txt | 52 Load module symbols. WARNING: use only with -k and LIVE kernel.
66 used. This interfaces starts by centering on the line with more
67 samples, TAB/UNTAB cycles through the lines with more samples.
73 be provided as a comma-separated list with no space: 0,1. Ranges of
74 CPUs are specified with -: 0-2. Default is to report samples on all
81 Interleave source code with assembly code. Enabled by default,
82 disable with --no-source.
85 Look for files with symbols relative to this directory.
|
| D | perf-archive.txt | 6 perf-archive - Create archive with object files with build-ids found in perf.data file
15 This command runs perf-buildid-list --with-hits, and collects the files with the
|
| D | perf-diff.txt | 39 Load module symbols. WARNING: use only with -k and LIVE kernel
67 Use a special separator character and don't pad with spaces, replacing
69 with a '.' character, that thus it's the only non valid separator.
81 Look for files with symbols relative to this directory.
85 Show only items with match in baseline.
120 baseline entry, are displayed with empty space within baseline column
124 - file A with samples f1, f2, f3, f4, f6
125 - file B with samples f2, f4, f5
126 - file C with samples f1, f2, f5
169 If specified the 'Delta' column is displayed with value 'd' computed as:
[all …]
|
| D | perf-trace.txt | 16 This command will show the events associated with the target, initially
20 This is a live mode tool in addition to working with perf.data files like
39 Prefixing with ! shows all syscalls but the ones specified. You may
71 specification with appended unit character - B/K/M/G. The
77 comma-separated list with no space: 0,1. Ranges of CPUs are specified with -: 0-2.
78 In per-thread mode with inheritance mode on (default), Events are captured only when
96 Show process COMM right beside its ID, on by default, disable with --no-comm.
100 Show only a summary of syscalls by thread with min, max, and average times
104 --with-summary::
105 Show all syscalls followed by a summary by thread with min, max, and
|
| D | perf-inject.txt | 6 perf-inject - Filter to augment the events stream with additional information
21 needs userspace processing to augment the events stream with additional
48 Decode Instruction Tracing data, replacing it with synthesized events.
54 Use with --itrace to strip out non-synthesized events.
|
| D | perf-buildid-list.txt | 16 tools can be used to fetch packages with matching symbol tables for use by
25 --with-hits::
26 Show only DSOs with hits.
|
| D | perf-probe.txt | 29 and C local variables) with debuginfo.
52 Can not use with -q.
57 Can not use with -v.
105 Forcibly add events with existing name.
118 space tracing. Can also be used with --funcs option.
139 2) Define event based on source file with line number
142 3) Define event based on source file with lazy pattern
157 …e, local data structure member (e.g. var->field, var.field2), local array with fixed index (e.g. a…
189 … for specifying filter-out rule. You also can give several rules combined with "&" or "|", and fol…
192 With --filter "foo* | bar*", perf probe -V shows variables which start with "foo" or "bar".
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/rtc/ |
| D | s3c-rtc.txt | 5 * "samsung,s3c2410-rtc" - for controllers compatible with s3c2410 rtc.
6 * "samsung,s3c2416-rtc" - for controllers compatible with s3c2416 rtc.
7 * "samsung,s3c2443-rtc" - for controllers compatible with s3c2443 rtc.
8 * "samsung,s3c6410-rtc" - for controllers compatible with s3c6410 rtc.
9 * "samsung,exynos3250-rtc" - (deprecated) for controllers compatible with
|
| D | moxa,moxart-rtc.txt | 6 - gpio-rtc-sclk : RTC sclk gpio, with zero flags
7 - gpio-rtc-data : RTC data gpio, with zero flags
8 - gpio-rtc-reset : RTC reset gpio, with zero flags
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi-changer.txt | 6 with "Type: Medium Changer" in /proc/scsi/scsi.
8 This is for *real* Jukeboxes. It is *not* supported to work with
49 I implemented the driver as character device driver with a NetBSD-like
52 should be source code compatible with NetBSD. So if there is any
54 it should work with this driver too.
66 I test and use the driver myself with a 35 slot cdrom jukebox from
67 Grundig. I got some reports telling it works ok with tape autoloaders
68 (Exabyte, HP and DEC). Some People use this driver with amanda. It
69 works fine with small (11 slots) and a huge (4 MOs, 88 slots)
70 magneto-optical Jukebox. Probably with lots of other changers too, most
[all …]
|
| D | ChangeLog.arcmsr | 10 ** 1.20.00.00 11/29/2004 Erich Chen bug fix with arcmsr_bus_reset when PHY error
11 ** 1.20.00.02 12/09/2004 Erich Chen bug fix with over 2T bytes RAID Volume
22 ** 1.20.00.06 3/12/2005 Erich Chen fix with arcmsr_pci_unmap_dma "unsigned long" cast,
25 ** 1.20.00.07 3/23/2005 Erich Chen bug fix with arcmsr_scsi_host_template_init
30 ** 1.20.00.08 6/23/2005 Erich Chen bug fix with abort command,
33 ** 1.20.00.09 9/12/2005 Erich Chen bug fix with abort command handling, firmware versi…
36 ** add DMA_64BIT_MASK for backward compatible with all 2.6.x
42 ** 1.20.00.12 9/30/2005 Erich Chen bug fix with 64bit platform's ccbs using if over 4G…
51 ** 1.20.00.13 11/15/2005 Erich Chen scheduling pending ccb with FIFO
62 ** inconsistency with sg_mod driver if application directly calls
[all …]
|
| D | ChangeLog.ips | 63 4.20.03 - Rename version to coincide with new release schedules
65 - Fix truncation of /proc files with cat
72 4.00.06 - Fix timeout with initial FFDC command
77 - Sync with other changes from the 2.3 kernels
79 4.00.04 - Rename structures/constants to be prefixed with IPS_
84 4.00.02 - Fix problem with PT DCDB with no buffer
95 3.60.00 - Bump max commands to 128 for use with ServeRAID
97 - Change version to 3.60 to coincide with ServeRAID release
|
| D | in2000.txt | 11 with. Done some heavy testing and it looks very good.
20 It appears that the driver works fine with serial
41 now we deal with all of them correctly. Thanks to Joerg
51 removed some kludge-code left over from struggles with
61 with it, start by doing 'cat /proc/scsi/in2000/0'. You
80 1.25 had a nasty bug that bit people with swap partitions
95 of in2000.c. For people with CDROM's or other devices
96 that have a tough time with sync negotiation, you can
119 run with the option to disconnect/reselect (if the device
131 minimum of debug messages. If you want to fool with the options,
[all …]
|
| D | qlogicfas.txt | 3 only works with the ISA, VLB, and PCMCIA versions of the Qlogic
24 rest of the modules won't interfere with the operation. The next
26 can be a simple ctrl-alt-delete with a boot floppy, or by using
27 loadlin with the kernel image accessible from DOS. If you are using
31 I am working with the PCMCIA group to make it more flexible, but that
40 with SCSI, there are other settings which can tune the bus.
69 the computer was left on for a few hours. It was worse with longer
|
| D | scsi_fc_transport.txt | 44 interact with the Fabric Port to join multiple fabrics. The port will
47 used together with VF so that the port can obtain multiple N_Port_IDs
53 be specified for the vport, with FCP_Initiator being the primary role
56 The fc_host associated with the physical adapter will export the ability
62 each will appear as a unique scsi_host with its own target and lun space.
71 if vports are to be associated with virtual machines, a XEN mgmt
81 with rports and scsi target objects underneath it. Currently the FC
135 is registered with the switch to identify the vport. For example,
141 When written with a "1", will tear down the vport.
144 When written with a "1", will transition the vport to a disabled.
[all …]
|
| /linux-4.4.14/Documentation/security/ |
| D | keys-ecryptfs.txt | 6 Each FEK is in turn encrypted with a File Encryption Key Encryption Key (FEFEK)
7 either in kernel space or in user space with a daemon called 'ecryptfsd'. In
10 the FEK is encrypted by 'ecryptfsd' with the help of external libraries in order
17 by the userspace utility 'mount.ecryptfs' shipped with the package
20 The 'encrypted' key type has been extended with the introduction of the new
21 format 'ecryptfs' in order to be used in conjunction with the eCryptfs
23 authentication token in its payload with a FEFEK randomly generated by the
48 Example of encrypted key usage with the eCryptfs filesystem:
50 Create an encrypted key "1000100010001000" of length 64 bytes with format
|
| D | SELinux.txt | 13 1. Compile the kernel with selinux enabled.
15 3. Make sure that you are not running with
17 you are, reboot with selinux disabled
24 kernel, with a single selinux user, role, and type.
|
| D | Smack.txt | 12 are encouraged to compare Smack with the other mechanisms
23 works best with file systems that support extended attributes,
44 smackaccess - report if a process with one label has access
45 to an object with another
47 These two commands are obsolete with the introduction of
53 In keeping with the intent of Smack, configuration data is
77 The Smack label of a process that execs a program file with
78 this attribute set will run with this attribute's value.
82 with the label contained in this attribute. This is a very
106 A process can see the Smack label it is running with by
[all …]
|
| D | Yama.txt | 3 selectable at build-time with CONFIG_SECURITY_YAMA, and can be controlled
32 work), or with CAP_SYS_PTRACE (i.e. "gdb --pid=PID", and "strace -p PID"
47 The sysctl settings (writable only with CAP_SYS_PTRACE) are:
56 with the inferior it wants to call PTRACE_ATTACH on. By default,
63 2 - admin-only attach: only processes with CAP_SYS_PTRACE may use ptrace
64 with PTRACE_ATTACH, or through children calling PTRACE_TRACEME.
66 3 - no attach: no processes may use ptrace with PTRACE_ATTACH nor via
|
| /linux-4.4.14/Documentation/isdn/ |
| D | INTERFACE | 11 register_isdn() with a pointer to that struct. Prior to that, it has
36 Changes in this document are marked with '***CHANGEx' where x representing
37 the version number. If that number starts with 0, it refers to the old,
38 separately distributed package. If it starts with one of the letters
87 int Channel-number locally to the driver. (starting with 0)
99 fields are described together with the descriptions of the possible
114 setup, etc. The exact meaning of the parameters is described with the
138 int channel-number locally to the HL-driver. (starts with 0)
167 int channel-number locally to the HL-driver. (starts with 0)
191 int channel-number locally to the HL-driver. (starts with 0)
[all …]
|
| D | README.fax | 2 Fax with isdn4linux
11 hylafax (with patch) for AVM capi.
16 NOTE: This implementation does *not* support fax with passive
25 - full support with both B-channels.
28 - full support with all B-channels.
|
| D | README.syncppp | 9 Compiling isdn4linux with sync PPP:
11 To compile isdn4linux with the sync PPP part, you have
18 Using isdn4linux with sync PPP:
26 one interface with the name 'ippp0' to saturate the
33 communicates with the isdn4linux link-level driver using the
49 with isdn4linux. Now call the ipppd with the '+mp' option.
|
| D | README.icn | 15 The card communicates with the PC by two interfaces:
17 configured with the switches.
18 2. A memory window with 16KB-256KB size, which can be setup in 16k steps
26 Two types of cards exist, one with dip-switches and one with
29 1. Setting for the card with hook-switches:
43 2. Setting for the card with dip-switches:
71 loading the kernel with LILO or LOADLIN. It accepts the following syntax:
81 idstring must start with a character! There is no way for the driver
109 idstring must start with a character! There is no way for the driver
121 The firmware is supplied together with the isdn4k-utils package. It
|
| D | INTERFACE.CAPI | 13 lingo) with Kernel CAPI to indicate their readiness to provide their service
14 to CAPI applications. CAPI applications also register with Kernel CAPI,
15 requesting association with a CAPI device. Kernel CAPI then dispatches the
26 CAPI drivers optionally register themselves with Kernel CAPI by calling the
27 Kernel CAPI function register_capi_driver() with a pointer to a struct
28 capi_driver. This structure must be filled with the name and revision of the
31 with a pointer to the same struct capi_driver.
33 CAPI drivers must register each of the ISDN devices they control with Kernel
34 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
35 struct capi_ctr before they can be used. This structure must be filled with
[all …]
|
| D | syncPPP.FAQ | 9 Q06: can I use asynchronous PPP encapsulation with network devices
40 of isdn4linux with the 'syncppp' encapsulation
50 (you can check this e.g with the program 'ifconfig')
56 A: Maybe you have compiled the ipppd with another
62 Q03: when I list the netdevices with ifconfig I see, that
77 ipppd with the '+mp' option.
83 the slave channels with the command:
99 ISDN Subsystem. Recompile with this option enabled.
119 devices with the standard PPP/pppd package
129 start a new one with another config to connect
[all …]
|
| D | README.audio | 48 AT+VRX Start recording. Emulator responds with
82 with CONNECT and starts sending audio data
88 with ATA, depending on the calling service, the emulator
89 responds with either CONNECT (data call) or VCON (voice call).
91 On outgoing voice calls, the emulator responds with VCON
97 Upon AT+VRX command, the emulator responds with CONNECT, and
103 recording, responding with VCON.
128 When sending audio data, upon AT+VTX command, emulator responds with
|
| D | README.HiSax | 1 HiSax is a Linux hardware-level driver for passive ISDN cards with Siemens
4 It is meant to be used with isdn4linux, an ISDN link-level module for Linux
18 along with this program; if not, write to the Free Software
62 Siemens I-Surf 2.0 (with IPAC, try type 12 asuscom)
78 If you know other passive cards with the Siemens chipset, please let me know.
88 with LILO or LOADLIN or, if built as a module, using insmod/modprobe with
95 needed to be configured with isapnp and worked only with the HiSax
123 won't work with the current modules package.
168 10 ELSA PCMCIA irq, io (set with card manager)
183 22 Sedlbauer Speed Star (PCMCIA) irq, io (set with card manager)
[all …]
|
| D | README.diversion | 1 The isdn diversion services are a supporting module working together with
5 document. The diversion services may be used with all cards supported by
22 along with this program; if not, write to the Free Software
50 with a special (or all) service identifiers are forwarded if the
76 type. Additionally the i4l services only work together with the HiSax
95 To compile the i4l code with diversion support you need to say yes to the
104 If the module is actually loaded and active may be checked with a
112 You also may put a "cat /proc/net/isdn/divert" in the background with the
115 conjunction with inetd and a small remote client on other machines inside
120 to do with that call.
|
| /linux-4.4.14/Documentation/devicetree/bindings/spi/ |
| D | fsl-imx-cspi.txt | 6 - "fsl,imx1-cspi" for SPI compatible with the one integrated on i.MX1
7 - "fsl,imx21-cspi" for SPI compatible with the one integrated on i.MX21
8 - "fsl,imx27-cspi" for SPI compatible with the one integrated on i.MX27
9 - "fsl,imx31-cspi" for SPI compatible with the one integrated on i.MX31
10 - "fsl,imx35-cspi" for SPI compatible with the one integrated on i.MX35
11 - "fsl,imx51-ecspi" for SPI compatible with the one integrated on i.MX51
|
| /linux-4.4.14/drivers/usb/usbip/ |
| D | usbip_protocol.txt | 28 sends an OP_REQ_IMPORT packet. The server replies with OP_REP_IMPORT. If the
102 OP_REP_DEVLIST: Reply with the list of exported USB devices.
117 | | | ends with the previous "number of exported
121 | | | USB device, string closed with zero byte, e.g.
123 | | | The unused bytes shall be filled with zero
127 | | | closed with zero byte, e.g. "3-2". The unused
128 | | | bytes shall be filled with zero bytes.
155 | | | together bNumInterfaces times, with the
167 i*0x138 + | | | with the busid field.
183 | | | A string closed with zero, the unused bytes
[all …]
|
| /linux-4.4.14/drivers/devfreq/ |
| D | Kconfig | 14 Like some CPUs with CPUfreq, a device may have multiple clocks.
21 to set its every clock accordingly with the "target" callback
24 When OPP is used with the devfreq device, it is recommended to
26 used with the devfreq device, you may use OPP helper
37 similar as ONDEMAND governor of CPUFREQ does. A device with
40 values to the governor with data field at devfreq_add_device().
78 the operating frequencies and voltages with OPP support.
79 This does not yet operate with optimal voltages.
89 operating frequencies and voltages with OPP support.
99 operating frequencies and voltages with OPP support.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | mandatory-locking.txt | 20 the kernel has decided to proceed with a read, but before the
46 with a "mandatory" locking scheme, whereby the operating system kernel would
78 to run mandatory lock candidates with setgid privileges.
83 I have considered the implementations of mandatory locking available with
91 contravention of SVID 3, which states that only calls to open() with the
93 definition, which is the "Right Thing", since only calls with O_TRUNC can
96 HP-UX even disallows open() with O_TRUNC for a file with advisory locks, not
122 2. If a process has locked a region of a file with a mandatory read lock, then
125 released, unless the process has opened the file with the O_NONBLOCK
126 flag in which case the system call will return immediately with the error
[all …]
|
| D | isofs.txt | 11 Unix for the most part doesn't know how to deal with Unicode.
12 There is also an option of doing UTF-8 translations with the
20 check=relaxed Matches filenames with different cases
21 check=strict Matches only filenames with the exact same case
36 showassoc Show files marked with the 'associated' bit
47 identical with ISO 9660.", so it is a valid and gratis substitute of the
|
| D | hpfs.txt | 19 that for files mode is anded with 0666. If you want files to have 'x'
43 What to do with extended attributes. 'no' - ignore them and use always
58 because kernel creates different files with names like bootsect.S and
74 attributes with keys "UID", "GID" or "MODE" and 2-byte values are created. Only
79 extended attribute UID=0. And when you umount the fs and mount it again with
86 attributes with different sizes, they won't be rewritten and changing these
93 attribute named "SYMLINK" with symlink value. Like on ext2, you can chown and
96 incompatible with OS/2. OS/2 PmShell symlinks are not supported because they are
112 OS/2 uppercases the search pattern with its system code page (852) and file
113 name it's comparing to with its code page (850). These could never match. Is it
[all …]
|
| D | tmpfs.txt | 22 RAM+swap use of a tmpfs instance with df(1) and du(1).
52 distributions should succeed with a tmpfs /tmp.
66 machine with highmem) the number of lowmem RAM pages,
76 mount with such options, since it allows any user with write access to
78 that instance in a system with many cpus making intensive use of it.
97 A memory policy with a valid NodeList will be saved, as specified, for
99 system, the mount option memory policy will be applied with a NodeList,
106 conjunction with their modes. These optional flags can be specified
117 Note that trying to mount a tmpfs with an mpol option will fail if the
121 NUMA capability (perhaps a safe recovery kernel), or with fewer nodes
[all …]
|
| D | dlmfs.txt | 6 dlmfs is built with OCFS2 as it requires most of its infrastructure.
24 - Right now it only works with the OCFS2 DLM, though support for other
48 ocfs2_hb_ctl (distributed with ocfs2-tools). Right now it requires
54 with ocfs2-tools.
63 'libo2dlm' (distributed with ocfs2-tools) which abstracts the file
75 distributed with ocfs2-tools.
96 open(2) with O_CREAT to ensure the resource inode is created - dlmfs does
113 close(2) drops the lock associated with your fd.
|
| /linux-4.4.14/drivers/staging/rdma/ipath/ |
| D | Kconfig | 8 devices to be used with both kernel upper level protocols such
9 as IP-over-InfiniBand as well as with userspace applications
10 (in conjunction with InfiniBand userspace access).
13 If you have this hardware you will need to boot with PAT disabled
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.OSS | 4 This file is a collection of all the old Readme files distributed with
10 you have problems with it, please contact him or the current device-specific
16 they are gone forever. Keeping this in mind and with a grain of salt this
26 sites). It gives instructions about using sound with Linux. It's bit out of
31 with OSS API.
38 contain useful utilities to be used with this driver.
145 values for the sound card than with DOS.
151 The following errors are likely with /dev/dsp and /dev/audio.
166 with impossible parameters. Check that the application is
175 Check that your kernel version works with this
[all …]
|
| D | PSS-updates | 14 with systems that were using previous versions of this driver. If you wish to
29 builtin Wearnes CDROM port. If this is the case with your PSS sound card you
30 should load aztcd with the appropriate port option that matches the port you
34 compatibility with systems using previous versions of this driver.
46 and/or CDROM port(s) of his PSS sound card. If this driver is loaded with this
47 parameter and with the parameter below set to true then a user can safely unload
48 this driver with the following command "rmmod pss && rmmod ad1848 && rmmod
52 full behavioral compatibility with previous versions of this driver.
63 retain full behavioral compatibility with previous versions of this driver.
69 of having to put it in a predefined location with a predefined name. The
|
| D | AudioExcelDSP16 | 12 The Audio Excel configuration, is now done with the standard Linux setup.
28 use with this module:
73 activating the audio card with the MS-DOS device driver, then you have to
77 1) Compile Linux kernel with standard sound driver, using the emulation
78 you want, with the parameters of your audio card,
81 3) Boot MS-DOS and configure the audio card with the boot time device
84 and will boot the new kernel with sound driver. The sound driver will find
96 > with my original SB16, thanks for the driver!
|
| D | SoundPro | 21 more advanced than the original AD1848 one. If your system works with
22 either WSS or SB16 and you are having problems with some mixer controls
32 assigned only to the SB16 subdevice (with isapnp). Windows documentation
41 no idea if the driver will work with it. I suspect it won't.
43 As with PnP cards, some configuration is required. There are two ways
69 in your isapnp configuration file, and that there is no conflict with
72 butting heads with another device.
80 loading with kmod, the kernel module loader, here is the section I
104 - come up with a scheme which allows recording volumes for each subdevice.
|
| /linux-4.4.14/Documentation/devicetree/bindings/serial/ |
| D | samsung_uart.txt | 3 The Samsung's UART controller is used for interfacing SoC with serial
9 - "samsung,s3c2410-uart" - compatible with ports present on S3C2410 SoC,
10 - "samsung,s3c2412-uart" - compatible with ports present on S3C2412 SoC,
11 - "samsung,s3c2440-uart" - compatible with ports present on S3C2440 SoC,
12 - "samsung,s3c6400-uart" - compatible with ports present on S3C6400 SoC,
13 - "samsung,s5pv210-uart" - compatible with ports present on S5PV210 SoC.
|
| D | fsl-lpuart.txt | 5 - "fsl,vf610-lpuart" for lpuart compatible with the one integrated
6 on Vybrid vf610 SoC with 8-bit register organization
7 - "fsl,ls1021a-lpuart" for lpuart compatible with the one integrated
8 on LS1021A SoC with 32-bit big-endian register organization
|
| D | qcom,msm-uartdm.txt | 5 software perspective it's mostly compatible with the MSM serial UART except
30 used with TX DMA channel. Required when using DMA for transmission
31 with UARTDM v1.3 and bellow.
33 used with RX DMA channel. Required when using DMA for reception
34 with UARTDM v1.3 and bellow.
43 - A uartdm v1.4 device with dma capabilities.
|
| /linux-4.4.14/arch/mips/bcm47xx/ |
| D | Kconfig | 17 Add support for old Broadcom BCM47xx boards with Sonics Silicon Backplane support.
19 This will generate an image with support for SSB and MIPS32 R1 instruction set.
33 Add support for new Broadcom BCM47xx boards with Broadcom specific Advanced Microcontroller Bus.
35 This will generate an image with support for BCMA and MIPS32 R2 instruction set.
|
| /linux-4.4.14/drivers/misc/mic/ |
| D | Kconfig | 11 If you are building a host/card kernel with an Intel MIC device
15 OS and tools for MIC to use with this driver are available from
28 If you are building a host/card kernel with an Intel MIC device
32 OS and tools for MIC to use with this driver are available from
48 If you are building a host kernel with an Intel MIC device then
52 OS and tools for MIC to use with this driver are available from
86 If you are building a host kernel with an Intel MIC device then
90 OS and tools for MIC to use with this driver are available from
104 If you are building a host kernel with an Intel MIC device then
108 OS and tools for MIC to use with this driver are available from
|
| /linux-4.4.14/Documentation/filesystems/pohmelfs/ |
| D | info.txt | 7 Each mountpoint is associated with a special index via this option.
15 retries exceed specified limit, dropped with error.
32 When the number of resends exceeds this limit, the transaction is completed with error.
57 Add server server1.net:1025 into the working set with index $idx
58 with appropriate hash algorithm and key file and cipher algorithm, mode and key file:
61 Mount filesystem with given index $idx to /mnt mountpoint.
68 Change IO priority to 123 (node with the highest priority gets read requests).
74 device none mounted on /mnt with fstype pohmel
83 is set to /mnt, server will negotiate hash/cipher with client, in case client requested it, there
99 Bulk single-client transafers usually are better handled with smaller number (like 1-3).
|
| /linux-4.4.14/fs/nls/ |
| D | Kconfig | 35 compatible with iso8859-1.
42 The Microsoft FAT file system family can deal with filenames in
54 The Microsoft FAT file system family can deal with filenames in
66 The Microsoft FAT file system family can deal with filenames in
79 The Microsoft FAT file system family can deal with filenames in
95 The Microsoft FAT file system family can deal with filenames in
110 The Microsoft FAT file system family can deal with filenames in
121 The Microsoft FAT file system family can deal with filenames in
132 The Microsoft FAT file system family can deal with filenames in
143 The Microsoft FAT file system family can deal with filenames in
[all …]
|
| /linux-4.4.14/Documentation/networking/ |
| D | de4x5.txt | 20 So far the driver is known to work with the following cards:
31 DE434, DE435 and DE500 cards and benchmarked with 'ttcp': it transferred
51 kernel. Do make sure you're not sharing interrupts with anything that
76 kernel with the de4x5 configuration turned off and reboot.
92 can compile with a DEC_ONLY define, or if loading as a module, use the
99 line with the rest (the DC21040 chip doesn't have a hardware timer).
111 aligned DMA transfers and the Alphas get alignment traps with non
114 I have added SROM decoding routines to make this driver work with any
117 the dc2104x chips should run correctly with the basic driver. I'm in
120 (with the latest SROM complying with the SROM spec V3: their first was
[all …]
|
| D | eql.txt | 10 with the 1.1.75 kernel, and is known to have patched cleanly with
11 1.1.86. Some testing with 1.1.92 has been done with the v1.1 patch
25 The eql driver has only been tested with the Livingston PortMaster-2e
30 good 1 to 2 KB/s slower than the test machine working with a 28.8 Kbps
47 with the eql driver. From patching, building, to installing.
52 If you do not have or cannot get a copy of the kernel with the eql
95 So far, I have only used the eql device with the DSLIP SLIP connection
158 either down the device with ifconfig (eql will automatically bury the
226 because I don't have a PPP-connection manager like SLIP has with
233 connections for use with the eql driver the weekend of Feb 25-26 '95
[all …]
|
| D | cops.txt | 5 Each mode corresponds with the type of card. It has been found
11 Right now these cards are known to work with the COPS driver. The
24 mode if you built a driver with dual support use board_type=1 or
25 board_type=2 for Dayna or Tangent with insmod.
40 Then bring up the interface with ifconfig. It will look something like this:
48 You will need to configure atalkd with something like the following to make
49 it work with the cops.c driver.
|
| D | timestamping.txt | 49 val is an integer with any of the following bits set. Setting other
90 machines with virtual devices where a transmitted packet travels
129 Generate a unique identifier along with each packet. A process can
137 This option associates each packet at send() with a unique
138 identifier and returns that along with the timestamp. The identifier
140 sockets, the counter increments with each sent packet. For stream
141 sockets, it increments with every byte.
149 timestamp is always looped along with a struct sock_extended_err.
158 are already supported unconditionally on all packets with receive
159 timestamps and on IPv6 packets with transmit timestamp. This option
[all …]
|
| D | 6pack.txt | 24 to experiment with something completely different from the known CSMA and
30 - Each packet transferred over the serial line is supplied with a checksum,
42 Matthias Welwarsky DG2FEF, comes along with the PC version of FlexNet.
60 with PC/FlexNet. Please do not ask me about the internals of this file as I
66 programmed with software called TAPR. In the latter case, the TNC
67 is supplied with a DIP switch so you can easily change between the
70 nowadays. If your TNC is not equipped with the switch mentioned above, you
79 The driver has been tested with kernel version 2.1.90. Use with older
93 To use the driver, the kissattach program delivered with the AX.25 utilities
130 different way than they are when the TNC is used with PC/FlexNet. When using
[all …]
|
| D | ixgbevf.txt | 18 be activated on kernels with CONFIG_PCI_IOV enabled.
21 with a max_vfs value of 1 or greater.
50 If an issue is identified with the released source code on the supported
51 kernel with a supported adapter, email the specific information related
|
| D | policy-routing.txt | 6 with attached information: gateway, device etc.
38 with attached information.
52 RTRF_VALVE - One way route (used with masquerading)
84 tables. Every rule is supplied with its own gateway, device
103 253 ASE routes with external metric
104 252 ASE routes with internal metric
120 Area classes must be terminated with reject record.
145 pretty ambiguous when used with NAT and masquerading.
|
| D | igbvf.txt | 21 driver supports virtual functions generated by the igb driver with a max_vfs
23 to the README included with the igb driver.
30 documentation supplied with your Intel Gigabit adapter. All hardware
31 requirements listed apply to use with Linux.
78 If an issue is identified with the released source code on the supported
79 kernel with a supported adapter, email the specific information related
|
| D | packet_mmap.txt | 5 This file documents the mmap() facility available with the PACKET
7 i) capture network traffic with utilities like tcpdump, ii) transmit network
88 the same way with or without PACKET_MMAP:
103 allocated RX and TX buffer ring with a single mmap() call.
118 bind() ---------> bind transmission socket with a network interface
138 In this case, you also need to bind(2) the TX_RING with sll_protocol = 0
141 Binding the socket to your network interface is mandatory (with zero copy) to
187 the frame (for payload alignment with SOCK_RAW mode for instance) you
188 can set tp_net (with SOCK_DGRAM) or tp_mac (with SOCK_RAW). In order
189 to make this work it must be enabled previously with setsockopt()
[all …]
|
| D | ray_cs.txt | 11 This driver also works with WebGear's Aviator 2.4 and Aviator Pro
27 with nondefault parameters, they can be edited in
61 To join an existing network with
70 operation with older breezecom access
88 string with maximum length of 32 chars
104 hex, must start with x eg
113 ray_debug integer Replaced with pc_debug
139 Does not work with non x86
141 Does not work with SMP
|
| D | fore200e.txt | 30 The FORE Systems 200E-series driver is shipped with firmware data being
32 The supplied firmware images should work with all adapters.
37 ForeThought CD-ROM supplied with your adapter by FORE Systems.
45 on the endianness of the host architecture. The driver is shipped with
51 1. Copy the new firmware binary files (with .bin, .bin1 or .bin2 suffix)
|
| /linux-4.4.14/Documentation/cris/ |
| D | README | 9 In order to compile this you need a version of gcc with support for the
30 The ETRAX 100LX is a 100 MIPS processor with 8kB cache, MMU, and a very broad
31 range of built-in interfaces, all with modern scatter/gather DMA.
60 The ETRAX FS is a 200MHz 32-bit RISC processor with on-chip 16kB
61 I-cache and 16kB D-cache and with a wide range of device interfaces
64 The ARTPEC-3 is a variant of the ETRAX FS with additional IO-units
77 a board with ETRAX 100LX. The displayed BogoMIPS value is 5 times too small :)
111 ttyS0 at 0xb0000060 is a builtin UART with DMA
112 ttyS1 at 0xb0000068 is a builtin UART with DMA
113 ttyS2 at 0xb0000070 is a builtin UART with DMA
[all …]
|
| /linux-4.4.14/Documentation/arm/SA1100/ |
| D | GraphicsClient | 23 Linux can be used with the ADS BootLoader that ships with the
29 board with the ADS bootloader, but should still work with Angel,
50 uncommented) would be loaded with:
55 and that minicom is preconfigured with /dev/ttyS1, 38400 baud, 8N1, no flow
78 - UCB1200 audio with new ucb_generic layer
91 - 16bpp mode requires a different cable than what ships with the board.
93 if you compile with 16bit mode support and switch into a lower bpp
|
| D | ADSBitsy | 15 Linux can be used with the ADS BootLoader that ships with the
37 - 16bpp mode requires a different cable than what ships with the board.
39 if you compile with 16bit mode support and switch into a lower bpp
|
| /linux-4.4.14/Documentation/frv/ |
| D | configuring.txt | 24 the kernel with MB93091 CB10, CB11, CB30, CB41, CB60, CB70 and CB451
25 CPU boards, and with the MB93093 PDK board.
80 Default configuration for the MB93091-VDK with both CPU board and
86 Default configuration for the MB93091-VDK with CPU board,
98 Default configuration for the MB93091-VDK with only CB70 CPU board
104 Default configuration for the MB93091-VDK with both CB451 CPU board and
109 Default configuration for the MB93091-VDK with CB451 CPU board, DAV
115 Default configuration for the MB93091-VDK with CB451 CPU board, DAV
121 Default configuration for the MB93091-VDK with only CB451 CPU board
|
| /linux-4.4.14/Documentation/fb/ |
| D | sstfb.txt | 7 on my computer, with my "Maxi Gamer 3D" and "Maxi Gamer 3d²" boards,
8 and with me "between chair and keyboard". Some people tested other
12 in progress, I feel uncomfortable with releasing tarballs of something
19 with the vga passthrou cable, I can only suggest borrowing a screen
25 This driver (should) work on ix86, with "late" 2.2.x kernel (tested
26 with x = 19) and "recent" 2.4.x kernel, as a module or compiled in.
41 # If you have only one monitor to play with, once you insmod the
69 (how does it work with vgacon ? short answer : it doesn't work)
102 Be careful with this option, it may be
122 driver with SST_DEBUG and SST_DEBUG_IOCTL set to 1
[all …]
|
| D | udlfb.txt | 7 DisplayLink chips provide simple hline/blit operations with some compression,
8 pairing that with a hardware framebuffer (16MB) on the other end of the
10 monitor with no CPU involvement until a pixel has to change.
13 result with a local shadow of the remote hardware framebuffer to identify
19 can support surprisingly high resolutions with good performance for
32 Advantages of supporting DisplayLink chips with kernel framebuffer interface:
35 one-to-one with the fbdev interface, making the driver quite small and
48 In the future, hopefully fbdev will be enhanced with an small standard
70 changed regions. Alternatively, udlfb can be recompiled with experimental
96 Unplug/replug USB device to apply with new settings
[all …]
|
| D | vt8623fb.txt | 18 * 4 bpp pseudocolor modes (with 18bit palette, two variants)
19 * 8 bpp pseudocolor mode (with 18bit palette)
33 There are two 4 bpp modes. First mode (selected if nonstd == 0) is mode with
35 with interleaved planes (1 byte interleave), MSB first. Both modes support
|
| D | vesafb.txt | 7 The idea is simple: Turn on graphics mode at boot time with the help
18 * It provides a nice large console (128 cols + 48 lines with 1024x768)
39 The graphic modes are NOT in the list which you get if you boot with
75 1. Note: LILO cannot handle hex, for booting directly with
77 2. Note: Some newer versions of LILO appear to work with those hex values,
88 with a broken console (and vesafb cannot do anything about this).
95 booting linux. If you are not happy with the 60 Hz refresh rate, you
99 available) and boot linux with loadlin.
102 * VBE 3.0 might work too. I have neither a gfx board with VBE 3.0
112 seems not to work with some BIOS versions, but there are options
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.net | 12 kernels can talk to each other, the host, and with the host's help,
29 running UML to exchange packets with its host over one of the
34 link with the host.
45 If you'd like to set up an IP network with the host and/or the
56 packets with the host over a TUN/TAP device. This option will only
57 work with a 2.4 host, unless you've applied the TUN/TAP patch to
68 network with its host over a point-to-point link. Unlike Ethertap,
77 networking, and details of a few quirks with it.
82 multiple hosts), Ethertap (to network with the host and the
92 UMLs on a single host to communicate with each other, but not to
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | twl4030-keypad.txt | 3 TWL4030's Keypad controller is used to interface a SoC with a matrix-type
9 This binding is based on the matrix-keymap binding with the following
16 - "ti,twl4030-keypad": For controllers compatible with twl4030 keypad
19 - <1>: For controllers compatible with twl4030 keypad controller.
|
| D | omap-keypad.txt | 3 TI's Keypad controller is used to interface a SoC with a matrix-type
9 This binding is based on the matrix-keymap binding with the following
16 - "ti,omap4-keypad": For controllers compatible with omap4 keypad
|
| /linux-4.4.14/Documentation/spi/ |
| D | butterfly | 5 a parallel port adapter cable, together with an "AVR Butterfly" to run
7 battery powered card with an AVR microcontroller and lots of goodies:
13 can come up with something fancier, providing ciruit protection to the
14 Butterfly and the printer port, or with a better power supply than two
19 SPI protocol drivers interact with the AVR, and could even let the AVR
21 easily with a "real SPI controller", instead of this bitbanger.
24 The first cable connections will hook Linux up to one SPI bus, with the
55 That would let you talk to the AVR using custom SPI-with-USI firmware,
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | TODO | 6 system. It allows blind users to interact with applications on the
11 The first issue has to do with the way speakup communicates with serial
12 ports. Currently, we communicate directly with the hardware
13 ports. This however conflicts with the standard serial port drivers,
16 communicate with USB devices. The current serial port handling code is
|
| /linux-4.4.14/drivers/isdn/hardware/mISDN/ |
| D | Kconfig | 11 Enable support for cards with Cologne Chip AG's
19 Enable support for cards with Cologne Chip AG's HFC multiport
39 Enable support for USB ISDN TAs with Cologne Chip AG's
60 tristate "Support for cards with Infineon chipset"
65 Enable support for cards with ISAC + HSCX, IPAC or IPAC-SX
69 tristate "Support for cards with Winbond 6692"
|
| /linux-4.4.14/net/can/ |
| D | Kconfig | 22 tristate "Raw CAN Protocol (raw access with CAN-ID filtering)"
29 To receive/send raw CAN messages, use AF_CAN with protocol CAN_RAW.
32 tristate "Broadcast Manager CAN Protocol (with content filtering)"
41 To use the Broadcast Manager, use AF_CAN with protocol CAN_BCM.
44 tristate "CAN Gateway/Router (with netlink configuration)"
51 They can be modified with AND/OR/XOR/SET operations as configured
|
| /linux-4.4.14/sound/soc/fsl/ |
| D | Kconfig | 187 tristate "Audio on the i.MX31ADS with WM1133-EV1 fitted"
194 Enable support for audio on the i.MX31ADS with the WM1133-EV1
195 PMIC board with WM8835x fitted.
206 board with TLV320AIC32X4 codec.
233 tristate "SoC Audio support for i.MX boards with wm8962"
240 Say Y if you want to add support for SoC audio on an i.MX board with
244 tristate "SoC Audio support for i.MX boards with the ES8328 codec"
256 tristate "SoC Audio support for i.MX boards with sgtl5000"
263 Say Y if you want to add support for SoC audio on an i.MX board with
267 tristate "SoC Audio support for i.MX boards with S/PDIF"
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/hwlock/ |
| D | hwlock.txt | 28 or multiple hwlocks, with each hwlock represented by
33 as the hwlocks, with one name per hwlock. Consumers can
40 the node hwlock1. hwlock1 is a hwlock provider with an argument specifier
52 the hwlock device node 'hwlock1' with #hwlock-cells value of 1, and another
53 hwlock within the hwlock device node 'hwlock2' with #hwlock-cells value of 2.
|
| /linux-4.4.14/arch/arm/mach-spear/ |
| D | Kconfig | 29 bool "SPEAr1310 Machine support with Device Tree"
36 bool "SPEAr1340 Machine support with Device Tree"
56 bool "SPEAr300 Machine support with Device Tree"
62 bool "SPEAr310 Machine support with Device Tree"
68 bool "SPEAr320 Machine support with Device Tree"
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | tlv320aic31xx.txt | 8 "ti,tlv320aic310x" - Generic TLV320AIC31xx with mono speaker amp
9 "ti,tlv320aic311x" - Generic TLV320AIC31xx with stereo speaker amp
34 * SPL, devices with stereo speaker amp
35 * SPR, devices with stereo speaker amp
36 * SPK, devices with mono speaker amp
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-class-rc | 33 Write fails with EINVAL if an invalid protocol combination or
42 Use in combination with /sys/class/rc/rcN/filter_mask to set the
45 the filter will be ignored. Otherwise the write will fail with
55 Use in combination with /sys/class/rc/rcN/filter to set the bits
60 the filter will be ignored. Otherwise the write will fail with
79 Write fails with EINVAL if an invalid protocol combination or
89 Use in combination with /sys/class/rc/rcN/wakeup_filter_mask to
95 Otherwise the write will fail with an error.
104 Use in combination with /sys/class/rc/rcN/wakeup_filter to set
110 Otherwise the write will fail with an error.
|
| D | sysfs-driver-hid-lenovo | 7 Applies to Thinkpad USB Keyboard with TrackPoint.
14 Applies to Thinkpad USB Keyboard with TrackPoint.
21 Applies to Thinkpad USB Keyboard with TrackPoint.
29 Applies to Thinkpad USB Keyboard with TrackPoint.
36 Applies to Thinkpad USB Keyboard with TrackPoint.
43 Applies to Thinkpad USB Keyboard with TrackPoint.
50 Applies to ThinkPad Compact (USB|Bluetooth) Keyboard with TrackPoint.
|
| D | sysfs-bus-rpmsg | 6 Every rpmsg device is a communication channel with a remote
7 processor. Channels are identified with a (textual) name,
18 Every rpmsg device is a communication channel with a remote
21 starts listening on one end of a channel, it assigns it with
36 Every rpmsg device is a communication channel with a remote
39 starts listening on one end of a channel, it assigns it with
58 Every rpmsg device is a communication channel with a remote
|
| D | sysfs-class-extcon | 8 with extcon_dev_register.
18 If there are cables mutually exclusive with each other,
19 such binary relations may be expressed with extcon_dev's
28 "show_name" defined, the callback will provide the name with
38 defined, the showing function is overridden with the optional
53 state number starting with 0x:
62 interface associated with each cable cannot update
|
| D | sysfs-bus-umc | 7 specification describes a PCI-based device with
19 The ID of this capability, with 0 being the radio
28 interface complies with.
|
| D | sysfs-wusb_cbaf | 13 2. The connection manager (CM) sees a device with CBA capability.
24 with the host.
37 the host with device by: writing a randomly
43 associating with a new device.
61 the CDID for any existing association with this host.
100 associate with the device.
|
| D | sysfs-firmware-memmap | 8 /proc/iomem (together with other resources).
12 the kernel merges that memory map with other information or
17 parameter segment of the kernel that should be booted with
23 are subdirectories with the number of the entry as their name:
37 start : The start address (as hexadecimal number with the
|
| /linux-4.4.14/drivers/scsi/arm/ |
| D | Kconfig | 10 Acorn system with one of these, say Y. If unsure, say N.
27 Say Y here to enable synchronous transfer negotiation with all
40 was either sold on its own or with an integral SCSI controller.
50 Acorn system with one of these, say Y. If unsure, say N.
57 system with one of these, say Y, otherwise 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/drivers/usb/gadget/legacy/ |
| D | Kconfig | 8 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
9 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
12 # With help from a special transceiver and a "Mini-AB" jack, systems with
34 Gadget Zero also works with the host-side "usb-skeleton" driver,
35 and with many kinds of host-side test software. You may need
48 this gadget connects to another OTG device, with this one using
60 This Gadget Audio driver is compatible with USB Audio Class
68 application may choose to do whatever it wants with the data
84 tristate "Ethernet Gadget (with CDC Ethernet support)"
96 That protocol is often avoided with pure Ethernet adapters, in
[all …]
|
| /linux-4.4.14/Documentation/block/ |
| D | pr.txt | 37 Only initiators with a registered key can write to the device,
42 Only initiators with a registered key can access the device.
46 Only initiators with a registered key can write to the device,
48 All initiators with a registered key are considered reservation
55 Only initiators with a registered key can access the device.
56 All initiators with a registered key are considered reservation
93 old_key and replaces it with a a new reservation of type for the
105 registered with the device and drops any existing reservation.
|
| /linux-4.4.14/arch/cris/arch-v10/ |
| D | Kconfig | 75 For products with only one controllable LED,
85 For products with only one controllable LED,
95 For products with only one controllable LED,
104 For products with only one or two controllable LEDs,
113 For products with only one or two controllable LEDs,
122 For products with only one or two controllable LEDs,
131 For products with only one or two controllable LEDs,
140 For products with only one or two controllable LEDs,
149 For products with only one or two controllable LEDs,
158 For products with only one or two controllable LEDs,
[all …]
|
| /linux-4.4.14/drivers/mmc/host/ |
| D | Kconfig | 13 platform with a Multimedia Card slot, say Y or M here.
33 If you have a PXA(R) platform with a Multimedia Card slot,
46 If you have a controller with this interface, say Y or M here. You
79 If you have a controller with this interface, say Y or M here.
105 If you have a controller with this interface, say Y or M here.
116 If you have a controller with this interface, say Y or M here.
128 If you have a controller with this interface, say Y or M here.
148 If you have a controller with this interface, say Y or M here.
162 If you have a controller with this interface, say Y or M here.
173 If you have a controller with this interface, say Y or M here.
[all …]
|
| /linux-4.4.14/Documentation/x86/x86_64/ |
| D | uefi.txt | 8 with EFI firmware and specifications are listed below.
13 support. Elilo with x86_64 support can be used.
15 3. x86_64 platform with EFI/UEFI firmware.
19 - Build the kernel with the following configuration.
28 elilo bootloader with x86_64 support, elilo configuration file,
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | interface.txt | 19 "ti,omap3-hsotgusb-interface-clock" - interface clock with USB specific HW
21 "ti,omap3-dss-interface-clock" - interface clock with DSS specific HW handling
22 "ti,omap3-ssi-interface-clock" - interface clock with SSI specific HW handling
23 "ti,am35xx-interface-clock" - interface clock with AM35xx specific HW handling
24 "ti,omap2430-interface-clock" - interface clock with OMAP2430 specific HW
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | ux500.txt | 13 - prcmu-clock: a subnode with one clock cell for PRCMU (power,
16 - prcc-periph-clock: a subnode with two clock cells for
22 - prcc-kernel-clock: a subnode with two clock cells for
28 - rtc32k-clock: a subnode with zero clock cells for the 32kHz
31 with zero clock cells.
|
| D | samsung,s3c2443-clock.txt | 5 the s3c24x family starting with the s3c2443.
10 - "samsung,s3c2416-clock" - controller compatible with S3C2416 SoC.
11 - "samsung,s3c2443-clock" - controller compatible with S3C2443 SoC.
12 - "samsung,s3c2450-clock" - controller compatible with S3C2450 SoC.
28 that they are defined using standard clock bindings with following
|
| D | samsung,s3c2410-clock.txt | 10 - "samsung,s3c2410-clock" - controller compatible with S3C2410 SoC.
11 - "samsung,s3c2440-clock" - controller compatible with S3C2440 SoC.
12 - "samsung,s3c2442-clock" - controller compatible with S3C2442 SoC.
28 expected that is are defined using standard clock bindings with a
|
| /linux-4.4.14/Documentation/power/ |
| D | drivers-testing.txt | 8 functional system with this driver loaded. Moreover, that should be done
11 cases involves slightly different operations and different interactions with
22 Once you have resolved the suspend/resume-related problems with your test system
34 d) Attempt to hibernate with the driver compiled directly into the kernel
41 f) Attempt to suspend to RAM using the s2ram tool with the driver loaded
45 should be mixed with the STR tests. If any of them fails, the driver cannot be
|
| D | charger-manager.txt | 9 Charger Manager is a platform_driver with power-supply-class entries.
10 An instance of Charger Manager (a platform-device created with Charger-Manager)
11 represents an independent battery with chargers. If there are multiple
12 batteries with their own chargers acting independently in a system,
20 * Support for multiple chargers (e.g., a device with USB, AC, and solar panels)
28 * Support for in suspend-to-RAM polling (with suspend_again callback)
55 notification to users with UEVENT.
57 2. Global Charger-Manager Data related with suspend_again
59 In order to setup Charger Manager with suspend-again feature
61 with setup_charger_manager(struct charger_global_desc *).
[all …]
|
| D | basic-pm-debugging.txt | 27 with broken BIOSes. In such cases the "shutdown" mode of hibernation might
42 facility available if the kernel is compiled with CONFIG_PM_DEBUG set. Then,
71 to use the "devices" test mode along with the "platform" mode of hibernation,
104 that there is a problem with the tasks freezer subsystem that should be
119 make sure to report the problem with the driver.
124 with these drivers compiled as modules). You may also try to use some special
127 If the "platform" test fails, there is a problem with the handling of the
139 devices has failed (these devices are suspended on one CPU with interrupts off),
150 If all of the hibernation test modes work, you can boot the system with the
153 probably is a problem with a driver statically compiled into the kernel and you
[all …]
|
| /linux-4.4.14/arch/cris/boot/compressed/ |
| D | README | 4 This can be slightly confusing because it's a process with many steps.
10 Those files together with a ROM filesystem can be catted together and
13 They can also be catted together and compressed with gzip, which is what
17 the binary file decompress.bin, which is catted together with piggy.img
|
| /linux-4.4.14/Documentation/w1/slaves/ |
| D | w1_ds2406 | 15 can be provided with power on a dedicated input. In TO-92 form, it provides
19 current state of each switch, with PIO A in bit 0 and PIO B in bit 1. The
20 driver ORs this state with 0x30, so shell scripts get an ASCII 0/1/2/3 to
21 work with. output is writable; bits 0 and 1 control PIO A and B,
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-flakey.txt | 12 Also, consider using this in combination with the dm-delay target too,
38 each matching bio with <value>.
43 'w' is incompatible with drop_writes.
50 - replaces the 32nd byte of READ bios with the value 1
53 - replaces the 224th byte of REQ_META (=32) bios with the value 0
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/uniphier/ |
| D | cache-uniphier.txt | 3 UniPhier SoCs are integrated with a full-custom outer cache controller system.
21 cache should be also compatible with "socionext,uniphier-system-cache".
24 indicated correctly with "next-level-cache" properties.
26 Example 1 (system with L2):
38 Example 2 (system with L2 and L3):
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | nct6683 | 31 Limit register locations on Intel boards with EC firmware version 1.0
34 with different register addresses. The specification describing the Intel
40 considered too risky with this firmware and has been disabled. All limits
43 The driver has only been tested with the Intel firmware, and by default
50 The driver has been reported to work with the following boards and
|
| D | ina2xx | 40 The INA219 is a high-side current shunt and power monitor with an I2C
41 interface. The INA219 monitors both shunt drop and supply voltage, with
44 The INA220 is a high or low side current shunt and power monitor with an I2C
47 The INA226 is a current shunt and power monitor with an I2C interface.
51 with an I2C interface. The chips monitor both a shunt voltage drop and
|
| /linux-4.4.14/Documentation/ia64/ |
| D | aliasing.txt | 25 page with both a cacheable mapping and an uncacheable mapping[1].
60 Linux/ia64 identity mappings are done with large pages, currently
74 are only partially populated, or populated with a combination of UC
79 User mappings are typically done with 16K or 64K pages. The smaller
81 homogeneous with respect to memory attributes.
106 physical address space, but it may be different on machines with
135 space are not in kern_memmap, but could be accessed with a UC
137 registers typically can be accessed only with four-byte or
153 region safely with kernel page table mappings, we can use
169 mmap of 0x0-0x9FFFF /dev/mem by "hwinfo" on HP sx1000 with VGA enabled
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | ssbi.txt | 4 communicate with a limited range of devices (mostly power management
13 with the slave device. This should be one of "ssbi", "ssbi2", or
18 with a compatible field.
|
| /linux-4.4.14/drivers/net/plip/ |
| D | Kconfig | 13 CD-ROM drive (a minimal system has to be transferred with floppies
18 ports (the connectors at the computers with 25 holes) are connected
19 with "null printer" or "Turbo Laplink" cables which can transmit 4
20 bits at a time (mode 0) or with special PLIP cables, to be used on
33 with the PLIP support in Linux versions 1.0.x. This option enlarges
|
| /linux-4.4.14/Documentation/devicetree/bindings/iio/ |
| D | iio-bindings.txt | 18 with a single IIO output and 1 for nodes with multiple
21 Example for a simple configuration with no trigger:
29 Example for a configuration with trigger:
58 with IIO specifiers.
71 This represents a device with two IIO inputs, named "vcc" and "vdd".
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | cafe_ccic | 3 and this driver was written with support from the OLPC project.
9 sensor is known to work with this controller at this time.
34 systems, however, it will work well with only two.
37 will consent to work with. Default is one, but, on slower systems,
38 better behavior with mplayer can be achieved by setting to a higher
49 Work is ongoing with this driver, stay tuned.
|
| D | videobuf | 24 it is possible. Unfortunately, it is not always possible; working with
29 contiguous; buffers allocated with vmalloc(), in other words. These
36 controllers cannot deal with anything else.
38 Videobuf can work with all three types of buffers, but the driver author
61 along with a list_head for the queue of available buffers. There will also
65 The next step is to write four simple callbacks to help videobuf deal with
103 VIDEOBUF_QUEUED. Note that this function is called with the queue spinlock
181 applications have a chance of working with the device. Videobuf makes it
182 easy to do that with the same code. To implement read(), the driver need
202 The poll() function can usually be implemented with a direct call to:
[all …]
|
| D | zr364xx.txt | 8 The driver works with several other cameras in webcam mode (see the list below).
13 If you manage to use your cam with this code, you can send me a mail (royale@zerezo.com) with the n…
15 Since version 0.70, this driver is only compatible with V4L2 API and 2.6.x kernels.
20 In order to use this driver, you must compile it with your kernel.
27 You can then use the camera with V4L2 compatible applications, for example Ekiga.
|
| /linux-4.4.14/drivers/vhost/ |
| D | Kconfig | 8 guest networking with virtio_net. Not to be confused with virtio_net
22 for use with virtio-scsi guests
40 This option allows vhost to support guests with a different byte
|
| /linux-4.4.14/drivers/pps/ |
| D | Kconfig | 14 Some antennae's PPS signals are connected with the CD (Carrier
15 Detect) pin of the serial line they use to communicate with the
18 Some antennae's PPS signals are connected with some special host
30 problem with PPS support and want to see more of what is going on.
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | ipoib.txt | 13 port using the P_Key at index 0. To create an interface with a
19 This will create an interface named ib0.8001 with P_Key 0x8001. To
39 fabric with a 2K MTU, the IPoIB MTU will be 2048 - 4 = 2044 bytes.
49 and communication with peers that don't support connected mode. In
75 By compiling the IPoIB driver with CONFIG_INFINIBAND_IPOIB_DEBUG set
82 virtual filesystem. By mounting this filesystem, for example with
90 is safe to enable this option with debug_level set to 0 for normal
94 the data path when data_debug_level is set to 1. However, even with
|
| /linux-4.4.14/Documentation/hid/ |
| D | hiddev.txt | 33 with the minor numbers starting at 96 and finishing at 111. Therefore,
60 This description should be read in conjunction with the HID
66 HID devices exchange data with the host computer using data
86 within <linux/hiddev.h>, along with some other useful #defines and
88 page shifted to the 16 high order bits ORed with the usage code. The
100 This ioctl call returns the HID application usage associated with the
113 The user passes in a hiddev_collection_info struct with the index
160 Returns the field information associated with a report in a
176 filled in with the report and field information associated with this
185 Returns the collection index associated with this usage. This
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | ste,nomadik.txt | 29 group that will be combined with the function to form a multiplexing
39 0: input with no pull
40 1: input with pull up,
41 2: input with pull down,
53 0: sleep input with no pull,
54 1: sleep input with pull up,
55 2: sleep input with pull down.
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | opencores,or1k-pic.txt | 5 - compatible : should be "opencores,or1k-pic-level" for variants with
6 level triggered interrupt lines, "opencores,or1k-pic-edge" for variants with
8 with the non-spec compliant or1200 type implementation.
|
| /linux-4.4.14/Documentation/dvb/ |
| D | faq.txt | 25 If you have a card with a built-in hardware MPEG-decoder the
27 you can use to watch TV with any v4l application. xawtv is known
28 to work. Note that you cannot change channels with xawtv, you
51 streams (PS) only, and can be used in conjunction with the
68 Henning Holtschneider's site with many interesting
93 MythTV - analog TV PVR, but now with DVB support, too
94 (with software MPEG decode)
110 you have configured with the dvbnet utility. Check if there
111 are any packets with the IP addr and MAC addr you have
112 configured with ifconfig.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu.txt | 28 - interrupts : Interrupt list, with the first #global-irqs entries
42 StreamIDs associated with it.
47 cache coherent with the CPU.
72 * Two DMA controllers, the first with two StreamIDs (0xd01d
73 * and 0xd01e) and the second with only one (0xd11c).
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | cpm.txt | 11 - reg : A 48-byte region beginning with CPCR.
24 - fsl,cpm-command : This value is ORed with the opcode and command flag
28 is associated with. If absent, an unused BRG
47 CPM-side offsets with pointer subtraction. It is recommended that
52 A child "data" node must exist, compatible with "fsl,cpm-muram-data", to
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | NAND.txt | 11 ECC code is not directly compatible with the default kernel ECC
17 The driver is capable of handling NAND flash with a 2KiB page
18 size, with support for hardware ECC generation and correction.
|
| /linux-4.4.14/scripts/coccinelle/api/ |
| D | resource_size.cocci | 66 msg="ERROR with %s" % (x)
75 msg="ERROR: Missing resource_size with %s" % (x)
83 msg="WARNING with %s" % (x)
92 msg="WARNING: Suspicious code. resource_size is maybe missing with %s" % (x)
|
| /linux-4.4.14/drivers/media/radio/si4713/ |
| D | Kconfig | 2 tristate "Silicon Labs Si4713 FM Radio Transmitter support with USB"
6 This is a driver for USB devices with the Silicon Labs SI4713
17 tristate "Silicon Labs Si4713 FM Radio Transmitter support with I2C"
21 This is a driver for I2C devices with the Silicon Labs SI4713
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-mcp23s08.txt | 2 8-/16-bit I/O expander with serial interface (I2C/SPI)
32 chip connected with the corresponding spi address set. For example if
33 you have a chip with address 3 connected, you have to set bit3 to 1,
52 with two interrupt outputs (these are the devices ending with 17 and
59 On devices with only one interrupt output this property is useless.
63 Example I2C (with interrupt):
|
| /linux-4.4.14/Documentation/acpi/ |
| D | gpio-properties.txt | 13 // Bluetooth device with reset and shutdown GPIOs
52 resource, second pin in that resource with the GPIO number of 31.
58 with GpioIo()/GpioInt() resources and device drivers still need to work with
67 to the GPIO lines it is going to use and provide the GPIO subsystem with a
77 respectively, in analogy with the _DSD GPIO property format specified above.
92 acpi_dev_add_driver_gpios() that will register it with the ACPI device object
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | exynos-dw-mshc.txt | 5 a SoC with storage medium such as eMMC or SD/MMC cards. This file documents
13 - "samsung,exynos4210-dw-mshc": for controllers with Samsung Exynos4210
15 - "samsung,exynos4412-dw-mshc": for controllers with Samsung Exynos4412
17 - "samsung,exynos5250-dw-mshc": for controllers with Samsung Exynos5250
19 - "samsung,exynos5420-dw-mshc": for controllers with Samsung Exynos5420
21 - "samsung,exynos7-dw-mshc": for controllers with Samsung Exynos7
23 - "samsung,exynos7-dw-mshc-smu": for controllers with Samsung Exynos7
|
| /linux-4.4.14/lib/fonts/ |
| D | Kconfig | 51 Small console font with Macintosh-style high-half glyphs. Some Mac
58 Console font with characters just a bit smaller than the default.
67 Small console font with PC-style control-character and high-half
75 Small console font with PC-style control characters and high-half
87 embedded devices with a 320x240 screen, to get a reasonable number
100 This is the high resolution console font for Sun machines with very
108 This is a high resolution console font for machines with very
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | leds-lp55xx.txt | 23 1: D1~6 with VDD, D7~9 with VOUT
24 2: D1~6 with VOUT, D7~9 with VDD
34 'lp5521_pri:channel1' and 'lp5521_pri:channel2', with a heartbeat trigger
61 9 LED channels with specific name. Internal clock used.
62 The I2C slave address is configurable with ASEL1 and ASEL0 pins.
|
| /linux-4.4.14/arch/arm/mach-s3c64xx/ |
| D | Kconfig | 41 Compile in platform device definition LCD backlight with PWM Timer
52 is always compiled with it.
67 Common setup code for S3C64XX with an 24bpp RGB display helper.
166 # At least some of the SMDK6410s were shipped with the card detect
180 at least some SMDK6410 boards come with the
189 at least some SMDK6410 boards come with the
208 with or without the 1190-EV1 fitted.
224 with or without the 1192-EV1 fitted.
315 Machine support for Samsung S3C6400/S3C6410 machines with Device Tree
320 supported with this machine file.
|
| /linux-4.4.14/Documentation/arm/sti/ |
| D | overview.txt | 9 ARM Linux. Currently STiH415, STiH416 SOCs are supported with both
26 Flattened Device Tree, which means, It works with any compatible board with
|
| /linux-4.4.14/net/ipv4/netfilter/ |
| D | ipt_REJECT.c | 39 switch (reject->with) { in reject_tg()
76 if (rejinfo->with == IPT_ICMP_ECHOREPLY) { in reject_tg_check()
79 } else if (rejinfo->with == IPT_TCP_RESET) { in reject_tg_check()
|
| /linux-4.4.14/Documentation/devicetree/bindings/usb/ |
| D | usb-ohci.txt | 9 - big-endian-regs : boolean, set this for hcds with big-endian registers
10 - big-endian-desc : boolean, set this for hcds with big-endian descriptors
11 - big-endian : boolean, for hcds with big-endian-regs + big-endian-desc
|
| /linux-4.4.14/Documentation/input/ |
| D | userio.txt | 12 to directly interact with the kernel's serio driver and control a virtual serio
17 In order to interact with the userio kernel module, one simply opens the
21 macros you need to interact with the device are defined in <linux/userio.h> and
35 that goes along with the command. In the event that the command doesn't have an
49 Registers the port with the serio driver and begins transmitting data back and
50 forth. Registration can only be performed once a port type is set with
|
| /linux-4.4.14/arch/arm/mach-pxa/ |
| D | sleep.S | 66 @ with core operating above 91 MHz
103 @ about suspending with PXBus operating above 133MHz
107 @ as possible to eliminate messing about with the refresh clock
108 @ as the system will restore with the original speed settings
115 @ ensure x1 for run and turbo mode with memory clock
128 @ point in preserving it here. we save it on the stack with the
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | device.txt | 20 Struct device associated with the underlying hardware.
26 pointer to a structure with elements that tend to be fixed for
49 Read value associated with on sensor event detectors. Note that
53 Write the value associated with on sensor event detectors. E.g.
71 will register the device with the iio core.
74 allocated prior to registering the device with the iio-core, but must
|
| /linux-4.4.14/Documentation/connector/ |
| D | connector.txt | 10 When the driver receives a special netlink message with the appropriate
38 callback function which will be called when a message with above idx.val
59 Registers new callback with connector core.
70 Unregisters new callback with connector core.
82 struct cn_msg * - message header(with attached data).
92 created for user with the same ID as in msg.
104 The current framework offers a transport layer with fixed headers. The
112 The sequence number is incremented with each message sent.
130 driver (it also registers itself with id={-1, -1}).
152 with a different group number, the userspace application must subscribe to
[all …]
|
| /linux-4.4.14/Documentation/xtensa/ |
| D | atomctl.txt | 3 with various combinations of:
11 The Core comes up with a default value of for the three types of cache ops:
16 which can implement RCW transactions. For FPGA cards with an External
31 with the cache being bypassed; for example studying cache alias problems.
|
| /linux-4.4.14/drivers/media/radio/si470x/ |
| D | Kconfig | 2 tristate "Silicon Labs Si470x FM Radio Receiver support with USB"
5 This is a driver for USB devices with the Silicon Labs SI470x
27 tristate "Silicon Labs Si470x FM Radio Receiver support with I2C"
30 This is a driver for I2C devices with the Silicon Labs SI470x
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 6.Followthrough | 3 At this point, you have followed the guidelines given so far and, with the
8 with, possibly, quite a bit of work yet to be done.
13 code. You, as the author of that code, will be expected to work with the
22 developers as they review the code. Working with reviewers can be, for
30 like to maintain a kernel with this code in it five or ten years later?
58 Note that you do not have to agree with every change suggested by
64 agree with the reviewer, take some time to think things over again. It can
82 raised issues and how you dealt with them; the patch changelog is a good
84 through list archives to familiarize themselves with what was said last
97 in mind, of course, that he may not agree with you either.
[all …]
|
| D | 3.Early-stage | 4 to jump right in and start coding. As with any significant project,
12 Like any engineering project, a successful kernel enhancement starts with a
16 with the proposed solution, and that can lead to difficulties.
18 Consider an example: some years ago, developers working with Linux audio
36 resulting disagreement left those developers feeling disillusioned with the
49 the right solution to the problem than they were with a specific module.
51 - and to discuss it with the development community before investing in the
70 discussions with the community before launching into implementation. Early
90 Years of experience with the kernel development community have taught a
117 avoided with some early discussion with the kernel developers.
[all …]
|
| /linux-4.4.14/Documentation/arm/ |
| D | uefi.txt | 12 Booting on a platform with firmware compliant with the UEFI specification
23 in a Flattened Device Tree (FDT) - so is only available with CONFIG_OF.
32 The kernel image built with stub support remains a valid kernel image for
43 The stub populates the FDT /chosen node with (and the kernel scans for) the
|
| /linux-4.4.14/arch/arm/mach-mvebu/ |
| D | Kconfig | 35 on the Marvell Armada 370 SoC with device tree.
50 on the Marvell Armada 375 SoC with device tree.
65 on the Marvell Armada 380/385 SoC with device tree.
79 on the Marvell Armada 39x SoC with device tree.
89 on the Marvell Armada XP SoC with device tree.
|
| /linux-4.4.14/tools/testing/selftests/ftrace/ |
| D | README | 31 * Take care with side effects as the tests are run with root privilege.
41 * Note that the tests are run with "set -e" (errexit) option. If any
52 * PASS: The test succeeded as expected. The test which exits with 0 is
56 with !0 is counted as failed test.
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 21 for dump, with a single operation of echo 1 > /sys/kernel/fadump_release_mem.
24 sysfs files section below) and can be easily integrated with kdump
27 Comparing with kdump or other strategies, firmware-assisted
31 with a fresh copy of the kernel. In particular,
39 The above can only be accomplished by coordination with,
43 -- The first kernel registers the sections of memory with the
55 booted with restricted memory. By default, the boot memory
72 boot memory size effectively booting with restricted memory
90 is only available on Power6 and above systems with recent
150 infrastructure (kdump scripts) to save the dump works fine with
[all …]
|
| /linux-4.4.14/Documentation/vm/ |
| D | hugetlbpage.txt | 16 First the Linux kernel needs to be built with the CONFIG_HUGETLBFS
56 returned to the huge page pool when freed by a task. A user with root
65 pool, a user with appropriate privilege can use either the mmap system call
76 with a huge page size selection parameter "hugepagesz=<size>". <size> must
77 be specified in bytes with optional scale suffix [kKmMgG]. The default huge
78 page size may be selected with the "default_hugepagesz=<size>" boot parameter.
93 task has default memory policy--is all on-line nodes with memory. Allowed
94 nodes with insufficient available, contiguous memory for a huge page will be
97 with the allocation and freeing of persistent huge pages.
103 allocating extra pages on other nodes with sufficient available contiguous
[all …]
|
| /linux-4.4.14/net/ipv6/netfilter/ |
| D | ip6t_REJECT.c | 44 switch (reject->with) { in reject_tg6()
82 if (rejinfo->with == IP6T_ICMP6_ECHOREPLY) { in reject_tg6_check()
85 } else if (rejinfo->with == IP6T_TCP_RESET) { in reject_tg6_check()
|
| /linux-4.4.14/Documentation/x86/ |
| D | pat.txt | 9 such attribute settings allowed. Added flexibility comes with guidelines for
10 not having memory type aliasing for the same physical memory with multiple
92 A. Exporting pages to users with remap_pfn_range, io_remap_pfn_range,
101 continue to use the above sequence, with either pgprot_noncached() or
107 Note that this set of APIs only works with IO (non RAM) regions. If driver
119 is made, should already have been ioremapped with WC attributes or PAT entries,
121 combine areas of IO memory desired to remain uncacheable with areas where
126 with size-constrained regions where otherwise MTRR write-combining would
162 Drivers should use ioremap_[uc|wc] to access PCI BARs with [uc|wc] access
195 Another, more verbose way of getting PAT related debug messages is with
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 9 trying to come up with a unified interface to manage the execution units and
29 * Only use fixed sized integers. To avoid conflicts with typedefs in userspace
61 * Have a plan for extending ioctls with new flags or new fields at the end of
71 an ioctl struct with random stack garbage in the yet unused parts. Which
78 Fun with Error Paths
88 example is sprite positioning values fed directly into the hardware with the
90 server doesn't bother with clamping itself and the cursor wraps around the
102 interrupting your main test suite constantly with signals. Thanks to X's
104 paths pretty much for free for graphics drivers. Also, be consistent with
106 userspace library. The i915 driver botched this with the set_tiling ioctl,
[all …]
|