| /linux/Documentation/usb/ |
| H A D | gadget_configfs.rst | 15 be connected to a USB Host to extend it with additional functions like a serial
20 functions, each function representing e.g. a serial connection or a SCSI disk.
22 Linux provides a number of functions for gadgets to use.
25 and which functions each configuration will provide.
39 In order for this to work configfs must be available, so CONFIGFS_FS must be
40 'y' or 'm' in .config. As of this writing USB_LIBCOMPOSITE selects CONFIGFS_FS.
50 http://www.spinics.net/lists/linux-usb/msg76388.html)
55 $ mount none $CONFIGFS_HOME -t configfs
60 -----------------------
82 In order to have a place to store them, a strings subdirectory must be created
[all …]
|
| H A D | functionfs.rst | 12 that kernel level composite functions provide when they are added to
15 This in particular means that the composite initialisation functions
16 may not be in init section (ie. may not use the __init tag).
25 them as needed also handling situation when numbers differ in
28 For more information about FunctionFS descriptors see :doc:`functionfs-desc`
40 What I also want to mention is that the FunctionFS is designed in such
41 a way that it is possible to mount it several times so in the end
42 a gadget could use several FunctionFS functions. The idea is that
50 $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid
51 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
[all …]
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 17 heavy load during peak usage. In addition to keeping systems up and running,
20 functions without a system reboot.
26 There are multiple mechanisms in the Linux kernel that are directly related
30 - The kernel probes are the most generic. The code can be redirected by
33 - The function tracer calls the code from a predefined location that is
35 compiler using the '-pg' gcc option.
37 - Livepatching typically needs to redirect the code at the very beginning
39 are in any way modified.
53 Functions are there for a reason. They take some input parameters, acquire or
54 release locks, read, process, and even write some data in a defined way,
[all …]
|
| H A D | reliable-stacktrace.rst | 15 functions may have live state and therefore may not be safe to patch. One way
16 to identify which functions are live is to use a stacktrace.
19 functions with live state, and best-effort approaches which can be helpful for
22 functions from a trace.
28 Architectures must implement one of the reliable stacktrace functions.
35 * The trace includes all functions that the task may be returned to, and the
38 * The return code is non-zero to indicate that the trace is not reliable.
41 In some cases it is legitimate to omit specific functions from the trace,
42 but all other functions must be reported. These cases are described in
47 function should attempt to detect such cases and return a non-zero error
[all …]
|
| /linux/Documentation/core-api/ |
| H A D | genalloc.rst | 4 There are a number of memory-allocation subsystems in the kernel, each
6 implement a new allocator for a specific range of special-purpose memory;
10 tested allocators. Back in 2005, Jes Sorensen lifted one of those
20 .. kernel-doc:: lib/genalloc.c
21 :functions: gen_pool_create
23 .. kernel-doc:: lib/genalloc.c
24 :functions: devm_gen_pool_create
27 allocations is set with min_alloc_order; it is a log-base-2 number like
31 required to track the memory in the pool. The nid parameter specifies
33 structures; it can be -1 if the caller doesn't care.
[all …]
|
| H A D | asm-annotations.rst | 4 Copyright (c) 2017-2019 Jiri Slaby
6 This document describes the new macros for annotation of data and code in
7 assembly. In particular, it contains information about ``SYM_FUNC_START``,
11 ---------
12 Some code like entries, trampolines, or boot code needs to be written in
13 assembly. The same as in C, such code is grouped into functions and
18 some functions as *global* in order to be visible outside of their translation
24 annotations in assembly. Due to the lack of their documentation, the macros
25 are used in rather wrong contexts at some locations. Clearly, ``ENTRY`` was
27 ``END`` used to mark the end of data or end of special functions with
[all …]
|
| H A D | debug-objects.rst | 2 The object-lifetime debugging infrastructure
15 - Activation of uninitialized objects
17 - Initialization of active objects
19 - Usage of freed/destroyed objects
22 can be compiled in with a minimal runtime impact and enabled on demand
31 the object type. Optional functions can and should be provided to fixup
39 - debug_object_init
41 - debug_object_init_on_stack
43 - debug_object_activate
45 - debug_object_deactivate
[all …]
|
| /linux/Documentation/power/ |
| H A D | opp.rst | 5 (C) 2009-2010 Nishanth Menon <nm@ti.com>, Texas Instruments Incorporated
11 3. OPP Search Functions
12 4. OPP Availability Control Functions
13 5. OPP Data Retrieval Functions
20 -------------------------------------------------
22 Complex SoCs of today consists of a multiple sub-modules working in conjunction.
23 In an operational system executing varied use cases, not all modules in the SoC
25 facilitate this, sub-modules in a SoC are grouped into domains, allowing some
41 - {300000000, 1000000}
42 - {800000000, 1200000}
[all …]
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-script-perl.txt | 1 perf-script-perl(1)
5 ----
6 perf-script-perl - Process trace data with a Perl script
9 --------
11 'perf script' [-s [Perl]:script[.pl] ]
14 -----------
17 built-in Perl interpreter. It reads and processes the input file and
18 displays the results of the trace analysis implemented in the given
22 ---------------
25 -g perl' in the same directory as an existing perf.data trace file.
[all …]
|
| H A D | perf-ftrace.txt | 1 perf-ftrace(1)
5 ----
6 perf-ftrace - simple wrapper for kernel's ftrace functionality
10 --------
15 -----------
20 single thread tracing currently and just reads trace_pipe in text and then
32 --------------
34 -p::
35 --pid=::
38 --tid=::
[all …]
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | marvell,armada-37xx-pinctrl.txt | 12 ------------------------
16 Refer to pinctrl-bindings.txt in this directory for details of the
22 - compatible: "marvell,armada3710-sb-pinctrl", "syscon, "simple-mfd"
24 "marvell,armada3710-nb-pinctrl", "syscon, "simple-mfd"
26 - reg: The first set of register are for pinctrl/gpio and the second
28 - interrupts: list of the interrupt use by the gpio
30 Available groups and functions for the North bridge:
33 - pins 20-24
34 - functions jtag, gpio
37 - pins 8-10
[all …]
|
| /linux/Documentation/PCI/endpoint/ |
| H A D | pci-vntb-howto.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 PCI Non-Transparent Bridge (NTB) Endpoint Function (EPF) User Guide
9 This document is a guide to help users use pci-epf-vntb function driver
11 be followed in the host side and EP side is given below. For the hardware
13 Documentation/PCI/endpoint/pci-vntb-function.rst
19 ---------------------------
21 To find the list of endpoint controller devices in the system::
32 -------------------------
34 To find the list of endpoint function drivers in the system::
36 # ls /sys/bus/pci-epf/drivers
[all …]
|
| H A D | pci-ntb-howto.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 PCI Non-Transparent Bridge (NTB) Endpoint Function (EPF) User Guide
9 This document is a guide to help users use pci-epf-ntb function driver
11 be followed in the host side and EP side is given below. For the hardware
13 Documentation/PCI/endpoint/pci-ntb-function.rst
19 ---------------------------
24 To find the list of endpoint controller devices in the system::
27 2900000.pcie-ep 2910000.pcie-ep
32 2900000.pcie-ep 2910000.pcie-ep
36 -------------------------
[all …]
|
| /linux/Documentation/driver-api/media/ |
| H A D | dtv-demux.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ---------------------
9 The Kernel Digital TV Demux kABI defines a driver-internal interface for
10 registering low-level, hardware specific driver to a hardware independent
12 The header file for this kABI is named ``demux.h`` and located in
15 The demux kABI should be implemented for each demux in the system. It is
20 Each demux receives its TS input from a DVB front-end or from memory, as
21 set via this demux kABI. In a system with more than one front-end, the kABI
22 can be used to select one of the DVB front-ends as a TS source for a demux,
23 unless this is fixed in the HW platform.
[all …]
|
| /linux/Documentation/arch/arm/omap/ |
| H A D | omap_pm.rst | 6 authors use these functions to communicate minimum latency or
13 - support the range of power management parameters present in the TI SRF;
15 - separate the drivers from the underlying PM parameter
19 - specify PM parameters in terms of fundamental units, such as
23 - allow drivers which are shared with other architectures (e.g.,
24 DaVinci) to add these constraints in a way which won't affect non-OMAP
27 - can be implemented immediately with minimal disruption of other
32 five power management functions for driver code:
36 (*pdata->set_max_mpu_wakeup_lat)(struct device *dev, unsigned long t)
40 (*pdata->set_max_dev_wakeup_lat)(struct device *dev, unsigned long t)
[all …]
|
| /linux/Documentation/bpf/ |
| H A D | bpf_licensing.rst | 10 "BPF" was originally introduced as BSD Packet Filter in
11 http://www.tcpdump.org/papers/bpf-usenix93.pdf. The corresponding instruction
15 However an instruction set is a specification for machine-language interaction,
17 application of a BSD license may be misleading in a certain context, as the
22 In 2014, the classic BPF instruction set was significantly extended. We
29 Using the eBPF instruction set requires implementing code in both kernel space
32 In Linux Kernel
33 ---------------
35 The reference implementations of the eBPF interpreter and various just-in-time
37 eBPF helper functions is also GPLv2 licensed. Interpreters, JITs, helpers,
[all …]
|
| /linux/tools/power/pm-graph/ |
| H A D | README | 8 pm-graph: suspend/resume/boot timing analysis tools
11 …Home Page: https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/overvi…
13 Report bugs/issues at bugzilla.kernel.org Tools/pm-graph
14 - https://bugzilla.kernel.org/buglist.cgi?component=pm-graph&product=Tools
16 Full documentation available online & in man pages
17 - Getting Started:
20 - Feature Summary:
21 https://www.intel.com/content/www/us/en/developer/topic-technology/open/pm-graph/features.html
23 - upstream version in git:
24 git clone https://github.com/intel/pm-graph/
[all …]
|
| /linux/rust/ |
| H A D | build_error.rs | 1 // SPDX-License-Identifier: GPL-2.0
3 //! Build-time error.
5 //! This crate provides a [const function][const-functions] `build_error`, which will panic in
6 //! compile-time if executed in [const context][const-context], and will cause a build error
9 //! It is used by `build_assert!` in the kernel crate, allowing checking of
10 //! conditions that could be checked statically, but could not be enforced in
11 //! Rust yet (e.g. perform some checks in [const functions][const-functions], but those
12 //! functions could still be called in the runtime).
14 //! For details on constant evaluation in Rust, please see the [Reference][const-eval].
16 //! [const-eval]: https://doc.rust-lang.org/reference/const_eval.html
[all …]
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | consumer.rst | 12 that depend on GPIOLIB or select GPIOLIB. The functions that allow a driver to
17 There are static inline stubs for all functions in the header file in the case
21 - Simple compile coverage with e.g. COMPILE_TEST - it does not matter that
25 - Truly optional GPIOLIB support - where the driver does not really make use
26 of the GPIOs on certain compile-time configurations for certain systems, but
27 will use it under other compile-time configurations. In this case the
28 consumer must make sure not to call into these functions, or the user will
31 ``[devm_]gpiod_get_optional()`` is a *bad idea*, and will result in weird
32 error messages. Use the ordinary getter functions with optional GPIOLIB:
35 All the functions that work with the descriptor-based GPIO interface are
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | reset.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
13 the `consumer driver interface <#consumer-driver-interface>`__ (`API reference
14 <#reset-consumer-api>`__), which allows peripheral drivers to request control
16 <#reset-controller-driver-interface>`__ (`API reference
17 <#reset-controller-driver-api>`__), which is used by drivers for reset
25 --------
37 Most commonly this is a single bit in reset controller register space that
39 is self-clearing and can be used to trigger a predetermined pulse on the
41 In more complicated reset controls, a single trigger action can launch a
60 Functions are provided to assert and deassert the controlled reset lines,
[all …]
|
| /linux/Documentation/trace/rv/ |
| H A D | da_monitor_instrumentation.rst | 7 In the example of the wip.dot monitor created on [1], it will look like::
50 Tracing callback functions
51 --------------------------
53 The first three functions are the starting point of the callback *handler
54 functions* for each of the three events from the wip model. The developer
74 In this case, the kernel event translates one to one with the automata
81 Initially, the *model* is placed in the initial state. However, the *system*
82 might or might not be in the initial state. The monitor cannot start
84 Otherwise, the monitor and the system could be out-of-sync.
92 "da_handle_start_event_$(MONITOR_NAME)(event)", in this case::
[all …]
|
| /linux/Documentation/arch/s390/ |
| H A D | pci.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 - Pierre Morel
17 -----------------------
28 ---------------
30 The S/390 debug feature (s390dbf) generates views to hold various debug results in sysfs directorie…
36 - /sys/kernel/debug/s390dbf/pci_msg/sprintf
48 Entries specific to zPCI functions and entries that hold zPCI information.
56 - /sys/bus/pci/slots/XXXXXXXX/power
59 powered off until all virtual functions are removed with:
64 - function_id
[all …]
|
| /linux/tools/power/pm-graph/config/ |
| H A D | example.cfg | 6 # command line. It also includes advanced settings for functions
9 # sudo ./sleepgraph.py -config config/example.cfg
14 # ---- General Options ----
26 output-dir: suspend-{hostname}-{date}-{time}
49 # Enable/disable runtime suspend for all devices, restore all after test (default: no-action)
53 # Switch the display on/off for the test using xset (default: no-action)
57 # Print the status of the test run in the given file (default: no-action)
64 # ---- Advanced Options ----
66 # Command to execute in lieu of suspend (default: "")
70 # graph user processes and cpu usage in the timeline (default: false)
[all …]
|
| /linux/drivers/gpu/drm/amd/display/dc/dml/dcn10/ |
| H A D | dcn10_fpu.c | 1 // SPDX-License-Identifier: MIT
7 * to deal in the Software without restriction, including without limitation
12 * The above copyright notice and this permission notice shall be included in
17 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
19 * OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
20 * ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
21 * OTHER DEALINGS IN THE SOFTWARE.
37 * compilation flags and the use of kernel_fpu_begin/end functions; ideally, we
38 * want to avoid spreading FPU access across multiple files. With this idea in
39 * mind, this file aims to centralize DCN10 functions that require FPU access
[all …]
|
| /linux/kernel/gcov/ |
| H A D | gcc_4_7.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * This code provides functions to handle gcc's profiling data format
9 * gcc/gcov-io.h
12 * Uses gcc-internal data definitions.
31 /* Since GCC 12.1 sizes are in BYTES and not in WORDS (4B). */
41 * struct gcov_ctr_info - information about counters for a single function
46 * at run-time with the exception of the values array.
54 * struct gcov_fn_info - profiling meta data per function
62 * at run-time.
66 * array in gcov_info. The key is used to detect which of a set of
[all …]
|