Searched +full:in +full:- +full:functions (Results 1 – 25 of 1164) sorted by relevance
12345678910>>...47
| /kernel/linux/linux-6.6/Documentation/usb/ |
| 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 …]
|
| D | functionfs.rst | 9 that kernel level composite functions provide when they are added to
12 This in particular means that the composite initialisation functions
13 may not be in init section (ie. may not use the __init tag).
22 them as needed also handling situation when numbers differ in
35 What I also want to mention is that the FunctionFS is designed in such
36 a way that it is possible to mount it several times so in the end
37 a gadget could use several FunctionFS functions. The idea is that
45 $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid
46 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
47 $ ( cd /dev/ffs-mtp && mtp-daemon ) &
[all …]
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| 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 …]
|
| D | functionfs.rst | 9 that kernel level composite functions provide when they are added to
12 This in particular means that the composite initialisation functions
13 may not be in init section (ie. may not use the __init tag).
22 them as needed also handling situation when numbers differ in
35 What I also want to mention is that the FunctionFS is designed in such
36 a way that it is possible to mount it several times so in the end
37 a gadget could use several FunctionFS functions. The idea is that
45 $ insmod g_ffs.ko idVendor=<ID> iSerialNumber=<string> functions=mtp,hid
46 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp
47 $ ( cd /dev/ffs-mtp && mtp-daemon ) &
[all …]
|
| /kernel/linux/linux-6.6/Documentation/core-api/ |
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/livepatch/ |
| D | livepatch.rst | 13 4.1. New functions
15 5. Livepatch life-cycle
30 heavy load during peak usage. In addition to keeping systems up and running,
33 functions without a system reboot.
39 There are multiple mechanisms in the Linux kernel that are directly related
43 - The kernel probes are the most generic. The code can be redirected by
46 - The function tracer calls the code from a predefined location that is
48 compiler using the '-pg' gcc option.
50 - Livepatching typically needs to redirect the code at the very beginning
52 are in any way modified.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/livepatch/ |
| 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, get or
54 release locks, read, process, and even write some data in a defined way,
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
15 bool "Automatically choose fastest RAID6 PQ functions"
19 Benchmark all available RAID6 PQ functions on init and choose the
30 converting bitfields between a CPU-usable representation and a
32 - Is little endian (bytes are reversed within a 32-bit group)
33 - The least-significant 32-bit word comes first (within a 64-bit
35 - The most significant bit of a byte is at its right (bit 0 of a
38 in the data sheets of the peripherals they are in control of.
40 When in doubt, say N.
49 This option enables the use of hardware bit-reversal instructions on
[all …]
|
| /kernel/linux/linux-6.6/lib/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
15 bool "Automatically choose fastest RAID6 PQ functions"
19 Benchmark all available RAID6 PQ functions on init and choose the
31 converting bitfields between a CPU-usable representation and a
33 - Is little endian (bytes are reversed within a 32-bit group)
34 - The least-significant 32-bit word comes first (within a 64-bit
36 - The most significant bit of a byte is at its right (bit 0 of a
39 in the data sheets of the peripherals they are in control of.
41 When in doubt, say N.
50 This option enables the use of hardware bit-reversal instructions on
[all …]
|
| /kernel/linux/linux-6.6/Documentation/power/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| 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 …]
|
| /kernel/linux/linux-5.10/tools/lib/bpf/ |
| D | README.rst | 1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
7 functions and types. Every group has its own naming convention
11 All types and functions provided by libbpf API should have one of the
16 --------------------
20 and map one-on-one to corresponding commands.
26 -------
28 Another class of types and functions provided by libbpf API is "objects"
29 and functions to work with them. Objects are high-level abstractions
42 program in ELF object and ``struct bpf_map`` is a map.
44 Functions that work with an object have names built from object name,
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| 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 …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| D | ftrace-uses.rst | 2 Using ftrace to hook to functions
16 beginning of functions in order to record and trace the flow of the kernel.
33 There are helper functions to help against recursion, and making sure
48 .. code-block:: c
77 no longer being called by functions after the unregister_ftrace_function()
87 .. code-block:: c
106 flags are set in the ftrace_ops structure, then this will be pointing
114 As functions can be called from anywhere, and it is possible that a function
116 recursion protection must be used. There are two helper functions that
117 can help in this regard. If you start your code with:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/PCI/endpoint/ |
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uvc | 1 What: /config/usb-gadget/gadget/functions/uvc.name
13 What: /config/usb-gadget/gadget/functions/uvc.name/control
27 What: /config/usb-gadget/gadget/functions/uvc.name/control/class
32 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/ss
37 What: /config/usb-gadget/gadget/functions/uvc.name/control/class/fs
42 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal
47 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output
52 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/output/default
66 bTerminalID a non-zero id of this terminal
69 What: /config/usb-gadget/gadget/functions/uvc.name/control/terminal/camera
[all …]
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | ftrace-uses.rst | 2 Using ftrace to hook to functions
16 beginning of functions in order to record and trace the flow of the kernel.
48 .. code-block:: c
77 no longer being called by functions after the unregister_ftrace_function()
87 .. code-block:: c
106 flags are set in the ftrace_ops structure, then this will be pointing
115 The ftrace_ops flags are all defined and documented in include/linux/ftrace.h.
146 itself or any nested functions that those functions call.
156 kernel patches uses. Without this flag the pt_regs->ip can not be
163 If this is set, then the callback will only be called by functions
[all …]
|
| /kernel/linux/linux-6.6/Documentation/sound/designs/ |
| D | midi-2.0.rst | 12 - Support of Universal MIDI Packet (UMP)
13 - Support of MIDI 2.0 protocol messages
14 - Transparent conversions between UMP and legacy MIDI 1.0 byte stream
15 - MIDI-CI for property and profile configurations
19 aligned, and each message can be put in a single packet. UMP can send
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
27 for the flexible profiles and configurations. It's represented in the
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
32 supported in user-space over the standard SysEx.
39 The access to UMP devices are provided in two ways: the access via
[all …]
|
12345678910>>...47