Home
last modified time | relevance | path

Searched refs:two (Results 1 – 200 of 1256) sorted by relevance

1234567

/linux-4.4.14/arch/arm/probes/kprobes/
Dtest-arm.c1179 #define COPROCESSOR_INSTRUCTIONS_ST_LD(two,cc) \ in kprobe_arm_test_cases() argument
1180 TEST_COPROCESSOR("stc"two" 0, cr0, [r13, #4]") \ in kprobe_arm_test_cases()
1181 TEST_COPROCESSOR("stc"two" 0, cr0, [r13, #-4]") \ in kprobe_arm_test_cases()
1182 TEST_COPROCESSOR("stc"two" 0, cr0, [r13, #4]!") \ in kprobe_arm_test_cases()
1183 TEST_COPROCESSOR("stc"two" 0, cr0, [r13, #-4]!") \ in kprobe_arm_test_cases()
1184 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], #4") \ in kprobe_arm_test_cases()
1185 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], #-4") \ in kprobe_arm_test_cases()
1186 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], {1}") \ in kprobe_arm_test_cases()
1187 TEST_COPROCESSOR("stc"two"l 0, cr0, [r13, #4]") \ in kprobe_arm_test_cases()
1188 TEST_COPROCESSOR("stc"two"l 0, cr0, [r13, #-4]") \ in kprobe_arm_test_cases()
[all …]
/linux-4.4.14/arch/sh/boards/mach-r2d/
DKconfig10 R2D-PLUS is the smaller of the two R2D board versions, equipped
18 R2D-1 is the larger of the two R2D board versions, equipped
19 with two PCI slots.
/linux-4.4.14/drivers/isdn/icn/
DKconfig5 This enables support for two kinds of ISDN-cards made by a German
7 line with two B-channels, 4B supports two ISDN lines. For running
/linux-4.4.14/Documentation/video4linux/
Dcpia2_overview.txt4 division of ST Microelectronics). There are two versions. The first is the
7 which can handle up to 30 fps VGA. Both coprocessors can be attached to two
11 The two chipsets operate almost identically. The core is an 8051 processor,
12 running two different versions of firmware. The 672 runs the VP4 video
14 mappings for the two chips. In these cases, the symbols defined in the
Dcafe_ccic32 - n_dma_bufs: The controller can cycle through either two or three DMA
34 systems, however, it will work well with only two.
/linux-4.4.14/arch/cris/arch-v10/
DKconfig104 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,
167 For products with only one or two controllable LEDs,
176 For products with only one or two controllable LEDs,
185 For products with only one or two controllable LEDs,
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/fsl/
Difc.txt9 - #address-cells : Should be either two or three. The first cell is the
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
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dfsl-quadspi.txt14 - fsl,qspi-has-second-chip: The controller has two buses, bus A and bus B.
15 Each bus can be connected with two NOR flashes.
18 But if there are two NOR flashes connected to the
Dpartition.txt19 mtd device. There are two valid values for both:
22 <2>: for partitions that require two 32-bit cells to represent their
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Dusb.txt5 - reg : the first two cells should contain usb registers location and
6 length, the next two two cells should contain PRAM location and
/linux-4.4.14/Documentation/devicetree/bindings/timer/
Dsamsung,exynos4210-mct.txt3 The Samsung's Multi Core Timer (MCT) module includes two main blocks, the
39 Example 1: In this example, the IP contains two local timers, using separate
40 interrupts, so two local timer interrupts have been specified,
50 Example 2: In this example, the timer interrupts are connected to two separate
Dstericsson-u300-apptimer.txt9 adopted for EPOC/Symbian with two specific IRQs for these tasks,
Dnvidia,tegra20-timer.txt4 running counter. The first two channels may also trigger a watchdog reset.
Dmediatek,mtk-timer.txt13 - clocks: Clocks driving the timer hardware. This list should include two
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-mcp23s08.txt17 - #gpio-cells : Should be two.
42 - #interrupt-cells : Should be two.
52 with two interrupt outputs (these are the devices ending with 17 and
53 those that have 16 IOs) have two IO banks: IO 0-7 form bank 1 and
54 IO 8-15 are bank 2. These chips have two different interrupt outputs:
Dgpio-mvebu.txt14 for which two entries are expected: one for the general registers,
25 interrupt source. Should be two.
38 - #gpio-cells: Should be two. The first cell is the pin number. The
Dgpio-clps711x.txt6 There should be two registers, first is DATA register, the second
9 - #gpio-cells: Should be two. The first cell is the pin number and
Dfsl-imx-gpio.txt7 one number. If two numbers, the first one is the interrupt shared
10 - #gpio-cells : Should be two. The first cell is the pin number and
Dgpio-davinci.txt11 - #gpio-cells : Should be two.
26 two cells specifier as described in Documentation/devicetree/bindings/
Dsodaville.txt13 The interrupt specifier consists of two cells encoded as follows:
22 /* two cells for GPIO and interrupt */
Dgpio-xlp.txt17 - #gpio-cells: Should be two. The first cell is the pin number and the second
21 - interrupt-cells: Should be two. The first cell is the GPIO Number. The
Dgpio-vf610.txt3 The Freescale PORT/GPIO modules are two adjacent modules providing GPIO
13 - #gpio-cells : Should be two. The first cell is the pin number and
Dpl061-gpio.txt5 - #gpio-cells : Should be two. The first cell is the pin number and the
Dcirrus,clps711x-mctrl-gpio.txt6 - #gpio-cells: Should be two. The first cell is the pin number and
Dgpio-zevio.txt6 - #gpio-cells: Should be two. The first cell is the pin number and the
D8xxx_gpio.txt25 - #gpio-cells: Should be two. The first cell is the pin number
36 - #interrupt-cells: Should be two. Defines the number of integer
Dgpio-74x164.txt7 - #gpio-cells : Should be two. The first cell is the pin number and
Dzx296702-gpio.txt5 - #gpio-cells : Should be two. The first cell is the pin number and the
Dgpio-xgene.txt9 - #gpio-cells: Should be two.
Dgpio-palmas.txt9 - #gpio-cells : Should be two.
Dgpio_atmel.txt7 - #gpio-cells: Should be two. The first cell is the pin number and
Dgpio-mpc8xxx.txt9 - #gpio-cells : Should be two. The first cell is the pin number and
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dcs35l32.txt20 of the two: Class G or adaptive LED voltage.
28 Determines the data packed in a two-CS35L32 configuration.
34 - cirrus,sdout-share : SDOUT sharing. Determines whether one or two CS35L32
Dmvebu-audio.txt15 with "marvell,dove-audio", a list of two interrupts, the first for
18 - clocks: one or two phandles.
Dadi,axi-i2s.txt7 The controller expects two clocks, the clock used for the AXI interface and
12 the core. The core expects two dma channels, one for transmit and one for
Dalc5632.txt13 - #gpio-cells : Should be two. The first cell is the pin number and the
/linux-4.4.14/Documentation/devicetree/bindings/dma/xilinx/
Dxilinx_dma.txt2 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
11 two channels per device. This node specifies the properties of each
Dxilinx_vdma.txt2 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
12 two channels per device. This node specifies the properties of each
/linux-4.4.14/arch/x86/boot/compressed/
Daslr.c126 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/input/
Delantech.txt55 per packet, and provides additional features such as position of two fingers,
57 for 2 fingers the concatenation of two 6 bytes packets) and allows tracking
284 firmware 1.x seem to map one, two and three finger taps
331 tw = 1 when two finger touch
481 Note that the two pairs of coordinates are not exactly the coordinates of the
482 two fingers, but only the pair of the lower-left and upper-right coordinates.
484 defined by these two points.
540 T: 1 = enable two finger mode auto correct
611 The packet format is exactly the same for two finger touch, except the hardware
612 sends two 6 byte packets. The first packet contains data for the first finger,
[all …]
Dgamepad.txt78 fashion. For example, the "Nintendo Wii Nunchuk" provides two trigger buttons
80 analog stick and two trigger buttons on the right side.
109 If all 4 action-buttons are present, they can be aligned in two
129 reported as ABS_RX, ABS_RY. Zero, one or two sticks may be present.
Djoystick-parport.txt62 port), and combine the currents of two or more data bits together.
80 NES and SNES pads have two input bits, Clock and Latch, which drive the
249 For joysticks with two buttons you connect the second button to pin 7 on
284 For two button sticks you also connect the other button.
462 gamecon.map2 and gamecon.map3 as additional command line parameters for two
465 There are two options specific to PSX driver portion. gamecon.psx_delay sets
501 can use db9.dev2 and db9.dev3 as additional command line parameters for two
517 for two more interfaces.
/linux-4.4.14/Documentation/networking/
Dipvlan.txt31 IPvlan has two modes of operation - L2 and L3. For a given master device,
32 you can select one of these two modes and all slaves on that master will
53 These two devices are very similar in many regards and the specific use
81 (a) Create two network namespaces - ns0, ns1
85 (b) Create two ipvlan slaves on eth0 (master device)
DPLIP.txt13 This device interface allows a point-to-point connection between two
31 The PLIP cable is all that's needed to connect two Linux boxes, and it
34 Connecting two Linux boxes takes only a second's decision and a few
90 Alpha, as of this writing). Between two such polls, there are 10^6/HZ usecs.
92 quite possible for the trigger timeout to expire between two such polls, as
135 two DB-25 male connectors symmetrically connected as follows:
Dxfrm_sync.txt43 A XFRM_MSG_NEWAE will have at least two TLVs (as is
105 Programs installing SAs will need to specify the two thresholds, however,
110 the two sysctls/proc entries are:
117 in incremental packet count. The default is two packets.
156 Note the two flags are mutually exclusive.
Deql.txt17 Which is worse? A huge fee for a 56K leased line or two phone lines?
107 could argue that MTU should be roughly half the usual size for two
135 Enslaving devices by hand requires two utility programs: eql_enslave
246 All testing I have done was with two 28.8 V.FC modems, one connecting
354 I have done some testing of this software, with two goals in
359 of SLIP connections run between two Linux systems (1.1.84) using
384 the load across two or more Cirrus chips.
Darcnet-hardware.txt23 First of all, you can get ARCnet cards in at least two speeds: 2.5 Mbps
35 There are two "types" of ARCnet - STAR topology and BUS topology. This
89 ARCnet (the classic 2.5 Mbps version) can be connected by two different
98 Cards for coax cabling are shipped in two different variants: for BUS and
105 are two types of hubs - active and passive. Passive hubs are small boxes
117 hubs come in two variants - dumb and smart. The dumb variant just
135 more than eleven active hubs between any two computers. That of course
142 Remember that you cannot connect two passive hubs together. The power loss
169 But that is not all! The two types can be connected together. According to
205 of the TP cards has two RJ (phone-cord style) connectors. The cards are
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dlbc.txt5 - #address-cells : Should be either two or three. The first cell is the
8 - #size-cells : Either one or two, depending on how large each chipselect
Dpmc.txt45 upon resume. The first two cells are as described for fsl,mpc8578-pmc.
49 fsl,mpc8548-pmc: Sleep specifiers consist of one or two cells, the
Dmpc5200.txt11 to the device based solely on the compatible value. If two drivers
28 should have two items in the compatible list:
116 configuration of the watchdog is not touched. This is useful in two cases:
165 speed. This property should contain two cells. The
172 The mpc5200 pic binding splits hardware IRQ numbers into two levels. The
/linux-4.4.14/arch/sh/lib/
Dchecksum.S76 add #-2, r5 ! Alignment uses up two bytes.
78 bt/s 1f ! Jump if we had at least two bytes.
232 add #-2,r6 ! Alignment uses up two bytes.
233 cmp/pz r6 ! Jump if we had at least two bytes.
278 ! src and dest equally aligned, but to a two byte boundary.
279 ! Handle first two bytes as a special case
/linux-4.4.14/Documentation/devicetree/bindings/spi/
Dsh-msiof.txt17 If two register sets are present, the first is to be
29 - dmas : Must contain a list of two references to DMA
32 - dma-names : Must contain a list of two DMA names, "tx" and "rx".
Dspi-rspi.txt36 - dmas : Must contain a list of two references to DMA specifiers,
38 - dma-names : Must contain a list of two DMA names, "tx" and "rx".
Dspi-davinci.txt22 are 0 and 1. Manual says one of the two possible interrupt
32 where first three are internal CS and last two are GPIO CS.
Dbrcm,bcm2835-spi.txt3 The BCM2835 contains two forms of SPI master controller, one known simply as
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Drenesas,cpg-mssr.txt9 - The MSSR block provides two functions:
28 - For CPG core clocks, the two clock specifier cells must be "CPG_CORE"
31 - For module clocks, the two clock specifier cells must be "CPG_MOD" and
Dux500.txt16 - prcc-periph-clock: a subnode with two clock cells for
22 - prcc-kernel-clock: a subnode with two clock cells for
Dst,nomadik.txt23 PLL nodes: these nodes represent the two PLLs on the system,
27 Required properties for the two PLL nodes:
Dclock-bindings.txt42 - this node defines a device with two clock outputs, the first named
51 For example, if we have two clocks <&oscillator 1> and <&oscillator 3>:
88 This represents a device with two clock inputs, named "baud" and "register".
130 signal generated by the external oscillator, and provides two output signals
Dgpio-mux-clock.txt9 - clocks: list of two references to parent clocks.
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dmoxa,moxart-dma.txt26 described in the dma.txt file, using a two-cell specifier for each channel:
28 The two cells in order are:
Dsun6i-dma.txt31 described in the dma.txt file, using a two-cell specifier for each
33 The two cells in order are:
Dfsl-edma.txt4 registers. channels are split into two groups, called DMAMUX0 and DMAMUX1,
60 in the dma.txt file, using a two-cell specifier for each channel: the 1st
/linux-4.4.14/Documentation/locking/
Dlockstat.txt118 This excerpt shows the first two lock class statistics. Line 01 shows the
121 statistics. These statistics come in two parts; the actual stats separated by a
129 The first lock (05-18) is a read/write lock, and shows two lines above the
131 they have two: contentions and [<IP>] symbol. The second set of contention
165 double_rq_lock actually acquires a nested lock of two spinlocks.
/linux-4.4.14/Documentation/hwmon/
Dadm103126 (ADM1030) or two (ADM1031) external diodes.
35 two. Each fan channel has its own low speed limit.
Dlm9349 The LM93 hardware monitor has a two wire digital interface compatible with
50 SMBus 2.0. Using an 8-bit ADC, the LM93 measures the temperature of two remote
52 voltages. To set fan speed, the LM93 has two PWM outputs that are each
72 The LM93 can monitor two #PROCHOT signals. The results are found in the
82 The monitoring intervals for the two #PROCHOT signals is also configurable.
91 It is possible to configure the LM93 to logically short the two #PROCHOT
110 The LM93 can monitor two #VRD_HOT signals. The results are found in the
132 The LM93 has a fixed or override mode for the two PWM outputs (although, there
201 however, there are only two tables of offsets: one each for temp[12] and
206 oscillation between two steps in the offsets table. These values are found in
[all …]
Dlm8328 Using the adm1021 driver for a LM83 should work, but only two temperatures
59 won't have to handle more than two temperatures. Thus, ADM1021 clones
69 CPU. The two other sensors must be used to measure the temperature of
70 two other points of the motherboard. We suspect these points to be the
Dltc297868 LTC2980 is a 16-channel Power System Manager, consisting of two LTC2977
69 in a single die. The chip is instantiated and reported as two separate chips
70 on two different I2C bus addresses.
74 LTM2987 is a 16-channel Power System Manager with two LTC2977 plus
76 as two separate chips on two different I2C bus addresses.
Dadm102515 * Only two possible addresses (0x2c - 0x2d).
31 voltage by measuring its own VCC. One input (two pins) is dedicated to a
35 One specificity of this chip is that the pin 11 can be hardwired in two
Dg760a18 The fan speed is programmed by setting the period via 'pwm1' of two
29 The 'alarms' file provides access to the two alarm bits provided by
Dw83l786ng27 The driver implements two temperature sensors, two fan rotation speed
Dadt747542 temperatures and two (2) or more voltages. It has four (4) 16-bit counters
87 configured either for two's complement format or "Offset 64" format,
96 The driver exposes two trip points per PWM channel.
102 speed when the temperature is between the two temperature boundaries.
Dpc8736038 PWM control circuitry for two fans. The PC87363 chip is similar, and the
43 but also monitoring eleven voltage inputs and two (PC87365) or up to four
116 The first two temperature channels are external. The third one (PC87366
128 the same time. Although it should be possible to mix the two sensor types,
139 external. Some of them (in7:Vsb, in8:Vdd and in10:AVdd) are divided by two
155 The chipsets can handle two sets of VID inputs (on dual-CPU systems), but
Dsht2124 only 3 x 3 mm footprint and 1.1 mm height. The difference between the two
46 e.g. maximum two measurements per second at the given resolution.
Dlm9523422 that can very accurately monitor the temperature of two (LM95233)
35 affects the hysteresis on all channels. The first two external sensors also
Dasc762126 Our conversion process produces a result that is reported as two bytes.
28 PWM output. These two bytes are "read-locked" to guarantee that once a
60 PECI Extended configuration allows for having more than two domains per
79 The aSC7621 has a two wire digital interface compatible with SMBus 2.0.
80 Using a 10-bit ADC, the aSC7621 measures the temperature of two remote diode
296 1 Processor contains two domains (0,1)
Dtmp40134 TMP431, TMP432 and TMP435 chips. These chips implement one or two remote
56 TMP432 is compatible with TMP401 and TMP431. It supports two external
Dmax166820 set; only two remote temperature inputs vs the four avaible on the other
21 two ICs.
Demc140336 contain up to four temperature sensors. EMC14x2 support two sensors
38 two external), and EMC14x4 support four sensors (one internal, three
Dadt746219 two. See the chip documentation for more details about the exact set of
64 the temperature is between the two temperature boundaries. PWM values range
Dthmc5072 The driver was tested on Compaq AP550 with two ADM1022 chips (one works
73 in the temp3 mode), five temperature readings and two fans.
Dadm102171 ADM1021-clones implement two temperature sensors. One of them is internal,
96 within them, with two temperature sensors. Other Xeon processors of this
99 If you have such an old Xeon, and you get two valid temperatures when
Dadm102641 Temperatures are measured in degrees Celsius. There are two external
55 two pulse per revolution fan is 661 RPM.
80 used to control fan speed. Usually only one of these two outputs will be
Df71805f39 three different modes (one manual, two automatic).
41 The Fintek F71872F/FG Super I/O chip is almost the same, with two
62 The two LSB of the voltage limit registers are not used (always 0), so
158 relationship between temperature and fan speed with two additional points
Dlm8029 The LM80 implements one temperature sensor, two fan rotation speed sensors,
32 Temperatures are measured in degrees Celsius. There are two sets of limits
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
Ddivider.txt24 ti,index-power-of-two - valid divisor values are powers of two. E.g:
71 - ti,index-power-of-two : valid divisor programming must be a power of two,
Ddra7-atl.txt7 signals - can compensate the drift between the two ws signal.
10 internally within the SoC or external components) two sets of bindings is needed:
/linux-4.4.14/Documentation/cgroups/
Dblkio-controller.txt11 Currently two IO control policies are implemented. First one is proportional
22 You can do a very simple testing of running two dd threads in two different
38 - Create two cgroups
45 - Create two same size files (say 512MB each) on same disk (file1, file2) and
46 launch two dd threads in different cgroup to read those files.
186 two fields specify the major and minor number of the device and
192 two fields specify the major and minor number of the device and
199 or async. First two fields specify the major and minor number of the
206 or async. First two fields specify the major and minor number of the
219 the type of operation - read or write, sync or async. First two fields
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Das3711.txt2 supplies, a battery charger and an RTC. So far only bindings for the two stepup
12 To use the SU1 converter as a backlight source the following two properties must
17 To use the SU2 converter as a backlight source the following two properties must
Dlp3943.txt7 LP3943 consists of two sub-devices, lp3943-gpio and lp3943-pwm.
/linux-4.4.14/drivers/mtd/onenand/
DKconfig58 Since the device is equipped with two DataRAMs, and two-plane NAND
59 Flash memory array, these two component enables simultaneous program
/linux-4.4.14/Documentation/w1/slaves/
Dw1_ds240614 not supported. In TSOC-6 form, the DS2406 provides two switch outputs and
18 The driver provides two sysfs files. state is readable; it gives the
Dw1_therm24 read sequence will initiate a temperature conversion then provide two
54 The DS28EA00 provides an additional two pins for implementing a sequence
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-kernel-boot_params4 Description: The /sys/kernel/boot_params directory contains two
21 of the list nodes. The list node subdirectory contains two
Dconfigfs-stp-policy39 Write two numbers: the first master and the last master number.
46 Write two numbers: the first channel and the last channel
Dsysfs-class-leds-gt683r7 of one LED will update the mode of its two sibling devices as
Dsysfs-dev7 stat(2). There are two directories, 'block' and 'char',
Dsysfs-kernel-uids9 are two users logged in, each with an equal number of
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-sh_mobile.txt23 - dmas : Must contain a list of two references to DMA
26 - dma-names : Must contain a list of two DMA names, "tx" and "rx".
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Drenesas,ipmmu-vmsa.txt13 support secure mode two interrupts must be specified, for non-secure and
22 - iommus: A reference to the IPMMU in two cells. The first cell is a phandle
/linux-4.4.14/Documentation/devicetree/bindings/cpufreq/
Darm_big_little_dt.txt38 clock-latency = <61036>; /* two CLK32 periods */
57 clock-latency = <61036>; /* two CLK32 periods */
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Datmel-usb.txt11 - clock-names: Should contains two strings
38 - clock-names: Should contains two strings
61 - clock-names: Should contains two strings
88 - clock-names: Should contains two strings
/linux-4.4.14/Documentation/thermal/
Dx86_pkg_temperature_thermal19 zone with maximum two user mode configurable trip points. Number of trip points
31 This contains two trip points:
/linux-4.4.14/Documentation/fmc/
Dfmc-write-eeprom.txt38 followed by data. The first byte is `w' for write, the next two bytes
39 represent the address, in little-endian byte order, and the next two
60 after two seconds. Please note, however, that if fmc-write-eeprom is
62 will be reprogrammed and thus will be unloaded after two seconds. The
Dmezzanine.txt44 Therefore, we have two tables of identifiers.
46 Matching of FRU information depends on two names, the manufacturer (or
53 Matching on FPGA cores depends on two numeric fields: the 64-bit vendor
113 For example, if you are using the trivial driver to load two different
114 gateware files to two different cards, you can use the following
/linux-4.4.14/Documentation/filesystems/
Dgfs2-uevents.txt18 The ADD uevent has two environment variables: SPECTATOR=[0|1]
27 uevent, along with the two environment variables for spectator and
33 The CHANGE uevent is used in two places. One is when reporting the
40 two environment variables, JID= which specifies the journal id which
Dqnx6.txt36 Each qnx6fs got two superblocks, each one having a 64bit serial number.
130 limited to 510 bytes. The first two starting bytes are used as length field
152 First the system area, that is split into two halves.
161 Bitmap blocks, Inode blocks and indirect addressing blocks for those two
/linux-4.4.14/Documentation/extcon/
Dporting-android-switch-class65 Example: a switch device driver w/ magic numbers for two cables.
84 does not need to get notified of its own events), there are two
107 exclusive, the two cables cannot be in ATTACHED state simulteneously.
120 The two files of switch class, name and state, are provided with
/linux-4.4.14/arch/arm/boot/dts/
Ddra7xx-clocks.dtsi221 ti,index-power-of-two;
737 ti,index-power-of-two;
941 ti,index-power-of-two;
950 ti,index-power-of-two;
959 ti,index-power-of-two;
968 ti,index-power-of-two;
977 ti,index-power-of-two;
986 ti,index-power-of-two;
995 ti,index-power-of-two;
1004 ti,index-power-of-two;
[all …]
/linux-4.4.14/Documentation/leds/
Dleds-lp3944.txt16 The LP3944 is a helper chip that can drive up to 8 leds, with two programmable
21 specified supplying two parameters:
/linux-4.4.14/Documentation/namespaces/
Dcompatibility-list.txt28 2. Intentionally, two equal user IDs in different user namespaces
34 The same is true for the IPC namespaces being shared - two users
/linux-4.4.14/Documentation/devicetree/bindings/display/exynos/
Dexynos_hdmi.txt19 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
Dexynos_mixer.txt16 b) sclk_hdmi: HDMI Special clock, one of the two possible inputs of
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dbrcm,unimac-mdio.txt15 Ethernet switch this MDIO block is integrated from, or must be two, if there
16 are two separate interrupts, first one must be "mdio done" and second must be
Dopencores-ethoc.txt5 - reg: two memory regions (address and length),
/linux-4.4.14/Documentation/timers/
Dhpet.txt15 HPET devices can support two interrupt routing modes. In one mode, the
19 mode where the first two comparators block interrupts from 8254 timers
/linux-4.4.14/Documentation/devicetree/bindings/phy/
Dphy-bindings.txt53 This node represents a controller that uses two PHYs, one for usb2 and one for
70 "1" to differentiate between the two PHYs.
/linux-4.4.14/Documentation/fb/
Dvt8623fb.txt18 * 4 bpp pseudocolor modes (with 18bit palette, two variants)
33 There are two 4 bpp modes. First mode (selected if nonstd == 0) is mode with
Darkfb.txt19 * 4 bpp pseudocolor modes (with 18bit palette, two variants)
36 There are two 4 bpp modes. First mode (selected if nonstd == 0) is mode with
Ds3fb.txt26 * 4 bpp pseudocolor modes (with 18bit palette, two variants)
45 There are two 4 bpp modes. First mode (selected if nonstd == 0) is mode with
/linux-4.4.14/arch/m32r/lib/
Dchecksum.S72 ; clear c-bit || Alignment uses up two bytes.
74 bgtz r1, 1f ; Jump if we had at least two bytes.
190 addi r1, #-2 ; Alignment uses up two bytes.
192 bgtz r1, 1f ; Jump if we had at least two bytes.
/linux-4.4.14/drivers/crypto/vmx/
Daesp8-ppc.pl1351 my ($two,$three,$four)=($outhead,$outperm,$outmask);
1440 vadduqm $two,$one,$one
1445 vadduqm $out2,$ivec,$two
1448 vadduqm $out3,$out1,$two
1451 vadduqm $out4,$out2,$two
1454 vadduqm $out5,$out3,$two
1457 vadduqm $out6,$out4,$two
1459 vadduqm $out7,$out5,$two
1461 vadduqm $ivec,$out6,$two # next counter value
1599 vadduqm $out2,$ivec,$two
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/remoteproc/
Dwkup_m3_rproc.txt21 - reg: Should contain the address ranges for the two internal
25 - reg-names: Contains the corresponding names for the two memory
/linux-4.4.14/Documentation/power/
Dapm-acpi.txt6 of the two technologies and puts power management in the hands of the
19 simply cannot mix and match the two. Only one power management
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dti,omap3isp.txt11 reg : the two registers sets (physical address and length) for the
21 #clock-cells : Must be 1 --- the ISP provides two external clocks,
/linux-4.4.14/tools/testing/selftests/rcutorture/doc/
DTREE_RCU-kconfig.txt11 CONFIG_NO_HZ_IDLE -- Do those not otherwise specified. (Groups of two.)
12 CONFIG_NO_HZ_FULL -- Do two, one with CONFIG_NO_HZ_FULL_SYSIDLE.
/linux-4.4.14/Documentation/devicetree/bindings/crypto/
Datmel-crypto.txt11 - dmas: List of two DMA specifiers as described in
33 - dmas: List of two DMA specifiers as described in
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Datmel,at91-pio4-pinctrl.txt11 - #interrupt-cells: should be two.
13 - #gpio-cells: should be two.
Dpinctrl-vt8500.txt11 - #interrupt-cells: Should be two.
13 - #gpio-cells : Should be two. The first cell is the pin number and the
Dqcom,apq8064-pinctrl.txt8 - #interrupt-cells: Should be two.
10 - #gpio-cells : Should be two.
Dqcom,msm8660-pinctrl.txt8 - #interrupt-cells: Should be two.
10 - #gpio-cells : Should be two.
Dmarvell,orion-pinctrl.txt10 - reg: two register areas, the first one describing the first two
Dqcom,ipq8064-pinctrl.txt8 - #interrupt-cells: Should be two.
10 - #gpio-cells : Should be two.
Dfsl,imx53-pinctrl.txt8 - fsl,pins: two integers array, represents a group of pins mux and config
Dfsl,imx51-pinctrl.txt8 - fsl,pins: two integers array, represents a group of pins mux and config
Dfsl,imx35-pinctrl.txt8 - fsl,pins: two integers array, represents a group of pins mux and config
Dfsl,imx6q-pinctrl.txt8 - fsl,pins: two integers array, represents a group of pins mux and config
Dfsl,imx6dl-pinctrl.txt8 - fsl,pins: two integers array, represents a group of pins mux and config
/linux-4.4.14/Documentation/
Dcircular-buffers.txt10 buffering. There are two sets of such features:
39 fixed, finite size into which there are two indices:
61 the buffer and be broken into two segments.
149 There are two sides to this: the producer that fills the buffer, and the
152 two sides can operate simultaneously.
189 producer must produce two elements before it could possibly corrupt the
Dclk.txt16 The interface itself is divided into two halves, each shielded from the
33 Tying the two halves of this interface together is struct clk_hw, which
35 allows for easy navigation between the two discrete halves of the common
242 The common clock framework uses two global locks, the prepare lock and the
254 This effectively divides operations in two groups from a locking perspective.
259 of the two groups needs to be protected by the drivers. An example of such a
Dcpu-load.txt28 switched between various states multiple times between two timer
38 time line between two timer interrupts
/linux-4.4.14/Documentation/w1/
Dw1.generic4 signal wire (plus ground, so two wires).
32 in nature, which can contain several (two or one) low-level operations.
35 and two byte address. At this step bus is reset and appropriate device
65 The driver for w1 bus master must provide at minimum two functions.
/linux-4.4.14/Documentation/devicetree/bindings/c6x/
Ddscr.txt6 to SoC with no two being alike.
50 offset and key values of two "kick" registers used to write protect other
56 MAC addresses are contained in two registers. Each element of a MAC address
57 is contained in a single byte. This property has two tuples. Each tuple has
/linux-4.4.14/Documentation/ia64/
Defirtc.txt42 The driver exposes two interfaces, one via the device file and a set of
49 "public" API of the two drivers. The specifics of the legacy RTC are still
80 Those two ioctl()s can be exercised with the hwclock command:
119 However writing such a program should be hard by simply using those two
/linux-4.4.14/Documentation/sound/oss/
Dbtaudio38 The chip knows two different modes. btaudio registers two dsp
68 downsampling by powers of two, so you can ask for more usual sample rates
/linux-4.4.14/tools/perf/Documentation/
Dperf-bench.txt32 (executing 1000000 pipe operations between two tasks)
120 (executing 1000000 pipe operations between two tasks)
127 (executing 1000 pipe operations between two tasks)
/linux-4.4.14/Documentation/x86/
Dearly-microcode.txt24 There are two legacy user space interfaces to load microcode, either through
28 In addition to these two legacy methods, the early loading method described
/linux-4.4.14/drivers/net/plip/
DKconfig10 reasonably fast mini network consisting of two (or, rarely, more)
17 The PLIP driver has two modes, mode 0 and mode 1. The parallel
/linux-4.4.14/arch/x86/include/asm/
Dspinlock.h67 static inline int __tickets_equal(__ticket_t one, __ticket_t two) in __tickets_equal() argument
69 return !((one ^ two) & ~TICKET_SLOWPATH_FLAG); in __tickets_equal()
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Dnxp,sc16is7xx.txt20 - #gpio-cells: Should be two. The first cell is the GPIO number and
56 - #gpio-cells: Should be two. The first cell is the GPIO number and
/linux-4.4.14/Documentation/devicetree/bindings/display/imx/
Dldb.txt6 The LVDS Display Bridge device tree node contains up to two lvds-channel
7 nodes describing each of the two LVDS encoder channels of the bridge.
55 On i.MX5, the internal two-input-multiplexer is used. Due to hardware
/linux-4.4.14/Documentation/mn10300/
DABI.txt20 The first two arguments (assuming up to 32-bits per argument) to a function are
30 word. For example, two byte-sized arguments will always be passed in separate
64 in which the callee may store the first two arguments.
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dcdns,xtensa-mx.txt13 * two cells: second cell == 0: internal irq number
Dinterrupts.txt41 length and format of the interrupt specifier. The following two variants are
67 b) two cells
/linux-4.4.14/Documentation/devicetree/bindings/thermal/
Ddove-thermal.txt9 The reg properties should contain two ranges. The first is for the
/linux-4.4.14/arch/alpha/lib/
Dstrlen.S34 nop # helps dual issue last two insns
Dstrncpy.S66 0: stq_u $31, 0($16) # zero two words
/linux-4.4.14/arch/arm/mach-s3c24xx/
Dsleep.S59 @@ load UART to allow us to print the two characters for
/linux-4.4.14/Documentation/devicetree/bindings/w1/
Dw1-gpio.txt6 - gpios: one or two GPIO specs:
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/
Dsynopsys.txt5 two bit errors.
/linux-4.4.14/fs/overlayfs/
DKconfig4 An overlay filesystem combines two filesystems - an 'upper' filesystem
/linux-4.4.14/Documentation/usb/
Dgadget_multi.txt15 have two configurations -- one with RNDIS and another with CDC ECM[3].
33 This is also true for two configuration set-up with RNDIS
39 For the gadget two work under Windows two conditions have to be met:
/linux-4.4.14/Documentation/power/powercap/
Dpowercap.txt148 control type called intel-rapl which contains two power zones, intel-rapl:0 and
150 two subzones, intel-rapl:j:0 and intel-rapl:j:1 (j = 0, 1), representing the
166 The Intel RAPL technology allows two constraints, short term and long term,
167 with two different time windows to be applied to each power zone. Thus for
/linux-4.4.14/Documentation/phy/
Dsamsung-usb2.txt22 the probe function and provides two callbacks to the Generic PHY
23 Framework. This two callbacks are used to power on and power off the
102 These two callbacks are used to power on and power off the phy
/linux-4.4.14/Documentation/virtual/kvm/devices/
Darm-vgic.txt37 redistributor register mappings. There are two 64K pages for each
45 The attr field of kvm_device_attr encodes two values:
67 The attr field of kvm_device_attr encodes two values:
/linux-4.4.14/Documentation/devicetree/bindings/arm/apm/
Dscu.txt7 - compatible : should contain two values. First value must be:
/linux-4.4.14/Documentation/devicetree/bindings/arm/samsung/
Dsysreg.txt4 - compatible : should contain two values. First value must be one from following list:
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
Dsa1100-rtc.txt7 - interrupts: Should be two. The first interrupt number is the rtc alarm
Drtc-mxc.txt10 - clocks: should contain two entries:
/linux-4.4.14/Documentation/i2c/busses/
Di2c-amd75623 Note that for the 8111, there are two SMBus adapters. The SMBus 1.0 adapter
/linux-4.4.14/Documentation/video4linux/cx2341x/
DREADME.vbi21 two different magic numbers were introduced:
23 'itv0': After this magic number two unsigned longs follow. Bits 0-17 of the first
/linux-4.4.14/Documentation/xtensa/
Dmmu.txt27 VA = virtual address (two upper nibbles of it);
28 PA = physical address (two upper nibbles of it);
/linux-4.4.14/Documentation/isdn/
DREADME.syncppp35 all devices at once. If you want to use two PPP connections
36 at the same time, you have to connect the ipppd to two
/linux-4.4.14/Documentation/devicetree/bindings/display/bridge/
Dadi,adv7511.txt24 pixel), "2x" (two clock cycles per pixel), "ddr" (one clock cycle per pixel,
48 The ADV7511 has two video ports. Their connections are modelled using the OF
Dadi,adv7123.txt17 The ADV7123 has two video ports. Their connections are modeled using the OF
Dthine,thc63lvdm83d.txt17 The THC63LVDM83D has two video ports. Their connections are modeled using the
/linux-4.4.14/Documentation/sound/alsa/
DCMIPCI.txt10 CM8x38 chip can use ADC as the second DAC so that two different stereo
11 channels can be used for front/rear playbacks. Since there are two
19 There are slight differences between the two DACs:
23 - The second DAC supports only two channel stereo.
53 There are two more controls regarding to the rear output.
69 4) channels. While the dual DAC supports two different rates or
DBt87x.txt46 The chip knows two different modes (digital/analog). snd-bt87x
47 registers two PCM devices, one for each mode. They cannot be used at
/linux-4.4.14/drivers/gpu/drm/armada/
DKconfig11 devices. There are two controllers on the device, each controller
/linux-4.4.14/Documentation/devicetree/bindings/media/i2c/
Dmt9m111.txt4 array size of 1280H x 1024V. It is programmable through a simple two-wire serial
Dmt9p031.txt5 two-wire serial interface.
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dfan53555.txt8 - fcs,suspend-voltage-selector: declare which of the two available
/linux-4.4.14/Documentation/cpu-freq/
Dcpufreq-nforce2.txt7 The module has two options:
/linux-4.4.14/Documentation/devicetree/bindings/rng/
Domap_rng.txt9 Note that these two versions are incompatible.
/linux-4.4.14/drivers/spmi/
DKconfig7 SPMI (System Power Management Interface) is a two-wire
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dmoxa,moxart-mmc.txt16 - dmas : Should contain two DMA channels, line request number must be 5 for
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-driver-w1_ds28e044 Description: read/write the contents of the two PIO's of the DS28E04-100
/linux-4.4.14/drivers/staging/sm750fb/
DTODO6 - check on hardware effects of removal of USE_HW_I2C and USE_DVICHIP (these two
/linux-4.4.14/Documentation/RCU/
Drcu.txt5 operations into two parts, one that prevents anyone from seeing the data
7 A "grace period" must elapse between the two parts, and this grace period
19 The advantage of RCU's two-part approach is that RCU readers need
/linux-4.4.14/Documentation/devicetree/bindings/mips/cavium/
Dciu2.txt20 /* Interrupts are specified by two parts:
Dciu.txt20 /* Interrupts are specified by two parts:
/linux-4.4.14/arch/m68k/ifpsp060/
Diskeleton.S186 | region. Note: the routine must lock two pages if the operand
187 | spans two pages.
254 | Note: the routine must unlock two pages if the operand spans
255 | two pages.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dpicoxcell.txt17 Note: two timers are required - one for the scheduler clock and one for the
/linux-4.4.14/Documentation/powerpc/
Dcpu_features.txt47 The END_FTR_SECTION macro has two simpler variations: END_FTR_SECTION_IFSET
49 cur_cpu_spec[0]->cpu_features) or is cleared, respectively. These two macros
/linux-4.4.14/Documentation/infiniband/
Duser_mad.txt6 "issm" device attached. For example, a two-port HCA will have two
7 umad devices and two issm devices, while a switch will have one
/linux-4.4.14/drivers/clk/
DKconfig59 multi-function devices have two fixed-rate oscillators,
110 The chip contains two PLLs with spread-spectrum clocking support and
124 clock. These multi-function devices have two (S2MPS14) or three
/linux-4.4.14/Documentation/kbuild/
Dmodules.txt204 The check for KERNELRELEASE is used to separate the two parts
205 of the makefile. In the example, kbuild will only see the two
207 two assignments. This is due to two passes made on the file:
217 to split up the makefile from example 1 into two files:
291 file. For example, if you wanted to build two modules, foo.ko
313 NOTE: There are two notable exceptions to this rule: larger
453 Module.symvers serves two purposes:
480 If you have two modules, foo.ko and bar.ko, where
/linux-4.4.14/arch/x86/lib/
Dchecksum_32.S72 subl $2, %ecx # Alignment uses up two bytes.
73 jae 1f # Jump if we had at least two bytes.
296 subl $2, %ecx # Alignment uses up two bytes.
297 jae 1f # Jump if we had at least two bytes.
/linux-4.4.14/Documentation/security/
Dkeys-request-key.txt56 The two async in-kernel calls may return keys that are still in the process of
57 being constructed. The two non-async ones will wait for construction to
85 two things:
126 /sbin/request-key at the appropriate places because (a) execve will discard two
/linux-4.4.14/Documentation/devicetree/bindings/input/
De3x0-button.txt5 This module provides a simple power button event via two interrupts.

1234567