Home
last modified time | relevance | path

Searched +full:multi +full:- +full:subsystems (Results 1 – 25 of 44) sorted by relevance

12

/Linux-v6.1/Documentation/devicetree/bindings/spi/
Dsprd,spi-adi.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/spi/sprd,spi-adi.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Orson Zhai <orsonzhai@gmail.com>
12 - Baolin Wang <baolin.wang7@gmail.com>
13 - Chunyan Zhang <zhang.lyra@gmail.com>
16 ADI is the abbreviation of Anolog-Digital interface, which is used to access
29 Thus we introduce one property named "sprd,hw-channels" to configure hardware
34 Since we have multi-subsystems will use unique ADI to access analog chip, when
[all …]
/Linux-v6.1/Documentation/process/
Dclang-format.rst3 clang-format
6 ``clang-format`` is a tool to format C/C++/... code according to
10 ``clang-format`` can be used for several purposes:
12 - Quickly reformat a block of code to the kernel style. Specially useful
15 - Spot style mistakes, typos and possible improvements in files
18 - Help you follow the coding style rules, specially useful for those
22 Its configuration file is ``.clang-format`` in the root of the kernel tree.
24 coding style. They also try to follow :ref:`Documentation/process/coding-style.rst <codingstyle>`
28 another ``.clang-format`` file in a subfolder.
31 Linux distributions for a long time. Search for ``clang-format`` in
[all …]
Dmaintainer-tip.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ---------------------
9 The tip tree is a collection of several subsystems and areas of
11 aggregation tree for several sub-maintainer trees. The tip tree gitweb URL
14 The tip tree contains the following subsystems:
16 - **x86 architecture**
20 corresponding subsystems and routed directly to mainline from
22 x86-specific KVM and XEN patches.
24 Some x86 subsystems have their own maintainers in addition to the
30 mail alias which distributes mails to the x86 top-level maintainer
[all …]
Dcoding-style.rst19 --------------
31 Now, some people will claim that having 8-character indentations makes
33 80-character terminal screen. The answer to that is that if you need
37 In short, 8-char indents make things easier to read, and have the added
43 instead of ``double-indenting`` the ``case`` labels. E.g.:
45 .. code-block:: c
67 .. code-block:: c
74 .. code-block:: c
81 .. code-block:: c
99 ----------------------------------
[all …]
/Linux-v6.1/drivers/nvmem/
Dsc27xx-efuse.c1 // SPDX-License-Identifier: GPL-2.0
10 #include <linux/nvmem-provider.h>
80 * On Spreadtrum platform, we have multi-subsystems will access the unique
82 * the multiple subsystems.
88 mutex_lock(&efuse->mutex); in sc27xx_efuse_lock()
90 ret = hwspin_lock_timeout_raw(efuse->hwlock, in sc27xx_efuse_lock()
93 dev_err(efuse->dev, "timeout to get the hwspinlock\n"); in sc27xx_efuse_lock()
94 mutex_unlock(&efuse->mutex); in sc27xx_efuse_lock()
103 hwspin_unlock_raw(efuse->hwlock); in sc27xx_efuse_unlock()
104 mutex_unlock(&efuse->mutex); in sc27xx_efuse_unlock()
[all …]
Dsprd-efuse.c1 // SPDX-License-Identifier: GPL-2.0
9 #include <linux/nvmem-provider.h>
79 * On Spreadtrum platform, we have multi-subsystems will access the unique
81 * the multiple subsystems.
87 mutex_lock(&efuse->mutex); in sprd_efuse_lock()
89 ret = hwspin_lock_timeout_raw(efuse->hwlock, in sprd_efuse_lock()
92 dev_err(efuse->dev, "timeout get the hwspinlock\n"); in sprd_efuse_lock()
93 mutex_unlock(&efuse->mutex); in sprd_efuse_lock()
102 hwspin_unlock_raw(efuse->hwlock); in sprd_efuse_unlock()
103 mutex_unlock(&efuse->mutex); in sprd_efuse_unlock()
[all …]
/Linux-v6.1/tools/perf/Documentation/
Dperf-bench.txt1 perf-bench(1)
5 ----
6 perf-bench - General framework for benchmark suites
9 --------
14 -----------
18 --------------
19 -r::
20 --repeat=::
23 -f::
24 --format=::
[all …]
/Linux-v6.1/Documentation/mm/
Dnuma.rst19 Each of the 'cells' may be viewed as an SMP [symmetric multi-processor] subset
20 of the system--although some components necessary for a stand-alone SMP system
22 connected together with some sort of system interconnect--e.g., a crossbar or
23 point-to-point link are common types of NUMA system interconnects. Both of
43 [cache misses] to be to "local" memory--memory on the same cell, if any--or
53 "closer" nodes--nodes that map to closer cells--will generally experience
65 the existing nodes--or the system memory for non-NUMA platforms--into multiple
68 application features on non-NUMA platforms, and as a sort of memory resource
70 [see Documentation/admin-guide/cgroup-v1/cpusets.rst]
73 subsystem, complete with its own free page lists, in-use page lists, usage
[all …]
/Linux-v6.1/tools/power/pm-graph/
Dsleepgraph.83 sleepgraph \- Suspend/Resume timing analysis
15 callgraph to give a detailed view of which devices/subsystems are
21 Generates output files in subdirectory: suspend-yymmdd-HHMMSS
27 \fB-h\fR
30 \fB-v\fR
33 \fB-verbose\fR
36 \fB-config \fIfile\fR
39 \fB-m \fImode\fR
42 \fB-o \fIname\fR
46 e.g. suspend-{hostname}-{date}-{time}
[all …]
DREADME8 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
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/
27 - Overview
[all …]
/Linux-v6.1/fs/xfs/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
10 on the SGI IRIX platform. It is completely multi-threaded, can
17 for complete details. This implementation is on-disk compatible
58 higher level guarantee of consistency. The on-disk data format for
65 with or without the generic quota support enabled (CONFIG_QUOTA) -
66 they are completely independent subsystems.
90 to applications via the inherit-realtime directory inode flag.
136 It converts ASSERT checks to WARN, so will log any out-of-bounds
139 not cause the kernel to panic on non-fatal errors.
150 and extra sanity-checking functions in various code paths.
/Linux-v6.1/Documentation/driver-api/
Dinterconnect.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ------------
20 on an SoC that can be multi-tiered.
22 Below is a simplified diagram of a real-world SoC interconnect bus topology.
26 +----------------+ +----------------+
27 | HW Accelerator |--->| M NoC |<---------------+
28 +----------------+ +----------------+ |
29 | | +------------+
30 +-----+ +-------------+ V +------+ | |
31 | DDR | | +--------+ | PCIe | | |
[all …]
Ddma-buf.rst4 The dma-buf subsystem provides the framework for sharing buffers for
5 hardware (DMA) access across multiple device drivers and subsystems, and
8 This is used, for example, by drm "prime" multi-GPU support, but is of
11 The three main components of this are: (1) dma-buf, representing a
18 ------------------
20 This document serves as a guide to device-driver writers on what is the dma-buf
27 exporter, and A as buffer-user/importer.
31 - implements and manages operations in :c:type:`struct dma_buf_ops
33 - allows other users to share the buffer by using dma_buf sharing APIs,
34 - manages the details of buffer allocation, wrapped in a :c:type:`struct
[all …]
/Linux-v6.1/Documentation/arm/
Dinterrupts.rst5 2.5.2-rmk5:
7 major architecture-specific subsystems.
10 MMU TLB. Each MMU TLB variant is now handled completely separately -
26 SA1100 ------------> Neponset -----------> SA1111
28 -----------> USAR
30 -----------> SMC9196
33 exclusive of each other - if you're processing one interrupt from the
36 IDE PIO-based interrupt on the SA1111 excludes all other SA1111 and
37 SMC9196 interrupts until it has finished transferring its multi-sector
51 GPIO0-10, and another for all the rest. It is just a container for
[all …]
/Linux-v6.1/Documentation/driver-api/pm/
Ddevices.rst1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
42 by implementing various role-specific suspend and resume methods to
[all …]
/Linux-v6.1/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
83 called worker-pools.
85 The cmwq design differentiates between the user-facing workqueues that
86 subsystems and drivers queue work items on and the backend mechanism
87 which manages worker-pools and processes the queued work items.
89 There are two worker-pools, one for normal work items and the other
91 worker-pools to serve work items queued on unbound workqueues - the
94 Subsystems and drivers can create and queue work items through special
[all …]
Dcpu_hotplug.rst26 A more novel use of CPU-hotplug support is its use today in suspend resume
27 support for SMP. Dual-core and HT support makes even a laptop run SMP kernels
81 from the map depending on the event is hot-add/hot-remove. There are currently
86 be read-only for most use. When setting up per-cpu resources almost always use
100 $ ls -lh /sys/devices/system/cpu
102 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu0
103 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu1
104 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu2
105 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu3
106 drwxr-xr-x 9 root root 0 Dec 21 16:33 cpu4
[all …]
/Linux-v6.1/drivers/mfd/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
44 tristate "Active-semi ACT8945A"
49 Support for the ACT8945A PMIC from Active-semi. This device
50 features three step-down DC/DC converters and four low-dropout
66 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
69 called sun4i-gpadc.
88 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
119 over at91-usart-serial driver and usart-spi-driver. Only one function
135 tristate "Atmel HLCDC (High-end LCD Controller)"
172 tristate "X-Powers AC100"
[all …]
/Linux-v6.1/drivers/media/pci/tw68/
Dtw68-core.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * tw68-core.c
10 * acknowledged. Full credit goes to them - any problems within this code
30 #include <linux/dma-mapping.h>
34 #include <media/v4l2-dev.h>
36 #include "tw68-reg.h"
47 static unsigned int video_nr[] = {[0 ... (TW68_MAXBOARDS - 1)] = UNSET };
51 static unsigned int card[] = {[0 ... (TW68_MAXBOARDS - 1)] = UNSET };
57 /* ------------------------------------------------------------------ */
60 * Please add any new PCI IDs to: https://pci-ids.ucw.cz. This keeps
[all …]
/Linux-v6.1/kernel/
Dcpu.c35 #include <linux/percpu-rwsem.h>
47 * struct cpuhp_cpu_state - Per cpu hotplug state storage
57 * @node: Remote CPU node; for multi-instance, do a
59 * @last: For multi-instance rollback, remember how far we got
62 * @done_up: Signal completion to the issuer of the task for cpu-up
63 * @done_down: Signal completion to the issuer of the task for cpu-down
94 STATIC_LOCKDEP_MAP_INIT("cpuhp_state-up", &cpuhp_state_up_map);
96 STATIC_LOCKDEP_MAP_INIT("cpuhp_state-down", &cpuhp_state_down_map);
116 * struct cpuhp_step - Hotplug state machine step
127 int (*multi)(unsigned int cpu, member
[all …]
/Linux-v6.1/Documentation/fb/
Dfbcon.rst16 etc. Theoretically, multi-colored fonts, blending, aliasing, and any feature
23 configuration tool. It is under Device Drivers->Graphics Support->
24 Console display driver support->Framebuffer Console Support.
31 always be available. However, using a chipset-specific driver will give you
36 support->Bootup logo.
38 Also, you will need to select at least one compiled-in font, but if
84 compiled-in fonts: 10x18, 6x10, 6x8, 7x14, Acorn8x8, MINI4x6,
112 3. fbcon=vc:<n1>-<n2>
128 - 0 - normal orientation (0 degree)
129 - 1 - clockwise orientation (90 degrees)
[all …]
/Linux-v6.1/mm/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
34 compress them into a dynamically allocated RAM-based memory pool.
180 zsmalloc is a slab-based memory allocator designed to store
264 sanity-checking than others. This option is most effective with
278 Try running: slabinfo -DA
298 utilization of a direct-mapped memory-side-cache. See section
301 the presence of a memory-side-cache. There are also incidental
304 default granularity of shuffling on the "MAX_ORDER - 1" i.e,
311 after runtime detection of a direct-mapped memory-side-cache.
327 On non-ancient distros (post-2000 ones) N is usually a safe choice.
[all …]
/Linux-v6.1/Documentation/networking/
Dcan.rst2 SocketCAN - Controller Area Network
20 .. _socketcan-motivation:
29 functionality. Usually, there is only a hardware-specific device
32 Queueing of frames and higher-level transport protocols like ISO-TP
34 character-device implementations support only one single process to
47 protocol family module and also vice-versa. Also, the protocol family
57 communicate using a specific transport protocol, e.g. ISO-TP, just
60 CAN-IDs, frames, etc.
62 Similar functionality visible from user-space could be provided by a
74 * **Abstraction:** In most existing character-device implementations, the
[all …]
/Linux-v6.1/include/drm/
Ddrm_drv.h4 * Copyright (c) 2009-2010, Code Aurora Forum.
47 * enum drm_driver_feature - feature flags
79 * multi-plane updates are not guaranteed to be tear-free) should not
152 * struct drm_driver - DRM driver structure
164 * Backward-compatible driver callback to complete initialization steps
169 * proper and race-free way to set up a &struct drm_device.
175 * Zero on success, non-zero value on failure.
183 * setting up driver-private data structures like buffer allocators,
184 * execution contexts or similar things. Such driver-private resources
203 * Useful for tearing down driver-private data structures allocated in
[all …]
/Linux-v6.1/Documentation/RCU/
Dchecklist.rst1 .. SPDX-License-Identifier: GPL-2.0
14 0. Is RCU being applied to a read-mostly situation? If the data
18 tool for the job. Yes, RCU does reduce read-side overhead by
19 increasing write-side overhead, which is exactly why normal uses
27 Yet another exception is where the low real-time latency of RCU's
28 read-side primitives is critically important.
33 counter-intuitive situation where rcu_read_lock() and
49 them -- even x86 allows later loads to be reordered to precede
59 2. Do the RCU read-side critical sections make proper use of
63 under your read-side code, which can greatly increase the
[all …]

12