Searched +full:enabled +full:- +full:strings (Results 1 – 25 of 50) sorted by relevance
12
| /Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 10 This will be one of the following strings:
12 'enabled'
16 'enabled' means the regulator output is ON and is supplying
20 supplying power to the system (unless some non-Linux
21 control has enabled it).
36 This will be one of the following strings:
38 - off
39 - on
40 - error
41 - fast
[all …]
|
| D | sysfs-firmware-acpi | 12 image: The image bitmap. Currently a 32-bit BMP.
40 enabled: If set, the ACPI core will handle notifications of
50 cause -EINVAL to be returned.
153 enable the GPE/Fixed Event is valid and enabled.
167 Besides this, user can also write specific strings to these files
180 0 enabled
183 3 enabled
192 4 enabled
200 7 enabled
206 7 enabled
|
| D | sysfs-power | 15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
18 Writing one of the above strings to this file causes the system
21 See Documentation/admin-guide/pm/sleep-states.rst for more
35 Writing one of the above strings to this file causes the mode
39 See Documentation/admin-guide/pm/sleep-states.rst for more
47 suspend-to-disk mechanism. Reading from this file returns
51 'firmware' - means that the memory image will be saved to disk
55 'platform' - the memory image will be saved by the kernel and
59 'shutdown' - the memory image will be saved by the kernel and
[all …]
|
| D | sysfs-class-mic | 8 PCIe form factor add-in Coprocessor card based on the Intel Many
26 MIC device. For example - "x100"
34 MIC device. For example - "A0" or "B0"
99 self-bootable machines. When read, this entry provides
134 valid strings:
135 a) linux - Boot a Linux image.
136 b) flash - Boot an image for flash updates.
178 enabled by default.
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | qcom-wled.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/qcom-wled.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <bjorn.andersson@linaro.org>
11 - Kiran Gunda <kgunda@codeaurora.org>
21 - qcom,pm8941-wled
22 - qcom,pmi8998-wled
23 - qcom,pm660l-wled
24 - qcom,pm8150l-wled
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-lm36274.txt | 1 * Texas Instruments LM36274 4-Channel LCD Backlight Driver w/Integrated Bias
3 The LM36274 is an integrated four-channel WLED driver and LCD bias supply.
4 The backlight boost provides the power to bias four parallel LED strings with
5 up to 29V total output voltage. The 11-bit LED current is programmable via
9 Documentation/devicetree/bindings/mfd/ti-lmu.txt
12 Documentation/devicetree/bindings/regulator/lm363x-regulator.txt
15 - compatible:
16 "ti,lm36274-backlight"
17 - reg : 0
18 - #address-cells : 1
[all …]
|
| /Documentation/usb/ |
| D | gadget_configfs.rst | 50 http://www.spinics.net/lists/linux-usb/msg76388.html)
55 $ mount none $CONFIGFS_HOME -t configfs
60 -----------------------
81 A gadget also needs its serial number, manufacturer and product strings.
82 In order to have a place to store them, a strings subdirectory must be created
85 $ mkdir strings/0x409
87 Then the strings can be specified::
89 $ echo <serial number> > strings/0x409/serialnumber
90 $ echo <manufacturer> > strings/0x409/manufacturer
91 $ echo <product> > strings/0x409/product
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | zynq-7000.txt | 15 - #clock-cells : Must be 1
16 - compatible : "xlnx,ps7-clkc"
17 - reg : SLCR offset and size taken via syscon < 0x100 0x100 >
18 - ps-clk-frequency : Frequency of the oscillator providing ps_clk in HZ
20 - clock-output-names : List of strings used to name the clock outputs. Shall be
24 - clocks : as described in the clock bindings
25 - clock-names : as described in the clock bindings
26 - fclk-enable : Bit mask to enable FCLKs statically at boot time.
28 FCLK will only be enabled if it is actually running at
32 The following strings are optional parameters to the 'clock-names' property in
[all …]
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 19 3) have a USB 3.0 super-speed A-to-A debugging cable.
28 When DbC is initialized and enabled, it will present a debug
30 super-speed port). The debug device is fully compliant with
32 performance full-duplex serial link between the debug target
41 Other uses include simpler, lockless logging instead of a full-
45 kernel with CONFIG_EARLY_PRINTK_USB_XDBC enabled. And, add below
58 "usbcore.autosuspend=-1"
63 should be a USB 3.0 super-speed A-to-A debugging cable.
74 # tail -f /var/log/kern.log
75 [ 1815.983374] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
[all …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | simple-pm-bus.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/bus/simple-pm-bus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Simple Power-Managed Bus
10 - Geert Uytterhoeven <geert+renesas@glider.be>
13 A Simple Power-Managed Bus is a transparent bus that doesn't need a real
18 clock must be enabled for child devices connected to the bus (either
19 on-SoC or externally) to function.
21 While "simple-pm-bus" follows the "simple-bus" set of properties, as
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | attributes.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 -------------------
17 sb.inode\_size = 256, then there are 256 - (128 + 28) = 100 bytes
18 available for in-inode extended attribute storage. The second place
26 Keys are generally assumed to be ASCIIZ strings, whereas values can be
27 strings or binary data.
32 .. list-table::
34 :header-rows: 1
36 * - Offset
37 - Type
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | ste,nomadik.txt | 4 - compatible: "stericsson,db8500-pinctrl", "stericsson,db8540-pinctrl",
5 "stericsson,stn8815-pinctrl"
6 - nomadik-gpio-chips: array of phandles to the corresponding GPIO chips
8 - prcm: phandle to the PRCMU managing the back end of this pin controller
10 Please refer to pinctrl-bindings.txt in this directory for details of the
23 (see pinctrl-bindings.txt):
26 - function: A string containing the name of the function to mux to the
28 - groups : An array of strings. Each string contains the name of a pin
30 set-up.
33 - pins: A string array describing the pins affected by the configuration
[all …]
|
| /Documentation/admin-guide/ |
| D | ext4.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 (64 bit) in keeping with increasing disk capacities and state-of-the-art
12 Mailing list: linux-ext4@vger.kernel.org
23 - The latest version of e2fsprogs can be found at:
35 - Create a new filesystem using the ext4 filesystem type:
37 # mke2fs -t ext4 /dev/hda1
41 # tune2fs -O extents /dev/hda1
46 # tune2fs -I 256 /dev/hda1
48 - Mounting:
50 # mount -t ext4 /dev/hda1 /wherever
[all …]
|
| D | kernel-parameters.txt | 5 force -- enable ACPI if default was off
6 on -- enable ACPI but allow fallback to DT [arm64]
7 off -- disable ACPI if default was on
8 noirq -- do not use ACPI for IRQ routing
9 strict -- Be less tolerant of platforms that are not
11 rsdt -- prefer RSDT over (default) XSDT
12 copy_dsdt -- copy DSDT to memory
26 If set to vendor, prefer vendor-specific driver
50 CONFIG_ACPI_DEBUG must be enabled to produce any ACPI
58 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]
|
| /Documentation/driver-api/ |
| D | eisa.rst | 5 :Author: Marc Zyngier <maz@wild-wind.fr.eu.org>
23 - The bus code implements most of the generic code. It is shared
29 - The bus root driver implements the glue between the bus hardware
37 - The driver offers the bus a list of devices that it manages, and
100 id_table an array of NULL terminated EISA id strings,
102 optionally be paired with a driver-dependent value
106 Documentation/driver-api/driver-model/driver.rst. Only .name,
155 dev generic device (see Documentation/driver-api/driver-model/device.rst)
187 A comma-separated list of slots to be enabled, even if the firmware
192 A comma-separated list of slots to be enabled, even if the firmware
[all …]
|
| D | isa.rst | 27 now (for oldisa-only drivers) become::
52 unsigned int id`` pair directly -- with the device creation completely
59 ALSA would want to keep the old non-load behaviour, it could stick all
69 (such as checking the user wants the card enabled and that port/irq/dma
85 if (dev->platform_data == isa_driver) {
86 if (!isa_driver->match ||
87 isa_driver->match(dev, to_isa_dev(dev)->id))
89 dev->platform_data = NULL;
96 to this driver. Platform devices compare strings, but we don't need to
98 dev->platform_data as a isa_driver pointer which we can then check here.
[all …]
|
| /Documentation/trace/ |
| D | events.rst | 24 ---------------------------------
59 ---------------------------
82 - 0 - all events this file affects are disabled
83 - 1 - all events this file affects are enabled
84 - X - there is a mixture of events enabled and disabled
85 - ? - this file does not affect any event
88 ---------------
92 trace_event=[event-list]
94 event-list is a comma separated list of events. See section 2.1 for event
97 3. Defining an event-enabled tracepoint
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 1 .. SPDX-License-Identifier: GPL-2.0
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
66 -----------
69 hardware-managed P-states (HWP) support. If it works in this mode, the
74 provides its own scaling algorithms for P-state selection. Those algorithms
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | sysfs-api.rst | 19 This how-to focuses on enabling new thermal zone and cooling devices to
30 - `[0-*]` denotes any positive number starting from 0
31 - `[1-*]` denotes any positive number starting from 1
37 ---------------------------------
49 /sys/class/thermal folder as `thermal_zone[0-*]`. It tries to bind all the
61 thermal zone device call-backs.
74 get the current mode (enabled/disabled) of the thermal zone.
76 - "enabled" means the kernel thermal management is
77 enabled.
78 - "disabled" will prevent kernel thermal driver action
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | marvell,xenon-sdhci.txt | 11 - compatible: should be one of the following
12 - "marvell,armada-3700-sdhci": For controllers on Armada-3700 SoC.
13 Must provide a second register area and marvell,pad-type.
14 - "marvell,armada-ap806-sdhci": For controllers on Armada AP806.
15 - "marvell,armada-cp110-sdhci": For controllers on Armada CP110.
17 - clocks:
22 - clock-names:
27 - reg:
28 * For "marvell,armada-3700-sdhci", two register areas.
31 Please follow the examples with compatible "marvell,armada-3700-sdhci"
[all …]
|
| /Documentation/scsi/ |
| D | BusLogic.rst | 1 .. SPDX-License-Identifier: GPL-2.0
21 Copyright 1995-1998 by Leonard N. Zubkoff <lnz@dandelion.com>
57 BT-948/958/958D, will always be available from my Linux Home Page at URL
69 the BT-948 PCI Ultra SCSI Host Adapter, and then again for the BT-958 PCI Wide
90 94555, USA and can be reached at 510/796-6100 or on the World Wide Web at
92 mail at techsup@mylex.com, by Voice at 510/608-2400, or by FAX at 510/745-7715.
101 -----------------------------------
115 Synchronous negotiation is enabled for all target devices and the host
116 adapter will attempt to negotiate for 20.0 mega-transfers/second.
120 Synchronous negotiation is enabled for all target devices and the host
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio.txt | 5 -----------------
7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
8 of this GPIO for the device. While a non-existent <name> is considered valid
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
24 and bit-banged data signals:
27 gpio-controller;
28 #gpio-cells = <2>;
32 data-gpios = <&gpio1 12 0>,
44 recommended to use the two-cell approach.
48 include/dt-bindings/gpio/gpio.h whenever possible:
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | brcm,brcmnand.txt | 3 The Broadcom Set-Top Box NAND controller supports low-level access to raw NAND
4 flash chips. It has a memory-mapped register interface for both control
15 - compatible : May contain an SoC-specific compatibility string (see below)
16 to account for any SoC-specific hardware bits that may be
21 string, like "brcm,brcmnand-v7.0"
23 brcm,brcmnand-v2.1
24 brcm,brcmnand-v2.2
25 brcm,brcmnand-v4.0
26 brcm,brcmnand-v5.0
27 brcm,brcmnand-v6.0
[all …]
|
| /Documentation/leds/ |
| D | leds-lp55xx.rst | 8 -----------
14 Device attributes for user-space interface
50 - Maximum number of channels
51 - Reset command, chip enable command
52 - Chip specific initialization
53 - Brightness control register access
54 - Setting LED output current
55 - Program memory address access for running patterns
56 - Additional device specific attributes
63 This pattern data is saved as a file in the user-land or
[all …]
|
| /Documentation/sound/hd-audio/ |
| D | notes.rst | 2 More Notes on HD-Audio Driver
11 HD-audio is the new standard on-board audio component on modern PCs
12 after AC97. Although Linux has been supporting HD-audio since long
15 This document explains the brief trouble-shooting and debugging
16 methods for the HD-audio hardware.
18 The HD-audio component consists of two parts: the controller chip and
19 the codec chips on the HD-audio bus. Linux provides a single driver
20 for all controllers, snd-hda-intel. Although the driver name contains
21 a word of a well-known hardware vendor, it's not specific to it but for
22 all controller chips by other companies. Since the HD-audio
[all …]
|
12