Home
last modified time | relevance | path

Searched +full:keep +full:- +full:power +full:- +full:in +full:- +full:suspend (Results 1 – 25 of 25) sorted by relevance

/Documentation/driver-api/media/
Dcamera-sensor.rst1 .. SPDX-License-Identifier: GPL-2.0
8 This document covers the in-kernel APIs only. For the best practices on
9 userspace API implementation in camera sensor drivers, please see
12 CSI-2, parallel and BT.656 buses
13 --------------------------------
15 Please see :ref:`transmitter-receiver`.
18 ---------------
24 firmware. **No other frequencies should be used in any circumstances.**
27 come out of the SoC, and in many cases a specific frequency is designed to be
28 used in the system. Using another frequency may cause harmful effects
[all …]
/Documentation/devicetree/bindings/regulator/
Drohm,bd71815-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/regulator/rohm,bd71815-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ROHM BD71815 Power Management Integrated Circuit regulators
10 - Matti Vaittinen <mazziesaccount@gmail.com>
14 see Documentation/devicetree/bindings/mfd/rohm,bd71815-pmic.yaml.
16 The regulator controller is represented as a sub-node of the PMIC node
33 regulator-name:
37 "^((ldo|buck)[1-5]|ldolpsr|ldodvref)$":
[all …]
/Documentation/devicetree/bindings/net/
Dmarvell-bt-8xxx.txt2 ------
9 - compatible : should be one of the following:
10 * "marvell,sd8897-bt" (for SDIO)
11 * "marvell,sd8997-bt" (for SDIO)
16 - marvell,cal-data: Calibration data downloaded to the device during
20 - marvell,wakeup-pin: It represents wakeup pin number of the bluetooth chip.
22 - marvell,wakeup-gap-ms: wakeup gap represents wakeup latency of the host
25 - interrupt-names: Used only for USB based devices (See below)
26 - interrupts : specifies the interrupt pin number to the cpu. For SDIO, the
27 driver will use the first interrupt specified in the interrupt
[all …]
/Documentation/driver-api/driver-model/
Ddriver.rst11 be multiple devices in a system that a driver supports, struct
37 .suspend = eepro100_suspend,
42 model because the bus they belong to has a bus-specific structure with
43 bus-specific fields that cannot be generalized.
48 completely bus-specific. Defining them as bus-specific entities would
49 sacrifice type-safety, so we keep bus-specific structures around.
51 Bus-specific drivers should include a generic struct device_driver in
52 the definition of the bus-specific driver. Like this::
59 A definition that included bus-specific fields would look like
69 .suspend = eepro100_suspend,
[all …]
/Documentation/devicetree/bindings/mmc/
Dmmc-controller.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mmc/mmc-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ulf Hansson <ulf.hansson@linaro.org>
18 (and the corresponding mmcblkN devices) by defining an alias in the
25 "#address-cells":
30 "#size-cells":
37 broken-cd:
42 cd-gpios:
[all …]
Dmtk-sd.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mmc/mtk-sd.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chaotian Jing <chaotian.jing@mediatek.com>
11 - Wenbin Mei <wenbin.mei@mediatek.com>
16 - enum:
17 - mediatek,mt2701-mmc
18 - mediatek,mt2712-mmc
19 - mediatek,mt6779-mmc
[all …]
/Documentation/driver-api/usb/
Dpower-management.rst1 .. _usb-power-management:
3 Power Management for USB
7 :Date: Last-updated: February 2014
11 ---------
12 * What is Power Management?
17 * Changing the default idle-delay time
19 * The driver interface for Power Management
25 * USB Port Power Control
26 * User Interface for Port Power Control
27 * Suggested Userspace Port Power Policy
[all …]
/Documentation/driver-api/
Ddevice_link.rst23 suspend/resume and shutdown ordering.
25 Device links allow representation of such dependencies in the driver core.
27 In its standard or *managed* form, a device link combines *both* dependency
28 types: It guarantees correct suspend/resume and shutdown ordering between a
35 suspend/resume and shutdown ordering is needed, the device link may
36 simply be set up with the ``DL_FLAG_STATELESS`` flag. In other words,
41 is instructed to runtime resume the supplier and keep it active
47 The earliest point in time when device links can be added is after
52 remains in a consistent state: E.g. a device link cannot be added in
53 the midst of a suspend/resume transition, so either commencement of
[all …]
/Documentation/devicetree/bindings/net/wireless/
Dti,wlcore.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Tony Lindgren <tony@atomide.com>
14 Note that the *-clock-frequency properties assume internal clocks. In case
21 - ti,wl1271
22 - ti,wl1273
23 - ti,wl1281
24 - ti,wl1283
25 - ti,wl1285
[all …]
/Documentation/devicetree/bindings/cpu/
Didle-states.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/cpu/idle-states.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
11 - Anup Patel <anup@brainfault.org>
15 1 - Introduction
18 ARM and RISC-V systems contain HW capable of managing power consumption
19 dynamically, where cores can be put in different low-power states (ranging
20 from simple wfi to power gating) according to OS PM policies. The CPU states
[all …]
/Documentation/gpu/amdgpu/display/
Dmpo-overview.rst6 'Documentation/gpu/amdgpu/display/dcn-overview.rst'.
10 fixed-function hardware in the display controller rather than using graphics or
11 compute shaders for composition. This can yield some power savings if it means
12 the graphics/compute pipelines can be put into low-power states. In summary,
15 * Decreased GPU and CPU workload - no composition shaders needed, no extra
17 * Plane independent page flips - No need to be tied to global compositor
18 page-flip present rate, reduced latency, independent timing.
20 .. note:: Keep in mind that MPO is all about power-saving; if you want to learn
21 more about power-save in the display context, check the link:
22 `Power <https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/power.rst>`__.
[all …]
/Documentation/admin-guide/
Dkernel-parameters.rst3 The kernel's command-line parameters
9 punctuation and sorting digits before letters in a case insensitive
12 The kernel parses parameters from the kernel command line up to "``--``";
16 Everything after "``--``" is passed as an argument to init.
18 Module parameters can be specified in two ways: via the kernel command
30 Hyphens (dashes) and underscores are equivalent in parameter names, so::
32 log_buf_len=1M print-fatal-signals=1
36 log-buf-len=1M print_fatal_signals=1
38 Double-quotes can be used to protect spaces in values, e.g.::
40 param="spaces in here"
[all …]
Dkernel-parameters.txt7 accepted. In most cases the overhead is negligible.
13 Advanced Configuration and Power Interface
16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
[all …]
/Documentation/i2c/
Dwriting-clients.rst16 Try to keep the kernel namespace as clean as possible. The best way to
19 it for non-exported symbols too. We will use the prefix ``foo_`` in this
28 routines, and should be zero-initialized except for fields with data you
29 provide. A client structure holds device-specific information like the
58 although you can use MODULE_ALIAS (passing "foo" in this example) to add
62 All other fields are for call-back functions which will be explained
70 structure at all. You should use this to keep device-specific data.
81 to NULL in remove() or if probe() failed anymore. The i2c-core does this
95 but many chips have some kind of register-value idea that can easily
103 if (reg < 0x10) /* byte-sized register */
[all …]
/Documentation/usb/
Dehci.rst5 27-Dec-2002
8 USB 2.0-capable host controller hardware. The USB 2.0 standard is
11 - "High Speed" 480 Mbit/sec (60 MByte/sec)
12 - "Full Speed" 12 Mbit/sec (1.5 MByte/sec)
13 - "Low Speed" 1.5 Mbit/sec
23 (TT) in the hub, which turns low or full speed transactions into
27 of EHCI from (in alphabetical order): Intel, NEC, Philips, and VIA.
31 While usb-storage devices have been available since mid-2001 (working
34 appear to be on hold until more systems come with USB 2.0 built-in.
36 more typical in the second half of 2002.
[all …]
/Documentation/sound/kernel-api/
Dwriting-an-alsa-driver.rst11 Architecture) <http://www.alsa-project.org/>`__ driver. The document
12 focuses mainly on PCI soundcards. In the case of other device types, the
19 low-level driver implementation details. It only describes the standard
26 -------
56 --------------
59 drivers. In this directory, the native ALSA modules are stored. The
60 sub-directories contain different modules and are dependent upon the
66 The code for OSS PCM and mixer emulation modules is stored in this
67 directory. The OSS rawmidi emulation is included in the ALSA rawmidi
68 code since it's quite small. The sequencer code is stored in
[all …]
/Documentation/input/
Devent-codes.rst1 .. _input-event-codes:
15 the same moment in time. In the following, the term "event" refers to a single
22 event code values using the EVIOCG* ioctls defined in linux/input.h. The event
23 reports supported by a device are also provided by sysfs in
25 provided in class/input/event*/device/properties.
31 type has a set of applicable codes to be used in generating events. See the
36 - Used as markers to separate events. Events may be separated in time or in
41 - Used to describe state changes of keyboards, buttons, or other key-like
46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units
51 - Used to describe absolute axis value changes, e.g. describing the
[all …]
/Documentation/sound/hd-audio/
Dnotes.rst2 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 …]
/Documentation/admin-guide/laptops/
Dthinkpad-acpi.rst9 - Borislav Deianov <borislav@users.sf.net>
10 - Henrique de Moraes Holschuh <hmh@hmh.eng.br>
12 http://ibm-acpi.sf.net/
19 This driver used to be named ibm-acpi until kernel 2.6.21 and release
20 0.13-20070314. It used to be in the drivers/acpi tree, but it was
21 moved to the drivers/misc tree and renamed to thinkpad-acpi for kernel
25 The driver is named "thinkpad-acpi". In some places, like module
29 "tpacpi" is used as a shorthand where "thinkpad-acpi" would be too
33 ------
38 - Fn key combinations
[all …]
/Documentation/hwmon/
Ddell-smm-hwmon.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
5 Kernel driver dell-smm-hwmon
8 :Copyright: |copy| 2002-2005 Massimo Dal Zotto <dz@debian.org>
12 -----------
24 -------------------
35 fan[1-4]_input RO Fan speed in RPM.
36 fan[1-4]_label RO Fan label.
37 fan[1-4]_min RO Minimal Fan speed in RPM
38 fan[1-4]_max RO Maximal Fan speed in RPM
39 fan[1-4]_target RO Expected Fan speed in RPM
[all …]
/Documentation/networking/device_drivers/wifi/intel/
Dipw2200.rst1 .. SPDX-License-Identifier: GPL-2.0
11 - Intel(R) PRO/Wireless 2200BG Network Connection
12 - Intel(R) PRO/Wireless 2915ABG Network Connection
16 both hardware adapters listed above. In this document the Intel(R)
20 Copyright |copy| 2004-2006, Intel Corporation
37 2. Ad-Hoc Networking
59 interference with these devices. In many instances Intel is required to
65 parameters include, without limitation, RF power, spectrum usage,
69 of the software provided in binary format with the wireless WLAN
78 the warranty and/or issues arising from regulatory non-compliance, and
[all …]
/Documentation/core-api/
Dworkqueue.rst31 In the original wq implementation, a multi threaded (MT) wq had one
33 thread system-wide. A single MT wq needed to keep around the same
60 * Use per-CPU unified worker pools shared by all wq to provide
71 In order to ease the asynchronous execution of functions a new
80 A work item can be executed in either a thread or the BH (softirq) context.
84 the worker threads become idle. These worker threads are managed in
85 worker-pools.
87 The cmwq design differentiates between the user-facing workqueues that
89 which manages worker-pools and processes the queued work items.
91 There are two worker-pools, one for normal work items and the other
[all …]
/Documentation/networking/dsa/
Ddsa.rst8 in joining the effort.
22 An Ethernet switch typically comprises multiple front-panel ports and one
26 kinds of Ethernet switches found in Small Home and Office products: routers,
27 gateways, or even top-of-rack switches. This host Ethernet controller will
28 be later referred to as "conduit" and "cpu" in DSA terminology and code.
30 The D in DSA stands for Distributed, because the subsystem has been designed
33 ports are referred to as "dsa" ports in DSA terminology and code. A collection
36 For each front-panel port, DSA creates specialized network devices which are
37 used as controlling and data-flowing endpoints for use by the Linux networking
39 interfaces in DSA terminology and code.
[all …]
/Documentation/virt/kvm/
Dapi.rst1 .. SPDX-License-Identifier: GPL-2.0
4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
13 - System ioctls: These query and set global attributes which affect the
14 whole kvm subsystem. In addition a system ioctl is used to create
17 - VM ioctls: These query and set attributes that affect an entire virtual
18 machine, for example memory layout. In addition a VM ioctl is used to
24 - vcpu ioctls: These query and set attributes that control the operation
28 the vcpu, except for asynchronous vcpu ioctl that are marked as such in
32 - device ioctls: These query and set attributes that control the operation
51 In general file descriptors can be migrated among processes by means
[all …]
/Documentation/admin-guide/sysctl/
Dkernel.rst5 .. See scripts/check-sysctl-docs to keep this up to date
12 For general info and legal blurb, please look in
13 Documentation/admin-guide/sysctl/index.rst.
15 ------------------------------------------------------------------------------
17 This file contains documentation for the sysctl files in
20 The files in this directory can be used to tune and monitor
21 miscellaneous and general things in the operation of the Linux
27 show up in ``/proc/sys/kernel``:
39 If BSD-style process accounting is enabled these values control
43 how often do we check the amount of free space (value is in
[all …]