Home
last modified time | relevance | path

Searched +full:sub +full:- +full:system (Results 1 – 25 of 1019) sorted by relevance

12345678910>>...41

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/
Dti,omap-remoteproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
15 other hardware accelerators, for achieving various system level goals.
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
[all …]
Dqcom,q6v5.txt6 - compatible:
10 "qcom,q6v5-pil",
11 "qcom,ipq8074-wcss-pil"
12 "qcom,msm8916-mss-pil",
13 "qcom,msm8974-mss-pil"
14 "qcom,msm8996-mss-pil"
15 "qcom,msm8998-mss-pil"
16 "qcom,sc7180-mss-pil"
17 "qcom,sdm845-mss-pil"
19 - reg:
[all …]
Dti,davinci-rproc.txt4 Binding status: Unstable - Subject to changes for DT representation of clocks
7 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
8 is used to offload some of the processor-intensive tasks or algorithms, for
9 achieving various system level goals.
11 The processor cores in the sub-system usually contain additional sub-modules
18 Each DSP Core sub-system is represented as a single DT node.
21 --------------------
24 - compatible: Should be one of the following,
25 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs
27 - reg: Should contain an entry for each value in 'reg-names'.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/remoteproc/
Dti,omap-remoteproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The OMAP family of SoCs usually have one or more slave processor sub-systems
14 that are used to offload some of the processor-intensive tasks, or to manage
15 other hardware accelerators, for achieving various system level goals.
17 The processor cores in the sub-system are usually behind an IOMMU, and may
18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2
[all …]
Dti,davinci-rproc.txt4 Binding status: Unstable - Subject to changes for DT representation of clocks
7 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
8 is used to offload some of the processor-intensive tasks or algorithms, for
9 achieving various system level goals.
11 The processor cores in the sub-system usually contain additional sub-modules
18 Each DSP Core sub-system is represented as a single DT node.
21 --------------------
24 - compatible: Should be one of the following,
25 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs
27 - reg: Should contain an entry for each value in 'reg-names'.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mailbox/
Dmtk-gce.txt9 mailbox.txt for generic information about mailbox device-tree bindings.
12 - compatible: can be "mediatek,mt8173-gce", "mediatek,mt8183-gce" or
13 "mediatek,mt6779-gce".
14 - reg: Address range of the GCE unit
15 - interrupts: The interrupt signal from the GCE block
16 - clock: Clocks according to the common clock binding
17 - clock-names: Must be "gce" to stand for GCE clock
18 - #mbox-cells: Should be 2.
25 - mboxes: Client use mailbox to communicate with GCE, it should have this
28 - mediatek,gce-client-reg: Specify the sub-system id which is corresponding
[all …]
/kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/hive_isp_css_include/device_access/
Ddevice_access.h1 /* SPDX-License-Identifier: GPL-2.0 */
4 Copyright (c) 2010 - 2015, Intel Corporation.
21 * Define the public interface for physical system
26 * The address representation is private to the system
29 * The system global address can differ by an offset;
40 * User provided file that defines the system address types:
41 * - hrt_address a type that can hold the (sub)system address range
45 * We cannot assume that the global system address size is the size of
46 * a pointer because a (say) 64-bit host can be simulated in a 32-bit
56 /*! Set the (sub)system base address
[all …]
/kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/hive_isp_css_include/device_access/
Ddevice_access.h1 /* SPDX-License-Identifier: GPL-2.0 */
4 Copyright (c) 2010 - 2015, Intel Corporation.
21 * Define the public interface for physical system
26 * The address representation is private to the system
29 * The system global address can differ by an offset;
40 * User provided file that defines the system address types:
41 * - hrt_address a type that can hold the (sub)system address range
45 * We cannot assume that the global system address size is the size of
46 * a pointer because a (say) 64-bit host can be simulated in a 32-bit
56 /*! Set the (sub)system base address
[all …]
/kernel/linux/linux-6.6/Documentation/admin-guide/perf/
Dalibaba_pmu.rst2 Alibaba's T-Head SoC Uncore Performance Monitoring Unit (PMU)
5 The Yitian 710, custom-built by Alibaba Group's chip development business,
6 T-Head, implements uncore PMU for performance and functional debugging to
7 facilitate system maintenance.
9 DDR Sub-System Driveway (DRW) PMU Driver
13 is independent of others to service system memory requests. And one DDR5
14 channel is split into two independent sub-channels. The DDR Sub-System Driveway
15 implements separate PMUs for each sub-channel to monitor various performance
20 sub-channels of the same channel in die 0. And the PMU device of die 1 is
23 Each sub-channel has 36 PMU counters in total, which is classified into
[all …]
/kernel/linux/linux-5.10/include/linux/soc/mediatek/
Dmtk-cmdq.h1 /* SPDX-License-Identifier: GPL-2.0 */
11 #include <linux/mailbox/mtk-cmdq-mailbox.h>
36 * cmdq_dev_get_client_reg() - parse cmdq client reg from the device
51 * cmdq_mbox_create() - create CMDQ mailbox client and channel
63 * cmdq_mbox_destroy() - destroy CMDQ mailbox client and channel
69 * cmdq_pkt_create() - create a CMDQ packet
78 * cmdq_pkt_destroy() - destroy the CMDQ packet
84 * cmdq_pkt_write() - append write command to the CMDQ packet
86 * @subsys: the CMDQ sub system code
87 * @offset: register offset from CMDQ sub system
[all …]
/kernel/linux/linux-6.6/include/linux/soc/mediatek/
Dmtk-cmdq.h1 /* SPDX-License-Identifier: GPL-2.0 */
11 #include <linux/mailbox/mtk-cmdq-mailbox.h>
33 * cmdq_dev_get_client_reg() - parse cmdq client reg from the device
48 * cmdq_mbox_create() - create CMDQ mailbox client and channel
57 * cmdq_mbox_destroy() - destroy CMDQ mailbox client and channel
63 * cmdq_pkt_create() - create a CMDQ packet
72 * cmdq_pkt_destroy() - destroy the CMDQ packet
78 * cmdq_pkt_write() - append write command to the CMDQ packet
80 * @subsys: the CMDQ sub system code
81 * @offset: register offset from CMDQ sub system
[all …]
/kernel/linux/linux-5.10/tools/perf/scripts/perl/
Dfailed-syscalls.pl1 # failed system call counts
5 # Displays system-wide failed system call totals
8 use lib "$ENV{'PERF_EXEC_PATH'}/scripts/perl/Perf-Trace-Util/lib";
9 use lib "./Perf-Trace-Util/lib";
18 sub raw_syscalls::sys_exit
29 sub syscalls::sys_exit
34 sub trace_end
38 printf("%-20s %10s\n", "comm", "# errors");
39 printf("%-20s %6s %10s\n", "--------------------", "----------");
45 printf("%-20s %10s\n", $comm, $failed_syscalls{$comm});
/kernel/linux/linux-6.6/tools/perf/scripts/perl/
Dfailed-syscalls.pl1 # failed system call counts
5 # Displays system-wide failed system call totals
8 use lib "$ENV{'PERF_EXEC_PATH'}/scripts/perl/Perf-Trace-Util/lib";
9 use lib "./Perf-Trace-Util/lib";
18 sub raw_syscalls::sys_exit
29 sub syscalls::sys_exit
34 sub trace_end
38 printf("%-20s %10s\n", "comm", "# errors");
39 printf("%-20s %6s %10s\n", "--------------------", "----------");
45 printf("%-20s %10s\n", $comm, $failed_syscalls{$comm});
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/
Dpalmas-pmic.txt11 - compatible : Should be from the list
12 ti,twl6035-pmic
13 ti,twl6036-pmic
14 ti,twl6037-pmic
15 ti,tps65913-pmic
16 ti,tps65914-pmic
17 ti,tps65917-pmic
18 ti,tps659038-pmic
20 ti,palmas-pmic
21 - interrupts : The interrupt number and the type which can be looked up here:
[all …]
Dmax8907.txt4 - compatible: "maxim,max8907"
5 - reg: I2C slave address
6 - interrupts: The interrupt output of the controller
7 - mbatt-supply: The input supply for MBATT, BBAT, SDBY, VRTC.
8 - in-v1-supply: The input supply for SD1.
9 - in-v2-supply: The input supply for SD2.
10 - in-v3-supply: The input supply for SD3.
11 - in1-supply: The input supply for LDO1.
13 - in20-supply: The input supply for LDO20.
14 - regulators: A node that houses a sub-node for each regulator within the
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/
Dpalmas-pmic.txt11 - compatible : Should be from the list
12 ti,twl6035-pmic
13 ti,twl6036-pmic
14 ti,twl6037-pmic
15 ti,tps65913-pmic
16 ti,tps65914-pmic
17 ti,tps65917-pmic
18 ti,tps659038-pmic
20 ti,palmas-pmic
21 - interrupts : The interrupt number and the type which can be looked up here:
[all …]
Dmax8907.txt4 - compatible: "maxim,max8907"
5 - reg: I2C slave address
6 - interrupts: The interrupt output of the controller
7 - mbatt-supply: The input supply for MBATT, BBAT, SDBY, VRTC.
8 - in-v1-supply: The input supply for SD1.
9 - in-v2-supply: The input supply for SD2.
10 - in-v3-supply: The input supply for SD3.
11 - in1-supply: The input supply for LDO1.
13 - in20-supply: The input supply for LDO20.
14 - regulators: A node that houses a sub-node for each regulator within the
[all …]
/kernel/linux/linux-5.10/scripts/
Dget_dvb_firmware2 # SPDX-License-Identifier: GPL-2.0-or-later
46 # ---------------------------------------------------------------
47 # Firmware-specific extraction subroutines
49 sub sp8870 {
53 my $outfile = "dvb-fe-sp8870.fw";
66 sub sp887x {
71 my $outfile = "dvb-fe-sp887x.fw";
86 sub tda10045 {
90 my $outfile = "dvb-fe-tda10045.fw";
104 sub tda10046 {
[all …]
Dleaking_addresses.pl2 # SPDX-License-Identifier: GPL-2.0-only
7 # - Scans dmesg output.
8 # - Walks directory tree and parses each file (for each directory in @DIRS).
10 # Use --debug to output path before parsing, this is useful to find files that
14 # When the system is idle it is likely that most files under /proc/PID will be
41 # Kernel addresses vary by architecture. We can only auto-detect the following
42 # architectures (using `uname -m`). (flag --32-bit overrides auto-detection.)
55 my $opt_32bit = 0; # Scan 32-bit kernel.
56 my $page_offset_32bit = 0; # Page offset for 32-bit kernel.
61 '/proc/device-tree',
[all …]
/kernel/linux/linux-6.6/scripts/
Dget_dvb_firmware2 # SPDX-License-Identifier: GPL-2.0-or-later
46 # ---------------------------------------------------------------
47 # Firmware-specific extraction subroutines
49 sub sp8870 {
53 my $outfile = "dvb-fe-sp8870.fw";
66 sub sp887x {
71 my $outfile = "dvb-fe-sp887x.fw";
86 sub tda10045 {
90 my $outfile = "dvb-fe-tda10045.fw";
104 sub tda10046 {
[all …]
Dleaking_addresses.pl2 # SPDX-License-Identifier: GPL-2.0-only
7 # - Scans dmesg output.
8 # - Walks directory tree and parses each file (for each directory in @DIRS).
10 # Use --debug to output path before parsing, this is useful to find files that
14 # When the system is idle it is likely that most files under /proc/PID will be
41 # Kernel addresses vary by architecture. We can only auto-detect the following
42 # architectures (using `uname -m`). (flag --32-bit overrides auto-detection.)
55 my $opt_32bit = 0; # Scan 32-bit kernel.
56 my $page_offset_32bit = 0; # Page offset for 32-bit kernel.
61 '/proc/device-tree',
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dmax77620.txt4 -------------------
5 - compatible: Must be one of
9 - reg: I2C device address.
12 -------------------
13 - interrupts: The interrupt on the parent the controller is
15 - interrupt-controller: Marks the device node as an interrupt controller.
16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells
17 variant of <../interrupt-controller/interrupts.txt>
19 are defined at dt-bindings/mfd/max77620.h.
21 - system-power-controller: Indicates that this PMIC is controlling the
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/
Dmax77620.txt4 -------------------
5 - compatible: Must be one of
9 - reg: I2C device address.
12 -------------------
13 - interrupts: The interrupt on the parent the controller is
15 - interrupt-controller: Marks the device node as an interrupt controller.
16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells
17 variant of <../interrupt-controller/interrupts.txt>
19 are defined at dt-bindings/mfd/max77620.h.
21 - system-power-controller: Indicates that this PMIC is controlling the
[all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelakex/
Dother.json3 … where the core was running in a manner where Turbo may be clipped to the Non-AVX turbo schedule.",
6 …s running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, AVX…
14 … running with power-delivery for license level 1. This includes high current AVX 256-bit instruct…
22 … running with power-delivery for license level 2 (introduced in Skylake Server microarchtecture). …
101 …e prefetches that were supplied by DRAM attached to this socket, unless in Sub NUMA Cluster(SNC) M…
110 …d by DRAM on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluste…
137 …d data reads that were supplied by DRAM attached to this socket, unless in Sub NUMA Cluster(SNC) M…
146 …nd data reads that were supplied by PMM attached to this socket, unless in Sub NUMA Cluster(SNC) M…
182 …d by DRAM on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluste…
191 …ed by PMM on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluste…
[all …]
/kernel/linux/linux-6.6/drivers/soc/ti/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
12 tristate "Keystone Queue Manager Sub System"
18 Packets are queued/de-queued by writing/reading descriptor address
29 Queue Manager Sub System.
40 c-states on AM335x. Also required for rtc and ddr in self-refresh low
44 tristate "TI AMx3 Wkup-M3 IPC Driver"
66 tristate "K3 Ring accelerator Sub System"
87 tristate "TI PRU-ICSS Subsystem Platform drivers"
91 TI PRU-ICSS Subsystem platform specific support.

12345678910>>...41