Home
last modified time | relevance | path

Searched +full:enabled +full:- +full:strings (Results 1 – 25 of 64) sorted by relevance

123

/Documentation/devicetree/bindings/leds/backlight/
Dqcom-wled.yaml1 # 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 <andersson@kernel.org>
11 - Kiran Gunda <quic_kgunda@quicinc.com>
21 - qcom,pm8941-wled
22 - qcom,pmi8950-wled
23 - qcom,pmi8994-wled
24 - qcom,pmi8998-wled
[all …]
/Documentation/ABI/testing/
Dsysfs-class-regulator10 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 …]
Dconfigfs-usb-gadget-ffs1 What: /config/usb-gadget/gadget/functions/ffs.name
13 strings to ep0, so the gadget can be
14 enabled - 0 otherwise.
Dsysfs-class-thermal3 Strings which represent the thermal zone type.
22 One of the predefined values in [enabled, disabled].
27 enabled
59 Strings which indicate the type of the trip point.
61 E.g. it can be one of critical, hot, passive, `active[0-*]`
84 The trip point in this thermal zone which `cdev[0-*]` is
85 associated with; -1 means the cooling device is not
92 The influence of `cdev[0-*]` in this thermal zone. This value
124 Documentation/driver-api/thermal/power_allocator.rst
133 Documentation/driver-api/thermal/power_allocator.rst
[all …]
Dsysfs-firmware-acpi55 image: The image bitmap. Currently a 32-bit BMP.
83 enabled: If set, the ACPI core will handle notifications of
93 cause -EINVAL to be returned.
196 enable the GPE/Fixed Event is valid and enabled.
210 Besides this, user can also write specific strings to these files
223 0 enabled
226 3 enabled
235 4 enabled
243 7 enabled
249 7 enabled
Dsysfs-power15 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 …]
/Documentation/devicetree/bindings/leds/
Dleds-lm36274.txt1 * 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/
Dgadget_configfs.rst50 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/
Dzynq-7000.txt15 - #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/
Dusb3-debug-port.rst19 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/
Dsimple-pm-bus.yaml1 # 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/
Dattributes.rst1 .. 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/
Dmediatek,mt7986-pinctrl.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/mediatek,mt7986-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sean Wang <sean.wang@kernel.org>
18 - mediatek,mt7986a-pinctrl
19 - mediatek,mt7986b-pinctrl
25 reg-names:
27 - const: gpio
28 - const: iocfg_rt
[all …]
Dmediatek,mt7981-pinctrl.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/mediatek,mt7981-pinctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Daniel Golle <daniel@makrotopia.org>
18 - mediatek,mt7981-pinctrl
24 reg-names:
26 - const: gpio
27 - const: iocfg_rt
28 - const: iocfg_rm
[all …]
Dste,nomadik.txt4 - 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/devicetree/bindings/gpio/
Dxlnx,gpio-xilinx.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/xlnx,gpio-xilinx.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Neeli Srinivas <srinivas.neeli@amd.com>
14 to an AXI4-Lite interface. The AXI GPIO can be configured as either
15 a single or a dual-channel device. The width of each channel is
22 - xlnx,xps-gpio-1.00.a
27 "#gpio-cells":
33 gpio-controller: true
[all …]
/Documentation/kbuild/
Dgendwarfksyms.rst8 When CONFIG_MODVERSIONS is enabled, symbol versions for modules
18 -----
23 Usage: gendwarfksyms [options] elf-object-file ... < symbol-list
26 -d, --debug Print debugging information
27 --dump-dies Dump DWARF DIE contents
28 --dump-die-map Print debugging information about die_map changes
29 --dump-types Dump type strings
30 --dump-versions Dump expanded type strings used for symbol versions
31 -s, --stable Support kABI stability features
32 -T, --symtypes file Write a symtypes file
[all …]
/Documentation/sound/designs/
Dmidi-2.0.rst12 - Support of Universal MIDI Packet (UMP)
13 - Support of MIDI 2.0 protocol messages
14 - Transparent conversions between UMP and legacy MIDI 1.0 byte stream
15 - MIDI-CI for property and profile configurations
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
32 supported in user-space over the standard SysEx.
65 When a device supports MIDI 2.0, the USB-audio driver probes and uses
69 `midi2_enable=0` option to snd-usb-audio driver module, too.
78 option to snd-usb-audio driver for skipping the UMP v1.1 inquiries.
[all …]
/Documentation/networking/
Dnetconsole.rst1 .. SPDX-License-Identifier: GPL-2.0
29 It can be used either built-in or as a module. As a built-in,
41 netconsole=[+][r][src-port]@[src-ip]/[<dev>],[tgt-port]@<tgt-ip>/[tgt-macaddr]
46 src-port source for UDP packets (defaults to 6665)
47 src-ip source IP to use (interface address)
49 tgt-port port for logging agent (6666)
50 tgt-ip IP address for logging agent
51 tgt-macaddr ethernet MAC address for logging agent (broadcast)
71 Built-in netconsole starts immediately after the TCP stack is
82 On distributions using a BSD-based netcat version (e.g. Fedora,
[all …]
/Documentation/netlink/specs/
Dethtool.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
10 -
11 name: udp-tunnel-type
12 enum-name:
14 entries: [ vxlan, geneve, vxlan-gpe ]
15 -
19 -
20 name: header-flags
22 entries: [ compact-bitsets, omit-reply, stats ]
[all …]
/Documentation/devicetree/bindings/sound/
Damlogic,axg-sound-card.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/amlogic,axg-sound-card.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jerome Brunet <jbrunet@baylibre.com>
13 - $ref: sound-card-common.yaml#
17 const: amlogic,axg-sound-card
19 audio-aux-devs:
20 $ref: /schemas/types.yaml#/definitions/phandle-array
23 audio-widgets:
[all …]
Dfsl-asoc-card.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/sound/fsl-asoc-card.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
28 - Shengjiu Wang <shengjiu.wang@nxp.com>
33 - items:
34 - enum:
35 - fsl,imx-sgtl5000
36 - fsl,imx25-pdk-sgtl5000
37 - fsl,imx53-cpuvo-sgtl5000
[all …]
/Documentation/driver-api/
Disa.rst27 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/driver-api/thermal/
Dintel_dptf.rst1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
31 ----------------------------
37 A set of UUIDs strings presenting available policies
41 UUID strings:
43 "42A441D6-AE6A-462b-A84B-4A8CE79027D3" : Passive 1
45 "3A95C389-E4B8-4629-A526-C52C88626BAE" : Active
47 "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" : Critical
49 "63BE270F-1C11-48FD-A6F7-3AF253FF3E2D" : Adaptive performance
51 "5349962F-71E6-431D-9AE8-0A635B710AEE" : Emergency call
[all …]
/Documentation/arch/x86/
Dcpuinfo.rst1 .. SPDX-License-Identifier: GPL-2.0
11 represents an ill-fated attempt from long time ago to put feature flags
18 because userspace doesn't care about them - glibc et al already use
21 And even if it doesn't show a particular feature flag - although the CPU
23 said CPU supports CPUID faulting - userspace can simply probe for the
27 Furthermore, those flag strings become an ABI the moment they appear
32 kernel has *enabled* and *supports*. As in: the CPUID feature flag is
56 On the other hand, a new kernel running on non-VAES hardware would also
83 ------------------------------------------------------------------
92 b: Flags can be from scattered CPUID-based features.
[all …]

123