| /linux-4.1.27/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 7 POHMELFS first began as a network filesystem with coherent local data and
11 * Locally coherent cache for data and metadata with (potentially) byte-range locks.
13 is very simple and does not use byte-ranges, although they are sent in
15 * Completely async processing of all events except creation of hard and symbolic
16 links, and rename events.
17 Object creation and data reading and writing are processed asynchronously.
19 Ability to create long paths to objects and remove arbitrarily huge
23 * Fast and scalable multithreaded userspace server. Being in userspace it works
24 with any underlying filesystem and still is much faster than async in-kernel NFS one.
26 automatically reconnects to second and so on).
[all …]
|
| /linux-4.1.27/Documentation/timers/ |
| D | hrtimers.txt | 9 back and forth trying to integrate high-resolution and high-precision
10 features into the existing timer framework, and after testing various
14 to solve this'), and spent a considerable effort trying to integrate
18 - the forced handling of low-resolution and high-resolution timers in
19 the same way leads to a lot of compromises, macro magic and #ifdef
20 mess. The timers.c code is very "tightly coded" around jiffies and
21 32-bitness assumptions, and has been honed and micro-optimized for a
23 for many years - and thus even small extensions to it easily break
25 code is very good and tight code, there's zero problems with it in its
45 error conditions in various I/O paths, such as networking and block
[all …]
|
| D | highres.txt | 1 High resolution timers and dynamic ticks design notes
5 and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
14 design of the Linux time(r) system before hrtimers and other building blocks
17 Note: the paper and the slides are talking about "clock event source", while we
23 - timeofday and clock source management
42 timeofday and clock source management
49 sources, which are registered in the framework and selected on a quality based
50 decision. The low level code provides hardware setup and readout routines and
60 The paper "We Are Not Getting Any Younger: A New Approach to Time and
72 period defined at compile time. The setup and selection of the event device
[all …]
|
| D | timekeeping.txt | 1 Clock sources, Clock events, sched_clock() and delay timers
10 specific implementations of clock sources, clockevents and several likewise
11 architecture-specific overrides of the sched_clock() function and some
17 sched_clock() is used for scheduling and timestamping, and delay timers
30 n bits which count from 0 to 2^(n-1) and then wraps around to 0 and start over.
34 The clock source shall have as high resolution as possible, and the frequency
35 shall be as stable and correct as possible as compared to a real-world wall
36 clock. It should not move unpredictably back and forth in time or miss a few
37 cycles here and there.
41 and the higher 16 bits in a second bus cycle with the counter bits
[all …]
|
| /linux-4.1.27/Documentation/fb/ |
| D | api.txt | 11 with frame buffer devices. In-kernel APIs between device drivers and the frame
15 behaviours differ in subtle (and not so subtle) ways. This document describes
23 Device and driver capabilities are reported in the fixed screen information
33 expect from the device and driver.
42 2. Types and visuals
49 Formats are described by frame buffer types and visuals. Some visuals require
51 bits_per_pixel, grayscale, red, green, blue and transp fields.
53 Visuals describe how color information is encoded and assembled to create
55 types and visuals are supported.
63 Padding at end of lines may be present and is then reported through the fixed
[all …]
|
| D | internals.txt | 19 Device independent unchangeable information about a frame buffer device and
25 Device independent changeable information about a frame buffer device and a
27 ioctl, and updated with the FBIOPUT_VSCREENINFO ioctl. If you want to pan
32 Device independent colormap information. You can get and set the colormap
33 using the FBIOGETCMAP and FBIOPUTCMAP ioctls.
40 Generic information, API and low level information about a specific frame
54 Monochrome (FB_VISUAL_MONO01 and FB_VISUAL_MONO10)
59 Pseudo color (FB_VISUAL_PSEUDOCOLOR and FB_VISUAL_STATIC_PSEUDOCOLOR)
62 color (including red, green, and blue intensities) for each possible pixel
63 value, and that color is displayed.
[all …]
|
| D | intel810.txt | 21 Intel 815 Internal graphics and AGP
28 - Supports a variable range of horizontal and vertical resolution and
32 - Supports color depths of 8, 16, 24 and 32 bits per pixel
36 - Full and optimized hardware acceleration at 8, 16 and 24 bpp
38 - Robust video state save and restore
67 is enabled, this will be ignored and computed as 3*xres/4. (This
94 select the minimum and maximum Horizontal Sync Frequency of the
97 ignored and values will be taken from the EDID block.
103 select the minimum and maximum Vertical Sync Frequency of the monitor
105 rate. If EDID probing is successful, these will be ignored and values
[all …]
|
| /linux-4.1.27/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 36 * 06-06-00 01.00.01 Update MPI_VERSION_MAJOR and MPI_VERSION_MINOR.
52 * Added defines for MPI_DIAG_PREVENT_IOC_BOOT and
68 * 11-15-02 01.02.08 Added define MPI_IOCSTATUS_TARGET_INVALID_IO_INDEX and
74 * and MPI_FUNCTION_DIAG_RELEASE.
81 * Added new function codes and new IOCStatus codes.
88 * 03-11-05 01.05.07 Removed function codes for SCSI IO 32 and
91 * 06-24-05 01.05.08 Added function codes for SCSI IO 32 and
114 * _LINK_STATUS, _LOOP_STATE and _LOGOUT.
115 * 08-11-00 01.00.05 Switched positions of MsgLength and Function fields in
119 * 12-04-00 01.01.02 Modified IOCFacts reply, added FWUpload messages, and
[all …]
|
| /linux-4.1.27/tools/power/cpupower/ |
| D | README | 7 For compilation pciutils-devel (pci/pci.h) and a gcc version
16 tools and programs to the cpufreq core and drivers in the Linux kernel. This
18 the interaction to the cpufreq core, and support for both the sysfs and proc
22 compilation and installation
30 /usr/lib; cpupower, cpufreq-bench_plot.sh to put in /usr/bin; and
32 differently and/or want to configure the package to your specific
33 needs, you need to open "Makefile" with an editor of your choice and
39 Many thanks to Mattia Dongili who wrote the autotoolization and
40 libtoolization, the manpages and the italian language file for cpupower;
41 to Dave Jones for his feedback and his dump_psb tool; to Bruno Ducrot for his
[all …]
|
| /linux-4.1.27/Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 11 communication between Modem and host. The host processes can open virtual AT
12 channels, initiate GPRS Data connections, Video channels and Utility Channels.
13 The Utility Channels are general purpose pipes between modem and host.
16 and host. Currently, UART and Loopback are available for Linux.
22 * CAIF Socket Layer and GPRS IP Interface.
59 The architecture is inspired by the design patterns "Protocol Layer" and
69 CAIF payload with receive and transmit functions.
70 - Clients must call configuration function to add and connect the
77 The CAIF protocol can be divided into two parts: Support functions and Protocol
81 CAIF Packet has functions for creating, destroying and adding content
[all …]
|
| /linux-4.1.27/drivers/edac/ |
| D | Kconfig | 4 # Licensed and distributed under the GPL
26 and:
48 levels are 0-4 (from low to high) and by default it is set to 2.
68 This is a simple debugfs interface to inject MCEs and test different
77 Some systems are able to detect and correct errors in main
79 detection and correction (EDAC - or commonly referred to ECC
98 It should be noticed that keeping both GHES and a hardware-driven
111 Support for error detection and correction of DRAM ECC errors on
118 Recent Opterons (Family 10h and later) provide for Memory Error
120 allows the operator/user to inject Uncorrectable and Correctable
[all …]
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | smsc47m192 | 5 * SMSC LPC47M192, LPC47M15x, LPC47M292 and LPC47M997
10 The LPC47M15x, LPC47M292 and LPC47M997 are compatible for
15 of the code and many helpful comments and suggestions.
22 of the SMSC LPC47M192 and compatible Super-I/O chips.
24 These chips support 3 temperature channels and 8 voltage inputs
27 They do also have fan monitoring and control capabilities, but the
28 these features are accessed via ISA bus and are not supported by this
29 driver. Use the 'smsc47m1' driver for fan monitoring and control.
31 Voltages and temperatures are measured by an 8-bit ADC, the resolution
37 Both voltage and temperature values are scaled by 1000, the sys files
[all …]
|
| D | vt1211 | 8 Datasheet: Provided by VIA upon request and under NDA
12 This driver is based on the driver for kernel 2.4 by Mark D. Studebaker and
15 Thanks to Joseph Chan and Fiona Gatt from VIA for providing documentation and
25 UCH1, bit 1 maps to UCH2 and so on. Setting a bit to 1
26 enables the thermal input of that particular UCH and
43 capabilities. It monitors 2 dedicated temperature sensor inputs (temp1 and
44 temp2), 1 dedicated voltage (in5) and 2 fans. Additionally, the chip
48 This chip also provides manual and automatic control of fan speeds (according
55 The following table shows the relationship between the vt1211 inputs and the
83 motherboard and edit sensors.conf accordingly.
[all …]
|
| D | dme1737 | 5 * SMSC DME1737 and compatibles (like Asus A8000)
8 Datasheet: Provided by SMSC upon request and under NDA
16 Datasheet: Provided by SMSC upon request and under NDA
20 Datasheet: Provided by SMSC upon request and under NDA
29 * force_start: bool Enables the monitoring of voltage, fan and temp inputs
30 and PWM output control functions. Using this parameter
33 * probe_all_addr: bool Include non-standard LPC addresses 0x162e and 0x164e
43 SMSC DME1737 and Asus A8000 (which are the same), SMSC SCH5027, SCH311x,
44 and SCH5127 Super-I/O chips. These chips feature monitoring of 3 temp sensors
45 temp[1-3] (2 remote diodes and 1 internal), 8 voltages in[0-7] (7 external and
[all …]
|
| D | lm77 | 18 10-bit ADC, and a digital comparator with user-programmable upper
19 and lower limit values.
21 The LM77 implements 3 limits: low (temp1_min), high (temp1_max) and
25 the limit and its hysteresis is always the same for all 3 limits.
30 was 80 degrees C, and the hysteresis was 75 degrees C, and you change
34 temp1_crit_hyst writable, while temp1_min_hyst and temp1_max_hyst are
36 temp1_crit_hyst and temp1_crit into the chip, and the same relative
37 hysteresis applies automatically to the low and high limits.
|
| D | ina2xx | 40 The INA219 is a high-side current shunt and power monitor with an I2C
41 interface. The INA219 monitors both shunt drop and supply voltage, with
42 programmable conversion times and filtering.
44 The INA220 is a high or low side current shunt and power monitor with an I2C
45 interface. The INA220 monitors both shunt drop and supply voltage.
47 The INA226 is a current shunt and power monitor with an I2C interface.
48 The INA226 monitors both a shunt voltage drop and bus supply voltage.
50 INA230 and INA231 are high or low side current shunt and power monitors
51 with an I2C interface. The chips monitor both a shunt voltage drop and
61 bus and shunt voltage conversion times multiplied by the averaging rate. We
[all …]
|
| D | max16065 | 34 monitor and sequence multiple system voltages. The MAX16065/MAX16066 can also
37 simultaneously, and the MAX16066 manages up to eight supply voltages.
39 The MAX16067 flash-configurable system manager monitors and sequences multiple
42 The MAX16068 flash-configurable system manager monitors and manages up to six
48 MAX16070 monitors up to twelve system voltages simultaneously, and the MAX16071
51 Each monitored channel has its own low and high critical limits. MAX16065,
52 MAX16066, MAX16070, and MAX16071 support an additional limit which is
54 MAX16070, and MAX16071 also support supply current monitoring.
65 WARNING: Do not access chip registers using the i2cdump command, and do not use
69 power loss, board resets, and/or Flash corruption. Worst case, your board may
[all …]
|
| D | tmp421 | 7 Addresses scanned: I2C 0x2a, 0x4c, 0x4d, 0x4e and 0x4f
11 Addresses scanned: I2C 0x4c, 0x4d, 0x4e and 0x4f
15 Addresses scanned: I2C 0x4c and 0x4d
19 Addresses scanned: I2C 0x2a, 0x4c, 0x4d, 0x4e and 0x4f
23 Addresses scanned: I2C 0x4c and 0x4d
33 TMP423, TMP441, and TMP442 temperature sensor chips. These chips
34 implement one local and up to one (TMP421, TMP441), up to two (TMP422,
36 in degrees Celsius. The chips are wired over I2C/SMBus and specified
38 for both the local and remote channels is 0.0625 degree C.
|
| D | pcf8591 | 20 The PCF8591 is an 8-bit A/D and D/A converter (4 analog inputs and one
33 - mode 2 : single ended and differential mixed
34 Pins AIN0 and AIN1 are single ended inputs for channels 0 and 1
54 2 = single ended and differential mixed
71 and <1> the chip address ([48..4f])
78 The in0_input, in1_input, in2_input and in3_input files are RO. Reading gives
80 configuration, files in2_input and in3_input may not exist. Values range
81 from 0 to 255 for single ended inputs and -128 to +127 for differential inputs
84 The out0_enable file is RW. Reading gives "1" for analog output enabled and
85 "0" for analog output disabled. Writing accepts "0" and "1" accordingly.
[all …]
|
| D | lm90 | 12 Addresses scanned: I2C 0x4c and 0x4d
17 Addresses scanned: I2C 0x4c and 0x4d
27 Addresses scanned: I2C 0x4c and 0x4d
32 Addresses scanned: I2C 0x4c and 0x4d
37 Addresses scanned: I2C 0x4c and 0x4d
42 Addresses scanned: I2C 0x4c and 0x4d
83 0x4c, 0x4d and 0x4e
89 0x4c, 0x4d and 0x4e
105 0x4c, 0x4d and 0x4e
143 MAX6658 and MAX6659 variants. The extra features of the MAX6659 are only
[all …]
|
| D | ads1015 | 27 in0: Voltage over AIN0 and AIN1.
28 in1: Voltage over AIN0 and AIN3.
29 in2: Voltage over AIN1 and AIN3.
30 in3: Voltage over AIN2 and AIN3.
31 in4: Voltage over AIN0 and GND.
32 in5: Voltage over AIN1 and GND.
33 in6: Voltage over AIN2 and GND.
34 in7: Voltage over AIN3 and GND.
69 In this case only in2_input (FS +/- 4.096 V, 128 SPS) and in4_input
|
| D | pc87360 | 5 * National Semiconductor PC87360, PC87363, PC87364, PC87365 and PC87366
12 Thanks to Sandeep Mehta, Tonko de Rooy and Daniel Ceregatti for testing.
22 *1: Forcibly enable internal voltage and temperature channels, except in9
23 2: Forcibly enable all voltage and temperature channels, except in9
24 3: Forcibly enable all voltage and temperature channels, including in9
26 Note that this parameter has no effect for the PC87360, PC87363 and PC87364
29 Also note that for the PC87366, initialization levels 2 and 3 don't enable
37 The National Semiconductor PC87360 Super I/O chip contains monitoring and
38 PWM control circuitry for two fans. The PC87363 chip is similar, and the
39 PC87364 chip has monitoring and PWM control for a third fan.
[all …]
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | soc-camera.txt | 9 of connecting to a variety of systems and interfaces, typically uses i2c for
10 control and configuration, and a parallel or a serial bus for data.
12 specialised interface, present on many SoCs, e.g. PXA27x and PXA3xx, SuperH,
14 - camera host bus - a connection between a camera host and a camera. Can be
15 parallel or serial, consists of data and control lines, e.g. clock, vertical
16 and horizontal synchronization signals.
22 drivers and camera sensor drivers. Later the soc-camera sensor API has been
31 The subsystem has been designed to support multiple camera host interfaces and
40 omap1_camera.c, pxa_camera.c, sh_mobile_ceu_camera.c, and multiple sensor
74 .add and .remove methods are called when a sensor is attached to or detached
[all …]
|
| D | README.davinci-vpbe | 32 Implements creation of video2 and video3 device nodes and
33 provides v4l2 device interface to manage VID0 and VID1 layers.
36 Loads up VENC, OSD and external encoders such as ths8200. It provides
41 controller port is done at init time based on default output and standard
46 for setting up the interface between VENC and external encoders based on
51 patch series, the interconnection and enabling and setting of the external
52 encoders is not present, and would be a part of the next patch series.
55 Responsible for setting outputs provided through internal DACs and also
59 the board specific table and the values are used to set the timings in
64 timings for the resolution supported and setting the dot clock. So we could
[all …]
|
| D | vivid.txt | 5 output, vbi capture and output, radio receivers and transmitters and a software
7 testing capture and output overlays.
9 Up to 64 vivid instances can be created, each with up to 16 inputs and 16 outputs.
15 These inputs and outputs act exactly as a real hardware device would behave. This
21 - Support for read()/write(), MMAP, USERPTR and DMABUF streaming I/O.
22 - A large list of test patterns and variations thereof
23 - Working brightness, contrast, saturation and hue controls
27 - Support for various pixel aspect ratios and video aspect ratios
29 - Supports crop/compose/scale in any combination for both input and output
32 - Supports all standard YUV and RGB formats, including two multiplanar YUV formats
[all …]
|
| /linux-4.1.27/Documentation/RCU/ |
| D | RTFP.txt | 4 This document describes RCU-related publications, and is followed by
7 and search engines will usually find what you are looking for.
9 The first thing resembling RCU was published in 1980, when Kung and Lehman
16 In 1982, Manber and Ladner [Manber82,Manber84] recommended deferring
22 In 1986, Hennessy, Osisek, and Seigh [Hennessy89] introduced passive
47 write-side contention and parallelize the other write-side overheads by
56 error, which typically slows convergence and thus increases the number of
61 structured data, such as the matrices used in scientific programs, and
88 Their approach requires memory barriers (and thus pipeline stalls),
89 but reduces memory latency, contention, and locking overheads.
[all …]
|
| D | lockdep.txt | 1 RCU and lockdep checking
4 aware of when each task enters and leaves any flavor of RCU read-side
6 that this is not the case in 2.6.32 and earlier). This allows lockdep's
8 deadlocks and the like.
18 These functions are conservative, and will therefore return 1 if they
37 invoked by both RCU readers and updaters.
41 is invoked by both RCU-bh readers and updaters.
45 is invoked by both RCU-sched readers and updaters.
49 is invoked by both SRCU readers and updaters.
54 that is invoked by both RCU readers and updaters.
[all …]
|
| /linux-4.1.27/Documentation/w1/masters/ |
| D | ds2490 | 17 which has 0x81 family ID integrated chip and DS2490
20 Notes and limitations.
21 - The weak pullup current is a minimum of 0.9mA and maximum of 6.0mA.
22 - The 5V strong pullup is supported with a minimum of 5.9mA and a
30 a write buffer and a read buffer (along with sizes) as arguments.
32 buffer, and strong pullup all in one command, instead of the current
33 1 reset bus, 2 write the match rom command and slave rom id, 3 block
34 write and read data. The write buffer needs to have the match rom
35 command and slave rom id prepended to the front of the requested
37 - The hardware supports normal, flexible, and overdrive bus
[all …]
|
| /linux-4.1.27/Documentation/sound/alsa/soc/ |
| D | overview.txt | 6 pxa2xx, au1x00, iMX, etc) and portable audio codecs. Prior to the ASoC
11 CPU. This is not ideal and leads to code duplication - for example,
16 event). These are quite common events on portable devices and often require
29 The ASoC layer is designed to address these issues and provide the following
33 and machines.
35 * Easy I2S/PCM audio interface setup between codec and SoC. Each SoC
36 interface and codec registers its audio interface capabilities with the
37 core and are subsequently matched and configured when the application
42 internal power blocks depending on the internal codec audio routing and any
45 * Pop and click reduction. Pops and clicks can be reduced by powering the
[all …]
|
| D | DAI.txt | 2 SoC controllers and portable audio CODECs today, namely AC97, I2S and PCM.
9 now also popular in many portable devices. This DAI has a reset line and time
10 multiplexes its data on its SDATA_OUT (playback) and SDATA_IN (capture) lines.
11 The bit clock (BCLK) is always driven by the CODEC (usually 12.288MHz) and the
13 frame is 21uS long and is divided into 13 time slots.
22 I2S is a common 4 wire DAI used in HiFi, STB and portable devices. The Tx and
23 Rx lines are used for audio transmission, whilst the bit clock (BCLK) and
25 controller or CODEC can drive (master) the BCLK and LRC clock lines. Bit clock
26 usually varies depending on the sample rate and the master system clock
28 ADC and DAC LRCLKs, this allows for simultaneous capture and playback at
[all …]
|
| D | machine.txt | 5 component drivers (e.g. codecs, platforms and DAIs). It also describes the
7 interrupts, clocking, jacks and voltage regulators.
9 The machine driver can contain codec and platform specific code. It registers
10 the audio subsystem with the kernel as a platform device and is represented by
22 /* the pre and post PM functions are used to do any PM work before and
23 * after the codec and DAIs do any PM work. */
45 The machine driver has pre and post versions of suspend and resume to take care
47 and DMA is suspended and resumed. Optional.
52 The machine DAI configuration glues all the codec and CPU DAIs together. It can
53 also be used to set up the DAI system clock and for any machine related DAI
[all …]
|
| D | pops_clicks.txt | 1 Audio Pops and Clicks
4 Pops and clicks are unwanted audio artifacts caused by the powering up and down
7 powered up and causes a popping noise on the speakers).
9 Pops and clicks can be more frequent on portable systems with DAPM. This is
11 depending on the audio usage and this can subsequently cause a small pop or
15 Minimising Playback Pops and Clicks
19 currently, however future audio codec hardware will have better pop and click
21 components in a specific order. This order is different for startup and
22 shutdown and follows some basic rules:-
28 This assumes that the codec PCM output path from the DAC is via a mixer and then
[all …]
|
| D | codec.txt | 4 The codec class driver is generic and hardware independent code that configures
5 the codec, FM, MODEM, BT or external DSP to provide audio capture and playback.
7 All platform and machine specific code should be added to the platform and
12 1) Codec DAI and PCM configuration
14 3) Mixers and audio controls
29 1 - Codec DAI and PCM configuration
31 Each codec driver must have a struct snd_soc_dai_driver to define its DAI and
32 PCM capabilities and operations. This struct is exported so that it can be
69 Regmap API for all codec IO. Please see include/linux/regmap.h and existing
73 3 - Mixers and audio controls
[all …]
|
| D | dapm.txt | 9 subsystem at all times. It is independent of other kernel PM and as
16 activity and audio mixer settings within the device.
19 audio subsystem, this includes internal codec power blocks and machine
24 1. Codec bias domain - VREF, VMID (core codec and audio power)
25 Usually controlled at codec probe/remove and suspend/resume, although
28 2. Platform/Machine domain - physically connected inputs and outputs
29 Is platform/machine and user action specific, is configured by the
30 machine driver and responds to asynchronous events e.g when HP
34 Automatically set when mixer and mux settings are changed by the user.
37 4. Stream domain - DACs and ADCs.
[all …]
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | AUTHORS | 5 The author wishes to express his appreciation and thanks to:
7 improvements. Thanks to IBM for allowing me time and test resources to pursue
8 this project, to Jim McDonough from IBM (and the Samba Team) for his help, to
11 side of the original CIFS Unix extensions and reviewing and implementing
16 Newbigin and others for their work on the Linux smbfs module. Thanks to
18 Workgroup for their work specifying this highly complex protocol and finally
19 thanks to the Samba team for their technical advice and encouragement.
33 Vince Negri and Dave Stahl (for finding an important caching bug)
38 Shaggy (Dave Kleikamp) for innumerable small fs suggestions and some good cleanup
39 Gunter Kukkukk (testing and suggestions for support of old servers)
[all …]
|
| D | TODO | 8 is a partial list of the known problems and missing features:
10 a) SMB3 (and SMB3.02) missing optional features:
25 e) improve support for very old servers (OS/2 and Win9x for example)
31 g) Better optimize open (and pathbased setfilesize) to reduce the
34 than resending (helps reduce server resource utilization and avoid
40 i) Finish inotify support so kde and gnome file list windows
44 j) Add GUI tool to configure /proc/fs/cifs settings and for display of
47 k) implement support for security and trusted categories of xattrs
56 and client. Add new protocol request to the CIFS protocol
60 n) DOS attrs - returned as pseudo-xattr in Samba format (check VFAT and NTFS for this too)
[all …]
|
| /linux-4.1.27/drivers/staging/unisys/Documentation/ |
| D | overview.txt | 10 normally be unsharable; specifically, PCI network interfaces and host
12 device is owned and managed by a small, single-purpose service
16 services, logging and diagnostics, and accessing the Linux console
20 modules, and a set of device driver modules. The support modules
27 in the interactions between the client drivers and the virtual adapter
34 The modules in this section handle shared devices and the virtual
35 buses required to support them. These modules use functions in and
40 The visorchipset module receives device creation and destruction
49 In operation, the visorchipset module processes device creation and
52 virtual bus and virtual device. Each bus and device is also associated
[all …]
|
| D | proc-entries.txt | 8 uislib module, including bus information and memory usage.
19 guest can be considered running and is shown as running in the s-Par
38 virthba module, including interrupt information and memory usage.
44 virtnic module, including interrupt information, send and receive
45 counts, and other device information.
49 clientstring and zone.
52 virtpci module, including virtual PCI bus information and device
58 Visorconinclient, visordiag, visornoop, visorserialclient, and
66 diag entry that presents the device number and visorbus name for that
73 and the Linux-based installation and recovery tool. These values are
[all …]
|
| /linux-4.1.27/Documentation/usb/ |
| D | CREDITS | 31 Linux USB driver effort and writing much of the larger uusbd driver.
35 and offering suggestions and sharing implementation experiences.
37 Additional thanks to the following companies and people for donations
38 of hardware, support, time and development (this is from the original
44 - 3Com GmbH for donating a ISDN Pro TA and supporting me
45 in technical questions and with test equipment. I'd never
52 Operating System and supports this project with
74 protocol. They've also donated a F-23 digital joystick and a
79 leading manufacturer for active and passive ISDN Controllers
80 and CAPI 2.0-based software. The active design of the AVM B1
[all …]
|
| D | WUSB-Design-overview.txt | 7 This program is free software; you can redistribute it and/or
30 and an Intel WiNET controller).
40 1. Devices and hosts: the basic structure
44 3. On the air: beacons and enumerating the radio neighborhood
58 these others are Wireless USB and TCP/IP, but seems Bluetooth and
74 many devices are present and the length of their beacons.
76 Devices have a MAC (fixed, 48 bit address) and a device (changeable, 16
77 bit address) and send periodic beacons to advertise themselves and pass
78 info on what they are and do. They advertise their capabilities and a
85 *UWB*: the Ultra-Wide-Band stack -- manages the radio and
[all …]
|
| D | gadget_serial.txt | 7 License and Disclaimer
9 This program is free software; you can redistribute it and/or
24 This document and the gadget serial driver itself are
38 This document assumes that you are familiar with Linux and
39 Windows and know how to configure and build Linux kernels, run
40 standard utilities, use minicom and HyperTerminal, and work with
41 USB and serial devices. It also assumes you configure the Linux
42 gadget and usb drivers as modules.
44 With version 2.3 of the driver, major and minor device nodes are
46 sysfs in /sys, and use "mdev" (in Busybox) or "udev" to make the
[all …]
|
| D | gadget_configfs.txt | 16 A USB Linux Gadget is a device which has a UDC (USB Device Controller) and can
27 and which functions each configuration will provide.
76 Each gadget needs to have its vendor id <VID> and product id <PID> specified:
81 A gadget also needs its serial number, manufacturer and product strings.
101 where <name> can be any string which is legal in a filesystem and the
131 where <name> corresponds to one of allowed function names and instance name
149 configurations specified and a number of functions available. What remains
168 configurations and functions.
226 where <config name>.<number> specify the configuration and <function> is
247 and remove the configurations
[all …]
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | nfs-rdma.txt | 7 Author: NetApp and Open Grid Computing
15 - Check RDMA and NFS Setup
21 This document describes how to install and setup the Linux NFS/RDMA client
22 and server software.
29 the full Connectathon test suite and operates over both Infiniband and iWARP
52 Ammasso AMS1100 iWARP adapter, and the Chelsio cxgb3 iWARP adapter.
54 - Install a Linux distribution and tools
56 The first kernel release to contain both the NFS/RDMA client and server was
57 Linux 2.6.25 Therefore, a distribution compatible with this and subsequent
80 Uncompress the package and follow the installation instructions.
[all …]
|
| D | nfsd-admin-interfaces.txt | 17 bound (and listening, for tcp) socket, or
22 udp and one tcp listener at port 2049 (see nfsd_init_socks).
24 On startup, nfsd and lockd grace periods start.
26 nfsd is shut down by a write of 0 to nfsd/threads. All locks and state
29 Between startup and shutdown, the number of threads may be adjusted up
33 For more detail about files under nfsd/ and what they control, see
39 Note that the rpc server requires the caller to serialize addition and
40 removal of listening sockets, and startup and shutdown of the server.
|
| D | rpc-cache.txt | 7 The caching replaces the old exports table and allows for
11 quite possibly very different in content and use. There is a corpus
16 - mapping from client name and filesystem to export options
19 - mappings between local UID/GID and remote UID/GID for sites that
26 - allowing an EXPIRED time on cache items, and removing
27 items after they expire, and are no longer in-use.
31 cache entries, and replaying those requests when the cache entry
42 It will also contain a key and some content.
43 Each cache element is reference counted and contains
44 expiry and update times for use in cache management.
[all …]
|
| /linux-4.1.27/Documentation/ |
| D | intel_txt.txt | 13 o Measurement and verification of launched environment
15 Intel TXT is part of the vPro(TM) brand and is also available some
17 based on the Q35, X38, Q45, and Q43 Express chipsets (e.g. Dell
18 Optiplex 755, HP dc7800, etc.) and mobile systems based on the GM45,
19 PM45, and GS45 Express chipsets.
40 uses Intel TXT to perform a measured and verified launch of an OS
48 w/ TXT support since v3.2), and now Linux kernels.
54 While there are many products and technologies that attempt to
57 Measurement Architecture (IMA) and Linux Integrity Module interface
62 starting at system reset and requires measurement of all code
[all …]
|
| D | workqueue.txt | 21 is needed and the workqueue (wq) API is the most commonly used
27 queue is called workqueue and the thread is called worker.
38 worker thread per CPU and a single threaded (ST) wq had one worker
41 wq users over the years and with the number of CPU cores continuously
46 provided was unsatisfactory. The limitation was common to both ST and
53 The tension between the provided level of concurrency and resource
55 choosing to use ST wq for polling PIOs and accepting an unnecessary
70 * Automatically regulate worker pool and level of concurrency so that
82 item pointing to that function and queue that work item on a
91 subsystems and drivers queue work items on and the backend mechanism
[all …]
|
| D | unshare.txt | 6 be used, its interface specification, design, implementation and
29 special resources and mechanisms to maintain these "threads". The Linux
30 kernel, in a clever and simple manner, does not make distinction
31 between processes and "threads". The kernel allows processes to share
32 resources and thus they can achieve legacy "threads" behavior without
33 requiring additional data structures and mechanisms in the kernel. The
65 such as per-user and/or per-security context instance of /tmp, /var/tmp or
72 can benefit from setting up private namespaces at login and
73 polyinstantiating /tmp, /var/tmp and other directories deemed
76 2.2 unsharing of virtual memory and/or open files
[all …]
|
| D | rpmsg.txt | 3 Note: this document describes the rpmsg bus and how to write rpmsg drivers.
14 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
16 and each of the other three cores (two M3 cores and a DSP) is running
19 Typically AMP remote processors employ dedicated DSP codecs and multimedia
20 hardware accelerators, and therefore are often used to offload CPU-intensive
38 system's physical memory and other sensitive hardware resources (e.g. on
39 OMAP4, remote cores and hardware accelerators may have direct access to the
44 exploiting remote bugs, and by that taking over the system, it is often
46 it can send messages on, and if possible, minimize how much control
51 and have a local ("source") rpmsg address, and remote ("destination") rpmsg
[all …]
|
| D | pnp.txt | 1 Linux Plug and Play Documentation
10 Plug and Play provides a means of detecting and setting resources for legacy or
11 otherwise unconfigurable devices. The Linux Plug and Play Layer provides these
18 The Linux Plug and Play user interface provides a means to activate PnP devices
19 for legacy and user level drivers that do not support Linux Plug and Play. The
26 resources - displays currently allocated resources and allows resource changes
93 The Unified Plug and Play Layer
95 All Plug and Play drivers, protocols, and services meet at a central location
96 called the Plug and Play Layer. This layer is responsible for the exchange of
97 information between PnP drivers and PnP protocols. Thus it automatically
[all …]
|
| D | CodingStyle | 5 linux kernel. Coding style is very personal, and I won't _force_ my
7 able to maintain, and I'd prefer it for most other things too. Please
11 and NOT read it. Burn them, it's a great symbolic gesture.
18 Tabs are 8 characters, and thus indentations are also 8 characters.
20 characters deep, and that is akin to trying to define the value of PI to
24 a block of control starts and ends. Especially when you've been looking
29 the code move too far to the right, and makes it hard to read on a
31 more than 3 levels of indentation, you're screwed anyway, and should fix
34 In short, 8-char indents make things easier to read, and have the added
39 to align the "switch" and its subordinate "case" labels in the same column
[all …]
|
| D | HOWTO | 5 instructions on how to become a Linux kernel developer and how to learn
22 and hints on how to work with the community. It will also try to
29 are not a good substitute for a solid C education and/or years of
31 - "The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
33 - "C: A Reference Manual" by Harbison and Steele [Prentice Hall]
35 The kernel is written using GNU C and the GNU toolchain. While it
40 divisions and floating point are not allowed. It can sometimes be
42 and the extensions that it uses, and unfortunately there is no
48 high standards for coding, style and procedure. These standards have
50 such a large and geographically dispersed team. Try to learn as much as
[all …]
|
| D | irqflags-tracing.txt | 5 the "irq-flags tracing" feature "traces" hardirq and softirq state, in
11 and CONFIG_PROVE_RW_LOCKING to be offered by the generic lock debugging
12 code. Otherwise only CONFIG_PROVE_MUTEX_LOCKING and
20 rather straightforward and risk-free manner.
25 - add and enable TRACE_IRQFLAGS_SUPPORT in their arch level Kconfig file
27 and then a couple of functional changes are needed as well to implement
33 irq-flags state, and complains loudly (and turns itself off) if the
37 fix and repeat. Once the system has booted up and works without a
41 excluded from the irq-tracing [and lock validation] mechanism via
45 implementation in an architecture: lockdep will detect that and will
|
| D | printk-formats.txt | 18 format specifier of its largest possible type and explicitly cast to it.
40 For printing symbols and function pointers. The 'S' and 's' specifiers
45 The 'B' specifier results in the symbol name with offsets and should be
48 when tail-call's are used and marked with the noreturn GCC attribute.
50 On ia64, ppc64 and parisc64 architectures function pointers are
51 actually function descriptors which must first be resolved. The 'F' and
52 'f' specifiers perform this resolution and then provide the same
53 functionality as the 'S' and 's' specifiers.
70 For printing struct resources. The 'R' and 'r' specifiers result in a
78 For printing a phys_addr_t type (and its derivatives, such as
[all …]
|
| D | SubmitChecklist | 7 These are all above and beyond the documentation that is provided in
8 Documentation/SubmittingPatches and elsewhere regarding submitting Linux
16 2: Builds cleanly with applicable or modified CONFIG options =y, =m, and
45 10: Use 'make checkstack' and 'make namespacecheck' and fix any problems
52 mandocs' to check the kernel-doc and fix any issues.
57 and CONFIG_DEBUG_OBJECTS_RCU_HEAD all simultaneously enabled.
59 13: Has been build- and runtime tested with and without CONFIG_SMP and
62 14: If the patch affects IO/Disk, etc: has been tested with and without
81 21: Has been checked with injection of at least slab and page-allocation
89 finding bugs like "warning: comparison between signed and unsigned".
[all …]
|
| D | phy.txt | 5 and how-to-use.
11 such as serialization, de-serialization, encoding, decoding and is responsible
13 controllers have PHY functionality embedded into it and others use an external
18 all over the Linux kernel to drivers/phy to increase code re-use and for
39 of_phy_provider_register and devm_of_phy_provider_register macros can be used to
40 register the phy_provider and it takes device and of_xlate as
48 devm_of_phy_provider_unregister and of_phy_provider_unregister can be used to
62 the device pointer and phy ops.
64 init, exit, power_on and power_off.
67 can use phy_set_drvdata() after creating the PHY and use phy_get_drvdata() in
[all …]
|
| D | CodeOfConflict | 5 to "traditional" ways of developing software. Your code and ideas
6 behind it will be carefully reviewed, often resulting in critique and
11 to create the most robust operating system kernel ever, and we do not
12 want to do anything to cause the quality of submission and eventual
18 <tab@lists.linux-foundation.org>, or the individual members, and they
20 information on who is on the Technical Advisory Board and what their
24 As a reviewer of code, please strive to keep things civil and focused on
25 the technical issues involved. We are all humans, and frustrations can
27 words of Bill and Ted, "Be excellent to each other."
|
| D | IRQ-domain.txt | 25 The irq_alloc_desc*() and irq_free_desc*() APIs provide allocation of
30 The irq_domain library adds mapping between hwirq and IRQ numbers on
36 specifiers to hwirq numbers, and can be easily extended to support
40 An interrupt controller driver creates and registers an irq_domain by
47 between hwirq and IRQ numbers. Mappings are added to the irq_domain
48 by calling irq_create_mapping() which accepts the irq_domain and a
51 the hwirq, and call the .map() callback so the driver can perform any
61 If the driver has the Linux IRQ number or the irq_data pointer, and
67 to Linux irq, and each mechanism uses a different allocation function.
76 the hwirq, and the IRQ number is stored in the table.
[all …]
|
| D | pi-futex.txt | 10 - even in the slowpath, the system call and scheduling pattern is very
24 determinism and well-bound latencies. Even in the worst-case, PI will
36 between 1:10 and 1:100. Lockless is hard, and the complexity of lockless
46 combined with medium-prio construct-audio-data threads and low-prio
47 display-colory-stuff threads. Add video and decoding to the mix and
51 unavoidable fact of life, and once we accept that multi-task userspace
65 Currently (without PI), if a high-prio and a low-prio task shares a lock
68 (i.e. all critical sections are short in duration and only execute a
71 could preempt the low-prio task while it holds the shared lock and
72 executes the critical section, and could delay it indefinitely.
[all …]
|
| D | iostats.txt | 4 Since 2.4.20 (and some versions before, with patches), and 2.5.45,
6 activity. Tools such as sar and iostat typically interpret these and do
12 places: one is in the file /proc/diskstats, and the other is within
16 Both /proc/diskstats and sysfs use the same source for the information
17 and so should not differ.
46 /proc/diskstats, the eleven fields will be preceded by the major and
47 minor device numbers, and device name. Each of these formats provides
51 overflow and wrap). Yes, these are (32-bit or 64-bit) unsigned long
52 (native word size) numbers, and on a very busy or long-lived system they
58 system-wide stats you'll have to find all the devices and sum them all up.
[all …]
|
| D | remoteproc.txt | 9 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
11 configuration, and each of the other three cores (two M3 cores and a DSP)
20 handlers, and then all rpmsg drivers will then just work
21 (for more information about the virtio-based rpmsg bus and its drivers,
24 just need to publish what kind of virtio devices do they support, and then
35 Returns 0 on success, and an appropriate error value otherwise.
44 this function will just decrement the power refcount and exit,
51 rproc_shutdown() returns, and users can still use it with a subsequent
63 /* let's power on and boot our remote processor */
67 * something went wrong. handle it and leave.
[all …]
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | configfs-spear-pcie-gadget | 8 as device and then program its various registers to configure it
18 link ... used to enable ltssm and read its status.
19 int_type ...used to configure and read type of supported
21 no_of_msi ... used to configure number of MSI vector needed and
23 inta ... write 1 to assert INTA and 0 to de-assert.
25 vendor_id ... used to write and read vendor id (hex)
26 device_id ... used to write and read device id (hex)
27 bar0_size ... used to write and read bar0_size
28 bar0_address ... used to write and read bar0 mapped area in hex.
29 bar0_rw_offset ... used to write and read offset of bar0 where
[all …]
|
| D | sysfs-block-zram | 5 The disksize file is read-write and specifies the disk size
14 The initstate file is read-only and shows the initialization
21 The reset file is write-only and allows resetting the
29 The num_reads file is read-only and specifies the number of
36 The num_writes file is read-only and specifies the number of
43 The invalid_io file is read-only and specifies the number of
50 The failed_reads file is read-only and specifies the number of
57 The failed_writes file is read-only and specifies the number of
64 The max_comp_streams file is read-write and specifies the
72 The comp_algorithm file is read-write and lets to show
[all …]
|
| D | sysfs-class-power | 6 This file is writeable and can be used to set the current
10 and once the counter drops out of considerable bounds, take
18 This file is writeable and can be used to set the assumed
27 This entry shows and sets the maximum time the max14577
30 will drop to 0 A) and will trigger interrupt.
41 This entry shows and sets the maximum time the max77693
44 will drop to 0 A) and will trigger interrupt.
55 This entry shows and sets the charging current threshold for
58 interrupt and start top-off charging mode.
70 This entry shows and sets the maximum time the max77693
[all …]
|
| /linux-4.1.27/Documentation/scsi/ |
| D | FlashPoint.txt | 15 drivers and information will be available on October 15th at
20 development and provided technical support for our host adapters for several
21 years, and are pleased to now make our FlashPoint products available to this
27 SPARC, SGI MIPS, Motorola 68k, Digital Alpha AXP and Motorola PowerPC
29 System, Emacs, and TCP/IP networking. Further information is available at
30 http://www.linux.org and http://www.ssc.com/.
35 and file server environments, are available in narrow, wide, dual channel,
36 and dual channel wide versions. These adapters feature SeqEngine
37 automation technology, which minimizes SCSI command overhead and reduces
43 producer of RAID technology and network management products. The company
[all …]
|
| D | ufs.txt | 25 embedded and removable flash memory based storage in mobile
26 devices such as smart phones and tablet computers. The specification
29 physical layer and MIPI Unipro as the link layer.
33 For UFS version 1.0 and 1.1 the target performance is as follows,
39 * High random IOPs and low latency
53 Task Manager and Device manager. The UFS interface is designed to be
55 protocol for versions 1.0 and 1.1 of UFS protocol layer.
56 UFS supports subset of SCSI commands defined by SPC-4 and SBC-3.
60 * Device manager: It handles device level operations and device
62 device power management operations and commands to Interconnect
[all …]
|
| D | ChangeLog.lpfc | 12 for fabric and nport logins out of lpfc_cmpl_els_flogi.
18 PRLI...) are errored back and scan() terminates.
28 find command in both TX and TX completion queues. Return ERROR
62 - kill struct lpfc_scsi_dma_buf and embedded the two members
67 ever used by the driver, just reported to userspace (and that in
72 32bit and 64bit defines on some archs.
82 * Revise TRANSPORT_PATCHES_V2 so that lpfc_target is removed and
84 * Changed RW attributes of scan_down, max_luns and fcp_bind_method
88 list and marked for ADISC.
102 * Use DMA_64BIT_MASK and DMA_32BIT_MASK defines instead of
[all …]
|
| D | BusLogic.txt | 1 BusLogic MultiMaster and FlashPoint SCSI Driver for Linux
19 BusLogic, Inc. designed and manufactured a variety of high performance SCSI
23 supported by this driver originated under the BusLogic name and so that name is
24 retained in the source code and documentation.
26 This driver supports all present BusLogic MultiMaster Host Adapters, and should
29 costly and rely on the host CPU, rather than including an onboard processor.
31 well and have very low command latency. BusLogic has recently provided me with
32 the FlashPoint Driver Developer's Kit, which comprises documentation and freely
34 is the library of code that runs on the host CPU and performs functions
40 to achieve the full performance that BusLogic SCSI Host Adapters and modern
[all …]
|
| D | osst.txt | 7 It is intended to help advanced users to understand the role of osst and to
8 get them started using (and maybe debugging) it.
23 Nevertheless, the OnStream tapes are nice pieces of hardware and therefore
25 The driver is free software. It's released under the GNU GPL and planned to
31 The osst is a new high-level SCSI driver, just like st, sr, sd and sg. It
34 are character devices with major no 206 and minor numbers like the /dev/stX
37 The driver started being a copy of st and as such, the osst devices'
44 that it used the same kernel structures and the same device node as st.
47 st and osst can coexist, each only accessing the devices it can support by
55 Compile your kernel and install the modules.
[all …]
|
| D | LICENSE.qla4xxx | 5 You may modify and redistribute the device driver code under the
17 Everyone is permitted to copy and distribute verbatim copies
23 freedom to share and change it. By contrast, the GNU General Public
24 License is intended to guarantee your freedom to share and change free
27 Foundation's software and to any other program whose authors commit to
34 have the freedom to distribute copies of free software (and charge for
37 in new free programs; and that you know you can do these things.
50 We protect your rights with two steps: (1) copyright the software, and
52 distribute and/or modify the software.
54 Also, for each author's protection and ours, we want to make certain
[all …]
|
| D | LICENSE.qla2xxx | 5 You may modify and redistribute the device driver code under the
18 Everyone is permitted to copy and distribute verbatim copies
24 freedom to share and change it. By contrast, the GNU General Public
25 License is intended to guarantee your freedom to share and change free
28 Foundation's software and to any other program whose authors commit to
35 have the freedom to distribute copies of free software (and charge for
38 in new free programs; and that you know you can do these things.
51 We protect your rights with two steps: (1) copyright the software, and
53 distribute and/or modify the software.
55 Also, for each author's protection and ours, we want to make certain
[all …]
|
| D | scsi-generic.txt | 7 drivers along with sd, st and sr (disk, tape and CDROM respectively). Sg
8 is more generalized (but lower level) than its siblings and tends to be
10 Thus sg is used for scanners, CD writers and reading audio CDs digitally
15 and examples.
25 - sg version 3 found in the lk 2.4 series (and the lk 2.5 series).
35 The LDP renders documents in single and multiple page HTML, postscript
36 and pdf. This document can also be found at:
45 and in the LDP archives.
49 and edit this file (removing its changelog for example) before placing it
50 in /usr/include/scsi/sg.h . Driver debugging information and other notes
[all …]
|
| D | cxgb3i.txt | 7 series of products) support iSCSI acceleration and iSCSI Direct Data Placement
9 as CRC computation and verification, and direct DMA to the final host memory
12 - iSCSI PDU digest generation and verification
14 On transmitting, Chelsio S3 h/w computes and inserts the Header and
16 On receiving, Chelsio S3 h/w computes and verifies the Header and
26 - PDU Transmit and Recovery
29 from the host driver, computes and inserts the digests, decomposes
30 the PDU into multiple TCP segments if necessary, and transmit all
35 segments, separating the header and data, calculating and verifying
40 The cxgb3i driver interfaces with open-iscsi initiator and provides the iSCSI
|
| D | advansys.txt | 2 RISC-based, Bus-Mastering, Fast (10 Mhz) and Ultra (20 Mhz) Narrow
3 (8-bit transfer) SCSI Host Adapters for the ISA, EISA, VL, and PCI
4 buses and RISC-based, Bus-Mastering, Ultra (20 Mhz) Wide (16-bit
9 cache and board LRAM. A CDB is a single SCSI command. The driver
55 ABP3950U2W - Bus-Master PCI LVD/Ultra2-Wide and Ultra-Wide (253 CDB)
58 Driver Compile Time Options and Debugging
69 detect problems with the driver and facilitate fixing these
75 Enabling this option adds tracing functions to the driver and the
78 of the driver execution image and add overhead to the execution of
85 If the driver is loaded at boot time and the LILO Driver Option
[all …]
|
| D | osd.txt | 5 allocation, placement, and accessing of variable-size data-storage containers,
6 called objects. Objects are intended to contain operating system and application
8 integral part of the object and provide metadata about the object. The standard
23 This is a SCSI ULD that registers for OSD type devices and provides a testing
28 Is an OSD based Linux file system. It uses the osd-initiator and osd-uld,
40 Files and Folders
55 Makefile For both in-tree and out-of-tree compilation
62 But even though, it should be intuitive and easy to use. Perhaps over time an
67 and initializes some global pools. This should be done once per scsi_device
72 OSD commands encoding, execution, and decoding of results:
[all …]
|
| /linux-4.1.27/arch/arm/mm/ |
| D | abort-lv4t.S | 22 bic r1, r1, #1 << 11 | 1 << 10 @ clear bits 11 and 10 of FSR
31 and r7, r8, #15 << 24
61 and r6, r8, r7
62 and r9, r8, r7, lsl #1
64 and r9, r8, r7, lsl #2
66 and r9, r8, r7, lsl #3
70 and r6, r6, #15 @ r6 = no. of registers to transfer.
71 and r9, r8, #15 << 16 @ Extract 'n' from instruction
83 and r9, r8, #0x00f @ get Rm / low nibble of immediate value
89 and r9, r8, #15 << 16 @ Extract 'n' from instruction
[all …]
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | squashfs.txt | 5 It uses zlib, lz4, lzo, or xz compression to compress files, inodes and
6 directories. Inodes in the system are very small and all blocks are packed to
11 use (i.e. in cases where a .tar.gz file may be used), and in constrained
37 "." and ".." in readdir: yes no
44 Squashfs compresses data, inodes and directories. In addition, inode and
45 directory data are highly compacted, and packed on byte boundaries. Each
47 file type, i.e. regular file, directory, symbolic link, and block/char device
54 create populated squashfs filesystems. This and other squashfs utilities
95 the source directory, and checked for duplicates. Once all file data has been
96 written the completed inode, directory, fragment, export, uid/gid lookup and
[all …]
|
| D | porting | 7 sb_set_blocksize() and sb_min_blocksize().
16 New methods: ->alloc_inode() and ->destroy_inode().
31 Add foo_alloc_inode() and foo_destroy_inode() - the former should allocate
32 foo_inode_info and return the address of ->vfs_inode, the latter should free
35 Make them ->alloc_inode and ->destroy_inode in your super_operations.
38 typically between calling iget_locked() and unlocking the inode.
47 ->read_super() is no more. Ditto for DECLARE_FSTYPE and DECLARE_FSTYPE_DEV.
50 success and negative number in case of error (-EINVAL unless you have more
63 Replace DECLARE_FSTYPE... with explicit initializer and have ->get_sb set as
73 same (i.e. parents and victim are locked, etc.).
[all …]
|
| D | overlayfs.txt | 25 only be unique when combined with st_dev, and both of these can change
26 over the lifetime of a non-directory object. Many applications and
27 tools ignore these values and will not be affected.
29 Upper and Lower
33 and a 'lower' filesystem. When a name exists in both filesystems, the
38 It would be more correct to refer to an upper and lower 'directory
40 directory trees to be in the same filesystem and there is no
44 The lower filesystem can be any filesystem supported by Linux and does
46 overlayfs. The upper filesystem will normally be writable and if it
47 is it must support the creation of trusted.* extended attributes, and
[all …]
|
| D | autofs4-mount-control.txt | 16 expire timeout and requesting expire checks. As is explained below,
24 getcwd(2) and the proc file system /proc/<pid>/cwd, no longer works
31 because autofs direct mounts and the implementation of "on demand mount
32 and expire" of nested mount trees have the file system mounted directly
37 a direct mount in disguise) and indirect.
39 Here is a master map with direct and indirect map entries:
44 and the corresponding map files:
50 and so on.
56 and so on.
58 For the above indirect map an autofs file system is mounted on /test and
[all …]
|
| D | xfs-self-describing-metadata.txt | 9 structures and indexes on disk and the algorithms for iterating them are
14 metadata is the allocation group headers (SB, AGF, AGFL and AGI), while all
17 validating and repairing the structure, there are limits to what they can
18 verify, and this in turn limits the supportable size of an XFS filesystem.
20 For example, it is entirely possible to manually use xfs_db and a bit of
29 to analyse and so that analysis blows out towards weeks/months of forensic work.
30 Most of the analysis work is slow and tedious, so as the amount of analysis goes
32 concern for supporting PB scale filesystems is minimising the time and effort
42 you can't look at a single metadata block in isolation and say "yes, it is
43 supposed to be there and the contents are valid".
[all …]
|
| D | sharedsubtree.txt | 25 and versioned filesystem.
39 2a) A shared mount can be replicated to as many mountpoints and all the
48 so the sample 'smount' program is no longer needed and has been
53 and the contents of both the mounts remain identical.
76 2b) A slave mount is like a shared mount except that mount and umount events
89 the new mount at /tmp becomes a shared mount and it is a replica of
126 let's say we have a mount at /mnt and we make is unbindable
165 So when a CD is inserted and mounted at /cdrom that mount gets
199 could have his/her own namespace and tailor it to his/her
217 and if /usr has a versioning filesystem mounted, then that
[all …]
|
| D | 00-INDEX | 10 - info and mount options for the Acorn Advanced Disc Filing System.
12 - info and examples for the distributed AFS (Andrew File System) fs.
14 - info and mount options for the Amiga Fast File System.
30 - directory containing CIFS filesystem documentation and example code.
34 - directory containing configfs documentation and example code.
59 - info, mount options and specifications for the Ext2 filesystem.
61 - info, mount options and specifications for the Ext3 filesystem.
63 - info, mount options and specifications for the Ext4 filesystem.
65 - info and mount options for the F2FS filesystem.
83 - info and mount options for the OS/2 HPFS.
[all …]
|
| D | path-lookup.txt | 1 Path walking and name lookup locking
9 path string. Then repeating the lookup from the child dentry and finding its
10 child with the next element, and so on.
12 Since it is a frequent operation for workloads like multiuser environments and
16 Prior to 2.5.10, dcache_lock was acquired in d_lookup (dcache hash lookup) and
18 algorithm changed this by holding the dcache_lock at the beginning and walking
21 the lock hold time significantly and affects performance in large SMP machines.
25 All the above algorithms required taking a lock and reference count on the
27 next path element. This is inefficient and unscalable. It is inefficient
28 because of the locks and atomic operations required for every dentry element
[all …]
|
| D | ubifs.txt | 12 To make it more clear, here is a small comparison of MTD devices and
15 1 MTD devices represent flash devices and they consist of eraseblocks of
19 eraseblock, write to some offset within an eraseblock, and erase a whole
21 block and write a whole block.
25 typically 100K-1G for SLC NAND and NOR flashes, and 1K-10K for MLC
27 5 Eraseblocks may become bad (only on NAND flashes) and software should
36 found in drivers/mtd/ubi. UBI is basically a volume management and
41 limitations like wear and bad blocks (items 4 and 5 in the above list).
44 very different and incompatible to JFFS2. The following are the main
47 * JFFS2 works on top of MTD devices, UBIFS depends on UBI and works on
[all …]
|
| D | ramfs-rootfs-initramfs.txt | 1 ramfs, rootfs and initramfs
10 mechanisms (the page cache and dentry cache) as a dynamically resizable
23 dentries and page cache as usual, but there's nowhere to write them to.
33 ramfs and ramdisk:
37 an area of RAM and used it as backing store for a filesystem. This block
40 fake block device into the page cache (and copying changes back out), as well
41 as creating and destroying dentries. Plus it needed a filesystem driver
42 (such as ext2) to format and interpret this data.
44 Compared to ramfs, this wastes memory (and memory bus bandwidth), creates
45 unnecessary work for the CPU, and pollutes the CPU caches. (There are tricks
[all …]
|
| D | inotify.txt | 17 the file and thus, worse, pins the mount. Dnotify is therefore infeasible
25 more fd's than are feasible to manage, and more fd's than are optimally
26 select()-able. Yes, root can bump the per-process fd limit and yes, users
27 can use epoll, but requiring both is a silly and extraneous requirement.
30 want: Users initialize inotify, once, and add n watches, requiring but one
31 fd and no twiddling with fd limits. Initializing an inotify instance two
33 cleanly--and we can, the idr layer makes stuff like this trivial--then we
38 fd returns all watch events and also any potential out-of-band data. If
41 - There would be no way to get event ordering. Events on file foo and
47 - We'd have to maintain n fd's and n internal queues with state,
[all …]
|
| D | exofs.txt | 5 exofs is a file system that uses an OSD and exports the API of a normal Linux
6 file system. Users access exofs like any other local file system, and exofs
11 time attributes and more. Each object is addressed by a 64bit ID, and is
13 attached to it, which are integral part of the object and provide metadata about
31 1. Download and compile exofs and open-osd initiator:
42 module. Use whatever parameters you compiled your Kernel with and
46 2. Get the OSD initiator and target set up properly, and login to the target.
64 performed and a clean file system will be created in the specified pid,
68 If pid already exists, it will be deleted and a new one will be created in
85 do-exofs format - an example of how to format and mkfs a new exofs.
[all …]
|
| D | ceph.txt | 5 performance, reliability, and scalability.
11 * High availability and reliability. No single point of failure.
21 In contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely
23 separates data and metadata management into independent server
24 clusters, similar to Lustre. Unlike Lustre, however, metadata and
28 across storage nodes in large chunks to distribute workload and
32 system extremely efficient and scalable.
37 and can tolerate arbitrary (well, non-Byzantine) node failures. The
41 directories, allowing entire directories of dentries and inodes to be
43 extremely large directories can be fragmented and managed by
[all …]
|
| /linux-4.1.27/Documentation/networking/ |
| D | README.sb1000 | 17 to configure the cable modem and network interface (usually called "cm0");
18 and
55 and to say "M" to the sb1000 driver. Also say "Y" or "M" to all the standard
56 networking questions to get TCP/IP and PPP networking support.
63 3.) Build and install the kernel and modules as usual.
68 of "pnpdump" to a file and editing this file to set the correct I/O ports,
69 IRQ, and DMA settings for all your PnP cards. Make sure none of the settings
72 errors and fix as necessary. (As an aside, I use I/O ports 0x110 and
73 0x310 and IRQ 11 for my SB1000 card and these work well for me. YMMV.)
78 the others referenced above. As root, unpack it into a temporary directory and
[all …]
|
| D | netif-msg.txt | 9 The design of the debugging message interface was guided and
11 to understand the history and evolution in order to understand current
12 practice and relate it to older driver source code.
16 level ranged from 0 to 7, and monotonically increased in verbosity.
24 3 Interface starts and stops, including normal status messages
25 4 Tx and Rx frame error messages, and abnormal driver operation
27 6 Status on each completed Tx packet and received Rx packets
28 7 Initial contents of Tx and Rx packets
31 e.g. "lance_debug", so that a kernel symbolic debugger could locate and
33 were consistently renamed to "debug" and allowed to be set as a module
[all …]
|
| D | README.ipw2100 | 32 Intel wireless LAN adapters are engineered, manufactured, tested, and
33 quality checked to ensure that they meet all necessary local and
35 are designated and/or marked to ship into. Since wireless LANs are
37 satellites, and other licensed and unlicensed devices, it is sometimes
38 necessary to dynamically detect, avoid, and limit usage to avoid
40 provide test data to prove regional and local compliance to regional and
42 product is granted. Intel's wireless LAN's EEPROM, firmware, and
44 radio operation and to ensure electromagnetic compliance (EMC). These
46 channel scanning, and human exposure.
50 adapters (e.g., the EEPROM and firmware). Furthermore, if you use any
[all …]
|
| D | altera_tse.txt | 6 using the SGDMA and MSGDMA soft DMA IP components. The driver uses the
9 and tested with ARM and NIOS processor hosts seperately. The anticipated use
10 cases are simple communications between an embedded system and an external peer
11 for status and simple configuration of the embedded system.
13 For more information visit www.altera.com and www.rocketboards.org. Support
14 forums for the driver may be found on www.rocketboards.org, and a design used
18 The Triple-Speed Ethernet, SGDMA, and MSGDMA components are all soft IP
19 components that can be assembled and built into an FPGA using the Altera
20 Quartus toolchain. Quartus 13.1 and 14.0 were used to build the design that
22 device tree for the driver, and may be found at rocketboards.org.
[all …]
|
| D | LICENSE.qlge | 4 You may modify and redistribute the device driver code under the
16 Everyone is permitted to copy and distribute verbatim copies
22 freedom to share and change it. By contrast, the GNU General Public
23 License is intended to guarantee your freedom to share and change free
26 Foundation's software and to any other program whose authors commit to
33 have the freedom to distribute copies of free software (and charge for
36 in new free programs; and that you know you can do these things.
49 We protect your rights with two steps: (1) copyright the software, and
51 distribute and/or modify the software.
53 Also, for each author's protection and ours, we want to make certain
[all …]
|
| D | LICENSE.qlcnic | 4 You may modify and redistribute the device driver code under the
16 Everyone is permitted to copy and distribute verbatim copies
22 freedom to share and change it. By contrast, the GNU General Public
23 License is intended to guarantee your freedom to share and change free
26 Foundation's software and to any other program whose authors commit to
33 have the freedom to distribute copies of free software (and charge for
36 in new free programs; and that you know you can do these things.
49 We protect your rights with two steps: (1) copyright the software, and
51 distribute and/or modify the software.
53 Also, for each author's protection and ours, we want to make certain
[all …]
|
| D | README.ipw2200 | 7 Note: The Intel(R) PRO/Wireless 2915ABG Driver for Linux and Intel(R)
45 Intel wireless LAN adapters are engineered, manufactured, tested, and
46 quality checked to ensure that they meet all necessary local and
48 are designated and/or marked to ship into. Since wireless LANs are
50 satellites, and other licensed and unlicensed devices, it is sometimes
51 necessary to dynamically detect, avoid, and limit usage to avoid
53 provide test data to prove regional and local compliance to regional and
55 product is granted. Intel's wireless LAN's EEPROM, firmware, and
57 radio operation and to ensure electromagnetic compliance (EMC). These
59 channel scanning, and human exposure.
[all …]
|
| D | phy.txt | 12 cable), and provides a register interface to allow drivers to determine what
13 settings were chosen, and to configure what settings are allowed.
15 While these devices are distinct from the network devices, and conform to a
18 amounts of redundant code. Also, on embedded systems with multiple (and
22 Since the PHYs are devices, and the management busses through which they are
28 3) Speed development time for new network drivers, and for new systems
41 1) read and write functions must be implemented. Their prototypes are:
46 mii_id is the address on the bus for the PHY, and regnum is the register
55 driver needs, setup the mii_bus structure, and register with the PAL using
59 4) Like any driver, the device_driver structure must be configured, and init
[all …]
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.sc | 3 DataCommute/BRI and TeleCommute/BRI adapters only and any other use is
8 Speaking of guarantees, THIS IS BETA SOFTWARE and as such contains
9 bugs and defects either known or unknown. Use this software at your own
12 our own option and without warranty. If you choose to assume all and
27 1.2 What is different between this driver and previous drivers?
32 2.1 Unpacking and installing the driver
39 3. Beta Change Summaries and Miscellaneous Notes
45 upon ISDN4Linux available separately or as included in Linux 2.0 and later.
47 type including DataCommute/BRI, DataCommute/PRI and TeleCommute/BRI for a
49 source form and needs to be complied before it can be used. It has been
[all …]
|
| D | README.diversion | 2 the isdn4linux and the HiSax module for passive cards.
3 Active cards, TAs and cards using a own or other driver than the HiSax
7 The diversion kernel interface and controlling tool divertctrl were written
11 This program is free software; you can redistribute it and/or modify
31 2. Required hard- and software
33 3. Compiling, installing and loading/unloading the module
34 Tracing calling and diversion information
36 4. Tracing calling and diversion information
44 The i4l diversion services offers call forwarding and logging normally
58 the checking process is finished and the rule matching will be applied
[all …]
|
| D | README.hysdn | 11 This program is free software; you can redistribute it and/or modify
38 6. Where to get additional info and help
44 PCI isdn cards Champ, Ergo and Metro. To enable support for this cards
45 enable ISDN support in the kernel config and support for HYSDN cards in
46 the active cards submenu. The driver may only be compiled and used if
47 support for loadable modules and the process filesystem have been enabled.
52 handlers for various protocols like ppp and others as well as config info
53 and firmware may be fetched from Hypercopes WWW-Site www.hypercope.de.
59 active AVM cards and in fact uses the same module.
64 The module has no command line parameters and auto detects up to 10 cards
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | fsl,ssi.txt | 13 - cell-index: The SSI, <0> = SSI1, <1> = SSI2, and so on.
14 - reg: Offset and length of the register set for the device.
15 - interrupts: <a b> where a is the interrupt number and b is a
16 field that represents an encoding of the sense and
29 - fsl,fifo-depth: The number of elements in the transmit and receive FIFOs.
33 mode. In this mode, pins SRCK, STCK, SRFS, and STFS must
35 SRCK and SRFS are ignored. Asynchronous mode allows
36 playback and capture to use different sample sizes and
37 sample rates. Some drivers may require that SRCK and STCK
38 be connected together, and SRFS and STFS be connected
[all …]
|
| D | fsl-sai.txt | 5 serial interfaces with frame synchronization such as I2S, AC97, TDM, and
13 - reg : Offset and length of the register set for the device.
17 - clock-names : Must include the "bus" for register access and
18 "mclk1", "mclk2", "mclk3" for bit clock and frame
23 - dma-names : Two dmas have to be defined, "tx" and "rx".
41 with Rx) which means both the transimitter and the
42 receiver will send and receive data by following
43 receiver's bit clocks and frame sync clocks.
47 means both transimitter and receiver will send and
48 receive data by following their own bit clocks and
[all …]
|
| D | samsung-i2s.txt | 8 secondary fifo, s/w reset control and internal mux for root clk src.
12 and 7.1 channel TDM support for playback. TDM (Time division multiplexing)
16 with only external dma and more no.of root clk sampling frequencies.
21 - reg: physical base address of the controller and length of memory mapped
23 - dmas: list of DMA controller phandle and DMA request line ordered pairs.
26 - clocks: Handle to iis clock and RCLK source clk.
28 i2s0 uses some base clks from CMU and some are from audio subsystem internal
29 clock controller. The clock names for i2s0 should be "iis", "i2s_opclk0" and
31 i2s1 and i2s2 uses clocks from CMU. The clock names for i2s1 and i2s2 should
32 be "iis" and "i2s_opclk0".
[all …]
|
| D | ingenic,jz4740-i2s.txt | 5 - reg : I2S registers location and length
6 - clocks : AIC and I2S PLL clock specifiers.
7 - clock-names: "aic" and "i2s"
8 - dmas: DMA controller phandle and DMA request line for I2S Tx and Rx channels
9 - dma-names: Must be "tx" and "rx"
|
| D | wm8960.txt | 13 R24 (Additional control 2) gets set, indicating that ADCLRC and DACLRC pins
14 will be disabled only when ADC (Left and Right) and DAC (Left and Right)
16 When wm8960 works on synchronize mode and DACLRC pin is used to supply
21 enabled and disabled together with HP_L and HP_R pins in response to jack
|
| /linux-4.1.27/drivers/staging/iio/light/ |
| D | Kconfig | 7 tristate "ISL 29018 light and proximity sensor"
12 If you say yes here you get support for ambient light sensing and
15 in lux, proximity infrared sensing and normal infrared sensing.
19 tristate "Intersil ISL29028 Concurrent Light and Proximity Sensor"
26 of ambient light and proximity.
29 tristate "TAOS TSL2580, TSL2581 and TSL2583 light-to-digital converters"
32 Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices.
36 tristate "TAOS TSL/TMD2x71 and TSL/TMD2x72 Family of light and proximity sensors"
41 Provides iio_events and direct access via sysfs.
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | MIXART.txt | 1 Alsa driver for Digigram miXart8 and miXart8AES/EBU soundcards
8 The miXart8 is a multichannel audio processing and mixing soundcard
9 that has 4 stereo audio inputs and 4 stereo audio outputs.
11 4 digital stereo audio inputs and outputs.
13 (AES/EBU, Word Clock, Time Code and Video Synchro)
15 The mainboard has a PowerPC that offers onboard mpeg encoding and
16 decoding, samplerate conversions and various effects.
27 stereo analog capture 'pcm0c' and 1 stereo analog playback 'pcm0p' device.
29 'pcm1c' and 1 stereo digital output 'pcm1p' per card.
41 Mono files will be played on the left and right channel. Each channel
[all …]
|
| D | SB-Live-mixer.txt | 18 This PCM device (it's the 4th PCM device (index 3!) and first subdevice
37 is mentioned in multiple controls, the signal is accumulated and can be wrapped
46 (this standard is used for connecting standalone DAC and ADC converters)
48 AC97 - a chip containing an analog mixer, DAC and ADC converters
52 and the DSP microcontroller can operate with the resulting sum.
57 This control is used to attenuate samples for left and right PCM FX-bus
58 accumulators. ALSA uses accumulators 0 and 1 for left and right PCM samples.
63 This control is used to attenuate samples for left and right PCM FX-bus
64 accumulators. ALSA uses accumulators 0 and 1 for left and right PCM samples.
70 This control is used to attenuate samples for left and right PCM FX-bus
[all …]
|
| D | Audigy-mixer.txt | 23 is mentioned in multiple controls, the signal is accumulated and can be wrapped
32 (this standard is used for connecting standalone DAC and ADC converters)
34 AC97 - a chip containing an analog mixer, DAC and ADC converters
38 and the DSP microcontroller can operate with the resulting sum.
42 This control is used to attenuate samples for left and right front PCM FX-bus
43 accumulators. ALSA uses accumulators 8 and 9 for left and right front PCM
49 This control is used to attenuate samples for left and right surround PCM FX-bus
50 accumulators. ALSA uses accumulators 2 and 3 for left and right surround PCM
68 This control is used to attenuate samples for left and right PCM FX-bus
69 accumulators. ALSA uses accumulators 0 and 1 for left and right PCM samples for
[all …]
|
| D | CMIPCI.txt | 16 card#0) for front and 4/6ch playbacks, while the second PCM device
21 - The first DAC supports U8 and S16LE formats, while the second DAC
27 44100 and 48000 Hz.
35 will be FULL VOLUME regardless of Master and PCM volumes.
41 front one) and was so excited. It was even with "Four Channel" bit
42 on and "double DAC" mode. Actually I could hear separate 4 channels
43 from front and rear speakers! But.. after reboot, all was gone.
54 The "Exchange DAC" switch is used to exchange front and rear playback
74 The 4.0 and 5.1 modes are defined as the pcm "surround40" and "surround51"
80 channels as you like and set the format S16LE. For example, for playback
[all …]
|
| D | HD-Audio-Controls.txt | 10 and "8ch". According to the configuration, this also controls the
15 headphone and line-out jacks. If built-in speakers and headphone
16 and/or line-out jacks are available on a machine, this controls
19 "Disabled" and "Enabled" state. When enabled, the speaker is muted
22 When both headphone and line-out jacks are present, it gives
23 "Disabled", "Speaker Only" and "Line-Out+Speaker". When
26 selected, plugging to a headphone jack mutes both speakers and
37 and the normal PCM playback are exclusive, i.e. when this is on, you
41 Swaps the center and LFE channel order. Normally, the left
42 corresponds to the center and the right to the LFE. When this is
[all …]
|
| D | compress_offload.txt | 9 constant bitrates payloads such as IEC61937 in mind. Arguments and
14 in system-on-chip designs, and DSPs are also integrated in audio
23 provide a control and data-streaming interface for audio DSPs.
27 API in the mainline kernel instead of the staging tree and make it
34 - separation between byte counts and time. Compressed formats may have
43 of the sampling rate, number of channels and bits per sample. In
45 may also provide support for a limited number of audio encoders and
50 popular formats used for audio and video capture and playback. It is
56 stereo. Likewise WMA10 level M3 may require too much memory and cpu
69 to expose, translate and make use of the capabilities of the audio
[all …]
|
| /linux-4.1.27/fs/reiserfs/ |
| D | README | 10 and likely will be in the future, licensed to other parties under
11 other licenses. If you add your code to governed files, and don't
13 code so the poor blight and his customers can keep things straight.
15 Reiser, and by adding your code to it, widely distributing it to
16 others or sending us a patch, and leaving the sentence in stating that
20 under the GPL, because he wants to know if it is okay to do so and put
23 though he feels motivated to motivate contributors, and you can surely
28 Further licensing options are available for commercial and/or other
31 it wrongly, and Richard Stallman agrees with me, when carefully read
33 to the owner of the copyright, and my interpretation of this shall
[all …]
|
| /linux-4.1.27/drivers/lguest/ |
| D | README | 4 5000-line projects which offer both such capability and glimpses of future
11 So get comfortable and keep your wits about you (both quick and humorous).
13 lguest, and hypervisors and x86 virtualization in general.
19 taste of its scope. Suitable for the armchair coders and other such
23 - Where we encounter the first tantalising wisps of code, and come to
27 - Whereby the Guest finds its voice and become useful, and our
31 - Where we trace back to the creation of the Guest, and thus begin our
35 - Where we master the Host code, through a long and tortuous journey.
39 - Where our understanding of the intertwined nature of Guests and Hosts
|
| /linux-4.1.27/Documentation/power/ |
| D | apm-acpi.txt | 5 Advanced Configuration and Power Interface (ACPI). ACPI is the newer
6 of the two technologies and puts power management in the hands of the
11 build a kernel with both ACPI and APM enabled (as of 2.3.x ACPI is
13 ACPI driver will override and disable APM, otherwise the APM driver
16 No, sorry, you cannot have both ACPI and APM enabled and running at
19 simply cannot mix and match the two. Only one power management
24 Both APM and ACPI rely on user-space daemons, apmd and acpid
27 and be sure that they are started sometime in the system boot process.
28 Go ahead and start both. If ACPI or APM is not available on your
|
| D | 00-INDEX | 4 - basic info about the APM and ACPI support.
6 - Debugging suspend and resume
12 - Testing suspend and resume support in device drivers
14 - How processes and controlled during suspend
30 - How to get suspend to ram working (and debug it when it isn't)
33 suspend-and-cpuhotplug.txt
34 - Explains the interaction between Suspend-to-RAM (S3) and CPU hotplug
35 swsusp-and-swap-files.txt
38 - How to use dm-crypt and software suspend (to disk) together
40 - Goals, implementation, and usage of software suspend (ACPI S3)
|
| D | drivers-testing.txt | 1 Testing suspend and resume support in device drivers
6 Unfortunately, to effectively test the support for the system-wide suspend and
7 resume transitions in a driver, it is necessary to suspend and resume a fully
9 several times, preferably several times in a row, and separately for hibernation
10 (aka suspend to disk or STD) and suspend to RAM (STR), because each of these
11 cases involves slightly different operations and different interactions with
14 Of course, for this purpose the test system has to be known to suspend and
25 a) Build the driver as a module, load it and try the test modes of hibernation
28 b) Load the driver and attempt to hibernate in the "reboot", "shutdown" and
31 c) Compile the driver directly into the kernel and try the test modes of
[all …]
|
| D | basic-pm-debugging.txt | 1 Debugging hibernation and suspend
11 and the system should create a hibernation image, reboot, resume and get back to
15 because some problems only show up on a second attempt at suspending and
16 resuming the system.] Moreover, hibernating in the "reboot" and "shutdown"
24 which is the default and recommended mode of hibernation.
50 - test the freezing of processes and suspending of devices
53 - test the freezing of processes, suspending of devices and platform
58 global control methods(*) and the disabling of nonboot CPUs
62 control methods(*), the disabling of nonboot CPUs and suspending of
66 and are only tested if the hibernation mode is set to "platform"
[all …]
|
| D | devices.txt | 14 power management goals, emphasizing the models and interfaces that are
30 This is something that device, bus, and class drivers collaborate on
31 by implementing various role-specific suspend and resume methods to
32 cleanly power down hardware and software subsystems, then reactivate
54 appropriate subsystem (bus type, device type or device class) driver and
57 various role-specific suspend and resume methods, so that the hardware
58 is cleanly powered down and reactivated without data or service loss.
61 very system-specific, and often device-specific. Also, that if enough devices
63 to entering some system-wide low-power state (system sleep) ... and that
68 for wakeup events), no more data read or written, and requests from upstream
[all …]
|
| D | suspend-and-interrupts.txt | 1 System Suspend and Device Interrupts
7 Suspending and Resuming Device IRQs
12 ->prepare, ->suspend and ->suspend_late callbacks have been executed for all
17 trigger and if any devices have not been suspended properly yet, it is better to
22 of suspended devices and cause unpredictable behavior to ensue as a result.
23 Unfortunately, such problems are very difficult to debug and the introduction
24 of suspend_device_irqs(), along with the "noirq" phase of device suspend and
36 suspend-resume cycle, including the "noirq" phases of suspending and resuming
37 devices as well as during the time when nonboot CPUs are taken offline and
39 but also to IPIs and to some other special-purpose interrupts.
[all …]
|
| /linux-4.1.27/Documentation/arm/ |
| D | kernel_mode_neon.txt | 8 * Isolate your NEON code in a separate compilation unit, and compile it with
10 * Put kernel_neon_begin() and kernel_neon_end() calls around the calls into your
12 * Don't sleep in your NEON code, and be aware that it will be executed with
18 It is possible to use NEON instructions (and in some cases, VFP instructions) in
20 register file is not preserved and restored at every context switch or taken
27 Lazy preserve and restore
29 The NEON/VFP register file is managed using lazy preserve (on UP systems) and
30 lazy restore (on both SMP and UP systems). This means that the register file is
31 kept 'live', and is only preserved and restored when multiple tasks are
35 instruction is issued, allowing the kernel to step in and perform the restore if
[all …]
|
| D | tcm.txt | 11 and a DTCM (data TCM). The DTCM can not contain any
14 minimum configuration is 4KiB ITCM and 4KiB DTCM.
17 location and size of TCM memories. arch/arm/include/asm/cputype.h
22 determine if ITCM (bits 1-0) and/or DTCM (bit 17-16) is present
26 Registers" at the ARM site) that can report and modify the location
27 size of TCM memories at runtime. This is used to read out and modify
28 TCM location and size. Notice that this is not a MMU table: you
39 will map ITCM to 0xfffe0000 and on, and DTCM to 0xfffe8000 and
40 on, supporting a maximum of 32KiB of ITCM and 32KiB of DTCM.
45 be able to lock and hide one of the banks for use by the secure
[all …]
|
| D | CCN.txt | 6 so nodes (devices) 0 and 1 are connected to crosspoint 0,
7 nodes 2 and 3 to crosspoint 1 etc.
13 description of available events and configuration options
17 and config2 fields of the perf_event_attr structure. The "events"
23 "port" (device port number) and "vc" (virtual channel ID) and
25 require comparator values ("cmp_l" and "cmp_h") and "mask", being
30 directory, with first 8 configurable by user and additional
33 Cycle counter is described by a "type" value 0xff and does
51 would try (and in most cases fail) to set up the same event
|
| D | IXP4xx | 12 in industrial control and other areas due to low cost and power
16 supports faster speeds, new memory and flash configurations, and more
38 The following components of the chips are not supported by Linux and
57 Open Source Developer's Guide for using uClinux and the Intel libraries
60 Simple one page summary of building a gateway using an IXP425 and Linux
80 into the kernel and we can use the standard read[bwl]/write[bwl]
83 problamatic if using video cards and other memory-heavy devices.
108 interface, one to 4-port 10/100 switch, and the third to and ADSL
117 The Avila platform is basically and IXDP425 with the 4 PCI slots
118 replaced with mini-PCI slots and a CF IDE interface hanging off
[all …]
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 6 This document describes the changes made by unified hierarchy and
33 cgroup allows an arbitrary number of hierarchies and each hierarchy
46 on the same hierarchy and most configurations resort to putting each
48 the cpu and cpuacct controllers, make sense to put on the same
56 restricts how cgroup is used in general and what controllers can do.
60 The key may contain any varying number of entries and is unlimited in
61 length, which makes it highly awkward to handle and leads to addition
83 general and controller-specific interface issues are also addressed in
92 command. Note that this is still under development and scheduled to
97 All controllers which support the unified hierarchy and are not bound
[all …]
|
| D | 00-INDEX | 4 - Description for Block IO Controller, implementation and usage details.
6 - Control Groups definition, implementation details, examples and API.
10 - documents the cpusets feature; assign CPUs and Mem to a set of tasks.
12 - Device Whitelist Controller; description, interface and security.
16 - HugeTLB Controller implementation and usage details.
22 - Network classifier cgroups details and usages.
24 - Network priority cgroups details and usages.
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 16 One of the most complicated parts of the X86 platform, and specifically,
18 and the complexity of emulating those devices. In addition, virtualization of
23 present some of the problems which arise and solutions available, giving
26 The purpose of this document is to collect data and information relevant to
28 information relevant to KVM and hardware-based virtualization.
34 First we discuss the basic hardware devices available. TSC and the related
35 KVM clock are special enough to warrant a full exposition and are described in
41 or PIT. The PIT has a fixed frequency 1.193182 MHz base clock and three
43 These three channels can be configured in different modes and have individual
44 counters. Channel 1 and 2 were not available for general use in the original
[all …]
|
| /linux-4.1.27/Documentation/power/regulator/ |
| D | overview.txt | 1 Linux voltage and current regulator framework
8 voltage and current regulators.
11 in order to save power and prolong battery life. This applies to both voltage
12 regulators (where voltage output is controllable) and current sinks (where
25 Most regulators can enable and disable their output whilst
26 some can control their output voltage and or current.
32 and often contains other subsystems.
59 That is one regulator and three power domains:
65 and this represents a "supplies" relationship:
76 This gives us two regulators and two power domains:
[all …]
|
| /linux-4.1.27/Documentation/vm/ |
| D | cleancache.txt | 12 that is not directly accessible or addressable by the kernel and is
13 of unknown and possibly time-varying size.
18 and a disk access is avoided.
21 in Xen (using hypervisor memory) and zcache (using in-kernel compressed
22 memory) and other implementations are in development.
35 by the kernel and so may or may not still be in cleancache at any later time.
37 Cleancache has complete discretion over what pages to preserve and what
38 pages to discard and when.
43 (presumably about-to-be-evicted) page into cleancache and associate it with
44 the pool id, a file key, and a page index into the file. (The combination
[all …]
|
| D | frontswap.txt | 5 (Note, frontswap -- and cleancache (merged at 3.0) -- are the "frontends"
6 and the only necessary changes to the core kernel for transcendent memory;
9 overview of frontswap and related kernel parts:
18 kernel and is of unknown and possibly time-varying size. The driver
20 frontswap_ops funcs appropriately and the functions it provides must
25 copy the page to transcendent memory and associate it with the type and
29 from transcendent memory and an "invalidate_area" will remove ALL pages
30 associated with the swap type (e.g., like swapoff) and notify the "device"
36 success, the data has been successfully saved to transcendent memory and
37 a disk write and, if the data is later read back, a disk read are avoided.
[all …]
|
| D | split_page_table_lock | 10 access to the table. At the moment we use split lock for PTE and PMD
13 There are helpers to lock/unlock a table and other accessor functions:
15 maps pte and takes PTE table lock, returns pointer to the taken
18 unlocks and unmaps PTE table;
20 allocates PTE table if needed and take the lock, returns pointer
34 tables and the architecture supports it (see below).
36 Hugetlb and split page table lock
53 everything required is done by pgtable_page_ctor() and pgtable_page_dtor(),
57 allocation: slab uses page->slab_cache and page->first_page for its pages.
64 allocation and pgtable_pmd_page_dtor() on freeing.
[all …]
|
| /linux-4.1.27/drivers/staging/slicoss/ |
| D | README | 3 Mojave cards (single port PCI Gigabit) both copper and fiber
4 Oasis cards (single and dual port PCI-x Gigabit) copper and fiber
5 Kalahari cards (dual and quad port PCI-e Gigabit) copper and fiber
7 The driver was actually tested on Oasis and Kalahari cards.
|
| /linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
| D | CPUfreq.txt | 8 the ability to change the core, memory and peripheral operating
13 There are two forms of the driver depending on the specific CPU and
15 PLL to feed the ARM, memory and peripherals via a series of dividers
16 and muxes and this is the implementation that is documented here. A
17 newer version where there is a separate PLL and clock divider for the
25 need to register and the interface to the generic drivers/cpufreq
27 and anything else associated with it. Any board that wants to use this
38 SoC and the driver as each device has different PLL and clock chains
45 The SLOW mode where the PLL is turned off altogether and the
62 board requires and any restrictions being placed on it.
[all …]
|
| D | S3C2412.txt | 15 The core clock code provides a set of clocks to the drivers, and allows
16 for source selection and a number of other features.
35 and reading or writing to them.
41 The UART hardware is similar to the S3C2440, and is supported by the
48 The NAND hardware is similar to the S3C2440, and is supported by the
56 control. The OHCI portion is supported by the ohci-s3c2410 driver, and
69 All the standard, and external interrupt sources are supported. The
76 The RTC hardware is similar to the S3C2410, and is supported by the
83 The watchdog hardware is the same as the S3C2410, and is supported by
95 The IIC hardware is the same as the S3C2410, and is supported by the
|
| /linux-4.1.27/Documentation/devicetree/bindings/regulator/ |
| D | ltc3589.txt | 1 Linear Technology LTC3589, LTC3589-1, and LTC3589-2 8-output regulators
9 ldo1, ldo2, ldo3, and ldo4, specifying the initialization data as
13 nodes for sw1, sw2, sw3, bb-out, ldo1, and ldo2 additionally need to specify
18 values R1 and R2 of the feedback voltage divider in ohms.
20 Regulators sw1, sw2, sw3, and ldo2 can regulate the feedback reference from
22 0.3625 * (1 + R1/R2) V and 0.75 * (1 + R1/R2) V. Regulators bb-out and ldo1
23 have a fixed 0.8 V reference and thus output 0.8 * (1 + R1/R2) V. The ldo3
24 regulator is fixed to 1.8 V on LTC3589 and to 2.8 V on LTC3589-1,2. The ldo4
25 regulator can output between 1.8 V and 3.3 V on LTC3589 and between 1.2 V
26 and 3.2 V on LTC3589-1,2 in four steps. The ldo1 standby regulator can not
[all …]
|
| /linux-4.1.27/drivers/usb/ |
| D | README | 3 * This source code. This is necessarily an evolving work, and
5 ("make pdfdocs", and then look at "usb.pdf" for host side and
10 such as those for USB OTG and the various device classes.
11 The USB specification has a good overview chapter, and USB
15 host controllers (on PCs, servers, and more); peripheral
17 cell phones); and hard-wired peripherals like Ethernet adapters.
23 Here is a list of what each subdirectory here is, and what is contained in
27 usbfs files and the hub class driver ("hub_wq").
30 includes UHCI, OHCI, EHCI, and others that might
33 gadget/ - This is for USB peripheral controller drivers and
[all …]
|
| /linux-4.1.27/Documentation/spi/ |
| D | butterfly | 4 This is a hardware and software project that includes building and using
6 firmware for user interfacing and/or sensors. A Butterfly is a $US20
7 battery powered card with an AVR microcontroller and lots of goodies:
8 sensors, LCD, flash, toggle stick, and more. You can use AVR-GCC to
9 develop firmware for this, and flash it using this adapter cable.
11 You can make this adapter from an old printer cable and solder things
12 directly to the Butterfly. Or (if you have the parts and skills) you
14 Butterfly and the printer port, or with a better power supply than two
19 SPI protocol drivers interact with the AVR, and could even let the AVR
25 AVR and a DataFlash chip; and to the AVR reset line. This is all you
[all …]
|
| D | spi-summary | 9 link used to connect microcontrollers to sensors, memory, and peripherals.
14 and parallel data lines with "Master Out, Slave In" (MOSI) or "Master In,
16 clocking modes through which data is exchanged; mode-0 and mode-3 are most
17 commonly used. Each clock cycle shifts data out and data in; the clock
32 touchscreen sensors and memory chips.
50 SPI is only one of the names used by such four-wire protocols, and
53 Serial Protocol"), PSP ("Programmable Serial Protocol"), and other
56 Some chips eliminate a signal line by combining MOSI and MISO, and
64 Microcontrollers often support both master and slave sides of the SPI
65 protocol. This document (and Linux) currently only supports the master
[all …]
|
| /linux-4.1.27/Documentation/input/ |
| D | joystick-parport.txt | 11 happen include burning your parallel port, and/or the sticks and joystick
12 and maybe even more. Like when a lightning kills you it is not our problem.
16 The joystick parport drivers are used for joysticks and gamepads not
17 originally designed for PCs and other computers Linux runs on. Because of
19 port, because of its ability to change single bits at will, and providing
20 both output and input bits is the most suitable port on the PC for
25 Many console and 8-bit computer gamepads and joysticks are supported. The
28 2.1 NES and SNES
30 The Nintendo Entertainment System and Super Nintendo Entertainment System
31 gamepads are widely available, and easy to get. Also, they are quite easy to
[all …]
|
| D | input-programming.txt | 11 just one button and the button is accessible at i/o port BUTTON_PORT. When
84 and sets up input bitfields. This way the device driver tells the other
87 type events, and from those only BTN_0 event code. Thus we only set these
100 This adds the button_dev structure to linked lists of the input driver and
102 device has appeared. input_register_device() may sleep and therefore must
109 which upon every interrupt from the button checks its state and reports it
125 for for example mouse movement, where you don't want the X and Y values
128 1.2 dev->open() and dev->close()
132 have an interrupt coming from it and the polling is too expensive to be done
134 can use the open and close callback to know when it can stop polling or
[all …]
|
| D | input.txt | 8 This program is free software; you can redistribute it and/or modify it
43 These modules talk to the hardware (for example via USB), and provide
48 These modules get events from input and pass them where needed via
50 simulated PS/2 interface to GPM and X and so on.
54 For the most usual configuration, with one USB mouse and one USB keyboard,
65 After this, the USB keyboard will work straight away, and the USB mouse
77 After that you have to point GPM (the textmode mouse cut&paste tool) and
90 When you do all of the above, you can use your USB mouse and keyboard.
102 usbhid is the largest and most complex driver of the whole suite. It
103 handles all HID devices, and because there is a very wide variety of them,
[all …]
|
| D | bcm5974.txt | 5 The USB initialization and package decoding was made by Scott Shawcroft as
19 Macbook Air and Macbook Pro laptops. It replaces the appletouch driver on
20 those computers, and integrates well with the synaptics driver of the Xorg
23 Known to work on Macbook Air, Macbook Pro Penryn and the new unibody
24 Macbook 5 and Macbook Pro 5.
29 The driver loads automatically for the supported usb device ids, and
30 becomes available both as an event device (/dev/input/event*) and as a
36 The Apple multi-touch trackpads report both mouse and keyboard events via
39 HID mouse and keyboard, and claim the whole device. To remedy, the usb
58 The driver was developed at the ubuntu forums in June 2008 [1], and now has
|
| D | cs461x.txt | 5 Vortex/Solo drivers as an example of decoration style, and ALSA
6 0.5.8a kernel drivers as an chipset documentation and samples.
12 Raw mode works fine with analog joystick front-end driver and cs461x
13 driver as a backend. I've tested this driver with CS4610, 4-axis and
15 play in xracer game using joystick, and the result is better than
18 The sensitivity and calibrate quality have not been tested; the two
20 screen in VJOYD); I have no documentation on my chip; and the existing
24 The patch contains minor changes of Config.in and Makefile files. All
28 ISA and PnP ISA series.
31 uses joystick as input device and PCM device as sound output in one time.
[all …]
|
| D | ntrig.txt | 6 This driver provides support for N-Trig pen and multi-touch sensors. Single
7 and multi-touch events are translated to the appropriate protocols for
8 the hid and input systems. Pen events are sufficiently hid compliant and
10 and utility functions accessible with sysfs and module parameters.
19 Note: values set at load time are global and will apply to all applicable
31 min_width both to decide activation and during activity
57 seem to be 12" sensors (Dell Latitude XT and XT2 and the HP TX2), and
67 seeing both inappropriately dropped contact and ghosts, contacts reported
73 processing and should be handled in tandem with tacking.
78 of events the more likely those events are from a real contact, and that the
[all …]
|
| D | event-codes.txt | 1 The input protocol uses a map of types and codes to express input device values
2 to userspace. This document describes the types and codes and how and when they
9 input event encompassing a type, code, and value.
13 input subsystem; drivers do not need to maintain the state and may attempt to
17 class/input/event*/device/capabilities/, and the properties of a device are
49 - Used to turn LEDs on devices on and off.
61 - A special type for power button and switch input.
76 - Used to synchronize and separate events into packets of input data changes
78 the REL_X and REL_Y values for one motion, then emit a SYN_REPORT. The next
79 motion will emit more REL_X and REL_Y values and send another SYN_REPORT.
[all …]
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | usage-model.txt | 1 Linux and the Device Tree
14 structure and language for describing hardware. More specifically, it
19 Structurally, the DT is a tree, or acyclic graph with named nodes, and
27 connections, and peripheral devices.
30 maximize use of existing support code, but since property and node
32 or create new ones by defining new nodes and properties. Be wary,
44 Device Tree to discover the topology of the hardware at runtime, and
48 Since Open Firmware is commonly used on PowerPC and SPARC platforms,
52 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
53 and 64-bit support, the decision was made to require DT support on all
[all …]
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 21 (*) Security model and SELinux.
38 reaping stale nodes and culling. This is called cachefilesd and lives in
41 The filesystem and data integrity of the cache are only as good as those of the
48 and whilst it is open, a cache is at least partially in existence. The daemon
49 opens this and sends commands down it to control the cache.
56 placed on the same medium as a live set of data, and will expand to make use of
57 spare space and automatically contract when the set of data requires more
65 The use of CacheFiles and its daemon requires the following features to be
66 available in the system and in the cache filesystem:
72 - openat() and friends.
[all …]
|
| /linux-4.1.27/Documentation/early-userspace/ |
| D | README | 7 "Early userspace" is a set of libraries and programs that provide
15 containing a root filesystem image. This archive is compressed, and
20 optimized for correctness and small size.
23 format, and is documented in the file "buffer-format.txt". There are
31 Your cpio archive should be specified in CONFIG_INITRAMFS_SOURCE and it
33 CONFIG_INITRAMFS_SOURCE and directory and file names are not allowed in
47 A source directory will have it and all of its contents packaged. The
49 directory, limited user and group ID translation can be performed.
59 When a combination of directories and files are specified then the
61 can create a 'root-image' directory and install all files into it.
[all …]
|
| /linux-4.1.27/kernel/ |
| D | Kconfig.hz | 11 beneficial for servers and NUMA systems that do not need to have
12 a fast response for user interaction and that may experience bus
13 contention and cacheline bounces as a result of timer interrupts.
22 100 Hz is a typical choice for servers, SMP and NUMA systems
31 on SMP and NUMA systems. If you are going to be using NTSC video
39 on SMP and NUMA systems and exactly dividing by both PAL and
40 NTSC frame rates for video and multimedia work.
45 1000 Hz is the preferred choice for desktop systems and other
|
| /linux-4.1.27/drivers/parisc/ |
| D | Kconfig | 7 The VSC, GSC and HSC busses were used from the earliest 700-series
8 workstations up to and including the C360/J2240 workstations. They
10 are not found in B1000, C3000, J5000, A500, L1000, N4000 and upwards.
17 The HP-PB bus was used in the Nova class and K-class servers.
26 U2/Uturn chip in "Virtual Mode" and use the I/O MMU.
36 and floppy. Note that you must still enable all the individual
44 older systems, including B/C/D/R class and 715/64, 715/80 and
46 used), a HIL interface chip and is also known to be used as the
55 incomplete and lacks support for card-to-host DMA.
69 All recent HP machines have PCI slots, and you should say Y here
[all …]
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-nice-design.txt | 1 This document explains the thinking about the revamped and streamlined
4 Nice levels were always pretty weak under Linux and people continuously
9 support was historically coupled to timeslice length, and timeslice
13 much stronger than they were before in 2.4 (and people were happy about
14 that change), and we also intentionally calibrated the linear timeslice
43 millisec) rescheduling. (and would thus trash the cache, etc. Remember,
44 this was long ago when hardware was weaker and caches were smaller, and
48 right minimal granularity - and this translates to 5% CPU utilization.
50 and we never got a single complaint about nice +19 being too _weak_ in
55 within the constraints of HZ and jiffies and their nasty design level
[all …]
|
| D | sched-design-CFS.txt | 8 CFS stands for "Completely Fair Scheduler," and is the new "desktop" process
9 scheduler implemented by Ingo Molnar and merged in Linux 2.6.23. It is the
17 power and which can run each task at precise equal speed, in parallel, each at
31 In CFS the virtual runtime is expressed and tracked via the per-task
33 timestamp and measure the "expected CPU time" a task should have gotten.
36 p->se.vruntime value --- i.e., tasks would execute simultaneously and no task
39 CFS's task picking logic is based on this p->se.vruntime value and it is thus
46 with a few add-on embellishments like nice levels, multiprocessing and various
55 task execution, and thus has no "array switch" artifacts (by which both the
56 previous vanilla scheduler and RSDL/SD are affected).
[all …]
|
| /linux-4.1.27/Documentation/ABI/stable/ |
| D | firewire-cdev | 7 firewire-core and IEEE 1394 device drivers implemented in
8 userspace. The ioctl(2)- and read(2)-based ABI is defined and
22 and local node
24 - Isochronous stream transmission and reception
25 - Asynchronous stream transmission and reception
27 - PHY packet transmission and reception
42 Due to the different scope of operations and in order to let
48 - PHY packet transmission and reception
51 during its entire life time. Bus topology changes, and hence
72 buffer completion, and unsolicited events such as bus resets,
[all …]
|
| /linux-4.1.27/Documentation/mmc/ |
| D | mmc-async-req.txt | 5 It depends. Fast eMMC and multiple cache levels with speculative cache
10 time between when an MMC request ends and another MMC request begins.
11 Using mmc_wait_for_req(), the MMC controller is idle while dma_map_sg and
21 prepare (major part of preparations are dma_map_sg() and dma_unmap_sg())
22 a request and how fast the memory is. The faster the MMC/SD is the
24 performance gain is 5% for large writes and 10% on large reads on a L2 cache
29 Details on measurements from IOZone and mmc_test
40 for completion of that request and starts the new one and returns. It
42 request it starts the new request and returns immediately.
47 There are two optional members in the mmc_host_ops -- pre_req() and
[all …]
|
| /linux-4.1.27/drivers/hwmon/ |
| D | Kconfig | 13 sensors and various additional features such as the ability to
15 should say Y here and also to the specific driver(s) for your
37 a problem with I2C support and want to see more of what is going
49 AB8500 die and two GPADC channels. The GPADC channel are preferably
60 and second revision of the Abit uGuru chip. The voltage and frequency
63 Abit motherboards from before end 2005). For more info and a list
76 and their settings is supported. The third revision of the Abit
78 2005). For more info and a list of which motherboards have which
85 tristate "Analog Devices AD7314 and compatibles"
89 AD7314, ADT7301 and ADT7302 temperature sensors.
[all …]
|
| /linux-4.1.27/arch/arm/crypto/ |
| D | aes-armv4.S | 4 @ project. The module is, however, dual licensed under OpenSSL and
13 @ Code uses single 1K S-box and is >2 times faster than code generated
16 @ in one instruction and emit combined result every cycle. The module
27 @ Cortex A8 core and ~25 cycles per byte processed with 128-bit key.
31 @ Profiler-assisted and platform-specific optimization resulted in 16%
32 @ improvement on Cortex A8 core and ~21.5 cycles per byte.
258 and r7,lr,r0
259 and r8,lr,r0,lsr#8
260 and r9,lr,r0,lsr#16
264 and r7,lr,r1,lsr#16 @ i0
[all …]
|
| /linux-4.1.27/Documentation/block/ |
| D | data-integrity.txt | 4 Modern filesystems feature checksumming of data and metadata to
21 Current storage controllers and devices implement various protective
22 measures, for instance checksumming and scrubbing. But these
25 DIF and the other integrity extensions is that the protection format
26 is well defined and every node in the I/O path can verify the
27 integrity of the I/O and reject it if corruption is detected. This
35 controller and storage device. However, many controllers actually
38 the protection information to be transferred to and from their
44 transferred between the controller and target. The T13 proposal is
48 520 (and 4104) byte sectors, we approached several HBA vendors and
[all …]
|
| D | biovecs.txt | 2 Immutable biovecs and biovec iterators:
12 update bi_sector and bi_size, and advance bi_idx to the next biovec. If it
13 ended up partway through a biovec, it would increment bv_offset and decrement
18 bi_size and bi_idx have been moved there; and instead of modifying bv_offset
19 and bv_len, struct bvec_iter has bi_bvec_done, which represents the number of
27 bio_iovec() and bio_iovec_iter() macros that return literal struct biovecs,
28 constructed from the raw biovecs but taking into account bi_bvec_done and
37 wrapper around bio_advance_iter() that operates on bio->bi_iter, and also
46 Having a real iterator, and making biovecs immutable, has a number of
53 it had to walk two different bios at the same time, keeping both bi_idx and
[all …]
|
| D | writeback_cache_control.txt | 17 a forced cache flush, and the Force Unit Access (FUA) flag for requests.
24 the filesystem and will make sure the volatile cache of the storage device
37 filesystem and will make sure that I/O completion for this request is only
44 Filesystems can simply set the REQ_FLUSH and REQ_FUA bits and do not have to
45 worry if the underlying devices need any explicit cache flushing and how
46 the Forced Unit Access is implemented. The REQ_FLUSH and REQ_FUA flags
53 These drivers will always see the REQ_FLUSH and REQ_FUA bits as they sit
55 bits need to be propagated to underlying devices, and a global flush needs
57 drivers that do not have a volatile cache the REQ_FLUSH and REQ_FUA bits
58 on non-empty bios can simply be ignored, and REQ_FLUSH requests without
[all …]
|
| D | cfq-iosched.txt | 18 (for sequential workloads) and service trees (for random workloads) before
19 queue is expired and CFQ selects next queue to dispatch from.
24 seeks and see improved throughput.
27 level and one should see an overall improved throughput on faster storage
29 side is that isolation provided from WRITES also goes down and notion of
32 So depending on storage and workload, it might be useful to set slice_idle=0.
33 In general I think for SATA/SAS disks and software RAID of SATA/SAS disks
37 throughput and acceptable latencies.
46 direction and consider them as being the "next" if they are within this
73 in higher end storage due to idle on sequential queue and allow dispatch
[all …]
|
| /linux-4.1.27/drivers/block/paride/ |
| D | Transition-notes | 4 Proof: All assignments to ps_tq_active and all scheduling of ps_tq happen
6 one in ps_set_intr() (A) and two in ps_tq_int() (B and C).
10 other than through B and we don't drop ps_spinlock between them.
12 the sum of numbers of A and C, since each call of ps_tq_int() is
14 A and each B is preceded by either A or C. Moments when we enter
15 ps_tq_int() are sandwiched between {A,C} and B in that sequence,
17 moments which, in turn, can not exceed the number of A and C.
19 1 and schedule ps_tq, ps_tq is executed, ps_tq_int() is entered,
24 * in do_pd_request1(): to calls of pi_do_claimed() and return in
29 and ps_set_intr()
[all …]
|
| /linux-4.1.27/Documentation/dvb/ |
| D | readme.txt | 4 The main development site and CVS repository for these
10 and the Wiki http://linuxtv.org/wiki/
13 API documentation, utilities and test/example programs
36 CI module as part from TwinHan cards and Clones.
42 contains frequently asked questions and their answers.
45 script to download and extract firmware for those devices
53 how to get DVB and udev up and running.
60 Technisat- and Flexcop B2C2 drivers.
62 Good luck and have fun!
|
| D | README.dvb-usb | 1 Documentation for dvb-usb-framework module and its devices
6 In March 2005 I got the new Twinhan USB2.0 DVB-T device. They provided specs and a firmware.
9 After reading some specs and doing some USB snooping, it realized, that the
16 (bulk and isoc are supported)
20 - firmware requesting and loading (currently just for the Cypress USB
25 depending on length of a register and the number of values that can be
26 multi-written and multi-read.
39 TODO: dynamic enabling and disabling of the pid-filter in regard to number of
53 added support for Conexant Hybrid reference design and Nebula DigiTV USB
55 2005-04-02 - re-enabled and improved remote control code.
[all …]
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-i801 | 4 * Intel 82801AA and 82801AB (ICH and ICH0 - part of the
5 '810' and '810E' chipsets)
35 On Intel Patsburg and later chipsets, both the normal host SMBus controller
36 and the additional 'Integrated Device Function' controllers are supported.
60 ICH3 (82801CA/CAM) and later devices (PCH) are Intel chips that are a part of
62 Pentium-based PCs, '815E' chipset, and others.
90 I2C block read is supported on the 82801EB (ICH5) and later chips.
96 The 82801DB (ICH4) and later chips support several SMBus 2.0 features.
102 PCI interrupt support is supported on the 82801EB (ICH5) and later chips.
109 SMBus device at 00:1f.3 in lspci, and you can't figure out any way in the
[all …]
|
| /linux-4.1.27/drivers/media/usb/pwc/ |
| D | philips.txt | 1 This file contains some additional information for the Philips and OEM webcams.
32 a lot of extra information, a FAQ, and the binary plugin 'PWCX'. This plugin
33 contains decompression routines that allow you to use higher image sizes and
36 under a NDA, and may therefore not be distributed as source; however, its use
44 camera; some programs depend on a particular image-size or -format and
50 320x240, 352x288 and 640x480 (of course, only for those cameras that
61 reasonable. You can set it between 2 and 5.
64 This is an integer between 1 and 10. It will tell the module the number of
65 buffers to reserve for mmap(), VIDIOCCGMBUF, VIDIOCMCAPTURE and friends.
83 the cam on close() and re-activate on open(). This will save power and
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 25 Represents the interface between the graphics processor and a external
31 - reg : should contain the VI registers location and length
36 Represents the data and control interface between the main processor
37 and graphics and audio processor.
42 - reg : should contain the PI registers location and length
64 - reg : should contain the DSP registers location and length
76 - reg : should contain the SI registers location and length
87 - reg : should contain the AI registers location and length
97 - reg : should contain the EXI registers location and length
107 - reg : should contain the OHCI registers location and length
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,idle-state.txt | 4 cpuidle-qcom is the cpuidle driver for Qualcomm SoCs and uses these idle
5 states. Idle states have different enter/exit latency and residency values.
20 cache hierarchy is also out of standby, and then the cpu is allowed to resume
22 driver and is not defined in the DT. The SPM state machine should be
23 configured to execute this state by default and after executing every other
26 Retention: Retention is a low power state where the core is clock gated and
27 the memory and the registers associated with the core are retained. The
30 sequence and would wait for interrupt, before restoring the cpu to execution
33 Standalone PC: A cpu can power down and warmboot if there is a sufficient time
34 between the time it enters idle and the next known wake up. SPC mode is used
[all …]
|
| /linux-4.1.27/drivers/usb/gadget/udc/ |
| D | Kconfig | 3 # (a) a peripheral controller, and
12 # With help from a special transceiver and a "Mini-AB" jack, systems with
22 # - licensed IP used in both SOC and discrete versions
42 dynamically linked module called "at91_udc" and force all
53 dynamically linked module called "lpc32xx_udc" and force all
61 the AT32AP700x, some AT91SAM9 and AT91CAP9 processors from Atmel.
79 Some of Freescale PowerPC and i.MX processors have a High Speed
86 dynamically linked module called "fsl_usb2_udc" and force
121 controller in the OMAP 1611, and should work with controllers
125 dynamically linked module called "omap_udc" and force all
[all …]
|
| /linux-4.1.27/Documentation/w1/slaves/ |
| D | w1_ds2406 | 5 * Maxim DS2406 (and other family 0x12) addressable switches
12 The w1_ds2406 driver allows connected devices to be switched on and off.
14 not supported. In TSOC-6 form, the DS2406 provides two switch outputs and
16 one output and uses parasitic power only.
19 current state of each switch, with PIO A in bit 0 and PIO B in bit 1. The
21 work with. output is writable; bits 0 and 1 control PIO A and B,
24 CRCs are checked on read and write. Failed checks cause an I/O error to be
|
| /linux-4.1.27/Documentation/s390/ |
| D | 3270.txt | 12 This paper describes installing and operating 3270 devices under
13 Linux/390. A 3270 device is a block-mode rows-and-columns terminal of
14 which I'm sure hundreds of millions were sold by IBM and clonemakers
15 twenty and thirty years ago.
17 You may have 3270s in-house and not know it. If you're using the
30 and this Linux-390 3270 driver, you have another way of talking to your
33 This paper covers installation of the driver and operation of a
39 You install the driver by installing a patch, doing a kernel build, and
48 script and the resulting /tmp/mkdev3270.
54 You may generate both 3270 and 3215 console support, or one or the
[all …]
|
| D | 3270.ChangeLog | 5 ESC sequences (especially coloring ones) and the strings
18 * Do read and write lengths correctly in fs3270_read()
19 and fs3270_write(), whilst never asking kmalloc()
20 for more than 0x800 bytes. Affects tubfs.c and tubio.h.
26 adding and invoking new tub3270_is_ours().
35 Specify y for CONFIG_3270 and y for CONFIG_3270_CONSOLE.
40 tubttybld.c and tubttyscl.c, for screen-building code and
43 build with both 2.4.0 and 2.2.16.2.
44 * color support and minimal other ESC-sequence support is added.
|
| D | DASD | 4 driver. It is valid for all types of DASDs and represents them to
6 single major number (254) and 4 minor numbers per volume (1 for the
7 physical volume and 3 for partitions). With respect to partitions see
11 in the kernel's parameter line or not at all. The 'from' and 'to'
15 in order of appearance and a minor number is reserved for any device
21 The driver currently supports ECKD-devices and there are stubs for
22 support of the FBA and CKD architectures. For the FBA architecture
25 We performed our testing on 3380 and 3390 type disks of different
26 sizes, under VM and on the bare hardware (LPAR), using internal disks
32 reserved for IPL records and IBM's volume label to assure
[all …]
|
| /linux-4.1.27/Documentation/accounting/ |
| D | taskstats.txt | 5 Taskstats is a netlink-based interface for sending per-task and
10 - efficiently provide statistics during lifetime of a task and on its exit
17 "pid", "tid" and "task" are used interchangeably and refer to the standard
21 "tgid", "process" and "thread group" are used interchangeably and refer to the
30 socket (NETLINK_GENERIC family) and sends commands specifying a pid or a tgid.
35 sends a register command and specifies a cpumask. Whenever a task exits on
38 to be limited and assists in flow control over the netlink interface and is
44 group, both past and present.
48 send commands and process responses, listen for per-tid/tgid exit data,
49 write the data received to a file and do basic flow control by increasing
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/ |
| D | clock-bindings.txt | 1 This binding is a work-in-progress, and are based on some experimental
6 nodes use a phandle and clock specifier pair to connect clock provider
18 with a single clock output and 1 for nodes with multiple
25 specific to the clock provider, and is only provided to
29 is recommended to omit this property and create a binding
43 "ckil" and the second named "ckih". Consumer nodes always reference
51 For example, if we have two clocks <&oscillator 1> and <&oscillator 3>:
66 clocks: List of phandle and clock specifier pairs, one pair
88 This represents a device with two clock inputs, named "baud" and "register".
89 The baud clock is connected to output 1 of the &osc device, and the register
[all …]
|
| D | nvidia,tegra124-car.txt | 1 NVIDIA Tegra124 and Tegra132 Clock And Reset Controller
7 for muxing and gating Tegra's clocks, and setting their rates.
11 - reg : Should contain CAR registers location and length
12 - clocks : Should contain phandle and clock specifiers for two clocks:
13 the 32 KHz "32k_in", and the board-specific oscillator "osc".
18 to Tegra124 and Tegra132) and <dt-bindings/clock/tegra124-car.h>
|
| /linux-4.1.27/Documentation/memory-devices/ |
| D | ti-emif.txt | 26 supports one or more of DDR2, DDR3, and LPDDR2 SDRAM protocols.
29 parameters and other settings during frequency, voltage and
34 DDR device details and other board dependent and SoC dependent
37 - Device AC timings: 'struct lpddr2_timings' and 'struct lpddr2_min_tck'
45 EMIF driver registers notifiers for voltage and frequency changes
46 affecting EMIF and takes appropriate actions when these are invoked.
54 - regcache_dump : dump of register values calculated and saved for all
|
| /linux-4.1.27/ |
| D | COPYING | 4 of the kernel, and does *not* fall under the heading of "derived work".
7 kernel) is copyrighted by me and others who actually wrote it.
22 Everyone is permitted to copy and distribute verbatim copies
28 freedom to share and change it. By contrast, the GNU General Public
29 License is intended to guarantee your freedom to share and change free
32 Foundation's software and to any other program whose authors commit to
39 have the freedom to distribute copies of free software (and charge for
42 in new free programs; and that you know you can do these things.
55 We protect your rights with two steps: (1) copyright the software, and
57 distribute and/or modify the software.
[all …]
|
| /linux-4.1.27/drivers/fmc/ |
| D | Kconfig | 9 FMC (FPGA Mezzanine Carrier) is a mechanical and electrical
12 and mezzanine based on identifiers stored in the internal I2C
15 The framework was born outside of the kernel and at this time
16 the off-tree code base is more complete. Code and documentation
25 that can be rewritten at run time and usef for matching
31 This is a fake mezzanine driver, to show how FMC works and test it.
38 This driver matches every mezzanine device and can write the
40 its binary and the function carrier->reprogram to actually do it.
46 This driver matches every mezzanine device and allows user
47 space to read and write registers using a char device. It
|
| /linux-4.1.27/Documentation/arm/Samsung/ |
| D | Overview.txt | 9 the current kernel support, how to use it and where to find the code
15 - S3C64XX: S3C6400 and S3C6410
23 deals with the architecture and drivers specific to these devices.
26 on the implementation details and specific support.
42 The directory layout is currently being restructured, and consists of
43 several platform directories and then the machine specific directories
46 plat-samsung provides the base for all the implementations, and is the
48 specific information. It contains the base clock, GPIO and device definitions
53 plat-s5p is for s5p specific builds, and contains common support for the
61 The old plat-s3c and plat-s5pc1xx directories have been removed, with
[all …]
|
| /linux-4.1.27/drivers/ide/ |
| D | Kconfig | 14 If you say Y here, your kernel will be able to manage ATA/(E)IDE and
15 ATAPI units. The most common cases are IDE hard drives and ATAPI
20 the newer ATA subsystem ("Serial ATA (prod) and Parallel ATA
54 and supports most modern SATA controllers. In order to use it
55 you may take a look at "Serial ATA (prod) and Parallel ATA
64 supports SATA controllers, and this (IDE) driver supports
97 For information about jumper settings and the question
108 and CD-ROM drives connected through a PCMCIA card.
114 Support for Delkin, ASKA, and Workbit Cardbus CompactFlash
115 Adapters. This may also work for similar SD and XD adapters.
[all …]
|
| /linux-4.1.27/drivers/hwmon/pmbus/ |
| D | Kconfig | 23 MDT040, NCP4200, NCP4208, PDT003, PDT006, PDT012, UDT020, and TPS40400.
29 tristate "Analog Devices ADM1275 and compatibles"
33 Devices ADM1075, ADM1275, and ADM1276 Hot-Swap Controller and Digital
40 tristate "National Semiconductor LM25066 and compatibles"
44 Semiconductor LM25056, LM25066, LM5064, and LM5066.
50 tristate "Linear Technologies LTC2978 and compatibles"
54 Technology LTC2974, LTC2977, LTC2978, LTC3880, LTC3883, and LTM4676.
60 bool "Regulator support for LTC2978 and compatibles"
64 Technology LTC2974, LTC2977, LTC2978, LTC3880, LTC3883, and LTM4676.
77 tristate "Maxim MAX34440 and compatibles"
[all …]
|
| /linux-4.1.27/Documentation/security/ |
| D | keys-trusted-encrypted.txt | 1 Trusted and Encrypted Keys
3 Trusted and Encrypted Keys are two new key types added to the existing kernel
5 and in both cases all keys are created in the kernel, and user space sees,
6 stores, and loads only encrypted blobs. Trusted Keys require the availability
8 Keys can be used on any system. All user level blobs, are displayed and loaded
9 in hex ascii for convenience, and are integrity verified.
11 Trusted Keys use a TPM both to generate and to seal the keys. Keys are sealed
12 under a 2048 bit RSA key in the TPM, and optionally sealed to specified PCR
13 (integrity measurement) values, and only unsealed by the TPM, if PCRs and blob
16 when the kernel and initramfs are updated. The same key can have many saved
[all …]
|
| /linux-4.1.27/tools/usb/usbip/ |
| D | COPYING | 6 Everyone is permitted to copy and distribute verbatim copies
12 freedom to share and change it. By contrast, the GNU General Public
13 License is intended to guarantee your freedom to share and change free
16 Foundation's software and to any other program whose authors commit to
23 have the freedom to distribute copies of free software (and charge for
26 in new free programs; and that you know you can do these things.
39 We protect your rights with two steps: (1) copyright the software, and
41 distribute and/or modify the software.
43 Also, for each author's protection and ours, we want to make certain
45 software. If the software is modified by someone else and passed on, we
[all …]
|
| /linux-4.1.27/drivers/staging/rtl8192e/ |
| D | license | 13 Everyone is permitted to copy and distribute verbatim copies of this license
19 share and change it. By contrast, the GNU General Public License is intended
20 to guarantee your freedom to share and change free software--to make sure
22 to most of the Free Software Foundation's software and to any other program
29 to distribute copies of free software (and charge for this service if you
31 can change the software or use pieces of it in new free programs; and that
44 We protect your rights with two steps: (1) copyright the software, and (2)
46 and/or modify the software.
48 Also, for each author's protection and ours, we want to make certain that
50 the software is modified by someone else and passed on, we want its
[all …]
|
| /linux-4.1.27/drivers/staging/rtl8192u/ |
| D | copying | 6 Everyone is permitted to copy and distribute verbatim copies
12 freedom to share and change it. By contrast, the GNU General Public
13 License is intended to guarantee your freedom to share and change free
16 Foundation's software and to any other program whose authors commit to
23 have the freedom to distribute copies of free software (and charge for
26 in new free programs; and that you know you can do these things.
39 We protect your rights with two steps: (1) copyright the software, and
41 distribute and/or modify the software.
43 Also, for each author's protection and ours, we want to make certain
45 software. If the software is modified by someone else and passed on, we
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/hwmon/ |
| D | ads1015.txt | 8 0: Voltage over AIN0 and AIN1.
9 1: Voltage over AIN0 and AIN3.
10 2: Voltage over AIN1 and AIN3.
11 3: Voltage over AIN2 and AIN3.
12 4: Voltage over AIN0 and GND.
13 5: Voltage over AIN1 and GND.
14 6: Voltage over AIN2 and GND.
15 7: Voltage over AIN3 and GND.
|
| /linux-4.1.27/Documentation/i2c/ |
| D | summary | 1 I2C and SMBus
9 don't meet branding requirements, and so are not advertised as being I2C.
11 SMBus (System Management Bus) is based on the I2C protocol, and is mostly
12 a subset of I2C protocols and signaling. Many I2C devices will work on an
16 and hardware monitoring chips.
20 meet both SMBus and I2C electrical constraints; and others which can't
39 data in the Client structure. Usually, Driver and Client are more closely
40 integrated than Algorithm and Adapter.
42 For a given configuration, you will need a driver for your I2C bus, and
|
| D | writing-clients | 4 To set up a driver, you need to do several things. Some are optional, and
22 Usually, you will implement a single driver structure, and instantiate
24 routines, and should be zero-initialized except for fields with data you
26 driver model device node, and its I2C address.
54 The name field is the driver name, and must not contain spaces. It
89 I have found it useful to define foo_read and foo_write functions for this.
94 The below functions are simple examples, and should not be copied
116 Probing and attaching
120 monitoring chips on PC motherboards, and thus used to embed some assumptions
121 that were more appropriate to SMBus (and PCs) than to I2C. One of these
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/ |
| D | exynos4-fimc-is.txt | 5 processor, ISP, DRC and FD IP blocks and peripheral devices such as UART, I2C
6 and SPI bus controllers, PWM and ADC.
12 - compatible : should be "samsung,exynos4212-fimc-is" for Exynos4212 and
14 - reg : physical base address and length of the registers set;
27 - reg : must contain PMU physical base address and size of the register set.
29 The following are the FIMC-IS peripheral device nodes and can be specified
37 - compatible : should be "samsung,exynos4212-i2c-isp" for Exynos4212 and
39 - reg : physical base address and length of the registers set;
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | README.OSS | 16 they are gone forever. Keeping this in mind and with a grain of salt this
17 document can be still interesting and very helpful.
25 Please read the SOUND-HOWTO (available from sunsite.unc.edu and other Linux FTP
27 date but still very useful. Information about bug fixes and such things
37 Packages "snd-util-3.8.tar.gz" and "snd-data-0.1.tar.Z"
57 Craig Metz 1/2 of the PAS16 Mixer and PCM support
59 Mika Liljeberg uLaw encoding and decoding routines
61 Greg Lee Volume computation algorithm for the GUS and
66 Anders Baekgaard Bug hunting and valuable suggestions.
69 Megens SA MIDI recording for SB and SB Pro (initial version).
[all …]
|
| /linux-4.1.27/arch/m68k/ifpsp060/ |
| D | TEST.DOC | 9 THE SOFTWARE is provided on an "AS IS" basis and without warranty.
13 and any warranty against infringement with regard to the SOFTWARE
14 (INCLUDING ANY MODIFIED VERSIONS THEREOF) and any accompanying written materials.
21 Motorola assumes no responsibility for the maintenance and support of the SOFTWARE.
23 You are hereby granted a copyright license to use, modify, and distribute the SOFTWARE
24 so long as this entire notice is retained without alteration in any modified and/or
25 redistributed versions, and that such modified versions are clearly identified as such.
32 The files itest.sa and ftest.sa contain simple tests to check
33 the state of the 68060ISP and 68060FPSP once they have been installed.
37 The release files itest.sa and ftest.sa are essentially
[all …]
|
| /linux-4.1.27/Documentation/crypto/ |
| D | asymmetric-keys.txt | 24 associated with the key and provides operations to describe and destroy it.
28 A completely in-kernel key retention and operation subtype can be defined, but
30 a TPM) that might be used to both retain the relevant key and perform
37 subtype of the key and define the operations that can be done on that key.
49 the opportunity to pre-parse a key and to determine the description the key
101 and key identifier representations:
115 required for verification, but not currently supported, and others
116 (eg. decryption and signature generation) require extra key data.
128 The caller must have already obtained the key from some source and can then use
129 it to check the signature. The caller must have parsed the signature and
[all …]
|
| D | descore-readme.txt | 7 This program is free software; you can redistribute it and/or modify
43 and then move on to the common abstract skeleton with this one in mind.
57 and password cracking, i haven't really bothered yet to speed up
70 encryption/decryption is still slower on the sparc and 68000.
71 more specifically, 19-40% slower on the 68020 and 11-35% slower
89 it's 39%-106% slower. because he was interested in fast crypt(3) and
98 crypt function and i didn't feel like ripping it out and measuring
100 des iteration; above, Quick (64k) takes 21 and Small (2k) takes 37.
102 to use only 128k. his tables and code are machine independent.
117 of tables and appears to be slow.
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
| D | renesas,pfc-pinctrl.txt | 1 * Renesas Pin Function Controller (GPIO and Pin Mux/Config)
4 R8A73A4 and R8A7740 it also acts as a GPIO controller.
22 - reg: Base address and length of each memory resource used by the pin
31 IRQ pins. This property is mandatory when the PFC handles GPIOs and
37 configuration node" and for the common pinctrl bindings used by client devices.
41 function to select on those pin(s) and pin configuration parameters (such as
42 pull-up and pull-down).
45 or grouped in child subnodes. Both pin muxing and configuration parameters can
46 be grouped in that way and referenced as a single pin configuration node by
50 pins or pin groups properties) and contain at least a function or one
[all …]
|
| /linux-4.1.27/drivers/pnp/pnpbios/ |
| D | Kconfig | 2 # Plug and Play BIOS configuration
5 bool "Plug and Play BIOS support"
9 Linux uses the PNPBIOS as defined in "Plug and Play BIOS
16 If you would like the kernel to detect and allocate resources to
19 conflicts between mainboard devices and other bus devices.
26 bool "Plug and Play BIOS /proc interface"
29 If you say Y here and to "/proc file system support", you will be
31 allocation, ESCD, and other PNPBIOS services. Using this
38 PNPBIOS /proc interface tools (lspnp and setpnp).
|
| /linux-4.1.27/drivers/zorro/ |
| D | zorro.ids | 8 # Manufacturers and Products. Please keep sorted.
22 1300 Warp Engine [Accelerator, SCSI Host Adapter and RAM Expansion]
40 5000 A2620 68020 [Accelerator and RAM Expansion]
41 5100 A2630 68030 [Accelerator and RAM Expansion]
90 3900 Hurricane 2800 [Accelerator and RAM Expansion]
91 5700 Hurricane 2800 [Accelerator and RAM Expansion]
103 0500 500 [SCSI Host Adapter and RAM Expansion]
112 1100 Magnum 40 [Accelerator and SCSI Host Adapter]
118 0800 Impact Series I [SCSI Host Adapter and RAM Expansion]
127 1000 DKM 1202 [FPU and RAM Expansion]
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/ |
| D | samsung,s3c24xx-irq.txt | 4 varying number of interrupt sources. The set consists of a main- and sub-
5 controller and on newer SoCs even a second main controller.
9 for machines before s3c2416 and "samsung,s3c2416-irq" for s3c2416 and later.
11 - reg: Physical base address of the controller and length of memory mapped
17 interrupt source. The value shall be 4 and interrupt descriptor shall
24 - 2 ... second main controller on s3c2416 and s3c2450
25 parent_irq contains the parent bit in the main controller and will be
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | gic.txt | 4 interrupts (PPI), shared processor interrupts (SPI) and software
7 Primary GIC is attached directly to the CPU and typically has PPIs and SGIs.
8 Secondary GICs are cascaded into the upward interrupt controller and do not
25 interrupt source. The type shall be a <u32> and the value shall be 3.
35 bits[3:0] trigger type and level flags.
44 DEFINED and as such not guaranteed to be present (most SoC available
45 in 2014 seem to ignore the setting of this flag and use the hardware
48 - reg : Specifies base physical address(s) and size of the GIC registers. The
49 first region is the GIC distributor register base and size. The 2nd region is
50 the GIC cpu interface register base and size.
[all …]
|
| /linux-4.1.27/arch/arm/boot/dts/ |
| D | alpine-db.dts | 4 * This program is free software; you can redistribute it and/or modify it
5 * under the terms and conditions of the GNU General Public License,
8 * Alternatively, redistribution and use in source and binary forms, with or
13 * this list of conditions and the following disclaimer.
16 * notice, this list of conditions and the following disclaimer in
17 * the documentation and/or other materials provided with the
|
| /linux-4.1.27/drivers/devfreq/ |
| D | Kconfig | 2 bool "Generic Dynamic Voltage and Frequency Scaling (DVFS) support"
5 A device may have a list of frequencies and voltages available.
10 Each device may have its own governor and policy. Devfreq can
11 reevaluate the device state periodically and/or based on the
17 is attached to a single device and returns a "representative"
20 responsibility to "interpret" the representative frequency and
76 and Exynos4212/4412 memory interface and bus (vdd_mif + vdd_int).
77 It reads PPMU counters of memory controllers and adjusts
78 the operating frequencies and voltages with OPP support.
88 It reads PPMU counters of memory controllers and adjusts the
[all …]
|