| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
| D | spi-sprd-adi.txt | 3 ADI is the abbreviation of Anolog-Digital interface, which is used to access
16 Thus we introduce one property named "sprd,hw-channels" to configure hardware
21 Since we have multi-subsystems will use unique ADI to access analog chip, when
26 Then we need one hardware spinlock to synchronize between the multiple subsystems.
34 - compatible: Should be "sprd,sc9860-adi".
35 - reg: Offset and length of ADI-SPI controller register space.
36 - #address-cells: Number of cells required to define a chip select address
37 on the ADI-SPI bus. Should be set to 1.
38 - #size-cells: Size of cells required to define a chip select address size
39 on the ADI-SPI bus. Should be set to 0.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/spi/ |
| D | sprd,spi-adi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/spi/sprd,spi-adi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Orson Zhai <orsonzhai@gmail.com>
11 - Baolin Wang <baolin.wang7@gmail.com>
12 - Chunyan Zhang <zhang.lyra@gmail.com>
15 ADI is the abbreviation of Anolog-Digital interface, which is used to access
28 Thus we introduce one property named "sprd,hw-channels" to configure hardware
33 Since we have multi-subsystems will use unique ADI to access analog chip, when
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | clang-format.rst | 3 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 …]
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | clang-format.rst | 3 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 …]
|
| D | maintainer-tip.rst | 1 .. 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 …]
|
| /kernel/linux/linux-5.10/drivers/nvmem/ |
| D | sc27xx-efuse.c | 1 // 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 …]
|
| D | sprd-efuse.c | 1 // 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 …]
|
| /kernel/linux/linux-6.6/drivers/nvmem/ |
| D | sc27xx-efuse.c | 1 // 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 sc27xx_efuse_lock()
89 ret = hwspin_lock_timeout_raw(efuse->hwlock, in sc27xx_efuse_lock()
92 dev_err(efuse->dev, "timeout to get the hwspinlock\n"); in sc27xx_efuse_lock()
93 mutex_unlock(&efuse->mutex); in sc27xx_efuse_lock()
102 hwspin_unlock_raw(efuse->hwlock); in sc27xx_efuse_unlock()
103 mutex_unlock(&efuse->mutex); in sc27xx_efuse_unlock()
[all …]
|
| D | sprd-efuse.c | 1 // 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 …]
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | perf-bench.txt | 1 perf-bench(1)
5 ----
6 perf-bench - General framework for benchmark suites
9 --------
14 -----------
18 --------------
19 -r::
20 --repeat=::
23 -f::
24 --format=::
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-bench.txt | 1 perf-bench(1)
5 ----
6 perf-bench - General framework for benchmark suites
9 --------
14 -----------
18 --------------
19 -r::
20 --repeat=::
23 -f::
24 --format=::
[all …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | numa.rst | 19 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 …]
|
| /kernel/linux/linux-6.6/Documentation/mm/ |
| D | numa.rst | 17 Each of the 'cells' may be viewed as an SMP [symmetric multi-processor] subset
18 of the system--although some components necessary for a stand-alone SMP system
20 connected together with some sort of system interconnect--e.g., a crossbar or
21 point-to-point link are common types of NUMA system interconnects. Both of
41 [cache misses] to be to "local" memory--memory on the same cell, if any--or
51 "closer" nodes--nodes that map to closer cells--will generally experience
63 the existing nodes--or the system memory for non-NUMA platforms--into multiple
66 application features on non-NUMA platforms, and as a sort of memory resource
68 [see Documentation/admin-guide/cgroup-v1/cpusets.rst]
71 subsystem, complete with its own free page lists, in-use page lists, usage
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/ |
| D | iommufd.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
20 I/O page tables for all IOMMUs, with room in the design to add non-generic
31 --------------------
35 - IOMMUFD_OBJ_IOAS, representing an I/O address space (IOAS), allowing map/unmap
41 - IOMMUFD_OBJ_DEVICE, representing a device that is bound to iommufd by an
44 - IOMMUFD_OBJ_HW_PAGETABLE, representing an actual hardware I/O page table
50 All user-visible objects are destroyed via the IOMMU_DESTROY uAPI.
52 The diagram below shows relationship between user-visible objects and kernel
68 | | IOAS |<--| |<------| | |
82 |------------>|iommu_domain| |struct device|
[all …]
|
| /kernel/linux/linux-6.6/tools/power/pm-graph/ |
| D | sleepgraph.8 | 3 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 …]
|
| /kernel/linux/linux-5.10/tools/power/pm-graph/ |
| D | sleepgraph.8 | 3 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 …]
|
| /kernel/linux/linux-5.10/fs/xfs/ |
| D | Kconfig | 1 # 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.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | interconnect.rst | 1 .. 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 …]
|
| D | dma-buf.rst | 4 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 …]
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | interrupts.rst | 5 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 …]
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/ |
| D | interrupts.rst | 5 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 …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. 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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. 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 …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | interconnect.rst | 1 .. 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 …]
|
| /kernel/linux/linux-6.6/fs/xfs/ |
| D | Kconfig | 1 # 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
51 bool "Support deprecated case-insensitive ascii (ascii-ci=1) format"
56 on systems that have been coerced into using ISO 8859-1, and it does
58 the locale settings in userspace, so it corrupts UTF-8 names.
66 beginning with "ascii-ci=". If the string "ascii-ci=1" is found, the
67 filesystem is a case-insensitive filesystem. If no such string is
74 To continue supporting case-insensitivity (ascii-ci=1), say Y.
85 higher level guarantee of consistency. The on-disk data format for
[all …]
|