Home
last modified time | relevance | path

Searched refs:uses (Results 1 – 200 of 804) sorted by relevance

12345

/linux-4.4.14/arch/cris/
DKconfig352 bool "Ser0 uses no DMA for output"
357 bool "Ser0 uses DMA6 for output"
367 bool "Ser0 uses DMA0 for output"
387 bool "Ser0 uses no DMA for input"
392 bool "Ser0 uses DMA7 for input"
402 bool "Ser0 uses DMA1 for input"
422 bool "Ser1 uses no DMA for input"
427 bool "Ser1 uses DMA5 for input"
438 bool "Ser1 uses DMA9 for input"
452 bool "Ser1 uses no DMA for output"
[all …]
DKconfig.debug19 (gdb) set remotebaud 115200 <- kgdb uses 115200 as default
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dmax8997-regulator.txt25 [1] If none of the 'max8997,pmic-buck[1/2/5]-uses-gpio-dvs' optional
30 If either of the 'max8997,pmic-buck[1/2/5]-uses-gpio-dvs' optional
40 - max8997,pmic-buck1-uses-gpio-dvs: 'buck1' can be controlled by gpio dvs.
41 - max8997,pmic-buck2-uses-gpio-dvs: 'buck2' can be controlled by gpio dvs.
42 - max8997,pmic-buck5-uses-gpio-dvs: 'buck5' can be controlled by gpio dvs.
98 max8997,pmic-buck1-uses-gpio-dvs;
99 max8997,pmic-buck2-uses-gpio-dvs;
100 max8997,pmic-buck5-uses-gpio-dvs;
Ds5m8767-regulator.txt28 [1] If none of the 's5m8767,pmic-buck[2/3/4]-uses-gpio-dvs' optional
33 If either of the 's5m8767,pmic-buck[2/3/4]-uses-gpio-dvs' optional
43 - s5m8767,pmic-buck2-uses-gpio-dvs: 'buck2' can be controlled by gpio dvs.
44 - s5m8767,pmic-buck3-uses-gpio-dvs: 'buck3' can be controlled by gpio dvs.
45 - s5m8767,pmic-buck4-uses-gpio-dvs: 'buck4' can be controlled by gpio dvs.
103 s5m8767,pmic-buck2-uses-gpio-dvs;
104 s5m8767,pmic-buck3-uses-gpio-dvs;
105 s5m8767,pmic-buck4-uses-gpio-dvs;
/linux-4.4.14/Documentation/ioctl/
Dioctl-decoding.txt5 uses 3 bits to encode read/write and 13 bits for size.
8 31-30 00 - no parameters: uses _IO macro
/linux-4.4.14/Documentation/rapidio/
Dtsi721.txt10 To generate SRIO maintenance transactions this driver uses one of Tsi721 DMA
14 RapidIO messaging support uses dedicated messaging channels for each mailbox.
15 For inbound messages this driver uses destination ID matching to forward messages
30 by setting CONFIG_RAPIDIO_DMA_ENGINE option. Tsi721 miniport driver uses seven
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-devices-system-ibm-rtl10 Users: The ibm-prtm userspace daemon uses this interface.
20 Users: The ibm-prtm userspace daemon uses this interface.
Dsysfs-class-rtc-rtc0-device-rtc_calibration12 daemon uses this interface.
Dsysfs-hypervisor-pmu7 uses. Accepted values are
Dsysfs-devices-power_state14 If the device node uses shared ACPI power resources, this state
Dsysfs-class-power-twl403029 TWL data sheets. This uses whatever
/linux-4.4.14/Documentation/devicetree/bindings/arm/mediatek/
Dmediatek,pericfg.txt15 The pericfg controller uses the common clk binding from
18 Also it uses the common reset controller binding from
Dmediatek,infracfg.txt15 The infracfg controller uses the common clk binding from
18 Also it uses the common reset controller binding from
Dmediatek,vencltsys.txt12 The vencltsys controller uses the common clk binding from
Dmediatek,apmixedsys.txt13 The apmixedsys controller uses the common clk binding from
Dmediatek,topckgen.txt13 The topckgen controller uses the common clk binding from
Dmediatek,imgsys.txt12 The imgsys controller uses the common clk binding from
Dmediatek,vdecsys.txt12 The vdecsys controller uses the common clk binding from
Dmediatek,vencsys.txt12 The vencsys controller uses the common clk binding from
Dmediatek,mmsys.txt12 The mmsys controller uses the common clk binding from
/linux-4.4.14/Documentation/hwmon/
Dpwm-fan4 This driver enables the use of a PWM module to drive a fan. It uses the
15 a PWM output. It uses the generic PWM interface, thus it can be used with
Dibmpowernv15 The driver uses the platform device infrastructure. It probes the device tree
22 which the driver uses to make an OPAL call to the firmware.
Dhtu2138 The driver uses the default resolution settings of 12 bit for humidity and 14
Dw83627hf55 The w83627_HF_ uses pins 110-106 as VID0-VID4. The w83627_THF_ uses the
Dsht2142 The driver uses the default resolution settings of 12 bit for humidity and 14
/linux-4.4.14/Documentation/kbuild/
DKconfig.recursion-issue-0214 # core requirement, and one uses "select" while the other uses "depends on" to
32 # with CORE, one uses "depends on" while the other uses "select". Another
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dssd1307fb.txt21 - solomon,com-seq: Display uses sequential COM pin configuration
22 - solomon,com-lrremap: Display uses left-right COM pin remap
23 - solomon,com-invdir: Display uses inverted COM pin scan direction
/linux-4.4.14/Documentation/filesystems/
Dgfs2.txt9 file system, but also uses a lock module to allow the computers coordinate
14 GFS uses interchangeable inter-node locking mechanisms, the currently
19 lock_dlm -- uses a distributed lock manager (dlm) for inter-node locking
Dlogfs.txt119 indirect block pointers. One difference is that LogFS uses a single
130 arithmetic simple and uses compression to save space.
187 uses the upper half of the address space for indirect blocks, the size
227 Currently logfs uses a hack that essentially copies part of fs/inode.c
235 logfs uses the top half of each inode's address space. The low 8TB
Dsquashfs.txt5 It uses zlib, lz4, lzo, or xz compression to compress files, inodes and
175 The index cache is designed to be memory efficient, and by default uses
244 recently accessed data Squashfs uses two small metadata and fragment caches.
257 uses the kernel page cache. Because the page cache operates on page sized
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dkeystone-gate.txt3 Binding for Keystone gate control driver which uses PSC controller IP.
5 This binding uses the common clock binding[1].
Dgpio-mux-clock.txt3 This binding uses the common clock binding[1].
Dfixed-factor-clock.txt3 This binding uses the common clock binding[1].
Dgpio-gate-clock.txt3 This binding uses the common clock binding[1].
Dsilabs,si514.txt4 This binding uses the common clock binding[1]. Details about the device can be
Dfixed-clock.txt3 This binding uses the common clock binding[1].
Daxi-clkgen.txt3 This binding uses the common clock binding[1].
Dcalxeda.txt3 This binding uses the common clock binding[1].
Dpwm-clock.txt3 This binding uses the common clock binding[1] and the common PWM binding[2].
Dzx296702-clk.txt3 This binding uses the common clock binding[1].
Dmarvell,berlin.txt3 This binding uses the common clock binding[1].
Dmoxa,moxart-clock.txt3 This binding uses the common clock binding[1].
Dclk-palmas-clk32kg-clocks.txt5 This binding uses the common clock binding ./clock-bindings.txt.
Dti,cdce925.txt4 This binding uses the common clock binding[1].
Dbrcm,bcm2835-cprman.txt3 This binding uses the common clock binding:
Dnvidia,tegra30-car.txt3 This binding uses the common clock binding:
Dnvidia,tegra114-car.txt3 This binding uses the common clock binding:
Dsilabs,si570.txt5 This binding uses the common clock binding[1]. Details about the devices can be
Dnvidia,tegra20-car.txt3 This binding uses the common clock binding:
Daltr_socfpga.txt3 This binding uses the common clock binding[1].
/linux-4.4.14/fs/sysfs/
DKconfig6 The sysfs filesystem is a virtual filesystem that the kernel uses to
16 /sbin/hotplug uses device and object attributes in sysfs to assist in
/linux-4.4.14/arch/arc/lib/
Dmemcpy-700.S34 ; uses long immediate
40 ; uses long immediate
Dstrlen.S16 ; uses long immediate
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dsirfsoc-dma.txt28 channel request line is 9 of the 2nd dma controller, while write channel uses
30 dma controller, while write channel uses 13 of the 1st dma controller:
/linux-4.4.14/fs/squashfs/
DKconfig7 filesystem for Linux. It uses zlib, lzo or xz compression to
76 By default Squashfs uses a single decompressor but it gives
83 This decompressor implementation uses up to two parallel
90 By default Squashfs uses a single decompressor but it gives
94 This decompressor implementation uses a maximum of one
95 decompressor per core. It uses percpu variables to ensure
207 SquashFS uses less memory at the expense of extra reads from disk.
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
Dfixed-factor-clock.txt5 This binding uses the common clock binding[1], and also uses the autoidle
Dfapll.txt5 This binding uses the common clock binding[1]. It assumes a
Dclockdomain.txt5 This binding uses the common clock binding[1] in consumer role.
Dautoidle.txt5 This binding uses the common clock binding[1]. It assumes a register mapped
Dcomposite.txt5 This binding uses the common clock binding[1]. It assumes a
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dmc13xxx.txt7 - fsl,mc13xxx-uses-adc : Indicate the ADC is being used
8 - fsl,mc13xxx-uses-codec : Indicate the Audio Codec is being used
9 - fsl,mc13xxx-uses-rtc : Indicate the RTC is being used
10 - fsl,mc13xxx-uses-touch : Indicate the touchscreen controller is being used
Dmax77686.txt5 are addressed using same i2c slave address whereas RTC submodule uses
Ds2mps11.txt33 instantiate a sub-node named "clocks". It uses the common clock binding
50 The s2msp15 uses the same compatible as s2mps13, as both provides similar clocks.
/linux-4.4.14/Documentation/ia64/
Daliasing.txt19 System memory typically uses the WB attribute. The UC attribute is
35 supported attributes for each region. At boot-time, the kernel uses
40 The kernel uses the efi_memmap table returned from GetMemoryMap() to
89 This uses remap_pfn_range(), which creates user mappings. These
109 "X" uses this to access VGA frame buffers. Using legacy_mem
129 This uses copy_from_user(), which implicitly uses a kernel
180 which uses a granule-sized UC mapping. This granule will cover some
/linux-4.4.14/Documentation/sound/alsa/
DSB-Live-mixer.txt58 accumulators. ALSA uses accumulators 0 and 1 for left and right PCM samples.
64 accumulators. ALSA uses accumulators 0 and 1 for left and right PCM samples.
71 accumulators. ALSA uses accumulators 0 and 1 for left and right PCM samples.
78 accumulators. ALSA uses accumulators 0 and 1 for left and right PCM.
86 accumulator. ALSA uses accumulators 0 and 1 for left and right PCM.
93 accumulators. ALSA uses accumulators 4 and 5 for left and right MIDI samples.
100 accumulator. ALSA uses accumulators 4 and 5 for left and right PCM.
107 accumulators. ALSA uses accumulators 2 and 3 for left and right rear PCM samples.
115 accumulators. ALSA uses accumulators 2 and 3 for left and right rear PCM samples.
122 ALSA uses accumulator 6 for center PCM sample. The result sample is forwarded
[all …]
DAudigy-mixer.txt43 accumulators. ALSA uses accumulators 8 and 9 for left and right front PCM
50 accumulators. ALSA uses accumulators 2 and 3 for left and right surround PCM
57 ALSA uses accumulator 6 for center PCM sample for 5.1 playback. The result sample
63 ALSA uses accumulator 7 for LFE PCM sample for 5.1 playback. The result sample
69 accumulators. ALSA uses accumulators 0 and 1 for left and right PCM samples for
76 accumulator. ALSA uses accumulators 0 and 1 for left and right PCM.
83 accumulators. ALSA uses accumulators 4 and 5 for left and right MIDI samples.
89 accumulator. ALSA uses accumulators 4 and 5 for left and right PCM.
DJack-Controls.txt4 ALSA uses kcontrols to export audio controls(switch, volume, Mux, ...)
/linux-4.4.14/Documentation/virtual/kvm/
Dhypercalls.txt17 S390 uses diagnose instruction as hypercall (0x500) along with hypercall
24 It uses R3-R10 and hypercall number in R11. R4-R11 are used as output registers.
27 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-class-backlight44 "firmware": The driver uses a standard firmware interface
45 "platform": The driver uses a platform-specific interface
Dvdso15 The vDSO uses symbol versioning; whenever you request a symbol from the
/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
68 This node represents a controller that uses one of the PHYs of the PHY provider
/linux-4.4.14/arch/m32r/lib/
Dchecksum.S64 ; clear c-bit || Alignment uses up bytes.
72 ; clear c-bit || Alignment uses up two bytes.
181 addi r1, #-1 ; Alignment uses up bytes.
190 addi r1, #-2 ; Alignment uses up two bytes.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Ddigicolor.txt3 Each device tree must specify which Conexant Digicolor SoC it uses.
Dsunxi.txt3 Each device tree must specify which Allwinner SoC it uses,
Dtegra.txt7 Each device tree must specify which Tegra SoC it uses, using one of the
/linux-4.4.14/Documentation/misc-devices/
Dbh1770glc.txt26 8 bit. Driver supports only one channel. Driver uses ALS results to estimate
30 Driver uses threshold interrupts to avoid need for polling the values.
93 RW - enable / disable proximity - uses counting logic
/linux-4.4.14/Documentation/crypto/
Ddescore-readme.txt54 275us to set a new key (uses 1k of key tables)
66 53us per encryption (uses 2k of tables)
67 96us to set a new key (uses 2.25k of key tables)
84 68us per encryption (uses 2k of tables)
85 96us to set a new key (uses 2.25k of key tables)
106 108us per encryption (uses 34k worth of tables)
107 134us to set a new key (uses 32k of key tables to get this speed!)
116 also very modified for crypt. his iteration code uses 16k
121 165us per encryption (uses 6k worth of tables)
122 478us to set a new key (uses <1k of key tables)
[all …]
/linux-4.4.14/arch/arm/boot/dts/
Dste-hrefv60plus.dtsi196 * Touch screen uses GPIO 143 for RST1, GPIO 146 for RST2 and
213 * Display Interface 1 uses GPIO 65 for RST (reset).
214 * Display Interface 2 uses GPIO 66 for RST (reset).
Dbcm5301x-nand-cs0-bch8.dtsi5 * and uses 8 bit ECC.
Domap3-sbc-t3517.dts17 /* Only one GPMC smsc9220 on SBC-T3517, CM-T3517 uses am35x Ethernet */
Dexynos4210-trats.dts304 max8997,pmic-buck1-uses-gpio-dvs;
305 max8997,pmic-buck2-uses-gpio-dvs;
306 max8997,pmic-buck5-uses-gpio-dvs;
Dimx27-phytec-phycore-som.dtsi91 fsl,mc13xxx-uses-adc;
92 fsl,mc13xxx-uses-rtc;
/linux-4.4.14/arch/arm/crypto/
DKconfig72 AES cipher algorithms (FIPS-197). AES uses the Rijndael
110 Use an implementation of AES in CBC, CTR and XTS modes that uses
120 that uses the 64x64 to 128 bit polynomial multiplication (vmull.p64)
/linux-4.4.14/arch/c6x/lib/
Ddivi.S32 ;; divi uses B5 to hold the original return address during
34 ;; remi uses B2 and A5 to hold the input values during the
Dremi.S32 ;; divi uses B5 to hold the original return address during
34 ;; remi uses B2 and A5 to hold the input values during the
Dremu.S32 ;; divi uses B5 to hold the original return address during
34 ;; remi uses B2 and A5 to hold the input values during the
Ddivu.S32 ;; divi uses B5 to hold the original return address during
34 ;; remi uses B2 and A5 to hold the input values during the
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dbrcm,cygnus-gpio.txt90 * Touchscreen that uses the CCM GPIO 0 and 1
99 /* Bluetooth that uses the ASIU GPIO 5, with polarity inverted */
Dnxp,lpc1850-scu.txt9 The lpc1850-scu driver uses the generic pin multiplexing and generic pin
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Drenesas,rsrc-card.txt29 dai-link uses bit clock inversion.
31 dai-link uses frame clock inversion.
Drenesas,fsi.txt15 - fsia,use-internal-clock : FSI uses internal clock when master mode.
Dsamsung-i2s.txt28 i2s0 uses some base clks from CMU and some are from audio subsystem internal
31 i2s1 and i2s2 uses clocks from CMU. The clock names for i2s1 and i2s2 should
Dsimple-card.txt56 dai-link uses bit clock inversion.
58 dai-link uses frame clock inversion.
/linux-4.4.14/Documentation/networking/
Dvxlan.txt27 This creates a new device named vxlan0. The device uses the multicast
32 and uses the Linux-selected value by default to maintain backwards
Dframerelay.txt2 drivers. The upper layer implements RFC1490 FR specification, and uses the
14 The DLCI uses a number of function calls to communicate with the FRAD, all
DPLIP.txt21 printer port. PLIP is a non-standard, but [can use] uses the standard
61 that uses the parallel port subsystem of the kernel in order to properly
112 PLIP uses several different data transfer methods. The first (and the
113 only one implemented in the early version of the code) uses a standard
/linux-4.4.14/arch/x86/boot/
Dmtools.conf.in13 # 2.88 MB floppy disk image (mostly for virtual uses)
/linux-4.4.14/fs/exofs/
DKconfig5 EXOFS is a file system that uses an OSD storage device,
/linux-4.4.14/fs/notify/dnotify/
DKconfig7 that uses signals to communicate events to user-space. There exist
/linux-4.4.14/Documentation/filesystems/nfs/
Drpc-server-gss.txt46 The classic upcall mechanism uses a custom text based upcall mechanism
67 The newer upcall mechanism uses RPC over a unix socket to a daemon
74 This upcall mechanism uses the kernel rpc client and connects to the gssproxy
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
Daxxia-reset.txt3 This driver can do reset of the Axxia SoC. It uses the registers in the syscon
/linux-4.4.14/drivers/pps/generators/
DKconfig12 utilizes STROBE pin of a parallel port to send PPS signals. It uses
/linux-4.4.14/Documentation/i2c/muxes/
Di2c-mux-gpio29 i2c-gpio-mux uses the platform bus, so you need to provide a struct
77 of any GPIO pin it uses as the device ID. This guarantees that every
/linux-4.4.14/Documentation/blockdev/
Dmflash.txt21 A. IO mode based on ATA protocol and uses some custom command. (read confirm,
23 B. IO mode uses SRAM bus interface.
/linux-4.4.14/drivers/thermal/samsung/
DKconfig8 This driver uses the Exynos core thermal APIs and TMU configuration
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dspear13xx-pcie.txt4 SPEAr13XX uses synopsis designware PCIe controller and ST MiPHY as phy
/linux-4.4.14/Documentation/devicetree/bindings/mips/
Dralink.txt6 it uses in the compatible property of the root node. The compatible
Dath79-soc.txt4 it uses in the compatible property of the root node. The compatible
/linux-4.4.14/Documentation/w1/masters/
Dw1-gpio10 GPIO 1-wire bus master driver. The driver uses the GPIO API to control the
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Darm_sbsa_uart.txt2 This UART uses a subset of the PL011 registers and consequently lives
/linux-4.4.14/block/partitions/
DKconfig76 running AIX. AIX actually uses a Logical Volume Manager, where
128 FreeBSD uses its own hard disk partition scheme on your PC. It
149 Like most systems, Solaris x86 uses its own hard disk partition
159 Like some systems, UnixWare uses its own slice table inside a
229 Like most systems, SunOS uses its own hard disk partition table
245 uses a proprietary partition table.
/linux-4.4.14/Documentation/devicetree/
D00-INDEX12 - How Linux uses DT and what DT aims to solve.
/linux-4.4.14/kernel/livepatch/
DKconfig16 module uses the interface provided by this option to register
/linux-4.4.14/Documentation/scsi/
Daha152x.txt106 SCSI uses block numbers to address blocks/sectors on a device.
107 The BIOS uses a cylinder/head/sector addressing scheme (C/H/S)
121 Basically this has no impact at all on Linux, because it also uses block
138 extended translation. This means that the BIOS uses 255 for heads,
Ddc395x.txt21 The driver uses the settings from the EEPROM set in the SCSI BIOS
22 setup. If there is no EEPROM, the driver uses default values.
/linux-4.4.14/drivers/media/pci/cobalt/
DKconfig16 very useful as an example of a real driver that uses all the
/linux-4.4.14/tools/perf/
DCREDITS1 Most of the infrastructure that 'perf' uses here has been reused
/linux-4.4.14/drivers/staging/fwserial/
DTODO12 1. This driver uses the same unregistered vendor id that the firewire core does
/linux-4.4.14/net/irda/irnet/
DKconfig11 uses synchronous PPP over a set of point to point IrDA sockets. You
/linux-4.4.14/Documentation/devicetree/bindings/watchdog/
Ddavinci-wdt.txt10 Needed if platform uses clocks.
/linux-4.4.14/drivers/staging/media/lirc/
DTODO5 - lirc_bt829 uses registers on a Mach64 VT, which has a separate kernel
/linux-4.4.14/Documentation/devicetree/bindings/iio/adc/
Dtwl4030-madc.txt12 - ti,system-uses-second-madc-irq: boolean, set if the second madc irq register
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Domap-usb.txt24 - ctrl-module : phandle of the control module this glue uses to write to
60 - extcon : phandle for the extcon device omap dwc3 uses to detect
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dexynos5-gsc.txt20 in the form of gscN, N = 0...3. G-Scaler driver uses these aliases
/linux-4.4.14/drivers/net/ppp/
DKconfig41 Support for the BSD-Compress compression method for PPP, which uses
62 Support for the Deflate compression method for PPP, which uses the
63 Deflate algorithm (the same algorithm that gzip uses) to compress
149 tunnels. L2TP is replacing PPTP for VPN uses.
/linux-4.4.14/Documentation/x86/
D00-INDEX12 - why and how Linux kernel uses exception tables on x86
/linux-4.4.14/drivers/md/bcache/
DKconfig5 Allows a block device to be used as cache for other devices; uses
/linux-4.4.14/fs/efs/
DKconfig7 uses the XFS file system for hard disk partitions however).
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DNAND.txt10 The driver uses a 512 byte (1 page) ECC code for this setup. The
/linux-4.4.14/Documentation/devicetree/bindings/clock/st/
Dst,clkgen-prediv.txt3 This binding uses the common clock binding[1].
Dst,clkgen-mux.txt6 This binding uses the common clock binding[1].
Dst,clkgen-divmux.txt3 This binding uses the common clock binding[1].
Dst,quadfs.txt8 This binding uses the common clock binding[1].
Dst,clkgen-pll.txt3 This binding uses the common clock binding[1].
Dst,clkgen.txt42 This binding uses the common clock binding[1].
Dst,clkgen-vcc.txt9 This binding uses the common clock binding[1].
/linux-4.4.14/Documentation/device-mapper/
Dcache-policies.txt95 The mq policy uses a lot of memory; 88 bytes per cache block on a 64
98 SMQ uses 28bit indexes to implement it's data structures rather than
100 has a 'hotspot' queue rather than a pre cache which uses a quarter of
104 All these mean smq uses ~25bytes per cache block. Still a lot of
Dera.txt89 The target uses a bitset to record writes in the current era. It also
91 that it uses a few 4k blocks for updating metadata.
Ddm-crypt.txt33 then sectors are encrypted according to their offsets (sector 0 uses key0;
34 sector 1 uses key1 etc.). <keycount> must be a power of two.
/linux-4.4.14/drivers/media/rc/
DKconfig65 uses the RC6 protocol, and you need software decoding support.
75 uses the JVC protocol, and you need software decoding support.
85 uses the Sony protocol, and you need software decoding support.
94 uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
104 uses the Sharp protocol, and you need software decoding support.
343 The driver uses omap DM timers for generating the carrier
/linux-4.4.14/drivers/ntb/
DKconfig8 ntb Linux driver uses this point-to-point communication as a method to
/linux-4.4.14/Documentation/i2c/busses/
Di2c-parport-light6 on the parport driver, and uses direct I/O access instead. This might be
Di2c-via31 A: This can happen. This driver uses the pins VIA recommends in their
Dscx200_acb13 By default the driver uses two base addresses 0x820 and 0x840.
Di2c-ocores18 i2c-ocores uses the platform bus, so you need to provide a struct
/linux-4.4.14/drivers/net/wireless/iwlegacy/
DKconfig20 This driver uses the kernel's mac80211 subsystem.
46 This driver uses the kernel's mac80211 subsystem.
/linux-4.4.14/Documentation/
DSM501.txt26 The core re-uses the platform device system as the platform device
58 The platform device driver uses a set of platform data to pass
Dio-mapping.txt65 The initial implementation of these functions uses existing mapping
74 On 32-bit processors with HIGHMEM defined, io_mapping_map_atomic_wc uses
Dpercpu-rw-semaphore.txt12 Locking for reading is very fast, it uses RCU and it avoids any atomic
Dpnp.txt104 - increments the number of uses by one
107 - deincrements the number of uses by one
134 - ACPI: among its many uses, ACPI provides information about system level
DSubmitChecklist47 but any one function that uses more than 512 bytes on the stack is a
101 26: If your modified source code depends on or uses any of the kernel
Dunicode.txt32 codes nor their uses match ISO 2022; Linux has two 8-bit codes (G0 and
63 The DEC VT220 uses a 6x10 character matrix, and these characters form
69 they are added at U+23BA, U+23BB, U+23BC, U+23BD. Linux now uses the
Dbraille-console.txt28 For simplicity, only one braille console can be enabled, other uses of
Dramoops.txt17 Ramoops uses a predefined memory area to store the dump. The start and size
38 The module uses a counter to record multiple dumps but the counter gets reset
/linux-4.4.14/drivers/staging/rtl8192e/
DKconfig7 If you have a wireless card that uses rtllib, say
/linux-4.4.14/drivers/staging/clocking-wizard/
Ddt-binding.txt3 This binding uses the common clock binding[1]. Details about the devices can be
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-sx150x.txt25 which case it uses the default two cell specifier as described in
Dgpio-atlas7.txt11 The GPIO controller also acts as an interrupt controller. It uses the default
Dgpio-adnp.txt15 which case it uses the default two cell specifier as described in
Dgpio-mcp23s08.txt21 - reg : For an address on its bus. I2C uses this a the I2C address of the chip.
22 SPI uses this to specify the chipselect line which the chip is
Dgpio-davinci.txt25 The GPIO controller also acts as an interrupt controller. It uses the default
/linux-4.4.14/drivers/media/dvb-core/
DKconfig24 allocation for any device that uses the DVB major number.
/linux-4.4.14/Documentation/cpuidle/
Dgovernor.txt12 any given time. cpuidle core uses different callbacks to the governor.
/linux-4.4.14/drivers/tty/hvc/
DKconfig87 This console uses the JTAG DCC on ARM to create a console under the HVC
96 This console uses the Blackfin JTAG to create a console under the
/linux-4.4.14/Documentation/powerpc/
Dbootwrapper.txt20 it uses the wrapper script (arch/powerpc/boot/wrapper) to generate target
52 PlayStation 3 support uses dtbImage. So do Embedded
73 sequence. The virtex405 platform uses this feature to
134 uses the -p (platform) argument as the main method of deciding which wrapper
/linux-4.4.14/Documentation/isdn/
DREADME.x25125 x25d[tc]e uses fixed lap_b addresses. With x75i, the side which
126 initiates the isdn connection uses the DTE's lap_b address while the
147 - an application program that uses linux PF_X25 sockets (some are
171 and telnetd that uses X.25 sockets instead of tcp/ip sockets. You can
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dltc2941.txt5 temperature monitoring, and uses a slightly different conversion
/linux-4.4.14/Documentation/arm/Samsung/
DGPIO.txt22 The gpio implementation uses gpiolib as much as possible, only providing
/linux-4.4.14/Documentation/aoe/
Dudev.txt4 # whether it uses one or two equal signs for SUBSYSTEM and KERNEL.
/linux-4.4.14/drivers/cpufreq/
DKconfig.arm165 It uses information gathered through existing hardware and
210 This driver uses SCPI Message Protocol driver to interact with the
248 This adds a CPUFreq driver which uses CPPC methods
/linux-4.4.14/Documentation/devicetree/bindings/x86/
Dce4100.txt4 The CE4100 SoC uses for in core peripherals the following compatible
/linux-4.4.14/drivers/pps/clients/
DKconfig13 which uses a kernel timer to generate the PPS signal.
/linux-4.4.14/Documentation/w1/slaves/
Dw1_ds240616 one output and uses parasitic power only.
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Drenesas,mmcif.txt22 - max-frequency: Maximum operating clock frequency, driver uses default clock
Datmel-hsmci.txt20 The node contains child nodes for each slot that the platform uses
/linux-4.4.14/Documentation/acpi/
Ddebug.txt75 The ACPI interpreter uses several different levels, but the Linux
126 statement uses ACPI_DB_INFO, which is macro based on the ACPI_LV_INFO
/linux-4.4.14/Documentation/s390/
DDASD5 Linux as block devices, namely "dd". Currently the DASD driver uses a
55 4096. We recommend no blksize lower than 1024 because the ext2fs uses
/linux-4.4.14/Documentation/sound/oss/
DALS25 the MPU401 interface on this card uses a different interrupt to the audio
44 card uses separate IRQs for the audio and MPU401 sections and there is no
/linux-4.4.14/Documentation/RCU/
Drcubarrier.txt89 uses multiple flavors of call_rcu(), then it must also use multiple
91 it uses call_rcu_bh(), call_srcu() on srcu_struct_1, and call_srcu() on
188 Of course, if you module uses call_rcu_bh(), you will need to invoke
189 rcu_barrier_bh() before unloading. Similarly, if your module uses
191 unloading. If your module uses call_rcu(), call_rcu_bh(), -and-
Drcu.txt42 RCU read-side critical sections. SRCU also uses CPU-local
62 o What guidelines should I follow when writing code that uses RCU?
/linux-4.4.14/Documentation/devicetree/bindings/hwmon/
Dads1015.txt43 The node contains child nodes for each channel that the platform uses.
/linux-4.4.14/Documentation/accounting/
Dcgroupstats.txt5 Per cgroup statistics infrastructure re-uses code from the taskstats
/linux-4.4.14/fs/cramfs/
DREADME96 Currently, mkcramfs #define's PAGE_CACHE_SIZE as 4096 and uses that
97 for blksize, whereas Linux-2.3.39 uses its PAGE_CACHE_SIZE, which in
140 The cost of option 2 relative to option 1 is that the code uses
/linux-4.4.14/drivers/staging/olpc_dcon/
DKconfig8 In order to support very low power operation, the XO laptop uses a
/linux-4.4.14/fs/gfs2/
DKconfig12 and writes to the block device like a local filesystem, but also uses
/linux-4.4.14/scripts/coccinelle/iterators/
Dlist_entry_update.cocci1 /// list_for_each_entry uses its first argument to get from one element of
/linux-4.4.14/Documentation/fault-injection/
Dprovoke-crashes.txt3 using different dumping solutions. The module uses KPROBEs to instrument
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-bus-usb17 level. The "on" level is meant for administrative uses.
/linux-4.4.14/Documentation/usb/
Dmass-storage.txt182 The Mass Storage Gadget uses the Mass Storage Function to handle
200 that MSG is a composite gadget (ie. uses the composite framework)
213 values for each logical unit. If one uses only a single logical
224 supported. MSG always uses SCSI protocol with bulk only
/linux-4.4.14/Documentation/sh/
Dregister-banks.txt22 Presently the kernel uses several of these registers.
/linux-4.4.14/drivers/gpu/drm/panel/
DKconfig47 TFT-LCD modules. The panel has a 2560x1600 resolution and uses
/linux-4.4.14/Documentation/arm64/
Dtagged-pointers.txt8 addresses in the AArch64 translation system and their potential uses
/linux-4.4.14/arch/alpha/lib/
Dev6-memset.S83 subq $3,8,$3 # E : Invert (for addressing uses)
260 subq $3,8,$3 # E : Invert (for addressing uses)
447 subq $3,8,$3 # E : Invert (for addressing uses)
/linux-4.4.14/Documentation/devicetree/bindings/leds/
Dleds-ktd2692.txt4 It uses ExpressWire single-wire programming for maximum flexibility.
/linux-4.4.14/Documentation/timers/
Dhpet.txt24 platform code which uses timer 0 or 1 as the main timer to intercept HPET
/linux-4.4.14/scripts/coccinelle/free/
Ddevm_free.cocci1 /// Find uses of standard freeing functons on values allocated using devm_
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
Dtimer.txt22 the OMAP device uses.
/linux-4.4.14/block/
DKconfig.iosched10 and sorting. Its main uses include non-disk based block devices like
/linux-4.4.14/drivers/spi/
DKconfig168 This uses a custom parallel port cable to connect to an AVR
239 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
310 MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
311 MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
321 mode. VF610 platform uses the controller.
329 From MPC8536, 85xx platform uses the controller, and all P10xx,
330 P20xx, P30xx,P40xx, P50xx uses this controller.
/linux-4.4.14/Documentation/thermal/
Dexynos_thermal_emulation24 changing temperature. However, this node only uses same delay of real sensing time, 938us.)

12345