/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-class-backlight-driver-adp8870 | 12 on this <backlight>. Values are between 0 and 127. This file 26 on this <backlight>. Values are between 0 and 127, typically 38 is enabled). Returns integer between 0 (dark) and 47 integer between 1..5 (1 = daylight, 2 = bright, ..., 5 = dark). 48 Writing a value between 1..5 forces the backlight controller
|
D | sysfs-bus-iio-adc-hi8435 | 22 The low voltage threshold range is between 2..21V. 23 Hysteresis between low and high thresholds can not be lower then 2 and 39 The high voltage threshold range is between 3..22V. 40 Hysteresis between low and high thresholds can not be lower then 2 and
|
D | sysfs-bus-usb-devices-usbsevseg | 25 hex: each character is between 0-15 26 ascii: each character is between '0'-'9' and 'A'-'F'.
|
D | sysfs-bus-usb-lvstest | 17 Validation device is connected. Timeout value must be between 0 25 Validation device is connected. Timeout value must be between 0
|
D | sysfs-class-lcd | 15 Current contrast of this LCD device. Value is between 0 and
|
D | sysfs-class-mei | 29 Also number of registers varies between 1 and 6
|
D | sysfs-class-extcon | 70 "x" (integer between 0 and 31) of an extcon device. 77 state of cable "x" (integer between 0 and 31) of an extcon
|
D | sysfs-devices | 8 and between different kernel versions, the layout of the
|
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/ |
D | ti,bq24735.txt | 14 must be between 128mA and 8.128A with a 64mA step resolution. The POR value 18 must be between 1.024V and 19.2V with a 16mV step resolution. The POR value 22 value must be between 128mA and 8.064A with a 128mA step resolution. The
|
D | msm-poweroff.txt | 5 between poweroff and restart is determined by unique power manager IC
|
/linux-4.4.14/Documentation/devicetree/bindings/ |
D | graph.txt | 7 control flow to devices, but there can be more complex connections between 10 There already is a simple directed graph between devices tree nodes using 23 Here the ports describe data interfaces, and the links between them are 87 Links between endpoints 94 'remote-endpoint' phandles pointing at each other form a link between the
|
D | ipmi.txt | 12 - reg-spacing - The number of bytes between register starts. Defaults to 1
|
/linux-4.4.14/drivers/mailbox/ |
D | Kconfig | 4 Mailbox is a framework to control hardware communication between 24 send short messages between Highbank's A9 cores and the EnergyCore 52 between the OS and a platform such as the BMC. This medium 63 to send message between processors. Say Y here if you want to use the
|
/linux-4.4.14/Documentation/devicetree/bindings/mips/cavium/ |
D | ciu2.txt | 13 the CIU and may have a value between 0 and 63. The second cell is 14 the bit within the bank and may also have a value between 0 and 63.
|
D | dma-engine.txt | 3 The Octeon DMA Engine transfers between the Boot Bus and main memory.
|
D | ciu.txt | 14 within the bank and may have a value between 0 and 63.
|
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ |
D | ti-aemif.txt | 96 Time between the end of one asynchronous memory 99 between a read followed by read or a write 103 Time between the beginning of a memory cycle 108 Time between the activation and deactivation of 113 Time between the deactivation of the read 120 Time between the beginning of a memory cycle 125 Time between the activation and deactivation of 130 Time between the deactivation of the write
|
D | mvebu-devbus.txt | 57 - devbus,acc-next-ps: Defines the time delay between the cycle that 62 - devbus,rd-setup-ps: Defines the time delay between DEV_CSn assertion to 71 - devbus,rd-hold-ps: Defines the time between the last data sample to the 96 inactive (high) between data beats of a burst write.
|
D | ath79-ddr-controller.txt | 4 to flush the FIFO between various devices and the DDR. This is mainly used
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/ |
D | hsta.txt | 6 between the plb4 and plb6 system buses to provide high speed data 7 transfer between memory and system peripherals as well as support for
|
/linux-4.4.14/net/nfc/nci/ |
D | Kconfig | 6 NCI (NFC Controller Interface) is a communication protocol between 18 NCI (NFC Controller Interface) is a communication protocol between
|
/linux-4.4.14/drivers/android/ |
D | Kconfig | 15 Binder is used in Android for both communication between processes, 20 between said processes.
|
/linux-4.4.14/arch/mips/kernel/ |
D | entry.S | 49 # between sampling and return 87 # signals dont change between 143 # signals dont change between
|
/linux-4.4.14/Documentation/devicetree/bindings/sound/ |
D | da7219.txt | 56 - dlg,a-d-btn-thr : Impedance threshold between buttons A and D 58 - dlg,d-b-btn-thr : Impedance threshold between buttons D and B 60 - dlg,b-c-btn-thr : Impedance threshold between buttons B and C 62 - dlg,c-mic-btn-thr : Impedance threshold between button C and Mic
|
D | simple-card.txt | 14 - simple-audio-card,routing : A list of the connections between audio components. 18 - simple-audio-card,mclk-fs : Multiplication factor between stream rate and codec 59 - mclk-fs : Multiplication factor between stream
|
D | atmel-at91sam9g20ek-wm8731-audio.txt | 6 - atmel,audio-routing: A list of the connections between audio components.
|
D | atmel-sam9x5-wm8731-audio.txt | 8 - atmel,audio-routing: A list of the connections between audio components.
|
D | samsung,odroidx2-max98090.txt | 9 - samsung,audio-routing : a list of the connections between audio
|
D | nvidia,tegra-audio-wm9712.txt | 12 - nvidia,audio-routing : A list of the connections between audio components.
|
D | rockchip-i2s.txt | 4 audio data transfer between devices in the system.
|
D | atmel-wm8904.txt | 6 - atmel,audio-routing: A list of the connections between audio components.
|
D | imx-audio-wm8962.txt | 13 - audio-routing : A list of the connections between audio components.
|
D | omap-twl4030.txt | 12 - ti,audio-routing: List of connections between audio components.
|
D | nvidia,tegra-audio-wm8753.txt | 12 - nvidia,audio-routing : A list of the connections between audio components.
|
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/ |
D | sti-mailbox.txt | 4 are passed between Application and Remote processors using shared memory. 37 - reg : Shared (between Application and Remote) memory address
|
D | omap-mailbox.txt | 4 The OMAP mailbox hardware facilitates communication between different processors 17 and tx interrupt source per h/w fifo. Communication between different processors 24 and interrupt lines between different instances. The interrupt lines can also be 56 used for the communication between the host processor and a remote processor.
|
/linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
D | cros-ec.txt | 23 clock rate. This property specifies the delay, in usecs, between the 27 between transactions is not long enough the EC may not be able to respond 29 specifies the delay, in usecs, introduced between transactions to account
|
/linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
D | ltc3589.txt | 21 0.3625 V to 0.75 V in 12.5 mV steps. The output voltage thus ranges between 25 regulator can output between 1.8 V and 3.3 V on LTC3589 and between 1.2 V
|
/linux-4.4.14/Documentation/devicetree/bindings/serial/ |
D | rs485.txt | 10 * a is the delay between rts signal and beginning of data sent in milliseconds. 12 * b is the delay between end of data sent and rts signal in milliseconds
|
/linux-4.4.14/Documentation/devicetree/bindings/net/ |
D | apm-xgene-enet.txt | 24 - phy-connection-type: Interface type between ethernet device and PHY device 41 Valid values are between 0 to 7, that maps to 45 Valid values are between 0 to 7, that maps to
|
/linux-4.4.14/Documentation/ |
D | cpu-load.txt | 28 switched between various states multiple times between two timer 38 time line between two timer interrupts
|
D | local_ops.txt | 43 not have a different behavior between SMP and UP, including asm-generic/local.h 61 different CPU between getting the per-cpu variable and doing the 113 between CPUs, explicit smp_wmb() and smp_rmb() memory barriers must be used 116 be a smp_wmb() between the buffer write and the counter increment and also a 117 smp_rmb() between the counter read and the buffer read.
|
D | sgi-ioc4.txt | 11 themselves) present in IOC4 are mixed-purpose between these several 23 the PCI resources that are shared between the IOC4 functions.
|
D | smsc_ece1099.txt | 35 interface. SMBus is a serial communication protocol between 50 between a Master device and a Companion device. The Master
|
D | highuid.txt | 4 when communicating between user and kernel space in an ioctl or data 71 communicate between user and kernel)
|
D | percpu-rw-semaphore.txt | 9 is bouncing between L1 caches of the cores, causing performance
|
D | xillybus.txt | 80 elementary data transport between an FPGA and the host, providing pipe-like 150 between write() calls, in particular when the process loses the CPU. 160 In summary, for synchronous pipes, data between the host and FPGA is 208 * channelnum: The pipe's identification number in communication between the 261 a data channel between the FPGA and the host. The distinction between channels 291 balances between bus bandwidth efficiency (preventing a lot of partially 305 to lay around in the DMA buffers between read() and write() anyhow.
|
/linux-4.4.14/fs/gfs2/ |
D | Kconfig | 11 that is shared between them (with FC, iSCSI, NBD, etc...). GFS reads 33 interface between GFS2 and the DLM, which is required to use GFS2
|
/linux-4.4.14/Documentation/i2c/busses/ |
D | i2c-ocores | 22 distance between registers and the input clock speed. 55 .regstep = 2, /* two bytes between registers */
|
/linux-4.4.14/Documentation/blockdev/drbd/ |
D | data-structure-v9.txt | 12 drbd_peer_device object sits at each intersection between a drbd_device and a 36 counted. The peer_device objects only serve to establish the links between
|
/linux-4.4.14/Documentation/devicetree/bindings/staging/iio/adc/ |
D | mxs-lradc.txt | 16 - fsl,ave-delay: delay between consecutive samples. Allowed value is 19 - fsl,settling: delay between plate switch to next sample. Allowed value is
|
/linux-4.4.14/Documentation/usb/ |
D | misc_usbsevseg.txt | 21 hex expects a value between 0-15 per character, 22 ascii expects a value between '0'-'9' and 'A'-'F'.
|
/linux-4.4.14/Documentation/hwmon/ |
D | lm77 | 24 register on the chip, which means that the relative difference between 35 read-only. Setting temp1_crit_hyst writes the difference between
|
D | gl518sm | 39 situation. Measurements are guaranteed between -10 degrees and +110 55 measures voltages between 0.000 and 5.865 volt, with a resolution of 0.023 56 volt. The other inputs measure voltages between 0.000 and 4.845 volt, with
|
D | lm78 | 25 There is almost no difference between the three supported chips. Functionally, 39 between -55 and +125 degrees, with a resolution of 1 degree. 52 inputs can measure voltages between 0 and 4.08 volts, with a resolution
|
D | adc128d818 | 24 Measurements are guaranteed between -55 and +125 degrees. The temperature 32 inputs can measure voltages between 0 and 2.55 volts, with a resolution
|
D | f71882fg | 94 to the border between the highest and one but highest temperature zones, and 107 between 0-100% of fan#_full_speed. It is assumed that if the BIOS programs 112 Switching between these modes requires re-initializing a whole bunch of 134 The fan speed is regulated to keep the temp the fan is mapped to between
|
D | emc1403 | 45 difference between the limit and its hysteresis is always the same for 56 are read-only. Setting temp1_crit_hyst writes the difference between
|
D | adt7462 | 63 The ADT7462 will scale the pwm between the lower and higher pwm speed when 64 the temperature is between the two temperature boundaries. PWM values range
|
D | adt7470 | 62 The ADT7470 will scale the pwm between the lower and higher pwm speed when 63 the temperature is between the two temperature boundaries. PWM values range
|
D | lm80 | 37 is unclear about this). Measurements are guaranteed between -55 and 52 inputs can measure voltages between 0 and 2.55 volts, with a resolution
|
D | tmp102 | 22 The TMP102 has a programmable update rate that can select between 8, 4, 1, and
|
D | hih6130 | 18 The difference between the two devices is that the HIH-6131 has a condensation
|
D | g762 | 50 integer value between 0 and 255. 0 stops the fan, 255 makes 55 the fan speed is programmed by setting a value between 0 and 255 via 'pwm1'
|
D | it87 | 184 voltage inputs can measure voltages between 0 and 4.08 volts, with a resolution 185 of 0.016 volt. IT8603E, IT8721F/IT8758E and IT8728F can measure between 0 and 186 3.06 volts, with a resolution of 0.012 volt. IT8732F can measure between 0 and 250 prevent fast switching between fan on and off. 254 between trip point N and trip point N+1 then the PWM output value is
|
/linux-4.4.14/Documentation/input/ |
D | multi-touch-protocol.txt | 46 The main difference between the stateless type A protocol and the stateful 100 raw data for all present contacts are sent between every synchronization 182 indicate the distance between the contact and the surface. 261 The distance, in surface units, between the contact and the surface. Zero 282 support is possible if the device can distinguish between the two axis, but 283 not (uniquely) any values in between. In such cases, the range of 297 the device cannot distinguish between the intended touch point and the 303 device cannot distinguish between the intended touch point and the tool 314 between different tool types, such as a finger or a pen. In such cases, the 356 the device can distinguish between a finger along the Y axis (0) and a [all …]
|
/linux-4.4.14/Documentation/devicetree/bindings/phy/ |
D | apm-xgene-phy.txt | 30 between 0 to 31 in unit of dB. Default is 3. 33 Range is between 0 to 199500 in unit of uV. 45 between 0 to 0x1f in unit of 18.2mV. Default is 0xf.
|
D | phy-bindings.txt | 30 In order to differentiate between these 2 PHYs, an additional specifier should be 70 "1" to differentiate between the two PHYs.
|
/linux-4.4.14/Documentation/devicetree/bindings/spi/ |
D | spi-fsl-dspi.txt | 20 - fsl,spi-cs-sck-delay: a delay in nanoseconds between activating chip 22 - fsl,spi-sck-cs-delay: a delay in nanoseconds between stopping the clock
|
/linux-4.4.14/Documentation/devicetree/bindings/media/xilinx/ |
D | video.txt | 9 tree using bindings documented in this directory. Connections between the IP 21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
|
D | xlnx,video.txt | 11 mappings between DMAs and the video IP cores.
|
/linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
D | ti-omap.txt | 6 This file documents differences between the core properties described 33 This file documents differences between the core properties described
|
D | sdhci-dove.txt | 3 This file documents differences between the core properties in mmc.txt
|
D | sdhci-spear.txt | 3 This file documents differences between the core properties in mmc.txt
|
D | brcm,bcm2835-sdhci.txt | 3 This file documents differences between the core properties described
|
D | orion-sdio.txt | 3 This file documents differences between the core properties in mmc.txt
|
D | sdhci-sirf.txt | 3 This file documents differences between the core properties in mmc.txt
|
D | brcm,kona-sdhci.txt | 3 This file documents differences between the core properties in mmc.txt
|
D | vt8500-sdmmc.txt | 3 This file documents differences between the core properties described
|
D | sdhci-atmel.txt | 3 This file documents the differences between the core properties in
|
D | brcm,sdhci-iproc.txt | 3 This file documents differences between the core properties described
|
D | pxa-mmc.txt | 13 This file documents differences between the core properties in mmc.txt
|
D | socfpga-dw-mshc.txt | 6 differences between the core Synopsys dw mshc controller properties described
|
D | img-dw-mshc.txt | 6 differences between the core Synopsys dw mshc controller properties described
|
D | mxs-mmc.txt | 6 This file documents differences between the core properties in mmc.txt
|
D | sdhci-fujitsu.txt | 3 This file documents differences between the core properties in mmc.txt
|
D | mmc-spi-slot.txt | 3 This file documents differences between the core properties described
|
D | mmc-pwrseq-simple.txt | 4 common properties between various SOC designs. It thus enables us to use the
|
D | samsung-sdhci.txt | 4 MMC, SD and eMMC storage mediums. This file documents differences between the
|
D | ti-omap-hsmmc.txt | 6 This file documents differences between the core properties described 85 dat1. The MMC driver will then toggle between idle and default state during
|
D | renesas,mmcif.txt | 3 This file documents differences between the core properties in mmc.txt
|
D | nvidia,tegra20-sdhci.txt | 6 This file documents differences between the core properties described
|
D | mtk-sd.txt | 6 This file documents differences between the core properties in mmc.txt
|
/linux-4.4.14/Documentation/ja_JP/ |
D | SubmitChecklist | 5 If you find any difference between this document and the original file 106 "warning: comparison between signed and unsigned" のようなメッセージは、
|
/linux-4.4.14/Documentation/scsi/ |
D | ufs.txt | 84 connection between UFS host and UFS device. UIC consists of 87 * UIC_SAP: To transport UPIU between UFS host and UFS device. 95 UFSHCD is a low level device driver which acts as an interface between 103 and prepares the controller to transfer commands/response between
|
D | dtc3x80.txt | 17 internal DMA, between SCSI bus and an on-chip 128-byte buffer. Double 19 between the on-chip buffer and CPU/RAM via memory moves.
|
D | scsi-parameters.txt | 58 Should be between 1 and 2^32-1. 62 Should be between 1 and 16384.
|
D | sym53c500_cs.txt | 5 (1) extensive kernel changes between 2.4 and 2.6.
|
/linux-4.4.14/Documentation/misc-devices/ |
D | lis3lv02d | 37 By default output values are scaled between -32768 .. 32767. In joystick raw 46 between normal mode and test mode. Chip specifications tell the acceptance 50 measured difference between modes. Axes are not remapped in selftest mode. 69 For better compatibility between the various laptops. The values reported by
|
D | ics932s401 | 21 percent the clock signal is being spread, which should be between 0 and -0.5%.
|
/linux-4.4.14/Documentation/arm/Samsung/ |
D | Bootloader-interface.txt | 1 Interface between kernel and boot loaders on Exynos boards 7 The document tries to describe currently used interface between Linux kernel
|
D | GPIO.txt | 26 GPIO numbering is synchronised between the Samsung and gpiolib system.
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | imx6q-tx6q-1110.dts | 31 * a poor man's way to create a 1:1 relationship between 53 * a poor man's way to create a 1:1 relationship between
|
D | imx6dl-tx6u-811x.dts | 31 * a poor man's way to create a 1:1 relationship between 53 * a poor man's way to create a 1:1 relationship between
|
D | kirkwood-db.dtsi | 11 * This file contains the definitions that are common between the 6281
|
D | omap4-panda-es.dts | 18 /* Audio routing is differnet between PandaBoard4430 and PandaBoardES */
|
D | kirkwood-openrd.dtsi | 10 * This file contains the definitions that are common between the three
|
D | imx6dl-tx6dl-comtft.dts | 29 * a poor man's way to create a 1:1 relationship between
|
/linux-4.4.14/Documentation/devicetree/bindings/bus/ |
D | ti-gpmc.txt | 64 - gpmc,bus-turnaround-ns: Turn-around time between successive accesses 65 - gpmc,cycle2cycle-delay-ns: Delay between chip-select pulses 74 - gpmc,cycle2cycle-diffcsen: Add "cycle2cycle-delay" between successive 76 - gpmc,cycle2cycle-samecsen: Add "cycle2cycle-delay" between successive
|
/linux-4.4.14/Documentation/networking/caif/ |
D | Linux-CAIF.txt | 11 communication between Modem and host. The host processes can open virtual AT 13 The Utility Channels are general purpose pipes between modem and host. 15 ST-Ericsson modems support a number of transports between modem 103 - CFMUX CAIF Mux layer. Handles multiplexing between multiple
|
/linux-4.4.14/drivers/video/fbdev/omap2/dss/ |
D | Kconfig | 56 DBI is a bus between the host processor and a peripheral, 92 SDI is a high speed one-way display serial bus between the host 101 DSI is a high speed half-duplex serial interface between the host
|
/linux-4.4.14/tools/perf/Documentation/ |
D | perf-bench.txt | 32 (executing 1000000 pipe operations between two tasks) 120 (executing 1000000 pipe operations between two tasks) 127 (executing 1000 pipe operations between two tasks)
|
D | perf-lock.txt | 19 between start and end <command>. And this command
|
/linux-4.4.14/net/l3mdev/ |
D | Kconfig | 9 This module provides glue between core networking code and device
|
/linux-4.4.14/Documentation/devicetree/bindings/input/ |
D | qcom,pm8xxx-keypad.txt | 63 Definition: time in microseconds to pause between successive scans 69 Definition: time in nanoseconds to pause between scans of each row in
|
D | atmel,maxtouch.txt | 20 Note: the numbering of the GPIOs and the bit they start at varies between
|
/linux-4.4.14/Documentation/isdn/ |
D | INTERFACE.fax | 4 Description of the fax-subinterface between linklevel and hardwarelevel of 7 The communication between linklevel (LL) and hardwarelevel (HL) for fax 24 capability-values and the command-codes between LL and HL.
|
D | README.sc | 27 1.2 What is different between this driver and previous drivers? 66 1.2 What is different between this driver and previous drivers? 73 versus between 16K and 64K. New methods for using the shared RAM 189 basic HDLC connection between its two channels. Two network 190 interfaces are created and two routes added between the channels. 214 PPP connection between the two channels. The file is almost
|
D | README.fax | 40 The interface between the link-level-module and the hardware-level driver
|
/linux-4.4.14/drivers/usb/mon/ |
D | Kconfig | 9 between peripheral-specific drivers and HC drivers will be built.
|
/linux-4.4.14/Documentation/devicetree/bindings/rng/ |
D | timeriomem_rng.txt | 6 - period : wait time in microseconds to use between samples
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/ |
D | arm,scpi.txt | 14 - shmem : List of phandle pointing to the shared memory(SHM) area between the 17 between the processors. 40 These clocks don't provide an entire range of values between the 59 A small area of SRAM is reserved for SCPI communication between application
|
D | kirkwood.txt | 14 between the "cpu_clk" and the "ddrclk".
|
D | vexpress.txt | 123 between the motherboard and the tile. The first cell defines the Chip 125 All interrupt lines between the motherboard and the tile are active 150 Static Memory Bus between the tile and motherboard. It must define
|
/linux-4.4.14/Documentation/trace/ |
D | events-kmem.txt | 53 impairs performance by disabling interrupts, dirtying cache lines between 84 between allocation and freeing. A number of drain or refill pages that occur 86 refills and drains could imply an imbalance between CPUs where too much work 90 line bounces due to writes between CPUs and worth investigating if pages
|
/linux-4.4.14/Documentation/video4linux/ |
D | soc-camera.txt | 14 - camera host bus - a connection between a camera host and a camera. Can be 21 The soc-camera subsystem initially provided a unified API between camera host 76 parameters between the host and the sensor. .init_videobuf2 is called by 149 V4L2 distinguishes between pixel formats, as they are stored in memory, and as 155 sample and stored in memory in the little-endian order with no gaps between
|
D | README.pvrusb2 | 45 The most important shearing layer is between the top 2 layers. A 81 pvrusb2-audio.[ch] - This is glue logic that resides between this 106 pvrusb2-eeprom.[ch] - This is glue logic that resides between this 185 pvrusb2-tuner.[ch] - This is glue logic that resides between this 199 pvrusb2-video-*.[ch] - This is glue logic that resides between this
|
/linux-4.4.14/drivers/usb/usbip/ |
D | usbip_protocol.txt | 30 to transfer the URB traffic between the client and the server. The client may 268 0x30 | | | URB data. For ISO transfers the padding between 315 | | | between each ISO packets is not transmitted. 336 | | | between each ISO packets is not transmitted. 358 | | | between each ISO packets is not transmitted.
|
/linux-4.4.14/Documentation/cpu-freq/ |
D | governors.txt | 143 up_threshold: defines what the average CPU usage between the samplings 146 to its default value of '95' it means that between the checking 170 powersave_bias: this parameter takes a value between 0 to 1000. It 181 Processors and above) value between 0 to 100% that tells software how 206 value to anywhere between 0 and 100 where '0' will effectively lock your 213 20% between samples to have the frequency decreased. 261 What's the difference between these two functions? When your governor
|
D | pcc-cpufreq.txt | 46 Processor Clocking Control (PCC) is an interface between the platform 48 performance (ie: frequency) between the platform firmware and the OS. 65 between the OS and platform firmware. PCC also implements a "doorbell" that 137 between the limits (1600 MHz, and 2933 MHz) specified in the message.
|
/linux-4.4.14/net/netlink/ |
D | Kconfig | 9 reduces overhead by avoiding copying data between kernel- and
|
/linux-4.4.14/fs/fscache/ |
D | Kconfig | 24 between CPUs. On the other hand, the stats are very useful for 41 bouncing between CPUs. On the other hand, the histogram may be
|
/linux-4.4.14/drivers/misc/vmw_vmci/ |
D | Kconfig | 10 high-speed communication between host and guest in a virtual
|
/linux-4.4.14/net/switchdev/ |
D | Kconfig | 9 This module provides glue between core networking code and device
|
/linux-4.4.14/Documentation/devicetree/bindings/iio/adc/ |
D | nuvoton-nau7802.txt | 9 configured valid values are between 2400 mV and 4500 mV.
|
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
D | snps,arc700-intc.txt | 13 between 0 to 31
|
D | snps,archs-intc.txt | 10 between 16 to 256
|
/linux-4.4.14/virt/kvm/ |
D | Kconfig | 28 # Toggle to switch between direct notification and batch job
|
/linux-4.4.14/Documentation/devicetree/bindings/net/wireless/ |
D | qcom,ath10k.txt | 11 length can vary between hw versions
|
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
D | fsl,imx27-pinctrl.txt | 12 PIN is an integer between 0 and 0xbf. imx27 has 6 ports with 32 configurable 14 number on the specific port (between 0 and 31).
|
/linux-4.4.14/Documentation/w1/masters/ |
D | omap-hdq | 17 communication between the master (HDQ/1-Wire controller) and the slave 24 difference between the HDQ and 1-wire mode is how the slave device responds to
|
/linux-4.4.14/Documentation/devicetree/bindings/dma/ |
D | renesas,rcar-dmac.txt | 5 can be dedicated to specific clients or shared between a large number of 11 number of clients to be served, channels must be shared between multiple DMA
|
D | mpc512x-dma.txt | 4 blocks of memory contents between memory and peripherals or
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
D | raideng.txt | 17 between child address space and parent address space 37 between child address space and parent address space
|
D | dma.txt | 12 - ranges : describes the mapping between the address space of the 82 - ranges : describes the mapping between the address space of the 142 - ranges : describes the mapping between the address space of the
|
D | ccf.txt | 18 between CCF version 1 and CCF version 2. This compatible
|
/linux-4.4.14/Documentation/devicetree/bindings/power/ |
D | da9150-fg.txt | 7 - dlg,update-interval: Interval time (milliseconds) between battery level checks.
|
D | rockchip-io-domain.txt | 5 kept in sync between the regulators and the SoC using a special 27 regulator. It changes the regulator between 3.3V and 1.8V at the
|
/linux-4.4.14/net/iucv/ |
D | Kconfig | 8 communication link between VM guests.
|
/linux-4.4.14/drivers/spmi/ |
D | Kconfig | 8 serial interface between baseband and application processors
|
/linux-4.4.14/net/irda/irnet/ |
D | Kconfig | 12 can use it between Linux machine or with W2k.
|
/linux-4.4.14/drivers/staging/iio/Documentation/ |
D | overview.txt | 8 The aim is to fill the gap between the somewhat similar hwmon and 12 devices. In some cases there is considerable overlap between these and
|
D | sysfs-bus-iio-impedance-analyzer-ad5933 | 11 Frequency increment in Hz (step size) between consecutive
|
/linux-4.4.14/Documentation/device-mapper/ |
D | dm-log.txt | 44 The structure used for communication between kernel and userspace are 46 diversity, and 2-way communication nature of the exchanges between
|
D | thin-provisioning.txt | 5 between them implement thin-provisioning and snapshots. 10 allows the sharing of data between volumes, thus reducing disk usage. 73 are shared between thin devices (i.e. through snapshots). If you have 103 $data_block_size must be between 128 (64KB) and 2097152 (1GB) and a 191 between the origin and the snapshot. Indeed the snapshot is no 212 (possibly shared between many VMs). 269 Data block size must be between 64KB (128 sectors) and 1GB
|
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/nintendo/ |
D | wii.txt | 25 Represents the interface between the graphics processor and a external 36 Represents the data and control interface between the main processor 133 enables communications between the Broadway and the Starlet processors.
|
D | gamecube.txt | 16 Represents the interface between the graphics processor and a external 27 Represents the data and control interface between the main processor
|
/linux-4.4.14/Documentation/filesystems/pohmelfs/ |
D | design_notes.txt | 25 * Client is able to switch between different servers (if one goes down, client 29 * Read request (data read, directory listing, lookup requests) balancing between multiple servers. 59 operations (like lookups or directory listings) between them according to IO priorities.
|
/linux-4.4.14/Documentation/networking/ |
D | altera_tse.txt | 10 cases are simple communications between an embedded system and an external peer 232 between 65 and 127 octets in length inclusive. 236 between 128 and 255 octets in length inclusive. 240 between 256 and 511 octets in length inclusive. 244 between 512 and 1023 octets in length inclusive. 248 between 1024 and 1518 octets in length inclusive. 252 frames between the length of 1519 and the maximum frame length configured
|
D | 6pack.txt | 12 6pack is a transmission protocol for data exchange between the PC and 17 channel. Special control data is exchanged between the PC and the TNC so 27 TNCs that are connected between each other and the PC by a daisy chain 67 is supplied with a DIP switch so you can easily change between the 72 of the EPROM between HIGH and LOW level. After having inserted the new EPROM
|
D | netdev-features.txt | 73 All dependencies between features should be resolved here. The resulting 79 stateless). It can be called multiple times between successive 144 NETIF_F_NETNS_LOCAL is set for devices that are not allowed to move between
|
/linux-4.4.14/Documentation/locking/ |
D | lockdep-design.txt | 19 dependencies between different lock-classes. The validator maintains a 91 other locking sequence between the acquire-lock operations, the 92 validator will still track all dependencies between locks.) 95 between any two lock-classes: 108 any rule violation between the new lock and any of the held locks. 136 cases there is an inherent "natural" ordering between the two objects 195 possible combination of locking interaction between CPUs, combined with
|
/linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
D | i2c-gpio.txt | 12 - i2c-gpio,delay-us: delay between GPIO operations (may depend on each platform)
|
/linux-4.4.14/Documentation/devicetree/bindings/display/bridge/ |
D | thine,thc63lvdm83d.txt | 5 transmission between a host and a flat panel.
|
/linux-4.4.14/drivers/bluetooth/ |
D | Kconfig | 83 UART (H4) is serial protocol for communication between Bluetooth 95 between Bluetooth device and host. This protocol is required for non 107 communication between host and Atheros AR300x Bluetooth devices. 119 between Bluetooth device and host. This protocol is required for 166 over serial port interface(H4) between controller and host.
|
/linux-4.4.14/net/9p/ |
D | Kconfig | 22 This builds support for a transports between
|
/linux-4.4.14/Documentation/arm/SA1100/ |
D | LART | 8 between 3.5V and 16V and is overdimensioned to support a range of
|
/linux-4.4.14/drivers/hwtracing/coresight/ |
D | Kconfig | 38 responsible for bridging the gap between the on-chip coresight 39 components and a trace for bridging the gap between the on-chip
|
/linux-4.4.14/Documentation/block/ |
D | deadline-iosched.txt | 38 deadline expiries are only checked between batches. fifo_batch controls the 41 This parameter tunes the balance between per-request latency and aggregate
|
/linux-4.4.14/arch/m68k/fpsp040/ |
D | x_unfl.S | 196 | WARNING: a0 and d0 are assumed to be intact between the denorm and 197 | round subroutines. All code between these two subroutines 211 | Differentiate between store to memory vs. store to register
|
/linux-4.4.14/arch/alpha/lib/ |
D | strncpy.S | 36 or $3, $24, $3 # clear the bits between the last
|
/linux-4.4.14/Documentation/devicetree/bindings/hwlock/ |
D | qcom-hwspinlock.txt | 3 The hardware block provides mutexes utilized between different processors on
|
/linux-4.4.14/net/vmw_vsock/ |
D | Kconfig | 9 allowing communication between Virtual Machines and hypervisor
|
/linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
D | nxp,lpc1850-gpio.txt | 14 - gpio-ranges : Mapping between GPIO and pinctrl
|
D | gpio-samsung.txt | 18 - Pin number: is a value between 0 to 7.
|
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/ |
D | sun4i.txt | 16 between 0 (least sensitive) and 15
|
/linux-4.4.14/Documentation/x86/x86_64/ |
D | fake-numa-for-cpusets | 56 Notice the difference between the system memory usage as reported by 57 /proc/meminfo between the restricted cpuset case above and the unrestricted
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | msr.txt | 68 write, or registration, is needed for each VCPU. The interval between 110 coordinated between the guest and the hypervisor. Availability 215 write, or registration, is needed for each VCPU. The interval between 261 in the window between guest testing it to detect 262 whether it can skip EOI apic write and between guest
|
/linux-4.4.14/sound/spi/ |
D | Kconfig | 33 Limited by hardware to be between 8000 Hz and 50000 Hz.
|
/linux-4.4.14/drivers/w1/ |
D | Kconfig | 22 There are three types of messages between w1 core and userspace:
|
/linux-4.4.14/Documentation/cpuidle/ |
D | governor.txt | 21 users can switch between drivers using /sysfs interface (when enabled).
|
/linux-4.4.14/Documentation/i2c/ |
D | i2c-protocol | 76 I2C device but may also be used between direction changes by some 88 between the messages of one transfer.
|
/linux-4.4.14/Documentation/mic/ |
D | scif_overview.txt | 32 DMA bandwidth comparison between the TCP (over ethernet over PCIe) stack versus 60 SCIF allows memory sharing via mmap(..) between processes on different PCIe
|
/linux-4.4.14/Documentation/devicetree/bindings/leds/ |
D | leds-ns2.txt | 11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and
|
/linux-4.4.14/Documentation/ko_KR/ |
D | stable_api_nonsense.txt | 5 If you find any difference between this document and the original file or
|
/linux-4.4.14/drivers/sh/intc/ |
D | Kconfig | 39 between system IRQs and the per-controller id tables.
|
/linux-4.4.14/Documentation/devicetree/bindings/usb/ |
D | keystone-usb.txt | 13 - ranges: allows valid 1:1 translation between child's address space and
|
/linux-4.4.14/drivers/gpu/vga/ |
D | Kconfig | 27 to switch between them. This adds support for dynamic switching when
|
/linux-4.4.14/Documentation/devicetree/bindings/soc/qcom/ |
D | qcom,smem.txt | 4 between various subsystems and OSes in Qualcomm platforms.
|
/linux-4.4.14/drivers/staging/android/ion/ |
D | Kconfig | 9 from userspace that can be shared between drivers.
|
/linux-4.4.14/Documentation/RCU/ |
D | torture.txt | 36 bursts help force races between forcing a given grace 39 fqs_holdoff Holdoff time (in microseconds) between consecutive calls 42 fqs_stutter Wait time (in seconds) between consecutive bursts 73 torture_type, with a delay between calls to allow for various 85 The number of seconds between each attempt to execute a 127 stat_interval The number of seconds between output of torture
|
/linux-4.4.14/drivers/usb/wusbcore/ |
D | Kconfig | 23 enable the secure communication between the host and the
|
/linux-4.4.14/Documentation/power/regulator/ |
D | design.txt | 28 - Many of the power supplies in the system will be shared between many
|
/linux-4.4.14/Documentation/devicetree/bindings/iio/light/ |
D | us5182d.txt | 21 sensor on evaluation board - roughly between 12-32 lux.
|
/linux-4.4.14/Documentation/ABI/stable/ |
D | firewire-cdev | 6 The character device files /dev/fw* are the interface between 21 - Query maximum speed of the path between this node
|
/linux-4.4.14/drivers/auxdisplay/ |
D | Kconfig | 59 int "Delay between each control writing (microseconds)" 63 Amount of time the ks0108 should wait between each control write
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-deadline.txt | 40 that makes it possible to isolate the behavior of tasks between each other. 61 interference between different tasks (bandwidth isolation), while the EDF[1] 150 The utilization of a real-time task is defined as the ratio between its 167 for tardiness (defined as the maximum between 0 and the difference 168 between the finishing time of a job and its absolute deadline). 211 between 0 and a maximum value L. The cited papers contain all of the 244 between total utilization (or density) and a fixed constant. If all tasks 268 Finally, it is important to understand the relationship between the 347 the sum of the ratio between runtime and period for all tasks is smaller 361 A main difference between deadline bandwidth management and RT-throttling [all …]
|
/linux-4.4.14/arch/arm/plat-samsung/ |
D | Kconfig | 37 this configuration should be between zero and two. The port 55 int "Space between gpio banks" 58 Add a number of spare GPIO entries between each bank for debugging
|
/linux-4.4.14/scripts/coccinelle/misc/ |
D | ifcol.cocci | 7 /// calculation does not distinguish between spaces and tabs, so code that
|
/linux-4.4.14/Documentation/devicetree/bindings/display/panel/ |
D | sharp,ls037v7dw01.txt | 20 between QVGA and VGA mode and the scan direction. As these pins can be also
|