Searched +full:out +full:- +full:functions (Results 1 – 25 of 321) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/usb/ |
| D | brcm,usb-pinmap.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/usb/brcm,usb-pinmap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Al Cooper <alcooperx@gmail.com>
15 - const: brcm,usb-pinmap
22 description: Interrupt for signals mirrored to out-gpios.
24 in-gpios:
29 brcm,in-functions:
30 $ref: /schemas/types.yaml#/definitions/string-array
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-usb-gadget-uac1_legacy | 1 What: /config/usb-gadget/gadget/functions/uac1_legacy.name
7 audio_buf_size - audio buffer size
8 fn_cap - capture pcm device file name
9 fn_cntl - control device file name
10 fn_play - playback pcm device file name
11 req_buf_size - ISO OUT endpoint request buffer size
12 req_count - ISO OUT endpoint request count
|
| /Documentation/filesystems/iomap/ |
| D | porting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
27 This worked well enough for direct/indirect-mapped filesystems such
28 as ext2, but is very inefficient for extent-based filesystems such
34 3. Direct access to storage on memory-like devices (fsdax) is only
40 No ->write_begin(), ->write_end() or direct_IO
49 Build the kernel, run fstests with the ``-g all`` option across a wide
53 The recommended approach is first to implement ``->iomap_begin`` (and
54 ``->iomap_end`` if necessary) to allow iomap to obtain a read-only
57 ``get_block()`` function for read-only mappings.
62 other read-only mapping operations will do the right thing.
[all …]
|
| /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
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
32 supported in user-space over the standard SysEx.
65 When a device supports MIDI 2.0, the USB-audio driver probes and uses
69 `midi2_enable=0` option to snd-usb-audio driver module, too.
78 option to snd-usb-audio driver for skipping the UMP v1.1 inquiries.
[all …]
|
| /Documentation/trace/ |
| D | ftrace-design.rst | 8 This document is out of date. Some of the description below doesn't
12 ------------
27 -------------
30 - STACKTRACE_SUPPORT - implement save_stack_trace()
31 - TRACE_IRQFLAGS_SUPPORT - implement include/asm/irqflags.h
35 --------------------
37 You will need to implement the mcount and the ftrace_stub functions.
40 "mcount", "_mcount", or even "__mcount". You can probably figure it out by
43 $ echo 'main(){}' | gcc -x c -S -o - - -pg | grep mcount
56 be (semi-)relevant.
[all …]
|
| /Documentation/sphinx/ |
| D | kerneldoc.py | 1 # coding=utf-8
21 # FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
47 """Extract kernel-doc comments from the specified file"""
55 'no-identifiers': directives.unchanged,
56 'functions': directives.unchanged,
62 cmd = [env.config.kerneldoc_bin, '-rst', '-enable-lineno']
64 # Pass the version string to kernel-doc, as it needs to use a different
67 cmd += ['-sphinx-version', sphinx.__version__]
75 tab_width = self.options.get('tab-width', self.state.document.settings.tab_width)
78 if 'functions' in self.options:
[all …]
|
| /Documentation/sound/cards/ |
| D | maya44.rst | 8 keep here as reference -- tiwai
18 Development is carried out by Rainer Zimmermann (mail@lightshed.de).
22 …tunately it has turned out difficult to get detailed programming information, so I (Rainer Zimmerm…
24 This is the first testing version of the Maya44 driver released to the alsa-devel mailing list (Feb…
27 The following functions work, as tested by Rainer Zimmermann and Piotr Makowski:
29 - playback and capture at all sampling rates
30 - input/output level
31 - crossmixing
32 - line/mic switch
33 - phantom power switch
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 1 .. SPDX-License-Identifier: GPL-2.0
14 This document describes the functions and the interfaces of the
20 ACPICA provides method tracing capability. And two functions are
24 -----------
28 ACPI_DEBUG_PRINT() macro can be reduced at 2 levels - per-component
30 /sys/module/acpi/parameters/debug_layer) and per-type level (known as
35 large to be put into the kernel log buffer. The idea thus is worked out
43 a. Filter out the debug layer/level matched logs when control methods
51 b. Filter out the debug layer/level matched logs when the specified
60 c. Filter out the debug layer/level matched logs when the specified
[all …]
|
| /Documentation/driver-api/ |
| 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
22 functionality, restart handlers are out of scope for the reset controller API.
25 --------
39 is self-clearing and can be used to trigger a predetermined pulse on the
60 Functions are provided to assert and deassert the controlled reset lines,
71 ---------------------------
[all …]
|
| D | spi.rst | 7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
8 line, and a "Master In, Slave Out" (MISO) data line. SPI is a full
9 duplex protocol; for each bit shifted out the MOSI line (one per clock)
12 additional chipselect line is usually active-low (nCS); four signals are
33 board-specific initialization code. A :c:type:`struct spi_driver
46 .. kernel-doc:: include/linux/spi/spi.h
49 .. kernel-doc:: drivers/spi/spi.c
50 :functions: spi_register_board_info
52 .. kernel-doc:: drivers/spi/spi.c
|
| D | mtdnand.rst | 10 The generic NAND driver supports almost all NAND and AG-AND based chips
31 --------------------------
33 The functions are marked with [XXX] identifiers in the short comment.
34 The identifiers explain the usage and scope of the functions. Following
37 - [MTD Interface]
39 These functions provide the interface to the MTD kernel API. They are
43 - [NAND Interface]
45 These functions are exported and provide the interface to the NAND
48 - [GENERIC]
50 Generic functions are not replaceable and provide functionality which
[all …]
|
| /Documentation/arch/sh/ |
| D | new-machine.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Paul Mundt <lethal@linux-sh.org>
18 of the board-specific code (with the exception of stboards) ended up
19 in arch/sh/kernel/ directly, with board-specific headers ending up in
20 include/asm-sh/. For the new kernel, things are broken out by board type,
24 Board-specific code::
27 |-- arch
28 | `-- sh
29 | `-- boards
30 | |-- adx
[all …]
|
| /Documentation/process/ |
| D | 4.Coding.rst | 6 While there is much to be said for a solid and community-oriented design
19 ---------
25 :ref:`Documentation/process/coding-style.rst <codingstyle>`. For much of
38 strangely-formatted code.
43 giving up a degree of control in a number of ways - including control over
49 as a way of getting their name into the kernel changelogs - or both. But
59 80-column limit, for example), just do it.
61 Note that you can also use the ``clang-format`` tool to help you with
62 these rules, to quickly re-format parts of your code automatically,
66 See the file :ref:`Documentation/dev-tools/clang-format.rst <clangformat>`
[all …]
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 every day; look for little things that are out of place or in need of tidying.
9 spiraled out of control.
11 Things don't always have to be perfect - nitpicking often does more harm than
12 good. But appreciate beauty when you see it - and let people know.
26 you're not sure if it can happen and not sure how to handle it yet - make it a
33 expensive - but don't turn everything into a debug mode assertion, so that
34 we're not stuck debugging undefined behaviour should it turn out that you were
37 Assertions are documentation that can't go out of date. Good assertions are
41 required to shake out bugs.
[all …]
|
| /Documentation/arch/arm/ |
| D | tcm.rst | 2 ARM TCM (Tightly-Coupled Memory) handling in Linux
7 Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
8 This is usually just a few (4-64) KiB of RAM inside the ARM
12 Harvard-architecture, so there is an ITCM (instruction TCM)
18 ARM CPUs have special registers to read out status, physical
20 defines a CPUID_TCM register that you can read out from the
24 determine if ITCM (bits 1-0) and/or DTCM (bit 17-16) is present
29 size of TCM memories at runtime. This is used to read out and modify
52 - FIQ and other interrupt handlers that need deterministic
55 - Idle loops where all external RAM is set to self-refresh
[all …]
|
| /Documentation/arch/x86/ |
| D | sgx.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 * Privileged (ring-0) ENCLS functions orchestrate the construction of the
15 * Unprivileged (ring-3) ENCLU functions allow an application to enter and
21 ENCLS functions, only the threads inside the enclave can access its memory. The
38 with an enclave. It is contained in a BIOS-reserved region of physical memory.
49 ------------------
67 ----------------------
76 remain read-only. EPCM permissions may only impose additional restrictions on
87 Enclave build functions
88 -----------------------
[all …]
|
| /Documentation/security/ |
| D | siphash.rst | 2 SipHash - a short input PRF
7 SipHash is a cryptographically secure PRF -- a keyed hash function -- that
9 cryptographers Daniel J. Bernstein and Jean-Philippe Aumasson. It is intended
14 an input buffer or several input integers. It spits out an integer that is
29 Using the functions
49 will constant fold at compile-time and automatically choose one of the
50 optimized functions.
61 get_random_bytes(&table->key, sizeof(table->key));
66 …return &table->hashtable[siphash(input, sizeof(*input), &table->key) & (HASH_SIZE(table->hashtable…
74 SipHash has a very high security margin, with its 128-bit key. So long as the
[all …]
|
| /Documentation/dev-tools/kunit/ |
| D | usage.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ----------
13 .. code-block:: c
38 .. code-block:: c
59 To learn about more KUnit expectations, see Documentation/dev-tools/kunit/api/test.rst.
69 .. code-block:: c
79 KUNIT_EXPECT_EQ(test, 0, add(-1, 1));
85 KUNIT_EXPECT_EQ(test, -1, add(INT_MAX, INT_MIN));
99 .. code-block:: c
111 for (i = 0; i < TEST_LEN-1; i++)
[all …]
|
| /Documentation/trace/rv/ |
| D | da_monitor_instrumentation.rst | 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
84 Otherwise, the monitor and the system could be out-of-sync.
112 enable and disable functions
113 ----------------------------
115 dot2k automatically creates two special functions::
120 These functions are called when the monitor is enabled and disabled,
127 For the wip case, these functions were named::
[all …]
|
| /Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 16 already held resources (e.g. locks - most commonly those used for the
22 used as shortcut. It turned out though that above approach has led to
25 of GFP_NOFS/GFP_NOIO can lead to memory over-reclaim or other memory
38 .. kernel-doc:: include/linux/sched/mm.h
39 :functions: memalloc_nofs_save memalloc_nofs_restore
40 .. kernel-doc:: include/linux/sched/mm.h
41 :functions: memalloc_noio_save memalloc_noio_restore
44 any critical section with respect to the reclaim is started - e.g.
50 Please note that the proper pairing of save/restore functions
59 GFP_KERNEL allocations deep inside the allocator which are quite non-trivial
|
| D | idr.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
18 only ID allocation, and as a result is much more memory-efficient.
50 either use the callback-based idr_for_each() or the
51 iterator-style idr_for_each_entry(). You may need to use
60 You can use idr_is_empty() to find out whether there are any
69 .. kernel-doc:: include/linux/idr.h
75 .. kernel-doc:: lib/idr.c
78 Functions and structures
81 .. kernel-doc:: include/linux/idr.h
82 :functions:
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra124-xusb-padctl.txt | 4 NOTE: It turns out that this binding isn't an accurate description of the XUSB
7 needed for USB. For the new binding, see ../phy/nvidia,tegra-xusb-padctl.txt.
11 assigned to one out of a set of different pads. Some of these pads have an
14 This document defines the device-specific binding for the XUSB pad controller.
16 Refer to pinctrl-bindings.txt in this directory for generic information about
17 pin controller device tree bindings and ../phy/phy-bindings.txt for details on
21 --------------------
22 - compatible: For Tegra124, must contain "nvidia,tegra124-xusb-padctl".
23 Otherwise, must contain '"nvidia,<chip>-xusb-padctl",
24 "nvidia-tegra124-xusb-padctl"', where <chip> is tegra132 or tegra210.
[all …]
|
| /Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 5 (C) 2011 - 2014 Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
8 I. Differences between CPU hotplug and Suspend-to-RAM
11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
14 Well, a picture is worth a thousand words... So ASCII art follows :-)
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
24 On a high level, the suspend-resume cycle goes like this::
26 |Freeze| -> |Disable nonboot| -> |Do suspend| -> |Enable nonboot| -> |Thaw |
33 -----------------
62 | ----------
76 frozen_cpus mask ----------
[all …]
|
| /Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 2 IRQ-flags state tracing
7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
9 every hardirqs-off/hardirqs-on, softirqs-off/softirqs-on event that
15 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
20 category, because lots of lowlevel assembly code deal with irq-flags
21 state changes. But an architecture can be irq-flags-tracing enabled in a
22 rather straightforward and risk-free manner.
25 code-organizational changes first:
27 - add and enable TRACE_IRQFLAGS_SUPPORT in their arch level Kconfig file
30 irq-flags-tracing support:
[all …]
|
| /Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.rst | 8 implement the API on its own. Now, as the framework factored out the common
11 as well as things to look out for.
15 ---------------------------------
19 needed. So, in general, the 'file_operations' struct and assorted functions can
20 go. Only very few driver-specific details have to be moved to other functions.
21 Here is a overview of the functions and probably needed actions:
23 - open: Everything dealing with resource management (file-open checks, magic
25 driver specific start-function. Note that for some drivers, the start-function
26 also serves as the ping-function. If that is the case and you need start/stop
27 to be balanced (clocks!), you are better off refactoring a separate start-function.
[all …]
|
12345678910>>...13