| /Documentation/spi/ |
| D | spidev_test.c | 33 static uint32_t mode; variable
60 if (mode & SPI_TX_QUAD) in transfer()
62 else if (mode & SPI_TX_DUAL) in transfer()
64 if (mode & SPI_RX_QUAD) in transfer()
66 else if (mode & SPI_RX_DUAL) in transfer()
68 if (!(mode & SPI_LOOP)) { in transfer()
69 if (mode & (SPI_TX_QUAD | SPI_TX_DUAL)) in transfer()
71 else if (mode & (SPI_RX_QUAD | SPI_RX_DUAL)) in transfer()
148 mode |= SPI_LOOP; in parse_opts()
151 mode |= SPI_CPHA; in parse_opts()
[all …]
|
| /Documentation/fb/ |
| D | s3fb.txt | 27 * 8 bpp pseudocolor mode (with 18bit palette)
29 * 24 bpp truecolor mode (RGB 888) on (only on Virge VX)
30 * 32 bpp truecolor mode (RGB 888) on (not on Virge VX)
31 * text mode (activated by bpp = 0)
32 * interlaced mode variant (not available in text mode)
33 * doublescan mode variant (not available in text mode)
38 Text mode is supported even in higher resolutions, but there is limitation to
41 limitation is not enforced by driver. Text mode supports 8bit wide fonts only
42 (hardware limitation) and 16bit tall fonts (driver limitation). Text mode
45 There are two 4 bpp modes. First mode (selected if nonstd == 0) is mode with
[all …]
|
| D | vt8623fb.txt | 19 * 8 bpp pseudocolor mode (with 18bit palette)
20 * 16 bpp truecolor mode (RGB 565)
21 * 32 bpp truecolor mode (RGB 888)
22 * text mode (activated by bpp = 0)
23 * doublescan mode variant (not available in text mode)
28 Text mode is supported even in higher resolutions, but there is limitation to
30 driver. Text mode supports 8bit wide fonts only (hardware limitation) and
33 There are two 4 bpp modes. First mode (selected if nonstd == 0) is mode with
34 packed pixels, high nibble first. Second mode (selected if nonstd == 1) is mode
48 * interlaced mode variant
[all …]
|
| D | arkfb.txt | 20 * 8 bpp pseudocolor mode (with 18bit palette)
22 * 24 bpp truecolor mode (RGB 888)
23 * 32 bpp truecolor mode (RGB 888)
24 * text mode (activated by bpp = 0)
25 * doublescan mode variant (not available in text mode)
29 Text mode is supported even in higher resolutions, but there is limitation to
31 hardware). This limitation is not enforced by driver. Text mode supports 8bit
33 limitation). Unfortunately character attributes (like color) in text mode are
36 There are two 4 bpp modes. First mode (selected if nonstd == 0) is mode with
37 packed pixels, high nibble first. Second mode (selected if nonstd == 1) is mode
[all …]
|
| D | viafb.modes | 28 mode "640x480-60"
31 timings 39722 48 16 33 10 96 2 endmode mode "480x640-60"
52 mode "640x480-75"
73 mode "640x480-85"
94 mode "640x480-100"
115 mode "640x480-120"
136 mode "720x480-60"
157 mode "800x480-60"
178 mode "720x576-60"
199 mode "800x600-60"
[all …]
|
| D | vesafb.txt | 7 The idea is simple: Turn on graphics mode at boot time with the help
12 graphics mode. Switching mode later on (in protected mode) is
13 impossible; BIOS calls work in real mode only. VESA BIOS Extensions
26 * graphic mode is slower than text mode...
35 You should compile in both vgacon (for text mode) and vesafb (for
36 graphics mode). Which of them takes over the console depends on
37 whenever the specified mode is text or graphics.
40 vga=ask and hit return. The mode you wish to use is derived from the
41 VESA mode number. Here are those VESA mode numbers:
50 The video mode number of the Linux kernel is the VESA mode number plus
[all …]
|
| D | sisfb.txt | 46 append="video=sisfb:mode:1024x768x16,mem:12288,rate:75"
50 modprobe sisfb mode=1024x768x16 rate=75 mem=12288
54 the parameter format is video=sisfb:mode:none or video=sisfb:mode:1024x768x16
55 (or whatever mode you want to use, alternatively using any other format
56 described above or the vesa keyword instead of mode). If compiled as a module,
57 the parameter format reads mode=none or mode=1024x768x16 (or whatever mode you
62 video=sisfb:mode:1024x768x16,rate:75,mem:12288
74 The desired display mode can be specified using the keyword "mode" with
80 - or simply use the VESA mode number in hexadecimal or decimal.
87 Additionally, sisfb understands the keyword "vesa" followed by a VESA mode
[all …]
|
| D | modedb.txt | 3 modedb default video mode support
6 Currently all frame buffer device drivers have their own video mode databases,
11 - one generic video mode database with a fair amount of standard videomodes
13 - the possibility to supply your own mode database for graphics hardware that
18 consider that to be a video mode option. If no frame buffer device is specified
19 in a video= option, fbmem considers that to be a global video mode option.
21 Valid mode specifiers (mode_option argument):
31 VESA(TM) Coordinated Video Timings instead of looking up the mode from a table.
33 If 'i' is specified, calculate for an interlaced mode. And if 'm' is
48 To force the VGA output to be enabled and drive a specific mode say:
[all …]
|
| /Documentation/devicetree/bindings/hsi/ |
| D | client-devices.txt | 9 - hsi-rx-mode: Receiver Bit transmission mode ("stream" or "frame")
10 - hsi-tx-mode: Transmitter Bit transmission mode ("stream" or "frame")
11 - hsi-mode: May be used instead hsi-rx-mode and hsi-tx-mode if
12 the transmission mode is the same for receiver and
16 - hsi-arb-mode: Arbitration mode for TX frame ("round-robin", "priority")
37 hsi-mode = "frame";
39 hsi-arb-mode = "round-robin";
|
| /Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 3 The endianness mode of CPU & Device scenarios:
15 meaning that the CPU and the Device are in the same endianness mode,
19 Scenario 1 : CPU in LE mode & device in LE mode.
26 Scenario 2 : CPU in LE mode & device in BE mode.
34 Scenario 3 : CPU in BE mode & device in BE mode.
41 Scenario 4 : CPU in BE mode & device in LE mode.
|
| /Documentation/ |
| D | svga.txt | 13 ** enter `scan' on the video mode prompt, pick the mode you want to use,
14 ** remember its mode ID (the four-digit hexadecimal number) and then
17 The video mode to be used is selected by a kernel parameter which can be
23 NORMAL_VGA - Standard 80x25 mode available on all display adapters.
25 EXTENDED_VGA - Standard 8-pixel font mode: 80x43 on EGA, 80x50 on VGA.
27 ASK_VGA - Display a video mode menu upon startup (see below).
32 mode list displayed may vary as the kernel version changes, because the
34 better to use absolute mode numbers instead.
36 0x.... - Hexadecimal video mode ID (also displayed on the menu, see below
42 The ASK_VGA mode causes the kernel to offer a video mode menu upon
[all …]
|
| /Documentation/input/ |
| D | cma3000_d0x.txt | 18 Motion Detect Mode: Its the low power mode where interrupts are generated only
21 Measurement Mode: This mode is used to read the acceleration data on X,Y,Z
24 Free fall Mode: This mode is intended to save system resources.
31 Initial configuration for bus mode is set in non volatile memory and can later
49 mode: Default Operating mode
90 mode:
91 0: power down mode
92 1: 100 Hz Measurement mode
93 2: 400 Hz Measurement mode
94 3: 40 Hz Measurement mode
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-msi-laptop | 46 Contains either 0 or 1 and indicates if turbo mode is turned
47 on. In turbo mode power LED is orange and processor is
48 overclocked. Turbo mode is available only if charging. It is
49 only possible to toggle turbo mode state by pressing Fn+F10,
51 If user presses Fn+F10 too frequent, turbo mode state is not
59 Contains either 0 or 1 and indicates if ECO mode is turned on.
60 In ECO mode power LED is green and userspace should do some
61 powersaving actions. ECO mode is available only on battery
62 power. ECO mode can only be toggled by pressing Fn+F10.
70 * 0 -> Turbo mode is off
[all …]
|
| /Documentation/ia64/ |
| D | fsys.txt | 12 Using the "epc" instruction effectively introduces a new mode of
13 execution to the ia64 linux kernel. We call this mode the
14 "fsys-mode". To recap, the normal states of execution are:
16 - kernel mode:
21 - user mode:
26 - bank 0 interruption-handling mode:
32 In contrast, fsys-mode has the following special properties:
41 - execution is interruptible and preemptible (an fsys-mode handler
46 in fsys-mode (they point to the user-level stacks, which may
49 In summary, fsys-mode is much more similar to running in user-mode
[all …]
|
| /Documentation/frv/ |
| D | kernel-ABI.txt | 22 (*) Internal kernel-mode register ABI
23 (*) Internal debug-mode register ABI
47 (1) User mode.
49 Basic userspace running mode.
51 (2) Kernel mode.
53 Normal kernel mode. There are many additional control registers
54 available that may be accessed in this mode, in addition to all the
55 stuff available to user mode. This has two submodes:
59 Exceptions will invoke the appropriate normal kernel mode
66 debug mode instead.
[all …]
|
| /Documentation/devicetree/bindings/serial/ |
| D | fsl-imx-uart.txt | 10 - fsl,irda-mode : Indicate the uart supports irda mode
11 - fsl,dte-mode : Indicate the uart works in DTE mode. The uart works
12 is DCE mode by default.
28 fsl,dte-mode;
|
| /Documentation/devicetree/bindings/iio/frequency/ |
| D | adf4350.txt | 27 for integer-N mode. Default = factional-N mode.
39 - adi,low-spur-mode-enable: Enables low spur mode.
40 Default = Low noise mode.
46 - adi,band-select-clock-mode-high-enable: Enables faster band
49 adi,12bit-clkdiv-mode != 0
50 - adi,clk-divider-mode:
51 Valid values for the clkdiv mode are:
60 Valid values for the power mode are:
66 Valid values for the power mode are:
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | adv7343.txt | 13 - adi,power-mode-sleep-mode: on enable the current consumption is reduced to
16 - adi,power-mode-pll-ctrl: PLL and oversampling control. This control allows
19 - ad,adv7343-power-mode-dac: array configuring the power on/off DAC's 1..6,
38 adi,power-mode-sleep-mode;
39 adi,power-mode-pll-ctrl;
|
| /Documentation/devicetree/bindings/mips/cavium/ |
| D | bootbus.txt | 55 - cavium,wait-mode: Optional. If present, wait mode (WAITM) is selected.
57 - cavium,page-mode: Optional. If present, page mode (PAGEM) is selected.
62 - cavium,ale-mode: Optional. If present, ALE mode is selected.
64 - cavium,sam-mode: Optional. If present, SAM mode is selected.
66 - cavium,or-mode: Optional. If present, OR mode is selected.
120 cavium,wait-mode;
|
| /Documentation/hwmon/ |
| D | g762 | 38 fan1_alarm: in closed-loop control mode, if fan RPM value is 25% out
42 pwm1_enable: set current fan speed control mode i.e. 1 for manual fan
47 pwm1_mode: set or get fan driving mode: 1 for PWM mode, 0 for DC mode.
49 pwm1: get or set PWM fan control value in open-loop mode. This is an
53 Both in PWM mode ('pwm1_mode' set to 1) and DC mode ('pwm1_mode' set to 0),
54 when current fan speed control mode is open-loop ('pwm1_enable' set to 1),
56 entry (0 stops the fan, 255 makes it run at full speed). In closed-loop mode
58 the chip via 'fan1_target'. In closed-loop mode, the target speed is compared
|
| D | f71882fg | 100 voltage) mode, where 0-100% duty cycle (0-100% of 12V) is specified. And RPM
101 mode where the actual RPM of the fan (as measured) is controlled and the speed
106 important difference is that in RPM mode the 0-100% controls the fan speed
108 RPM mode, it will also set fan#_full_speed properly, if it does not then
113 registers, so the mode which the BIOS has set is kept. The mode is
116 Three different fan control modes are supported; the mode number is written
118 chips, and some modes may only be available in RPM / PWM mode.
119 Writing an unsupported mode will result in an invalid parameter error.
121 * 1: Manual mode
123 fan#_full_speed by writing to the pwm# file. This mode is only
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,sta350.txt | 27 If parameter is missing, mode 0 will be enabled.
48 - st,ffx-power-output-mode: string
49 The FFX power output mode selects how the FFX output timing is
53 - "full-power-mode"
57 Only required for "st,ffx-power-output-mode" ==
74 - st,am-reduction-mode:
75 If present, FFX mode runs in AM reduction mode, otherwise normal
76 FFX mode is used.
78 - st,odd-pwm-speed-mode:
79 If present, PWM speed mode run on odd speed mode (341.3 kHz) on all
[all …]
|
| D | renesas,fsi.txt | 9 - fsia,stream-mode-support : FSI supports 16bit stream mode.
10 - fsia,use-internal-clock : FSI uses internal clock when master mode.
13 - fsib,stream-mode-support : same as fsia
24 fsia,stream-mode-support;
|
| /Documentation/sound/alsa/ |
| D | Audiophile-Usb.txt | 44 activated at the same time depending on the audio mode selected:
81 module. This module can work in a default mode (without any device-specific
82 parameter), or in an "advanced" mode with the device-specific parameter called
85 3.1 - Default Alsa driver mode
89 capabilities at startup and activate the required mode when required
91 24bit-depth-mode and immediately after wants to switch to a 16bit-depth mode,
98 panel to switch the device working mode. Thus as we'll see in next section, this
99 Default Alsa driver mode can lead to device misconfigurations.
101 Let's get back to the Default Alsa driver mode for now. In this case the
106 * hw:1,2 is Do in AC3/DTS passthrough mode
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | davinci-nand.txt | 42 - nand-ecc-mode: operation mode of the NAND ecc mode. ECC mode
58 - ti,davinci-ecc-mode: operation mode of the NAND ecc mode. ECC mode
86 nand-ecc-mode = "hw";
|