Home
last modified time | relevance | path

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

12345678910>>...23

/linux/Documentation/firmware-guide/acpi/
H A 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 …]
/linux/Documentation/w1/slaves/
H A 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 …]
/linux/arch/arm/include/asm/
H A Dmcpm.h1 /* SPDX-License-Identifier: GPL-2.0-only */
6 * Copyright: (C) 2012-2013 Linaro Limited
40 * branch once it is ready to re-enter the kernel using ptr, or NULL if it
59 * mcpm_is_available - returns whether MCPM is initialized and available
66 * mcpm_cpu_power_up - make given CPU in given cluster runable
71 * The identified CPU is brought out of reset. If the cluster was powered
87 * mcpm_cpu_power_down - power the calling CPU down
89 * The calling CPU is powered down.
92 * then the cluster is prepared for power-down too.
96 * On success this does not return. Re-entry in the kernel is expected
[all …]
/linux/Documentation/userspace-api/media/dvb/
H A 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.
H A 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 …]
/linux/Documentation/devicetree/bindings/sound/
H A 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 …]
/linux/Documentation/sound/soc/
H A 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 …]
/linux/Documentation/networking/devlink/
H A 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 …]
/linux/Documentation/trace/coresight/
H A 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 …]
H A 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 …]
/linux/Documentation/devicetree/bindings/rtc/
H A 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 …]
H A Dsophgo,cv1800b-rtc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/rtc/sophgo,cv1800b-rtc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The RTC (Real Time Clock) is an independently powered module in the chip. It
11 contains a 32KHz oscillator and a Power-On-Reset (POR) sub-module, which can
14 power-on, power-off and reset.
17 powered. System software can use the 8051 to manage wake conditions and wake
22 https://github.com/sophgo/sophgo-doc/tree/main/SG200X/TRM
25 - sophgo@lists.linux.dev
[all …]
/linux/drivers/pci/hotplug/
H A Dpciehp.h1 /* SPDX-License-Identifier: GPL-2.0+ */
6 * Copyright (C) 2001 Greg Kroah-Hartman (greg@kroah.com)
8 * Copyright (C) 2003-2004 Intel Corporation
36 pci_dbg(ctrl->pcie->port, format, ## arg)
38 pci_err(ctrl->pcie->port, format, ## arg)
40 pci_info(ctrl->pcie->port, format, ## arg)
42 pci_warn(ctrl->pcie->port, format, ## arg)
47 * struct controller - PCIe hotplug controller
53 * @inband_presence_disabled: In-Band Presence Detect Disable supported by
61 * @cmd_busy: flag set on Slot Control register write, cleared by IRQ handler
[all …]
H A Drpaphp_pci.c1 // SPDX-License-Identifier: GPL-2.0+
3 * PCI Hot Plug Controller Driver for RPA-compliant PPC64 platform.
15 #include <asm/pci-bridge.h>
23 * RTAS call get-sensor-state(DR_ENTITY_SENSE) return values as per PAPR:
24 * -- generic return codes ---
25 * -1: Hardware Error
26 * -2: RTAS_BUSY
27 * -3: Invalid sensor. RTAS Parameter Error.
28 * -- rtas_get_sensor function specific return codes ---
29 * -9000: Need DR entity to be powered up and unisolated before RTAS call
[all …]
/linux/drivers/platform/x86/
H A Dtoshiba_bluetooth.c1 // SPDX-License-Identifier: GPL-2.0-only
8 * Thanks to Matthew Garrett for background info on ACPI innards which
9 * normal people aren't meant to understand :-)
35 bool powered; member
78 return -ENXIO; in toshiba_bluetooth_present()
83 return -ENODEV; in toshiba_bluetooth_present()
97 return -ENXIO; in toshiba_bluetooth_status()
110 return -ENXIO; in toshiba_bluetooth_enable()
115 pr_err("Could not power ON Bluetooth device\n"); in toshiba_bluetooth_enable()
116 return -ENXIO; in toshiba_bluetooth_enable()
[all …]
/linux/drivers/input/joystick/
H A Ddb9.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * Copyright (c) 1999-2001 Vojtech Pavlik
5 * Based on the work of:
112 { "Multisystem (0.8.0.2-dual) joystick", db9_multi_btn, 1, 2, 2, 1, 1 },
113 { "Amiga CD-32 pad", db9_cd32_btn, 7, 1, 2, 1, 1 },
128 static void db9_saturn_write_sub(struct parport *port, int type, unsigned char data, int powered, i… in db9_saturn_write_sub() argument
134 c = 0x80 | 0x30 | (powered ? 0x08 : 0) | (pwr_sub ? 0x04 : 0) | data; in db9_saturn_write_sub()
138 c = 0x40 | data << 4 | (powered ? 0x08 : 0) | (pwr_sub ? 0x04 : 0) | 0x03; in db9_saturn_write_sub()
142 c = ((((data & 2) ? 2 : 0) | ((data & 1) ? 4 : 0)) ^ 0x02) | !powered; in db9_saturn_write_sub()
171 static unsigned char db9_saturn_read_analog(struct parport *port, int type, int powered) in db9_saturn_read_analog() argument
[all …]
/linux/drivers/phy/amlogic/
H A Dphy-meson-axg-mipi-pcie-analog.c1 // SPDX-License-Identifier: GPL-2.0
16 #include <dt-bindings/phy/phy.h>
53 bool powered; member
59 regmap_update_bits(priv->regmap, HHI_MIPI_CNTL0, in phy_bandgap_enable()
62 regmap_update_bits(priv->regmap, HHI_MIPI_CNTL0, in phy_bandgap_enable()
68 regmap_update_bits(priv->regmap, HHI_MIPI_CNTL0, in phy_bandgap_disable()
70 regmap_update_bits(priv->regmap, HHI_MIPI_CNTL0, in phy_bandgap_disable()
78 regmap_update_bits(priv->regmap, HHI_MIPI_CNTL0, in phy_dsi_analog_enable()
81 regmap_update_bits(priv->regmap, HHI_MIPI_CNTL0, in phy_dsi_analog_enable()
83 regmap_update_bits(priv->regmap, HHI_MIPI_CNTL0, in phy_dsi_analog_enable()
[all …]
/linux/arch/mips/kernel/
H A Dsmp-cps.c1 // SPDX-License-Identifier: GPL-2.0-or-later
19 #include <asm/mips-cps.h>
22 #include <asm/pm-cps.h>
26 #include <asm/smp-cps.h>
78 timeout--; in power_up_other_cluster()
159 0x0, CSEGX_SIZE - 1); in allocate_cps_vecs()
172 end = SZ_4G - 1; in allocate_cps_vecs()
186 return -ENOMEM; in allocate_cps_vecs()
241 for (v = 0; v < min_t(int, core_vpes, NR_CPUS - nvpes); v++) { in cps_smp_setup()
278 /* If we have an FPU, enroll ourselves in the FPU-full mask */ in cps_smp_setup()
[all …]
/linux/Documentation/ABI/testing/
H A 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.
/linux/drivers/media/i2c/ccs/
H A Dccs-quirk.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * drivers/media/i2c/ccs/ccs-quirk.h
8 * Copyright (C) 2011--2012 Nokia Corporation
18 * struct ccs_quirk - quirks for sensors that deviate from SMIA++ standard
20 * @limits: Replace sensor->limits with values which can't be read from
21 * sensor registers. Called the first time the sensor is powered up.
22 * @post_poweron: Called always after the sensor has been fully powered on.
31 * -write: Is this read (false) or write (true) access?
32 * -reg: Pointer to the register to access
33 * -val: Register value, set by the caller on write, or
[all …]
/linux/drivers/bluetooth/
H A Dhci_bcm.c1 // SPDX-License-Identifier: GPL-2.0-or-later
53 * struct bcm_device_data - device specific data
55 * @drive_rts_on_open: drive RTS signal on ->open() when platform requires it
69 * struct bcm_device - device driver resources
106 * @drive_rts_on_open: drive RTS signal on ->open() when platform requires it
166 static int irq_polarity = -1;
168 MODULE_PARM_DESC(irq_polarity, "IRQ polarity 0: active-high 1: active-low");
172 if (hu->serdev) in host_set_baudrate()
173 serdev_device_set_baudrate(hu->serdev, speed); in host_set_baudrate()
180 struct hci_dev *hdev = hu->hdev; in bcm_set_baudrate()
[all …]
/linux/Documentation/devicetree/bindings/net/bluetooth/
H A 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 …]
/linux/arch/arm/boot/dts/marvell/
H A Dkirkwood-nas2big.dts1 // SPDX-License-Identifier: GPL-2.0
11 /dts-v1/;
13 #include "kirkwood-netxbig.dtsi"
17 compatible = "lacie,nas2big", "lacie,netxbig", "marvell,kirkwood-88f6282", "marvell,kirkwood";
26 stdout-path = &uart0;
31 /* The on-chip RTC is not powered (no supercap). */
37 * the other netxbig-compatible boards.
48 compatible = "gpio-fan";
49 alarm-gpios = <&gpio0 25 GPIO_ACTIVE_LOW>;
54 compatible = "simple-bus";
[all …]
/linux/Documentation/devicetree/bindings/power/
H A 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 <rafael@kernel.org>
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 …]
/linux/Documentation/driver-api/
H A 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

12345678910>>...23