Home
last modified time | relevance | path

Searched +full:wakeup +full:- +full:event +full:- +full:action (Results 1 – 13 of 13) sorted by relevance

/Documentation/devicetree/bindings/input/
Dgpio-keys.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/input/gpio-keys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
15 - gpio-keys
16 - gpio-keys-polled
23 poll-interval: true
26 …"^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switc…
35 - items:
[all …]
/Documentation/i2c/
Dslave-interface.rst5 by Wolfram Sang <wsa@sang-engineering.com> in 2014-15
10 example for the latter is the slave-eeprom driver, which acts as a dual memory
16 use a character device, be in-kernel only, or something completely different::
20 +-----------+ v +---------+ v +--------+ v +------------+
21 | Userspace +........+ Backend +-----------+ Driver +-----+ Controller |
22 +-----------+ +---------+ +--------+ +------------+
24 ----------------------------------------------------------------+-- I2C
25 --------------------------------------------------------------+---- Bus
35 them as described in the document instantiating-devices.rst. The only
38 instantiating the slave-eeprom driver from userspace at the 7 bit address 0x64
[all …]
/Documentation/admin-guide/pm/
Dsuspend-flows.rst1 .. SPDX-License-Identifier: GPL-2.0
12 At least one global system-wide transition needs to be carried out for the
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows
28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and
31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states
33 boils down to the platform-specific actions carried out by the suspend and
37 *platform-dependent suspend* states in what follows.
42 Suspend-to-idle Suspend Code Flow
[all …]
/Documentation/trace/rv/
Druntime-verification.rst10 Instead of relying on a fine-grained model of a system (e.g., a
11 re-implementation a instruction level), RV works by analyzing the trace of the
17 that require a re-implementation of the entire system in a modeling language.
20 events, avoiding, for example, the propagation of a failure on safety-critical
32 system, a set of instances of the monitor (per-cpu monitor, per-task monitor,
36 Linux +---- RV Monitor ----------------------------------+ Formal
38 +-------------------+ +----------------+ +-----------------+
40 | Tracing | -> | Instance(s) | <- | Model |
42 +-------------------+ +----------------+ +-----------------+
45 | +----------+ |
[all …]
/Documentation/trace/
Dhistogram-design.rst1 .. SPDX-License-Identifier: GPL-2.0
20 generally be truncated - only enough to make the point is displayed.
22 'hist_debug' trace event files
26 event file named 'hist_debug' will appear in each event's
35 can do with histograms - create one with a single key on a single
36 event and cat the output::
59 What this does is create a histogram on the sched_waking event using
63 The hitcount value is a per-bucket value that's automatically
83 from the event's trace_event_file along with various bits related to
85 which is used to grab the field's data from the ftrace event buffer
[all …]
Dhistogram.rst2 Event Histograms
10 Histogram triggers are special event triggers that can be used to
11 aggregate trace event data into histograms. For information on
12 trace events and event triggers, see Documentation/trace/events.rst.
18 A histogram trigger command is an event trigger command that
19 aggregates event hits into a hash table keyed on one or more trace
20 event format fields (or stacktrace) and a set of running totals
21 derived from one or more trace event format fields and/or event
28 [:clear][:name=histname1][:nohitcount][:<handler>.<action>] [if <filter>]
30 When a matching event is hit, an entry is added to a hash table
[all …]
Dftrace.rst2 ftrace - Function Tracer
13 - Written for: 2.6.28-rc2
14 - Updated for: 3.10
15 - Updated for: 4.13 - Copyright 2017 VMware Inc. Steven Rostedt
16 - Converted to rst format - Changbin Du <changbin.du@intel.com>
19 ------------
24 performance issues that take place outside of user-space.
32 One of the most common uses of ftrace is the event tracing.
33 Throughout the kernel is hundreds of static event points that
41 ----------------------
[all …]
/Documentation/power/
Dpci.rst13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
38 as a result of an external event requiring the device to be active, which may
41 PCI devices may be put into low-power states in two ways, by using the device
50 Devices supporting the native PCI PM usually can generate wakeup signals called
53 to put the device that sent it into the full-power state. However, the PCI Bus
[all …]
/Documentation/admin-guide/mm/
Duserfaultfd.rst8 Userfaults allow the implementation of on-demand paging from userland
38 Vmas are not suitable for page- (or hugepage) granular fault tracking
48 is a corner case that would currently return ``-EBUSY``).
54 ----------------------
63 - Any user can always create a userfaultfd which traps userspace page faults
67 - In order to also trap kernel page faults for the address space, either the
84 --------------------------
101 - The ``UFFD_FEATURE_EVENT_*`` flags indicate that various other events
103 detail below in the `Non-cooperative userfaultfd`_ section.
105 - ``UFFD_FEATURE_MISSING_HUGETLBFS`` and ``UFFD_FEATURE_MISSING_SHMEM``
[all …]
/Documentation/arch/x86/
Dintel_txt.rst6 Technology (Intel(R) TXT), defines platform-level enhancements that
13 - Provides dynamic root of trust for measurement (DRTM)
14 - Data protection in case of improper shutdown
15 - Measurement and verification of launched environment
18 non-vPro systems. It is currently available on desktop systems
30 - LinuxTAG 2008:
31 http://www.linuxtag.org/2008/en/conf/events/vp-donnerstag.html
33 - TRUST2008:
34 http://www.trust-conference.eu/downloads/Keynote-Speakers/
35 3_David-Grawrock_The-Front-Door-of-Trusted-Computing.pdf
[all …]
/Documentation/admin-guide/thermal/
Dintel_powerclamp.rst6 - Arjan van de Ven <arjan@linux.intel.com>
7 - Jacob Pan <jacob.jun.pan@linux.intel.com>
12 - Goals and Objectives
15 - Idle Injection
16 - Calibration
19 - Effectiveness and Limitations
20 - Power vs Performance
21 - Scalability
22 - Calibration
23 - Comparison with Alternative Techniques
[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
17 - VM ioctls: These query and set attributes that affect an entire virtual
24 - vcpu ioctls: These query and set attributes that control the operation
32 - device ioctls: These query and set attributes that control the operation
80 facility that allows backward-compatible extensions to the API to be
104 the ioctl returns -ENOTTY.
122 -----------------------
139 -----------------
[all …]
/Documentation/admin-guide/
Dkernel-parameters.txt16 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
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]