Home
last modified time | relevance | path

Searched +full:powered +full:- +full:on (Results 1 – 25 of 133) sorted by relevance

123456

/Documentation/firmware-guide/acpi/
Dnon-d0-probe.rst1 .. SPDX-License-Identifier: GPL-2.0
10 In some cases it may be preferred to leave certain devices powered off for the
11 entire system bootup if powering on these devices has adverse side effects,
12 beyond just powering on the said device.
22 The downside of using _DSC is that as the device is not powered on, even if
28 ---
33 the device will not be powered on (put in D0 state) for probe.
36 --------
39 to [1] for more information on device power states.
41 .. code-block:: text
[all …]
/Documentation/devicetree/bindings/usb/
Dusb251xb.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Microchip USB 2.0 Hi-Speed Hub Controller
10 - Richard Leitner <richard.leitner@skidata.com>
15 - microchip,usb2422
16 - microchip,usb2512b
17 - microchip,usb2512bi
18 - microchip,usb2513b
19 - microchip,usb2513bi
[all …]
/Documentation/userspace-api/media/dvb/
Dfe-diseqc-reset-overload.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 FE_DISEQC_RESET_OVERLOAD - Restores the power to the antenna subsystem, if it was powered off due -
31 If the bus has been automatically powered off due to power overload,
34 is manually powered off. Not all Digital TV adapters support this ioctl.
39 On success 0 is returned.
41 On error -1 is returned, and the ``errno`` variable is set
45 :ref:`Generic Error Codes <gen-errors>` chapter.
Dfrontend_f_open.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 fe-open - Open a frontend device
18 .. code-block:: c
53 The device can be opened in read-only mode, which only allows monitoring
57 In a system with multiple front-ends, it is usually the case that
59 long as a front-end device is opened in read/write mode, other open()
60 calls in read/write mode will either fail or block, depending on whether
61 non-blocking or blocking mode was specified. A front-end device opened
62 in blocking mode can later be put into non-blocking mode (and vice
67 powered up, and that other front-ends may have been powered down to make
[all …]
Dfrontend_f_close.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 fe-close - Close a frontend device
18 .. code-block:: c
33 This system call closes a previously opened front-end device. After
34 closing a front-end device, its corresponding hardware might be powered
40 On success 0 is returned.
42 On error -1 is returned, and the ``errno`` variable is set
46 :ref:`Generic Error Codes <gen-errors>` chapter.
/Documentation/w1/slaves/
Dw1_therm.rst16 -----------
42 A bulk read of all devices on the bus could be done writing ``trigger``
44 send the convert command to all devices on the bus, and if parasite
45 powered devices are detected on the bus (and strong pullup is enabled
47 time required by parasited powered device on the line. Reading
49 -1 if at least one sensor still in conversion, 1 if conversion is complete
54 ``temperature`` on this device will return the temperature measured at the
60 adjust it (write). A temperature conversion time depends on the device type and
72 the sensor. Resolution is reset when the sensor gets power-cycled.
79 ``resolution`` entry on each device, if supported by the sensor.
[all …]
/Documentation/sound/soc/
Dpops-clicks.rst6 of components within the audio subsystem. This is noticeable on PCs when an
8 powered up and causes a popping noise on the speakers).
10 Pops and clicks can be more frequent on portable systems with DAPM. This is
11 because the components within the subsystem are being dynamically powered
12 depending on the audio usage and this can subsequently cause a small pop or
23 shutdown and follows some basic rules:-
26 Startup Order :- DAC --> Mixers --> Output PGA --> Digital Unmute
28 Shutdown Order :- Digital Mute --> Output PGA --> Mixers --> DAC
39 playback in that components are powered in a sequence depending upon stream
43 Startup Order - Input PGA --> Mixers --> ADC
[all …]
/Documentation/devicetree/bindings/power/
Dapple,pmgr-pwrstate.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/apple,pmgr-pwrstate.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hector Martin <marcan@marcan.st>
13 - $ref: power-domain.yaml#
23 Documentation/devicetree/bindings/power/power-domain.yaml.
25 represented via power-domains relationships between these nodes.
28 for the top-level PMGR node documentation.
33 - enum:
[all …]
Dpower-domain.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/power-domain.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rafael J. Wysocki <rjw@rjwysocki.net>
11 - Kevin Hilman <khilman@kernel.org>
12 - Ulf Hansson <ulf.hansson@linaro.org>
15 System on chip designs are often divided into multiple PM domains that can be
25 \#power-domain-cells property in the PM domain provider node.
29 pattern: "^(power-controller|power-domain|performance-domain)([@-].*)?$"
[all …]
Dstarfive,jh7110-pmu.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/starfive,jh7110-pmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Walker Chen <walker.chen@starfivetech.com>
14 powered on/off by software based on different application scenes to save power.
19 - starfive,jh7110-pmu
27 "#power-domain-cells":
31 - compatible
32 - reg
[all …]
/Documentation/devicetree/bindings/rtc/
Dmaxim-ds1302.txt1 * Maxim/Dallas Semiconductor DS-1302 RTC
5 The device uses the standard MicroWire half-duplex transfer timing.
6 Master output is set on low clock and sensed by the RTC on the rising
7 edge. Master input is set by the RTC on the trailing edge and is sensed
8 by the master on low clock.
12 - compatible : Should be "maxim,ds1302"
16 - reg : Should be address of the device chip select within
19 - spi-max-frequency : DS-1302 has 500 kHz if powered at 2.2V,
20 and 2MHz if powered at 5V.
22 - spi-3wire : The device has a shared signal IN/OUT line.
[all …]
/Documentation/devicetree/bindings/sound/
Dti,tlv320adc3xxx.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ricard Wanderlof <ricardw@axis.com>
18 - $ref: dai-common.yaml#
23 - ti,tlv320adc3001
24 - ti,tlv320adc3101
30 '#sound-dai-cells':
33 '#gpio-cells':
36 gpio-controller: true
[all …]
Dqcom,pm8916-wcd-analog-codec.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/sound/qcom,pm8916-wcd-analog-codec.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Konrad Dybcio <konradybcio@kernel.org>
13 The analog WCD audio codec found on Qualcomm PM8916 PMIC.
17 const: qcom,pm8916-wcd-analog-codec
25 interrupt-names:
27 - const: cdc_spk_cnp_int
28 - const: cdc_spk_clip_int
[all …]
Drt5660.txt7 - compatible : "realtek,rt5660".
9 - reg : The I2C address of the device.
13 - clocks: The phandle of the master clock to the CODEC
14 - clock-names: Should be "mclk"
16 - realtek,in1-differential
17 - realtek,in3-differential
18 Boolean. Indicate MIC1/3 input are differential, rather than single-ended.
20 - realtek,poweroff-in-suspend
21 Boolean. If the codec will be powered off in suspend, the resume should be
24 - realtek,dmic1-data-pin
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-usb-devices-usbsevseg1 What: /sys/bus/usb/.../powered
5 Description: Controls whether the device's display will powered.
6 A value of 0 is off and a non-zero value is on.
28 hex: each character is between 0-15
29 ascii: each character is between '0'-'9' and 'A'-'F'.
41 Description: Controls the decimal places on the device.
Dsysfs-driver-bd9571mwv-regulator1 What: /sys/bus/i2c/devices/.../bd9571mwv-regulator.*.auto/backup_mode
6 if DDR power rails will be kept powered during system suspend.
7 ("on"/"1" = enabled, "off"/"0" = disabled).
18 wake-up switch,
23 4. Switch accessory power switch on, to resume the
/Documentation/networking/devlink/
Ddevlink-linecard.rst1 .. SPDX-License-Identifier: GPL-2.0
10 The ``devlink-linecard`` mechanism is targeted for manipulation of
27 according to the physical line card slots available on the device.
36 - Device driver would instruct the ASIC to prepare all
39 that reside on the line card, according to the line card type
41 being physically connected or powered-up
42 * Setup splitter cable on line card ports
44 - As on the ordinary ports, user may provision a splitter
51 * Line card is not inserted or powered-down
53 - The carrier is always down
[all …]
/Documentation/devicetree/bindings/net/bluetooth/
Dmediatek,bluetooth.txt13 - compatible: Must be
14 "mediatek,mt7663u-bluetooth": for MT7663U device
15 "mediatek,mt7668u-bluetooth": for MT7668U device
16 - vcc-supply: Main voltage regulator
18 If the pin controller on the platform can support both pinmux and GPIO
21 - pinctrl-names: Should be "default", "runtime"
22 - pinctrl-0: Should contain UART RXD low when the device is powered up to
24 - pinctrl-1: Should contain UART mode pin ctrl
26 Else, the pin controller on the platform only can support pinmux control and
27 the GPIO control still has to rely on the dedicated GPIO controller such as
[all …]
/Documentation/trace/coresight/
Dcoresight-ect.rst1 .. SPDX-License-Identifier: GPL-2.0
11 --------------------
21 0 C 0----------->: : +======>(other CTI channel IO)
22 0 P 0<-----------: : v
24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+
25 ####### in_trigs : : (id 0-3) ***** ::::::: v
26 # ETM #----------->: : ^ #######
27 # #<-----------: : +---# ETR #
41 CoreSight devices on the trace data path. When these devices are enabled the
42 attached CTIs will also be enabled. By default/on power up the CTIs have
[all …]
Dcoresight-cpu-debug.rst9 ------------
11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
13 debug module and it is mainly used for two modes: self-hosted debug and
15 debugger connects with SoC from JTAG port; on the other hand the program can
16 explore debugging method which rely on self-hosted debug mode, this document
17 is to focus on this part.
19 The debug module provides sample-based profiling extension, which can be used
21 every CPU has one dedicated debug module to be connected. Based on self-hosted
29 --------------
31 - During driver registration, it uses EDDEVID and EDDEVID1 - two device ID
[all …]
/Documentation/devicetree/bindings/tpm/
Dtpm-common.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/tpm/tpm-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lukas Wunner <lukas@wunner.de>
14 pattern: '^tpm(@[0-9a-f]+)?$'
23 linux,sml-base:
28 linux,sml-size:
33 memory-region:
37 powered-while-suspended:
[all …]
/Documentation/driver-api/
Dwbrf.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
4 WBRF - Wifi Band RFI Mitigations
8 there may be likely interference of relatively high-powered harmonics of
26 Producer: such component who can produce high-powered radio frequency
27 Consumer: such component who can adjust its in-use frequency in
42 The GUID used for the _DSM is 7B7656CF-DC3D-4C1C-83E9-66E721DE3070.
53 .. kernel-doc:: drivers/platform/x86/amd/wbrf.c
61 2. On using some frequency band, call `acpi_amd_wbrf_add_remove` with 'add'
63 3. Or on stopping using some frequency band, call
74 4. On receiving a notification for frequency band change, run
/Documentation/devicetree/bindings/leds/
Dregulator-led.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/regulator-led.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 Regulator LEDs are powered by a single regulator such that they can
14 be turned on or off by enabling or disabling the regulator. The available
15 brightness settings will be inferred from the available voltages on the
16 regulator, and any constraints on the voltage or current will need to be
17 specified on the regulator.
[all …]
/Documentation/devicetree/bindings/timer/
Darm,twd-timer.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/timer/arm,twd-timer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ARM Timer-Watchdog Timer
10 - Rob Herring <robh@kernel.org>
13 ARM 11MP, Cortex-A5 and Cortex-A9 are often associated with a per-core
14 Timer-Watchdog (aka TWD), which provides both a per-cpu local timer
17 The TWD is usually attached to a GIC to deliver its two per-processor
23 - arm,cortex-a9-twd-timer
[all …]
/Documentation/devicetree/bindings/media/i2c/
Dadv7343.txt3 The ADV7343 are high speed, digital-to-analog video encoders in a 64-lead LQFP
4 package. Six high speed, 3.3 V, 11-bit video DACs provide support for composite
5 (CVBS), S-Video (Y-C), and component (YPrPb/RGB) analog outputs in standard
10 - compatible: Must be "adi,adv7343"
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
17 internal PLL 1 circuit to be powered down and the
19 - ad,adv7343-power-mode-dac: array configuring the power on/off DAC's 1..6,
20 0 = OFF and 1 = ON, Default value when this
22 - ad,adv7343-sd-config-dac-out: array configure SD DAC Output's 1 and 2, 0 = OFF
[all …]

123456