| /linux-4.4.14/tools/testing/selftests/rcutorture/doc/ |
| D | TREE_RCU-kconfig.txt | 8 CONFIG_DEBUG_OBJECTS_RCU_HEAD -- Do one.
10 CONFIG_HZ_PERIODIC -- Do one.
12 CONFIG_NO_HZ_FULL -- Do two, one with CONFIG_NO_HZ_FULL_SYSIDLE.
13 CONFIG_NO_HZ_FULL_SYSIDLE -- Do one.
17 CONFIG_RCU_BOOST -- one of PREEMPT_RCU.
20 CONFIG_RCU_FANOUT_LEAF -- Do one non-default.
21 CONFIG_RCU_FAST_NO_HZ -- Do one, but not with CONFIG_RCU_NOCB_CPU_ALL.
23 CONFIG_RCU_NOCB_CPU_ALL -- Do one.
24 CONFIG_RCU_NOCB_CPU_NONE -- Do one.
25 CONFIG_RCU_NOCB_CPU_ZERO -- Do one.
[all …]
|
| /linux-4.4.14/lib/ |
| D | atomic64_test.c | 35 int one = 1; in test_atomic() local
41 TEST(, add, +=, -one); in test_atomic()
43 TEST(, sub, -=, -one); in test_atomic()
57 long long one = 1LL; in test_atomic64() local
69 TEST(64, add, +=, -one); in test_atomic64()
71 TEST(64, sub, -=, -one); in test_atomic64()
83 r += -one; in test_atomic64()
84 BUG_ON(atomic64_add_return(-one, &v) != r); in test_atomic64()
93 r -= -one; in test_atomic64()
94 BUG_ON(atomic64_sub_return(-one, &v) != r); in test_atomic64()
[all …]
|
| /linux-4.4.14/net/rxrpc/ |
| D | sysctl.c | 19 static const unsigned one = 1; variable
46 .extra1 = (void *)&one,
54 .extra1 = (void *)&one,
62 .extra1 = (void *)&one,
72 .extra1 = (void *)&one,
80 .extra1 = (void *)&one,
90 .extra1 = (void *)&one,
98 .extra1 = (void *)&one,
108 .extra1 = (void *)&one,
117 .extra1 = (void *)&one,
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/serial/ |
| D | pl011.txt | 5 - reg: exactly one register range with length 0x1000
6 - interrupts: exactly one interrupt specifier
10 When present, must have one state named "default",
20 of the block. Just listing one clock (the first one) is
27 When present, may have one or two dma channels.
28 The first one must be named "rx", the second one
|
| D | fsl-lpuart.txt | 5 - "fsl,vf610-lpuart" for lpuart compatible with the one integrated
7 - "fsl,ls1021a-lpuart" for lpuart compatible with the one integrated
11 - clocks : phandle + clock specifier pairs, one for each entry in clock-names
15 - dmas: A list of two dma specifiers, one for each entry in dma-names.
|
| D | mrvl,pxa-ssp.txt | 5 - compatible: Must be one of
15 - dmas: Two dma phandles, one for rx, one for tx
|
| D | arm_sbsa_uart.txt | 8 - reg: exactly one register range
9 - interrupts: exactly one interrupt specifier
|
| /linux-4.4.14/security/keys/ |
| D | sysctl.c | 16 static const int zero, one = 1, max = INT_MAX; variable
25 .extra1 = (void *) &one,
34 .extra1 = (void *) &one,
43 .extra1 = (void *) &one,
52 .extra1 = (void *) &one,
|
| /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
|
| D | sh-msiof.txt | 15 If only one register set is present, it is to be used
30 specifiers, one for transmission, and one for
34 Must contain one of the following values:
42 Must contain one of the following values:
|
| D | spi-mt65xx.txt | 4 - compatible: should be one of the following.
18 The first should be one of the following. It's PLL.
21 It's the default one.
|
| D | spi-rspi.txt | 19 - interrupts : A list of interrupt-specifiers, one for each entry in
37 one for transmission, and one for reception.
|
| /linux-4.4.14/net/netfilter/ipset/ |
| D | Kconfig | 31 This option adds the bitmap:ip set type support, by which one
40 This option adds the bitmap:ip,mac set type support, by which one
49 This option adds the bitmap:port set type support, by which one
58 This option adds the hash:ip set type support, by which one
68 This option adds the hash:ip,mark set type support, by which one
77 This option adds the hash:ip,port set type support, by which one
87 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
97 one can store IPv4/IPv6 address, protocol/port, and IPv4/IPv6
107 one can store MAC (ethernet address) elements in a set.
116 one can store two IPv4/IPv6 subnets, and a protocol/port in a set.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/usb/ |
| D | gr-udc.txt | 15 - interrupts : Interrupt numbers for this device. Either one interrupt number
16 for all interrupts, or one for status related interrupts, one for IN
17 endpoint related interrupts and one for OUT endpoint related interrupts.
23 number. If the property is present it typically contains one entry for
29 number. If the property is present it typically contains one entry for
|
| D | usb-xhci.txt | 4 - compatible: should be one of "generic-xhci",
10 - interrupts: one XHCI interrupt should be described here.
|
| D | ehci-omap.txt | 9 - reg: should contain one register range i.e. start and length
15 This property is required if at least one of the ports are in
|
| D | renesas_usbhs.txt | 4 - compatible: Must contain one of the following:
21 to the number of channels (DnFIFOs) minus one.
|
| D | nvidia,tegra20-ehci.txt | 11 "nvidia,<chip>-ehci" plus at least one of the above, where <chip> is
14 - clocks : Must contain one entry, for the module clock.
|
| D | msm-hsusb.txt | 48 - qcom,otg-control: OTG control (VBUS and ID notifications) can be one of
66 - qcom,phy-num: Select number of pyco-phy to use, can be one of
67 0 - PHY one, default
83 device, which provide "USB-HOST" cable events. If one of
|
| D | ci-hdrc-usb2.txt | 4 - compatible: should be one of:
14 - phy_type: the type of the phy connected to the core. Should be one
51 to external connector device, which provide "USB-HOST" cable events. If one
58 - fsl,usbmisc: phandler of non-core register device, with one
|
| /linux-4.4.14/drivers/usb/dwc3/ |
| D | Kconfig | 61 Say 'Y' or 'M' here if you have one such device
68 Recent Exynos5 SoCs ship with one DesignWare Core USB3 IP inside,
69 say 'Y' or 'M' if you have one such device.
88 Say 'Y' or 'M' here if you have one such device
95 STMicroelectronics SoCs with one DesignWare Core USB3 IP
97 Say 'Y' or 'M' if you have one such device.
104 Recent Qualcomm SoCs ship with one DesignWare Core USB3 IP inside,
105 say 'Y' or 'M' if you have one such device.
|
| /linux-4.4.14/Documentation/devicetree/bindings/timer/ |
| D | renesas,mtu2.txt | 11 - compatible: must be one or more of the following:
18 - interrupts: interrupt specifiers for the timer, one for each entry in
20 - interrupt-names: must contain one entry named "tgi?a" for each enabled
21 channel, where "?" is the channel index expressed as one digit from "0" to
24 - clocks: a list of phandle + clock-specifier pairs, one for each entry
|
| D | nvidia,tegra30-timer.txt | 13 - interrupts : A list of 6 interrupts; one per each of timer channels 1
14 through 5, and one for the shared interrupt for the remaining channels.
15 - clocks : Must contain one entry, for the module clock.
|
| D | renesas,tmu.txt | 11 - compatible: must contain one or more of the following:
20 - interrupts: interrupt-specifier for the timer, one per channel.
22 - clocks: a list of phandle + clock-specifier pairs, one for each entry
|
| D | nvidia,tegra20-timer.txt | 10 - interrupts : A list of 4 interrupts; one per timer channel.
11 - clocks : Must contain one entry, for the module clock.
|
| D | samsung,exynos4210-mct.txt | 5 up-counter and can generate 4 interrupts when the counter reaches one of the
8 one CPU local timer instantiated in MCT for every CPU in the system.
35 as ones compatible with "samsung,exynos4412-mct", only one local timer
76 value or just the first one.
|
| D | st,stih407-lpc | 16 - st,lpc-mode : The LPC can run either one of three modes:
20 One (and only one) mode must be selected.
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/i2c/ |
| D | adv7604.txt | 4 HDMI receiver. The ADV7604 has four multiplexed HDMI inputs and one analog
5 input, and the ADV7611 has one HDMI input and no analog input. The 7612 is
12 - compatible: Must contain one of the following
19 detection pins, one per HDMI input. The active flag indicates the GPIO
22 The device node must contain one 'port' child node per device input and output
32 The digital output port node must contain at least one endpoint.
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ |
| D | renesas,du.txt | 5 - compatible: must be one of the following.
12 - reg: A list of base address and length of each memory resource, one for
14 - reg-names: Name of the memory resources. The DU requires one memory
15 resource for the DU core (named "du") and one memory resource for each
22 - clocks: A list of phandles + clock-specifier pairs, one for each entry in
27 - R8A779[0134] use one functional clock per channel and one clock per LVDS
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | sdhci-pxa.txt | 10 * for "mrvl,pxav2-mmc" and "mrvl,pxav3-mmc", one register area for
14 one for the SDHCI registers themselves, the second one for the
15 AXI/Mbus bridge registers of the SDHCI unit, the third one for the
19 - clocks: Array of clocks required for SDHCI; requires at least one for
|
| D | samsung-sdhci.txt | 9 - compatible: should be one of the following
17 - pinctrl-names: Should contain only one value - "default".
|
| D | nvidia,tegra20-sdhci.txt | 14 plus one of the above, where <chip> is tegra132 or tegra210.
15 - clocks : Must contain one entry, for the module clock.
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | brcm,unimac-mdio.txt | 4 - compatible: should one from "brcm,genet-mdio-v1", "brcm,genet-mdio-v2",
6 - reg: address and length of the regsiter set for the device, first one is the
7 base register, and the second one is optional and for indirect accesses to
14 - interrupts: must be one if the interrupt is shared with the Ethernet MAC or
16 are two separate interrupts, first one must be "mdio done" and second must be
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | designware-i2s.txt | 7 clocks. The controller expects one clock: the clock used as the sampling
11 the core. The core expects one or two dma channels: one for transmit and
12 one for receive.
|
| D | mvebu-audio.txt | 18 - clocks: one or two phandles.
19 The first one is mandatory and defines the internal clock.
20 The second one is optional and defines an external clock.
|
| D | cs42xx8.txt | 5 - compatible : must contain one of "cirrus,cs42448" and "cirrus,cs42888"
9 - clocks : a list of phandles + clock-specifiers, one for each entry in
|
| D | nvidia,tegra30-i2s.txt | 6 "nvidia,<chip>-i2s" plus at least one of the above, where <chip> is
9 - clocks : Must contain one entry, for the module clock.
|
| D | adi,axi-i2s.txt | 12 the core. The core expects two dma channels, one for transmit and one for
|
| D | rockchip-spdif.txt | 9 - compatible: should be one of the following:
18 - clocks: a list of phandle + clock-specifier pairs, one for each entry
|
| D | rockchip-i2s.txt | 8 - compatible: should be one of the followings
18 - clocks: a list of phandle + clock-specifer pairs, one for each entry in clock-names.
|
| /linux-4.4.14/Documentation/devicetree/bindings/w1/ |
| D | w1-gpio.txt | 6 - gpios: one or two GPIO specs:
7 - the first one is used as data I/O pin
8 - the second one is optional. If specified, it is used as
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | abilis,tb10x-ictl.txt | 5 one-to-one mapping of external interrupt sources to CPU interrupts and
19 are mapped one-to-one to parent interrupts.
|
| D | brcm,bcm7038-l1-intc.txt | 4 directly to one of the HW INT lines on each CPU. Every BCM7xxx set-top chip
32 this one is cascaded from
38 /proc/irq/ interface. In the simplest possible configuration, only one
39 reg range and one interrupt-parent is needed.
|
| D | brcm,bcm3380-l2-intc.txt | 8 - contains one or more enable/status word pairs, which often appear at
16 - reg: specifies one or more enable/status pairs, in the following format:
22 this one is cascaded from
|
| D | brcm,bcm7120-l2-intc.txt | 16 - has one 32-bit enable word and one 32-bit status word
60 this one is cascaded from
77 parent. This should have one 32-bit word per enable/status pair.
|
| D | arm,vic.txt | 9 - compatible : should be one of
21 - valid-mask : A one cell big bit mask of valid interrupt sources. Each bit
25 - valid-wakeup-mask : A one cell big bit mask of interrupt sources that can be
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | inotify.txt | 30 want: Users initialize inotify, once, and add n watches, requiring but one
48 versus just one. It is a lot messier in the kernel. A single, linear
63 Additionally, it _is_ possible to more than one instance and
64 juggle more than one queue and thus more than one associated fd. There
65 need not be a one-fd-per-process mapping; it is one-fd-per-queue and a
66 process can easily want more than one queue.
73 file descriptor-based one that allows basic file I/O and poll/select.
|
| D | quota.txt | 8 of used inodes there are actually two limits. The first one is called softlimit
9 and the second one hardlimit. An user can never exceed a hardlimit for any
38 Currently, the interface supports only one message type QUOTA_NL_C_WARNING.
43 - type of quota being exceeded (one of USRQUOTA, GRPQUOTA)
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | DefaultKeyAssignments | 13 KeyPad-7 Say Previous Line (UP one line)
14 KeyPad-9 Say Next Line (down one line)
17 KeyPad-4 Say Previous Word (left one word)
19 KeyPad-6 Say Next Word (right one word)
23 KeyPad-1 Say Previous Character (left one letter)
24 KeyPad-3 Say Next Character (right one letter)
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | samsung,sysmmu.txt | 13 System MMUs are in many to one relation with peripheral devices, i.e. single
14 peripheral device might have multiple System MMUs (usually one for each bus
15 master), but one System MMU can handle transactions from only one peripheral
21 * MFC has one System MMU on its left and right bus.
22 * FIMD in Exynos5420 has one System MMU for window 0 and 4, the other system MMU
24 * M2M Scalers and G2D in Exynos5420 has one System MMU on the read channel and
|
| D | arm,smmu.txt | 12 - compatible : Should be one of:
33 For SMMUv2 implementations, there must be exactly one
73 * and 0xd01e) and the second with only one (0xd11c).
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | cpm.txt | 10 one of two different order for the CPM
16 - unused-units : specifier consist of one cell. For each
20 - idle-doze : specifier consist of one cell. For each
24 - standby : specifier consist of one cell. For each
28 - suspend : specifier consist of one cell. For each
|
| /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/Documentation/devicetree/bindings/thermal/ |
| D | armada-thermal.txt | 5 - compatible: Should be set to one of the following:
13 The first one is required for the sensor register;
14 the second one is required for the control register
|
| D | thermal.txt | 30 control one or more internal sensors.
35 Size: one cell nodes with only one sensor, and at least 1 on nodes
65 Size: one cell to specify minimum and maximum cooling state used
75 Size: one cell
79 Size: one cell
90 Size: one cell
94 Size: one cell
122 Size: one cell The contribution is a ratio of the sum
135 thermal zone node must contain, apart from its own properties, one sub-node
136 containing trip nodes and one sub-node containing all the zone cooling maps.
[all …]
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-ryos | 4 Description: When written, this file lets one select which data from which
24 Description: When written, this file lets one set the default of all keys for
34 Description: When written, this file lets one set the function of the
44 Description: When written, this file lets one set the function of the macro
54 Description: When written, this file lets one set the function of the
64 Description: When written, this file lets one set the function of the
74 Description: When written, this file lets one set the function of the
84 Description: When written, this file lets one deactivate certain keys like
95 Description: When written, this file lets one set the backlight intensity for
106 Description: When written, this file lets one store macros with max 480
[all …]
|
| D | sysfs-driver-hid-roccat-isku | 23 Description: When written, this file lets one deactivate certain keys like
34 Description: When written, this file lets one set the function of the
44 Description: When written, this file lets one set the function of the
54 Description: When written, this file lets one set the function of the
64 Description: When written, this file lets one set the function of the macro
74 Description: When written, this file lets one set the function of the media
84 Description: When written, this file lets one set the function of the
94 Description: When written, this file lets one set the time in secs since
102 Description: When written, this file lets one set the backlight intensity for
113 Description: When written, this file lets one store macros with max 500
[all …]
|
| /linux-4.4.14/drivers/tty/serial/ |
| D | sc16is7xx.c | 351 struct sc16is7xx_one *one = to_sc16is7xx_one(port, port); in sc16is7xx_line() local
353 return one->line; in sc16is7xx_line()
742 struct sc16is7xx_one *one = to_sc16is7xx_one(ws, reg_work); in sc16is7xx_reg_proc() local
746 spin_lock_irqsave(&one->port.lock, irqflags); in sc16is7xx_reg_proc()
747 config = one->config; in sc16is7xx_reg_proc()
748 memset(&one->config, 0, sizeof(one->config)); in sc16is7xx_reg_proc()
749 spin_unlock_irqrestore(&one->port.lock, irqflags); in sc16is7xx_reg_proc()
752 sc16is7xx_port_update(&one->port, SC16IS7XX_MCR_REG, in sc16is7xx_reg_proc()
754 (one->port.mctrl & TIOCM_LOOP) ? in sc16is7xx_reg_proc()
758 sc16is7xx_port_update(&one->port, SC16IS7XX_IER_REG, in sc16is7xx_reg_proc()
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | graph.txt | 14 have multiple specifiable ports, each of which can be linked to one or more
32 connected to this port. If a single port is connected to more than one
34 If more than one port is present in a device node or there is more than one
92 remote endpoint should contain a 'remote-endpoint' property. If it has one,
117 If there is more than one 'port' or more than one 'endpoint' node or 'reg'
|
| /linux-4.4.14/drivers/scsi/arm/ |
| D | Kconfig | 10 Acorn system with one of these, say Y. If unsure, say N.
50 Acorn system with one of these, say Y. If unsure, say N.
57 system with one of these, say Y, otherwise say N.
64 you have one of these, say Y. If unsure, say N.
75 Acorn system with one of these, say Y. If unsure, say N.
83 system with one of these, say Y. If unsure, say N.
|
| /linux-4.4.14/net/sctp/ |
| D | sysctl.c | 44 static int one = 1; variable
110 .extra1 = &one,
119 .extra1 = &one,
178 .extra1 = &one,
196 .extra1 = &one,
205 .extra1 = &one,
214 .extra1 = &one,
223 .extra1 = &one,
299 .extra1 = &one,
|
| /linux-4.4.14/Documentation/devicetree/bindings/pwm/ |
| D | pxa-pwm.txt | 4 - compatible: should be one or more of:
10 Note that one device instance must be created for each PWM that is used, so the
11 length covers only the register window for one PWM output, not that of the
|
| D | imx-pwm.txt | 4 - compatible : should be "fsl,<soc>-pwm" and one of the following
6 - "fsl,imx1-pwm" for PWM compatible with the one integrated on i.MX1
7 - "fsl,imx27-pwm" for PWM compatible with the one integrated on i.MX27
|
| D | nvidia,tegra20-pwm.txt | 6 "nvidia,<chip>-pwm", plus one of the above, where <chip> is tegra114,
11 - clocks: Must contain one entry, for the module clock.
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | e3x0-button.txt | 8 - compatible: should be one of the following
12 - interrupts: should be one of the following
14 - interrupt-names: should be one of the following
|
| D | twl4030-pwrbutton.txt | 9 - compatible: should be one of the following
11 - interrupts: should be one of the following
|
| D | twl4030-keypad.txt | 15 - compatible: should be one of the following
18 - interrupt: should be one of the following
|
| /linux-4.4.14/kernel/ |
| D | sysctl.c | 124 static int __maybe_unused one = 1; variable
382 .extra1 = &one,
391 .extra2 = &one,
424 .extra2 = &one,
434 .extra1 = &one,
499 .extra2 = &one,
633 .extra1 = &one,
634 .extra2 = &one,
652 .extra1 = &one,
653 .extra2 = &one,
[all …]
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.net | 11 provide one or more virtual network devices through which the UML
21 enable at least one of the following transport options to actually
29 running UML to exchange packets with its host over one of the
31 UMLs can use additional Ethertap devices, one per running UML.
47 Slip Transport. You'll need at least one of them, but may choose
48 more than one without conflict. If you don't need UML networking,
84 UMLs on a single host). You may choose more than one without
91 This User-Mode Linux network transport allows one or more running
107 transports. You'll need at least one of them, but may choose
108 more than one without conflict. If you don't need UML networking,
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-imx.txt | 5 - "fsl,imx1-i2c" for I2C compatible with the one integrated on i.MX1 SoC
6 - "fsl,imx21-i2c" for I2C compatible with the one integrated on i.MX21 SoC
7 - "fsl,vf610-i2c" for I2C compatible with the one integrated on Vybrid vf610 SoC
15 - dmas: A list of two dma specifiers, one for each entry in dma-names.
|
| D | i2c-sunxi-p2wi.txt | 7 - compatible : Should one of the following:
18 A P2WI may contain one child node encoding a P2WI slave device.
|
| D | i2c-mux.txt | 5 multiplexer/switch will have one child node for each child
26 with two NXP pca8574 GPIO expanders attached, one each to
|
| D | i2c-sh_mobile.txt | 24 specifiers, one for transmission, and one for
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | atmel-flexcom.txt | 4 controller and an USART. Only one function can be used at a time and is chosen
14 - ranges: Should be one range for the full I/O register region
16 - atmel,flexcom-mode: Should be one of the following values:
25 The phandle provided by the clocks property of the child is the same as one for
|
| D | omap-usb-tll.txt | 6 - reg : should contain one register range i.e. start and length
12 - clocks: a list of phandles and clock-specifier pairs, one for each entry in
|
| D | as3711.txt | 22 Additionally one of these properties must be provided to select the type of
30 and one of these to select the over-voltage protection pin
36 If "su2-feedback-curr-auto" is selected, one or more of the following properties
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | renesas,rcar-dmac.txt | 8 Each DMA client is connected to one dedicated port of the DMAC, identified by
21 - interrupts: interrupt specifiers for the DMAC, one for each entry in
23 - interrupt-names: one entry per channel, named "ch%u", where %u is the
24 channel number ranging from zero to the number of channels minus one.
27 - clocks: a list of phandle + clock-specifier pairs, one for each entry
|
| D | renesas,usb-dmac.txt | 6 - interrupts: interrupt specifiers for the DMAC, one for each entry in
8 - interrupt-names: one entry per channel, named "ch%u", where %u is the
9 channel number ranging from zero to the number of channels minus one.
|
| D | dma.txt | 69 - dmas: List of one or more DMA specifiers, each consisting of
77 - dma-names: Contains one identifier string for each DMA specifier in
86 1. A device with one DMA read channel, one DMA write channel:
103 3. A device with three channels, one of which has two alternatives:
|
| D | nbpfaxi.txt | 7 - compatible: must be one of
18 slave is connected, the second one is flags. Flags is a bitmask
|
| D | qcom_bam_dma.txt | 4 - compatible: must be one of the following:
9 - interrupts: Should contain the one interrupt shared by all channels
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/bridge/ |
| D | adi,adv7511.txt | 10 - compatible: Should be one of "adi,adv7511", "adi,adv7511w" or "adi,adv7513"
21 - adi,input-colorspace: The input color space, one of "rgb", "yuv422" or
23 - adi,input-clock: The input clock type, one of "1x" (one clock cycle per
24 pixel), "2x" (two clock cycles per pixel), "ddr" (one clock cycle per pixel,
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | omap54xx-clocks.dtsi | 124 ti,index-starts-at-one;
167 ti,index-starts-at-one;
197 ti,index-starts-at-one;
222 ti,index-starts-at-one;
231 ti,index-starts-at-one;
240 ti,index-starts-at-one;
249 ti,index-starts-at-one;
258 ti,index-starts-at-one;
267 ti,index-starts-at-one;
276 ti,index-starts-at-one;
[all …]
|
| D | dra7xx-clocks.dtsi | 211 ti,index-starts-at-one;
231 ti,index-starts-at-one;
242 ti,index-starts-at-one;
274 ti,index-starts-at-one;
300 ti,index-starts-at-one;
342 ti,index-starts-at-one;
376 ti,index-starts-at-one;
410 ti,index-starts-at-one;
421 ti,index-starts-at-one;
455 ti,index-starts-at-one;
[all …]
|
| D | omap44xx-clocks.dtsi | 156 ti,index-starts-at-one;
193 ti,index-starts-at-one;
225 ti,index-starts-at-one;
236 ti,index-starts-at-one;
255 ti,index-starts-at-one;
292 ti,index-starts-at-one;
310 ti,index-starts-at-one;
327 ti,index-starts-at-one;
343 ti,index-starts-at-one;
375 ti,index-starts-at-one;
[all …]
|
| D | am43xx-clocks.dtsi | 218 ti,index-starts-at-one;
229 ti,index-starts-at-one;
240 ti,index-starts-at-one;
258 ti,index-starts-at-one;
284 ti,index-starts-at-one;
302 ti,index-starts-at-one;
321 ti,index-starts-at-one;
613 ti,index-starts-at-one;
689 ti,index-starts-at-one;
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/xilinx/ |
| D | xilinx_dma.txt | 2 target devices. It can be configured to have one channel or two channels.
3 If configured as two channels, one is to transmit to the device and another
10 - dma-channel child node: Should have atleast one channel and can have upto
55 - dma-names: a list of DMA channel names, one per "dmas" entry
|
| D | xilinx_vdma.txt | 2 It can be configured to have one channel or two channels. If configured
3 as two channels, one is to transmit to the video device and another is
11 - dma-channel child node: Should have at least one channel and can have up to
65 - dma-names: a list of DMA channel names, one per "dmas" entry
|
| /linux-4.4.14/Documentation/devicetree/bindings/crypto/ |
| D | atmel-crypto.txt | 13 - dma-names: Contains one identifier string for each DMA specifier
35 - dma-names: Contains one identifier string for each DMA specifier
58 - dma-names: Contains one identifier string for each DMA specifier
59 in the dmas property. Only one "tx" string needed.
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-mvebu.txt | 12 - reg: Address and length of the register set for the device. Only one
14 for which two entries are expected: one for the general registers,
15 one for the per-cpu registers.
18 managed by this GPIO bank. There can be more than one interrupt
|
| D | fsl-imx-gpio.txt | 7 one number. If two numbers, the first one is the interrupt shared
8 by low 16 pins and the second one is for high 16 pins.
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | jack.txt | 8 - It allows more than one jack detection method to work together on one
23 mechanisms, one for the headphone and one for the microphone. Some
63 least one to be useful.
70 the list of pins to update then set up one or more jack detection
|
| /linux-4.4.14/Documentation/ |
| D | lzo.txt | 12 the format matches the standard one. The purpose of this document is to
54 Certain encodings involve one extra byte, others involve two extra bytes
60 practice, only one instruction needs to know whether 0, less than 4, or more
66 End of stream is declared when a block copy of distance 0 is seen. Only one
67 instruction may encode this distance (0001HLLL), it takes one LE16 operand
116 Always followed by exactly one byte : H H H H H H H H
126 Always followed by exactly one byte : H H H H H H H H
132 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S
140 Always followed by exactly one LE16 : D D D D D D D D : D D D D D D S S
148 Always followed by exactly one byte : H H H H H H H H
[all …]
|
| D | circular-buffers.txt | 18 To use these facilities, as discussed below, there needs to be just one
19 producer and just one consumer. It is possible to handle multiple producers by
48 empty; and the buffer is full when the head pointer is one less than the tail
60 be careful, however, as a region more than one unit in size may wrap the end of
150 consumer that empties it. Only one thing should be filling a buffer at any one
151 time, and only one thing should be emptying a buffer at any one time, but the
167 /* insert one item into the buffer */
188 there is always one element of the array left empty. Therefore, the
209 /* extract one item from the buffer */
|
| D | padata.txt | 67 change just one of the cpumasks. Here cpumask_type is one of PADATA_CPU_SERIAL,
69 To simply add or remove one CPU from a certain cpumask the functions
71 remove and mask is one of PADATA_CPU_SERIAL, PADATA_CPU_PARALLEL.
94 is one of PADATA_CPU_SERIAL, PADATA_CPU_PARALLEL and cpumask is a pointer
127 exactly one call to the above-mentioned parallel() function, on one CPU, so
139 the previous one completes. When a task does complete, parallel() (or
153 The one remaining function in the padata API should be called to clean up
|
| D | parport.txt | 2 includes the ability to share one port between multiple device
29 to tell the parport code that you want three PC-style ports, one at
30 0x3bc with no IRQ, one at 0x378 using IRQ 7, and one at 0x278 with an
79 You can have many `parport=...' statements, one for each port you want
142 has more than one in which case they are separated
194 is loaded it will create one lp device for each port found. You can
210 case - if you only have one port, it will default to being /dev/lp0,
258 If _that_ works fine, then one of the hardware modes isn't working
|
| D | workqueue.txt | 30 functions associated with the work items one after the other. When
37 In the original wq implementation, a multi threaded (MT) wq had one
38 worker thread per CPU and a single threaded (ST) wq had one worker
48 worker pool. A MT wq could provide only one execution context per CPU
49 while a ST wq one for the whole system. Work items had to compete for
86 off of the queue, one after the other. If no work is queued, the
94 There are two worker-pools, one for normal work items and the other
126 stalling should be optimal. As long as there are one or more runnable
160 there is one.
196 have this flag set. The wq is guaranteed to have at least one
[all …]
|
| D | kernel-per-CPU-kthreads.txt | 57 To reduce its OS jitter, do one of the following:
76 first one back online. Once you have onlined the CPUs in question,
78 timer back onto one of the CPUs in question.
100 TASKLET_SOFTIRQ: Do one or more of the following:
108 for example, ensure that at most one runnable kthread is present
131 CPUs, force them all offline before bringing the first one
134 back onto one of the CPUs in question.
135 RCU_SOFTIRQ: Do at least one of the following:
199 for an interval of one second. Of course, larger values
205 (based on an earlier one from Gilad Ben-Yossef) that
[all …]
|
| D | hw_random.txt | 40 available, while "rng_current" lists the one which is currently
41 connected to /dev/hwrng. If your system has more than one
42 RNG available, you may change the one used by writing a name from
67 1) Only one RNG is supported by this driver, 2) The location
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/backlight/ |
| D | pm8941-wled.txt | 16 - qcom,current-boost-limit: mA; boost current limit; one of:
19 - qcom,switching-freq: kHz; switching frequency; one of:
23 - qcom,ovp: V; Over-voltage protection limit; one of:
|
| /linux-4.4.14/Documentation/input/ |
| D | gpio-tilt.txt | 5 Orientation can be provided by one or more than one tilt switches,
6 i.e. each tilt switch providing one axis, and the number of axes
31 one axis in 4 steps and emits the current tilt via two GPIOs.
|
| D | gameport-programming.txt | 18 If your hardware supports more than one io address, and your driver can
19 choose which one to program the hardware to, starting from the more exotic
27 space (is above 0x1000), use that one, and don't map the ISA mirror.
30 gameport. Although only one ioport is really used, the gameport usually
31 occupies from one to sixteen addresses in the io space.
45 isn't as easy as a basic IO one, but not so much complex:
104 more than one gameport instance simultaneously, use the ->private member of
|
| D | joystick-parport.txt | 39 the output lines of the parallel port are shared, while one of 5 available
42 This protocol is handled by the gamecon.c driver, so that's the one
52 some data pin. For most gamepad and parport implementations only one pin is
223 was written. It allows only one joystick / gamepad per parallel port, but
262 For some people just one joystick per parallel port is not enough, and/or
263 want to use them on one parallel port together with NES/SNES/PSX pads. This is
274 and one pullup resistor. First, you connect the Directions and the button
290 for the NES / SNES pads in section 2.1 of this file - that is, one data pin
308 supports only one button per joystick. For more information on how to build the
328 +----------------------------> Data --- (one of 10,11,12,13,15)
[all …]
|
| D | cs461x.txt | 25 needed code have been moved to one separate file cs461x.c like ns558.c
31 uses joystick as input device and PCM device as sound output in one time.
34 separately of ALSA modules. So, you can use only one joystick driver
|
| D | rotary-encoder.txt | 31 one step
34 one step (half-period mode)
37 one step (quarter-period mode)
58 meaning that there it has seen half the way of a one-step transition.
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | rcar_vin.txt | 5 family of devices. The current blocks are always slaves and suppot one input
8 - compatible: Must be one of the following
24 as described in video-interfaces.txt[1]. Only the first one will
25 be considered as each vin interface has one input port.
|
| D | samsung-s5k5baf.txt | 26 The device node should contain one 'port' child node with one child 'endpoint'
36 supports only one data lane without re-mapping.
|
| /linux-4.4.14/arch/arm/mach-at91/ |
| D | Kconfig | 21 Select this if ou are using one of Atmel's SAMA5D2 family SoC.
32 Select this if you are using one of Atmel's SAMA5D3 family SoC.
46 Select this if you are using one of Atmel's SAMA5D4 family SoC.
75 Select this if you are using one of those Atmel SoC:
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | qcom,coincell-charger.txt | 21 must be one of: 800, 1200, 1700, 2100
27 must be one of: 2500, 3000, 3100, 3200
34 This charger is a sub-node of one of the 8941 PMIC blocks, and is specified
|
| /linux-4.4.14/Documentation/devicetree/bindings/spmi/ |
| D | spmi.txt | 15 pair. The address must be in the range 0-15 (4 bits). The type must be one of
20 Each child node must have one and only one 'reg' entry of type SPMI_USID.
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | divider.txt | 7 only one input clock or parent. By default the value programmed into
8 the register is one less than the actual divisor value. E.g:
17 ti,index-starts-at-one - valid divisor values start at 1, not the default
69 - ti,index-starts-at-one : valid divisor programming starts at 1, not zero,
86 ti,index-starts-at-one;
104 ti,index-starts-at-one;
|
| D | mux.txt | 7 parents, one of which can be selected as output. This clock does not
24 "index-starts-at-one" modified the scheme as follows:
47 - ti,index-starts-at-one : valid input select programming starts at 1, not
59 ti,index-starts-at-one;
|
| D | composite.txt | 8 a multiplexer clock with multiple input clock signals or parents, one
17 merged to this clock. The component clocks shall be of one of the
47 ti,index-starts-at-one;
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | configfs-usb-gadget | 69 This group contains "Feature Descriptors" specific for one
70 gadget's USB interface or one interface group described
82 This group contains "Extended Property Descriptors" specific for one
83 gadget's USB interface or one interface group described
123 b_vendor_code - one-byte value used for custom per-device and
|
| D | sysfs-bus-iio-trigger-sysfs | 19 one should write this name string to
28 In order to achieve this, one should write a positive integer
39 achieve this, one should write a positive integer into the
|
| D | sysfs-kernel-boot_params | 5 files: "data" and "version" and one subdirectory "setup_data".
19 as a link list. In "setup_data" subdirectory there's one
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | ultrasound | 29 just one 8 bit DMA channel. Recording will not work with one DMA
30 channel if it's a 16 bit one.
|
| /linux-4.4.14/Documentation/devicetree/bindings/watchdog/ |
| D | st_lpc_wdt.txt | 12 - compatible : Must be one of: "st,stih407-lpc" "st,stih416-lpc"
17 - st,lpc-mode : The LPC can run either one of three modes:
21 One (and only one) mode must be selected.
|
| D | marvel.txt | 11 - reg : Should contain two entries: first one with the
12 timer control address, second one with the
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Sound-FAQ | 14 log, telling which card type is used. Like this one:
22 new entries which are not listed yet. If there isn't one for your
23 card, you can check if one of the existing entries does work for you
28 example. If your board has one, you might have to load a helper
29 module like msp3400.o to make sound work. If there isn't one for the
30 chip used on your board: Bad luck. Start writing a new one. Well,
47 bt848 chip. Another one is the data register (BT848_GPIO_DATA), where
85 Another one with bt878 support is available from
99 audioall=a set the values of the audiomux array (one
|
| /linux-4.4.14/Documentation/leds/ |
| D | ledtrig-transient.txt | 5 a one shot timer. The current support allows for setting two timers, one for
10 gets deactivated. There is no provision for one time activation to implement
14 Without one shot timer interface, user space can still use timer trigger to
21 PMIC. There is a need to activate one shot timer to control the vibrate
25 Transient trigger addresses the need for one shot timer activation. The
82 activate - one shot timer activate mechanism.
92 duration - one shot timer value. When activate is set, duration value
99 held for the duration of the one shot timer and then the
134 - Timer activation is one shot and extending and/or shortening the timer
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | emc1403 | 37 (one internal, one external). EMC14x3 support three sensors (one internal,
38 two external), and EMC14x4 support four sensors (one internal, three
|
| D | adt7411 | 21 internal temperature sensor, but an external one can also be connected (one
|
| /linux-4.4.14/Documentation/scsi/ |
| D | megaraid.txt | 11 interfaces with the applications on one side and all the low level drivers
19 iii. Implement any policy mechanisms in one place.
67 Common module dedicates one uioc_t packet to each controller registered. This
68 can easily be more than one. But since megaraid is the only low level driver
69 today, and it can handle only one ioctl, there is no reason to have more. But
|
| D | dtc3x80.txt | 36 SCSI-2), and one CDROM drive. Interrupts works great for all but one
37 specific hard drive. For this one, the driver will eventually hang in
|
| /linux-4.4.14/drivers/net/ |
| D | veth.c | 168 struct pcpu_vstats one; in veth_get_stats64() local
170 tot->tx_dropped = veth_stats_one(&one, dev); in veth_get_stats64()
171 tot->tx_bytes = one.bytes; in veth_get_stats64()
172 tot->tx_packets = one.packets; in veth_get_stats64()
177 tot->rx_dropped = veth_stats_one(&one, peer); in veth_get_stats64()
178 tot->rx_bytes = one.bytes; in veth_get_stats64()
179 tot->rx_packets = one.packets; in veth_get_stats64()
|
| /linux-4.4.14/Documentation/devicetree/bindings/c6x/ |
| D | dscr.txt | 8 In general, the Device State Configuration Registers (DSCR) will provide one or
9 more configuration registers often protected by a lock register where one or
42 than one ethernet port is available.
65 Each tuple describes a range of identical bitfields used to control one or
66 more devices (one bitfield per device). The layout of each tuple is:
82 identical bitfields used to provide status for one or more devices (one
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | radiotrack.txt | 49 The RadioTrack (base) ioport is configurable for 0x30c or 0x20c. Only one
53 parallel with one write to the ioport. The only feedback available through
91 1 0 : "one" bit phase 1
92 1 1 : "one" bit phase 2
141 to write a "one" bit,
143 disable, "one" bit phase 1, tuner adjust)
145 disable, "one" bit phase 2, tuner adjust)
|
| D | README.cx88 | 39 like this one:
57 * the tuner type used by the card. You can try to find one by
59 know which one the card has you can also have a look at the
|
| /linux-4.4.14/Documentation/fault-injection/ |
| D | provoke-crashes.txt | 17 one of INT_HARDWARE_ENTRY, INT_HW_IRQ_EN, INT_TASKLET_ENTRY,
22 It can be one of PANIC, BUG, EXCEPTION, LOOP, OVERFLOW,
37 KPROBE instrumentation. This mode is the only one available when the module
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 21 state bits (one for MMIO and one for DMA, they get set together but can be
54 - For MSIs, we have two windows in the address space (one at the top of
55 the 32-bit space and one much higher) which, via a combination of the
56 address and MSI value, will result in one of the 2048 interrupts per
66 from the CPU address space to the PCI address space. There is one M32
98 scheme where individual function BARs can be "grouped" to fit in one or
136 than one segment, we end up with more than one PE#. There is a HW
143 "master PE" which is the one used for DMA, MSIs, etc., and "secondary
172 is a BAR0 for one of the VFs. Note that even though the VF BAR
178 - M32 window: There's one M32 window, and it is split into 256
[all …]
|
| /linux-4.4.14/Documentation/usb/ |
| D | functionfs.txt | 18 only one (endpoints and strings numbers starting from one and
24 (one for each declared endpoint) which handle communication on
53 just one function with any name.
57 parameter's value is just a one-element list, then the behaviour
|
| D | gadget_multi.txt | 15 have two configurations -- one with RNDIS and another with CDC ECM[3].
22 To make use of the gadget one needs to make it work on host side --
24 As one might expect, things one need to do very from system to system.
34 configuration being the first one. Linux host will use the second
69 gadget, one needs to use the [[file:linux.inf]] file provided with this
91 provided functions one should change gadget's vendor and/or product ID
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/ |
| D | auo_pixcir_ts.txt | 8 first one is the interrupt gpio and second one the reset gpio
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | primecell.txt | 19 - dmas : From common DMA binding. If present, refers to one or more dma channels.
21 Devices with exactly one receive and transmit channel shall name
25 - interrupts : one or more interrupt specifiers
|
| D | armada-38x.txt | 12 following property before the previous one:
19 following property before the previous one:
|
| D | tegra.txt | 7 Each device tree must specify which Tegra SoC it uses, using one of the
16 Each device tree must specify which one or more of the following
|
| D | picoxcell.txt | 17 Note: two timers are required - one for the scheduler clock and one for the
|
| D | vexpress-sysreg.txt | 23 - compatible value : one of
66 details. Each child of such node describes one function and must
68 - compatible value : must be one of (corresponding to the TRM):
87 are using more than one function/device number pair
|
| D | vexpress.txt | 4 ARM's Versatile Express platform consists of a motherboard and one
11 can be initialized in one of two different configurations ("memory
12 maps"), care must be taken to include the correct one.
27 If a tile comes in several variants or can be used in more then one
107 - when daughterboards are stacked on one site, their position
110 - when describing tiles consisting more than one DCC, its number
131 where name is one of:
|
| D | cci.txt | 11 space and multiple sets of interface control registers, one per slave
27 through the CCI interconnect is the same as the one seen from the
34 Definition: must contain one of the following:
76 Definition: must be set to one of {"ace", "ace-lite"}
98 Definition: Must contain one of:
118 Definition: list of counter overflow interrupts, one per
|
| D | coherency-fabric.txt | 24 * For "marvell,armada-375-coherency-fabric", only one pair is needed
27 * For "marvell,armada-380-coherency-fabric", only one pair is needed
|
| D | twd.txt | 12 - compatible : Should be one of:
37 - compatible : Should be one of:
|
| /linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas-memory-controllers.txt | 4 Renesas R-Mobile and SH-Mobile SoCs contain one or more memory controllers.
5 These memory controllers differ from one SoC variant to another, and are called
17 - compatible: Must be one of the following SoC-specific values:
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/exynos/ |
| D | exynos_hdmi.txt | 4 - compatible: value should be one among the following:
19 c) sclk_pixel: Pixel special clock, one of the two possible inputs of
21 d) sclk_hdmiphy: HDMI PHY clock output, one of two possible inputs of
|
| D | exynos_mixer.txt | 4 - compatible: value should be one of the following:
16 b) sclk_hdmi: HDMI Special clock, one of the two possible inputs of
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-emc.txt | 10 and chosen using the ramcode board selector. If omitted, only one
51 * The simplest is if there is just one set of tables in the device tree,
57 * The slightly more complex one is when more than one memory configuration
59 early boot by selecting one out of possible 4 memory settings based
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | fan53555.txt | 4 - compatible: one of "fcs,fan53555", "silergy,syr827", "silergy,syr828"
10 voltage. The other one is used for the runtime voltage setting
|
| /linux-4.4.14/Documentation/devicetree/bindings/rtc/ |
| D | armada-380-rtc.txt | 7 - reg: a list of base address and size pairs, one for each entry in
11 * "rtc-soc" for the SoC related registers and among them the one
|
| D | rtc-mxc.txt | 11 * one for the input reference
12 * one for the the SoC RTC
|
| D | rtc-st-lpc.txt | 16 - st,lpc-mode : The LPC can run either one of three modes:
20 One (and only one) mode must be selected.
|
| /linux-4.4.14/Documentation/timers/ |
| D | hpet.txt | 8 Each HPET has one fixed-rate counter (at 10+ MHz, hence "High Precision")
10 each of which can generate oneshot interrupts and at least one of which has
15 HPET devices can support two interrupt routing modes. In one mode, the
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | phy-bindings.txt | 53 This node represents a controller that uses two PHYs, one for usb2 and one for
68 This node represents a controller that uses one of the PHYs of the PHY provider
|
| D | phy-stih407-usb.txt | 9 - resets : list of phandle and reset specifier pairs. There should be two entries, one
10 for the whole phy and one for the port
|
| D | qcom-dwc3-usb-phy.txt | 8 - compatible: should contain one of the following:
13 - clocks: a list of phandles and clock-specifier pairs, one for each entry in
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | allwinner,sunxi-pinctrl.txt | 9 - compatible: Should be one of the followings (depending on you SoC):
28 A pinctrl node should contain at least one subnodes representing the
31 configuration, drive strength and pullups. If one of these options is
80 Consumers that would want to refer to one or the other (or both)
|
| /linux-4.4.14/Documentation/power/ |
| D | interface.txt | 5 userspace, regardless of what architecture or platform one is
14 Writing to this file one of those strings causes the system to
26 Additionally, /sys/power/disk can be used to turn on one of the two testing
38 selected one in brackets, for example
42 Writing to this file will accept one of
|
| /linux-4.4.14/Documentation/devicetree/bindings/ata/ |
| D | sata_rcar.txt | 4 - compatible : should contain one of the following:
12 - interrupts : must consist of one interrupt specifier.
|
| D | pata-arasan.txt | 9 - clock-frequency: Interface clock rate, in Hz, one of
26 - dmas: one DMA channel, as described in bindings/dma/dma.txt
|
| /linux-4.4.14/Documentation/devicetree/bindings/iio/accel/ |
| D | bma180.txt | 17 For the bma250 the first interrupt listed must be the one
19 listed must be the one connected to the INT2 pin.
|
| /linux-4.4.14/arch/x86/boot/compressed/ |
| D | aslr.c | 126 static bool mem_overlaps(struct mem_vector *one, struct mem_vector *two) in mem_overlaps() argument
129 if (one->start + one->size <= two->start) in mem_overlaps()
132 if (one->start >= two->start + two->size) in mem_overlaps()
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | kcopyd.txt | 4 Kcopyd provides the ability to copy a range of sectors from one block-device
5 to one or more other block-devices, with an asynchronous completion
18 of the copy is given as one io_region structure, and the destinations of the
|
| D | persistent-data.txt | 46 copy-on-write) or allocating a fresh one. Shadowing is elided within
60 implementations: a simpler one for managing blocks on a different
61 device (eg. thinly-provisioned data blocks); and one for managing
73 Currently there is only one data structure, a hierarchical btree.
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-domains.txt | 15 Each scheduling domain must have one or more CPU groups (struct sched_group)
16 which are organised as a circular one way linked list from the ->groups
24 is treated as one entity. The load of a group is defined as the sum of the
45 CPU's runqueue and the newly found busiest one and starts moving tasks from it
58 might have just one domain covering its one NUMA level.
|
| /linux-4.4.14/net/wireless/ |
| D | db.txt | 3 # enables CONFIG_CFG80211_INTERNAL_REGDB. Almost no one actually needs to
11 # need to replace this file with one containing appropriately formatted
|
| /linux-4.4.14/Documentation/devicetree/bindings/hwlock/ |
| D | qcom-hwspinlock.txt | 9 Definition: must be one of:
16 Definition: one cell containing:
|
| /linux-4.4.14/fs/dlm/ |
| D | lowcomms.c | 979 int one = 1; in sctp_connect_to_sock() local
1027 kernel_setsockopt(sock, SOL_TCP, TCP_NODELAY, (char *)&one, in sctp_connect_to_sock()
1028 sizeof(one)); in sctp_connect_to_sock()
1072 int one = 1; in tcp_connect_to_sock() local
1122 kernel_setsockopt(sock, SOL_TCP, TCP_NODELAY, (char *)&one, in tcp_connect_to_sock()
1123 sizeof(one)); in tcp_connect_to_sock()
1167 int one = 1; in tcp_create_listen_sock() local
1184 kernel_setsockopt(sock, SOL_TCP, TCP_NODELAY, (char *)&one, in tcp_create_listen_sock()
1185 sizeof(one)); in tcp_create_listen_sock()
1188 (char *)&one, sizeof(one)); in tcp_create_listen_sock()
[all …]
|
| /linux-4.4.14/drivers/md/ |
| D | Kconfig | 18 This driver lets you combine several hard disk partitions into one
19 logical block device. This can be used to simply append one
20 partition to another one or to combine several redundant hard disks
54 partitions by simply appending one to the other.
67 partitions into one logical device in such a fashion as to fill them
68 up evenly, one chunk here and one chunk there. This will increase
135 contain data sectors, and one drive contains the parity protection.
137 while a RAID-5 set distributes the parity across the drives in one
146 in one of the available parity distribution methods.
370 contain data sectors, and one drive contains the parity protection.
[all …]
|
| /linux-4.4.14/arch/mips/alchemy/ |
| D | Platform | 33 # boards can specify their own <gpio.h> in one of their include dirs.
35 # compiler picks the board one. If they don't, it will make sure
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,kpss-acc.txt | 4 There is one ACC register region per CPU within the KPSS remapped region as
13 Definition: should be one of:
|
| /linux-4.4.14/net/dccp/ |
| D | sysctl.c | 23 one = 1, variable
62 .extra1 = &one,
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | qca,ath79-pll.txt | 6 - compatible: has to be "qca,<soctype>-cpu-intc" and one of the following
17 - #clock-cells: has to be one
|
| D | renesas,cpg-mstp-clocks.txt | 12 - compatible: Must be one of the following
28 - clocks: Reference to the parent clocks, one per output clock. The parents
34 The clocks, clock-output-names and clock-indices properties contain one entry
|
| /linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | ifc.txt | 12 - #size-cells : Either one or two, depending on how large each chipselect
15 - interrupts: IFC may have one or two interrupts. If two interrupt
18 interrupt (NAND_EVTER_STAT). If there is only one,
|
| /linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ti/ |
| D | emif.txt | 4 TI SoCs. EMIF supports, based on the IP revision, one or more of
27 part attached to CS1, it should be the same type as the one on CS0,
30 - cal-resistor-per-cs : Have this property if the board has one
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-dev-attrs.txt | 38 always one 512 byte sector. For SD, "erase_size" is 512
46 is being erased, but erasing one partition will make
58 (especially for SD where it is just one sector),
63 erase size if a card specifies one, otherwise it is
|
| /linux-4.4.14/Documentation/vm/ |
| D | active_mm.txt | 42 one.
52 users) plus one if there are any real users.
54 Usually there is at least one real user, but it could be that the real
72 instead (which makes more sense anyway - the test is basically one of "do
78 would have thought it, but the alpha actually ends up having one of the
|
| D | soft-dirty.txt | 4 writes to. In order to do this tracking one should
16 64-bit qword is the soft-dirty one. If set, the respective PTE was
33 unmaps a previously mapped memory region and then maps a new one at exactly
|
| D | idle_page_tracking.txt | 23 DETAILS section). To mark a page idle one has to set the bit corresponding to
32 For huge pages the idle flag is set only on the head page, so one has to read
41 workload one should:
52 one wants to ignore certain types of pages, e.g. mlocked pages since they
63 space, in which case one or more PTEs it is mapped to will have the Accessed bit
87 as noted above, uses the Accessed bit to promote actively referenced pages, one
|
| /linux-4.4.14/Documentation/devicetree/bindings/reserved-memory/ |
| D | reserved-memory.txt | 5 one can create child nodes describing particular reserved (excluded from
21 Each child of the reserved-memory node specifies one or more regions of
81 one default of all device drivers (named linux,cma@72000000 and 64MiB in size),
82 one dedicated to the framebuffer device (named framebuffer@78000000, 8MiB), and
83 one for multimedia processing (named multimedia-memory@77000000, 64MiB).
|
| /linux-4.4.14/Documentation/networking/ |
| D | nfc.txt | 62 * activate_target - select and initialize one of the targets found
93 If the polling operation finds one or more targets, the event TARGETS_FOUND is
98 All polling operations requested through one netlink socket are stopped when
113 To establish a connection with one target, the user must create an
116 netlink event. As a target can support more than one NFC protocol, the user
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | binding.txt | 26 to find one that supports it. In order to determine that, the device
27 ID of the device must match one of the device IDs that the driver
45 the class to which it belongs. Device drivers belong to one and only one
97 one. The device is removed from that list and the symlinks removed.
|
| /linux-4.4.14/Documentation/cpuidle/ |
| D | governor.txt | 20 More than one governor can be registered at the same time and
22 More than one governor part is supported for developers to easily experiment
|
| /linux-4.4.14/Documentation/fb/ |
| D | deferred_io.txt | 6 IO. The following example may be a useful explanation of how one such setup
24 As can be seen from above, one benefit is roughly to allow bursty framebuffer
37 Another one may be if one has a device framebuffer that is in an usual format,
|
| /linux-4.4.14/Documentation/devicetree/bindings/iio/adc/ |
| D | xilinx-xadc.txt | 8 other one is available on all series 7 platforms and is a softmacro with a AXI
13 - compatible: Should be one of
29 * "single": External multiplexer mode is used with one
59 Each child node represents one channel and has the following
|
| /linux-4.4.14/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 19 consumer devices via optical or electrical physical layers directly to one
35 one of the peripheral interfaces of a network interface controller (e.g.
38 to MOST via one the following ways: character devices, ALSA, Networking or
77 Depending on how the driver should interface to the application, one or more
116 should travel to the host within one USB transaction need to be written to
124 allocated within one MOST frame, is calculated that fit into _one_ 512 byte
134 packets within one USB transaction. This renders
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | fsmc-nand.txt | 16 are valid. Zero means one clockcycle, 15 means 16 clock
25 one cycle, 255 means 256 cycles.
30 command is asserted. Zero means one cycle, 255 means 256
|
| /linux-4.4.14/ipc/ |
| D | ipc_sysctl.c | 100 static int one = 1; variable
132 .extra2 = &one,
159 .extra2 = &one,
|
| /linux-4.4.14/Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 9 For one device driver, which will run in different scenarios above
10 on different SoCs using the devicetree, we need one way to simplify
|
| /linux-4.4.14/Documentation/accounting/ |
| D | taskstats.txt | 36 one of the cpus in the cpumask, its per-pid statistics are sent to the
37 registered listener. Using cpumasks allows the data received by one listener
75 The taskstats payload is one of the following three kinds:
78 a pid/tgid consist of one attribute, of type TASKSTATS_CMD_ATTR_PID/TGID,
83 consist of one attribute, of type
167 To avoid losing statistics, userspace should do one or more of the following:
173 each listener. In the extreme case, there could be one listener for each cpu.
175 of cpus to which it listens, especially if they are listening to just one cpu.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | rcu.txt | 5 operations into two parts, one that prevents anyone from seeing the data
6 item being destroyed, and one that actually carries out the destruction.
47 o If I am running on a uniprocessor kernel, which can only do one
58 primitives. Or grab one of the cscope databases from:
76 Of these, one was allowed to lapse by the assignee, and the
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | msi-pic.txt | 4 - compatible : compatible list, may contain one or two entries
13 - reg : It may contain one or two regions. The first region should contain
19 - interrupts : each one of the interrupts here is one entry per 32 MSIs,
99 In the PAMU, each PCI controller is given only one primary window. The
|
| /linux-4.4.14/drivers/media/radio/ |
| D | radio-rtrack2.c | 59 static void one(struct radio_isa_card *isa) in one() function
81 one(isa); in rtrack2_s_frequency()
|
| /linux-4.4.14/tools/perf/tests/ |
| D | sample-parsing.c | 64 COMP(read.one.value); in samples_same()
74 COMP(read.one.id); in samples_same()
226 sample.read.one.value = 0x08789faeb786aa87ULL; in do_test()
227 sample.read.one.id = 99; in do_test()
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | mvebu-mbus.txt | 6 - compatible: Should be set to one of the following:
52 the first one controls the devices decoding window,
53 the second one controls the SDRAM decoding window and
82 The MBus children address space is comprised of two cells: the first one for
83 the window ID and the second one for the offset within the window.
200 with one another or with the system memory ranges.
202 Each entry in the property refers to exactly one window. If the operating system
|
| /linux-4.4.14/drivers/usb/gadget/legacy/ |
| D | Kconfig | 48 this gadget connects to another OTG device, with this one using
50 one serve as the USB host instead (in the "B-Host" role).
81 without one.
92 This driver implements Ethernet style communication, in one of
170 of several ethernet frames into one USB transfer and different
194 The Function Filesystem (FunctionFS) lets one create USB
196 lets one create USB gadgets in user space. This allows creation
292 The MIDI Gadget acts as a USB Audio device, with one MIDI
293 input and one MIDI output. These MIDI jacks appear as
329 This driver provides two functions in one configuration:
[all …]
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.syncppp | 5 You need one thing beside the isdn4linux package:
26 one interface with the name 'ippp0' to saturate the
38 I've implemented one additional option for the ipppd:
|
| D | README.icn | 21 the lowlevel-module (see README). If using more than one card,
26 Two types of cards exist, one with dip-switches and one with
85 If you like to use more than one card, you can use the program
114 version like to the kernel-builtin one.
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/xilinx/ |
| D | xlnx,video.txt | 7 Xilinx video IP pipeline processes video streams through one or more Xilinx
17 - dmas, dma-names: List of one DMA specifier and identifier string (as defined
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/omap/ |
| D | prcm.txt | 5 each describing one module and the clock hierarchy under it. see [1] for
11 - compatible: Must be one of:
|