| /Documentation/devicetree/bindings/power/reset/ |
| D | nvmem-reboot-mode.txt | 1 NVMEM reboot mode driver
3 This driver gets reboot mode magic value from reboot-mode driver
4 and stores it in a NVMEM cell named "reboot-mode". Then the bootloader
9 - compatible: should be "nvmem-reboot-mode".
10 - nvmem-cells: A phandle to the reboot mode provided by a nvmem device.
11 - nvmem-cell-names: Should be "reboot-mode".
13 The rest of the properties should follow the generic reboot-mode description
14 found in reboot-mode.txt
17 reboot-mode {
18 compatible = "nvmem-reboot-mode";
[all …]
|
| D | reboot-mode.yaml | 4 $id: http://devicetree.org/schemas/power/reset/reboot-mode.yaml#
7 title: Generic reboot mode core map
13 This driver get reboot mode arguments and call the write
18 All mode properties are vendor specific, it is a indication to tell
20 as mode-xxx = <magic> (xxx is mode name, magic should be a non-zero value).
23 - normal: Normal reboot mode, system reboot with command "reboot".
24 - recovery: Android Recovery mode, it is a mode to format the device or update a new image.
25 …- bootloader: Android fastboot mode, it's a mode to re-flash partitions on the Android based devic…
26 - loader: A bootloader mode, it's a mode used to download image on Rockchip platform,
30 mode-normal:
[all …]
|
| D | syscon-reboot-mode.yaml | 4 $id: http://devicetree.org/schemas/power/reset/syscon-reboot-mode.yaml#
7 title: Generic SYSCON reboot mode driver
13 This driver gets reboot mode magic value from reboot-mode driver
17 parental dt-node plus the offset. So the SYSCON reboot-mode node
22 const: syscon-reboot-mode
30 description: Offset in the register map for the mode register (in bytes)
33 "^mode-.+":
35 description: Vendor-specific mode value written to the mode register
45 #include <dt-bindings/soc/rockchip,boot-mode.h>
47 reboot-mode {
[all …]
|
| /Documentation/driver-api/usb/ |
| D | typec_bus.rst | 2 API for USB Type-C Alternate Mode drivers
11 every alternate mode, so every alternate mode will need a custom driver.
14 modes by using the SVID and the mode number.
17 mode a port supports, and separate device for every alternate mode the partner
19 mode devices, and the port alternate mode devices must be handled by the port
22 When a new partner alternate mode device is registered, it is linked to the
23 alternate mode device of the port that the partner is attached to, that has
24 matching SVID and mode. Communication between the port driver and alternate mode
27 The port alternate mode devices are used as a proxy between the partner and the
28 alternate mode drivers, so the port drivers are only expected to pass the SVID
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-typec | 5 Shows if the mode is active or not. The attribute can be used
6 for entering/exiting the mode. Entering/exiting modes is
8 does not return until the enter/exit mode operation has
9 finished. The attribute is notified when the mode is
11 Entering/exiting a mode will also generate uevent KOBJ_CHANGE.
19 Shows description of the mode. The description is optional for
22 What: /sys/bus/typec/devices/.../mode
26 The index number of the mode returned by Discover Modes USB
27 Power Delivery command. Depending on the alternate mode, the
28 mode index may be significant.
[all …]
|
| D | sysfs-bus-intel_th-devices-msc | 7 What: /sys/bus/intel_th/devices/<intel_th_id>-msc<msc-id>/mode
11 Description: (RW) Configure MSC operating mode:
13 - "single", for contiguous buffer mode (high-order alloc);
14 - "multi", for multiblock mode;
15 - "ExI", for DCI handler mode;
16 - "debug", for debug mode;
19 If operating mode changes, existing buffer is deallocated,
29 In single mode, this is a single number of pages, has to be
30 power of 2. In multiblock mode, this is a comma-separated list
43 multi-window mode. In "multi" mode, accepts writes of "1", thereby
[all …]
|
| 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 …]
|
| D | sysfs-platform-renesas_usb3 | 7 The file can show/change the drd mode of usb.
9 Write the following string to change the mode:
11 - "host" - switching mode from peripheral to host.
12 - "peripheral" - switching mode from host to peripheral.
16 - "host" - The mode is host now.
17 - "peripheral" - The mode is peripheral now.
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-netxbig.txt | 10 Mode (gpio-ext bus), delay_on and delay_off.
15 - mode-addr: Mode register address on gpio-ext bus.
16 - mode-val: Mode to value mapping. Each entry is represented by two integers:
17 A mode and the corresponding value on the gpio-ext bus.
37 mode-addr = <0>;
38 mode-val = <NETXBIG_LED_OFF 0
47 mode-addr = <0>;
48 mode-val = <NETXBIG_LED_OFF 0
56 mode-addr = <3>;
57 mode-val = <NETXBIG_LED_OFF 0
[all …]
|
| /Documentation/admin-guide/ |
| D | svga.rst | 4 Video Mode Selection Support 2.13
12 This small document describes the "Video Mode Selection" feature which
21 enter ``scan`` on the video mode prompt, pick the mode you want to use,
22 remember its mode ID (the four-digit hexadecimal number) and then
25 The video mode to be used is selected by a kernel parameter which can be
31 NORMAL_VGA - Standard 80x25 mode available on all display adapters.
33 EXTENDED_VGA - Standard 8-pixel font mode: 80x43 on EGA, 80x50 on VGA.
35 ASK_VGA - Display a video mode menu upon startup (see below).
40 mode list displayed may vary as the kernel version changes, because the
42 better to use absolute mode numbers instead.
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-class-typec | 9 alternate mode.
11 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/
15 Every supported mode will have its own directory. The name of
16 a mode will be "mode<index>" (for example mode1), where <index>
17 is the actual index to the mode VDO returned by Discover Modes
20 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/description
24 Shows description of the mode. The description is optional for
27 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/vdo
32 for this mode.
34 What: /sys/class/typec/<port|partner|cable>/<dev>/mode<index>/active
[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/fb/ |
| D | arkfb.rst | 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 | s3fb.rst | 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.rst | 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 | sisfb.rst | 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
81 - or simply use the VESA mode number in hexadecimal or decimal.
88 Additionally, sisfb understands the keyword "vesa" followed by a VESA mode
[all …]
|
| /Documentation/input/devices/ |
| D | cma3000_d0x.rst | 20 Motion Detect Mode:
21 Its the low power mode where interrupts are generated only
24 Measurement Mode:
25 This mode is used to read the acceleration data on X,Y,Z
28 Free fall Mode:
29 This mode is intended to save system resources.
38 Initial configuration for bus mode is set in non volatile memory and can later
61 mode:
62 Default Operating mode
109 mode::
[all …]
|
| /Documentation/networking/ |
| D | ipvlan.rst | 34 ip link add link <master> name <slave> type ipvlan [ mode MODE ] [ FLAGS ]
36 MODE: l3 (default) | l3s | l2
42 L3 bridge mode::
45 (b) This command will create IPvlan link in L2 bridge mode::
47 bash# ip link add link eth0 name ipvl0 type ipvlan mode l2 bridge
49 (c) This command will create an IPvlan device in L2 private mode::
51 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 private
53 (d) This command will create an IPvlan device in L2 vepa mode::
55 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 vepa
63 operate in the same (selected) mode. The RX mode is almost identical except
[all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | adc128d818.txt | 6 - Mode 0: 7 single-ended voltage readings (IN0-IN6),
8 - Mode 1: 8 single-ended voltage readings (IN0-IN7),
10 - Mode 2: 4 pseudo-differential voltage readings
13 - Mode 3: 4 single-ended voltage readings (IN0-IN3),
18 If no operation mode is configured via device tree, the driver keeps the
19 currently active chip operation mode (default is mode 0).
29 - ti,mode: Operation mode (u8) (see above).
32 Example (operation mode 2):
37 ti,mode = /bits/ 8 <2>;
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-g-mode.rst | 32 Pointer to CEC mode.
40 filehandle to initiator and/or follower mode which can be exclusive
41 depending on the chosen mode. The initiator is the filehandle that is
61 by the follower. The follower can enable the passthrough mode. In that
65 the passthrough mode. See :ref:`cec-core-processing` for details.
77 .. _cec-mode-initiator_e:
84 * .. _`CEC-MODE-NO-INITIATOR`:
90 * .. _`CEC-MODE-INITIATOR`:
97 * .. _`CEC-MODE-EXCL-INITIATOR`:
111 .. _cec-mode-follower_e:
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | micrel.txt | 7 - micrel,led-mode : LED mode value to set for PHYs with configurable LEDs.
9 Configure the LED mode with single value. The list of PHYs and the
20 See the respective PHY datasheet for the mode values.
23 bit selects 25 MHz mode
26 than 50 MHz clock mode.
31 actually select a mode.
39 - micrel,fiber-mode: If present the PHY is configured to operate in fiber mode
41 Some PHYs, such as the KSZ8041FTL variant, support fiber mode, enabled
43 registers whether the PHY is in fiber mode, so this boolean device tree
46 In fiber mode, auto-negotiation is disabled and the PHY can only work in
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-hi3798cv200-combphy.txt | 8 - #phy-cells: Should be 1. The cell number is used to select the phy mode
16 - hisilicon,fixed-mode: If the phy device doesn't support mode select
17 but a fixed mode setting, the property should be present to specify
18 the particular mode.
19 - hisilicon,mode-select-bits: If the phy device support mode select,
25 - Between hisilicon,fixed-mode and hisilicon,mode-select-bits, one and only
28 COMBPHY configuration/state and PERI_CTRL register used to select PHY mode.
48 hisilicon,fixed-mode = <PHY_TYPE_USB3>;
57 hisilicon,mode-select-bits = <0x0008 11 (0x3 << 11)>;
|
| /Documentation/translations/zh_CN/filesystems/ |
| D | debugfs.rst | 36 和“ mode”挂载选项。请注意，debugfs API仅按照GPL协议导出到模块。
51 struct dentry *debugfs_create_file(const char *name, umode_t mode,
62 struct dentry *debugfs_create_file_size(const char *name, umode_t mode,
72 void debugfs_create_u8(const char *name, umode_t mode,
74 void debugfs_create_u16(const char *name, umode_t mode,
76 struct dentry *debugfs_create_u32(const char *name, umode_t mode,
78 void debugfs_create_u64(const char *name, umode_t mode,
85 void debugfs_create_x8(const char *name, umode_t mode,
87 void debugfs_create_x16(const char *name, umode_t mode,
89 void debugfs_create_x32(const char *name, umode_t mode,
[all …]
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-send-mode.rst | 14 LIRC_GET_SEND_MODE/LIRC_SET_SEND_MODE - Get/set current transmit mode.
21 ``int ioctl(int fd, LIRC_GET_SEND_MODE, __u32 *mode)``
25 ``int ioctl(int fd, LIRC_SET_SEND_MODE, __u32 *mode)``
33 ``mode``
34 The mode used for transmitting.
39 Get/set current transmit mode.
41 Only :ref:`LIRC_MODE_PULSE <lirc-mode-pulse>` and
42 :ref:`LIRC_MODE_SCANCODE <lirc-mode-scancode>` are supported by for IR send,
71 - Invalid mode or invalid mode for this device.
|
| D | lirc-get-rec-mode.rst | 14 LIRC_GET_REC_MODE/LIRC_SET_REC_MODE - Get/set current receive mode.
21 ``int ioctl(int fd, LIRC_GET_REC_MODE, __u32 *mode)``
25 ``int ioctl(int fd, LIRC_SET_REC_MODE, __u32 *mode)``
33 ``mode``
34 Mode used for receive.
39 Get and set the current receive mode. Only
40 :ref:`LIRC_MODE_MODE2 <lirc-mode-mode2>` and
41 :ref:`LIRC_MODE_SCANCODE <lirc-mode-scancode>` are supported.
69 - Invalid mode or invalid mode for this device.
|