Home
last modified time | relevance | path

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

12345678910>>...31

/Linux-v6.1/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,qcs404-wcss-pil"
13 "qcom,msm8916-mss-pil",
14 "qcom,msm8974-mss-pil"
15 "qcom,msm8996-mss-pil"
16 "qcom,msm8998-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 …]
Dti,k3-dsp-rproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-dsp-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 The TI K3 family of SoCs usually have one or more TI DSP Core sub-systems
14 that are used to offload some of the processor-intensive tasks or algorithms,
15 for achieving various system level goals.
17 These processor sub-systems usually contain additional sub-modules like
23 Each DSP Core sub-system is represented as a single DT node. Each node has a
[all …]
/Linux-v6.1/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 …]
/Linux-v6.1/include/linux/soc/mediatek/
Dmtk-cmdq.h1 /* SPDX-License-Identifier: GPL-2.0 */
11 #include <linux/mailbox/mtk-cmdq-mailbox.h>
31 * cmdq_dev_get_client_reg() - parse cmdq client reg from the device
46 * cmdq_mbox_create() - create CMDQ mailbox client and channel
55 * cmdq_mbox_destroy() - destroy CMDQ mailbox client and channel
61 * cmdq_pkt_create() - create a CMDQ packet
70 * cmdq_pkt_destroy() - destroy the CMDQ packet
76 * cmdq_pkt_write() - append write command to the CMDQ packet
78 * @subsys: the CMDQ sub system code
79 * @offset: register offset from CMDQ sub system
[all …]
/Linux-v6.1/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 …]
/Linux-v6.1/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 …]
/Linux-v6.1/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});
/Linux-v6.1/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 …]
/Linux-v6.1/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 …]
/Linux-v6.1/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 bool "K3 Ring accelerator Sub System"
87 tristate "TI PRU-ICSS Subsystem Platform drivers"
91 TI PRU-ICSS Subsystem platform specific support.
/Linux-v6.1/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.",
9 …s running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, AVX…
21 … running with power-delivery for license level 1. This includes high current AVX 256-bit instruct…
33 … running with power-delivery for license level 2 (introduced in Skylake Server microarchtecture). …
138 …e prefetches that were supplied by DRAM attached to this socket, unless in Sub NUMA Cluster(SNC) M…
149 …d by DRAM on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluste…
182 …d data reads that were supplied by DRAM attached to this socket, unless in Sub NUMA Cluster(SNC) M…
193 …nd data reads that were supplied by PMM attached to this socket, unless in Sub NUMA Cluster(SNC) M…
237 …d by DRAM on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluste…
248 …ed by PMM on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluste…
[all …]
/Linux-v6.1/fs/ubifs/
Dshrinker.c1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright (C) 2006-2008 Nokia Corporation.
16 * would add additional overhead to the file system fast paths. So the shrinker
19 * If the root of a TNC sub-tree is clean and old enough, then the children are
21 * dumps entire sub-trees.
23 * The age of znodes is just the time-stamp when they were last looked at.
27 * un-mounts, which is done by the 'ubifs_infos_lock' and 'c->umount_mutex'.
32 /* List of all UBIFS file-system instances */
49 * shrink_tnc - shrink TNC tree.
50 * @c: UBIFS file-system description object
[all …]
/Linux-v6.1/Documentation/usb/
Dgadget_serial.rst7 (updated 8-May-2008 for v2.3)
11 ----------------------
25 MA 02111-1307 USA.
35 -------------
48 no longer statically defined. Your Linux based system should mount
55 --------
57 side driver. It runs on a Linux system that has USB device side
58 hardware; for example, a PDA, an embedded Linux system, or a PC
65 --------------------------------------
66 | Host-Side CDC ACM USB Host |
[all …]
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-bus-nfit10 (RO) Serial number of the NVDIMM (non-volatile dual in-line
44 (RO) Handle (i.e., instance number) for the SMBIOS (system
54 (RO) The flags in the NFIT memory device sub-structure indicate
74 mapped directly into system physical address space and / or a
80 only expect one code per-dimm as they will ignore
113 http://pmem.io/documents/NVDIMM_DSM_Interface-V1.6.pdf
114 https://github.com/HewlettPackard/hpe-nvm/blob/master/Documentation/
132 (RO) Sub-system vendor id of the NVDIMM non-volatile memory
141 (RO) Sub-system revision id of the NVDIMM non-volatile memory subsystem
142 controller, assigned by the non-volatile memory subsystem
[all …]
/Linux-v6.1/Documentation/devicetree/bindings/pinctrl/
Dimg,pistachio-pinctrl.txt5 interrupt controller, and pinmux + pinconf device. The system ("east") pin
8 each. The GPIO banks are represented as sub-nodes of the pad controller node.
10 Please refer to pinctrl-bindings.txt, ../gpio/gpio.txt, and
11 ../interrupt-controller/interrupts.txt for generic information regarding
15 --------------------------------------------
16 - compatible: "img,pistachio-system-pinctrl".
17 - reg: Address range of the pinctrl registers.
19 Required properties for GPIO bank sub-nodes:
20 --------------------------------------------
21 - interrupts: Interrupt line for the GPIO bank.
[all …]
/Linux-v6.1/Documentation/userspace-api/media/
Dglossary.rst1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
33 A character device node in the file system used to control and
51 **Field-programmable Gate Array**
56 See https://en.wikipedia.org/wiki/Field-programmable_gate_array.
65 together make a larger user-facing functional peripheral. For
73 **Inter-Integrated Circuit**
75 A multi-master, multi-slave, packet switched, single-ended,
77 like sub-device hardware components.
79 See http://www.nxp.com/docs/en/user-guide/UM10204.pdf.
113 - :term:`CEC API`;
[all …]
/Linux-v6.1/Documentation/userspace-api/media/v4l/
Dopen.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
29 :ref:`V4L2 sub-devices <subdev>`.
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
34 are called **video-node-centric**.
36 Userspace can check if a V4L2 hardware peripheral is MC-centric by
38 :ref:`device_caps field <device-capabilities>`.
[all …]
Dvidioc-enumstd.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_ENUMSTD - VIDIOC_SUBDEV_ENUMSTD - Enumerate supported video standards
52 .. flat-table:: struct v4l2_standard
53 :header-rows: 0
54 :stub-columns: 0
57 * - __u32
58 - ``index``
59 - Number of the video standard, set by the application.
60 * - :ref:`v4l2_std_id <v4l2-std-id>`
61 - ``id``
[all …]
/Linux-v6.1/Documentation/filesystems/
Dzonefs.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ZoneFS - Zone filesystem for Zoned block devices
10 zonefs is a very simple file system exposing each zone of a zoned block device
11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
22 example of this approach is the implementation of LSM (log-structured merge)
25 system rather than as a range of sectors of the entire disk. The introduction
31 -------------------
62 by sub-directories. This file structure is built entirely using zone information
63 provided by the device and so does not require any complex on-disk metadata
[all …]
/Linux-v6.1/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/
Dbase.c44 const int slot = pt->base >> pt->ptp->shift; in nvkm_mmu_ptp_put()
45 struct nvkm_mmu_ptp *ptp = pt->ptp; in nvkm_mmu_ptp_put()
50 if (!ptp->free) in nvkm_mmu_ptp_put()
51 list_add(&ptp->head, &mmu->ptp.list); in nvkm_mmu_ptp_put()
52 ptp->free |= BIT(slot); in nvkm_mmu_ptp_put()
54 /* If there's no more sub-allocations, destroy PTP. */ in nvkm_mmu_ptp_put()
55 if (ptp->free == ptp->mask) { in nvkm_mmu_ptp_put()
56 nvkm_mmu_ptc_put(mmu, force, &ptp->pt); in nvkm_mmu_ptp_put()
57 list_del(&ptp->head); in nvkm_mmu_ptp_put()
74 ptp = list_first_entry_or_null(&mmu->ptp.list, typeof(*ptp), head); in nvkm_mmu_ptp_get()
[all …]
/Linux-v6.1/Documentation/arm/keystone/
Dknav-qmss.rst9 The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of
10 the main hardware sub system which forms the backbone of the Keystone
11 multi-core Navigator. QMSS consist of queue managers, packed-data structure
15 management of the packet queues. Packets are queued/de-queued by writing or
29 Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
40 git://git.ti.com/keystone-rtos/qmss-lld.git
43 channels. This firmware is available under ti-keystone folder of
46 git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
49 ubifs file system and provide a sym link to k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin
50 in the file system and boot up the kernel. User would see
[all …]

12345678910>>...31