Searched +full:sub +full:- +full:modules (Results 1 – 25 of 343) sorted by relevance
12345678910>>...14
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | qcom_camss.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ------------
25 ----------------------------------
30 - 2 / 3 CSIPHY modules. They handle the Physical layer of the CSI2 receivers.
32 - 2 / 4 CSID (CSI Decoder) modules. They handle the Protocol and Application
36 - ISPIF (ISP Interface) module. Handles the routing of the data streams from
38 - 1 / 2 VFE (Video Front End) module(s). Contain a pipeline of image processing
48 -----------------------
52 - Input from camera sensor via CSIPHY;
53 - Generation of test input data by the TG in CSID;
[all …]
|
| D | fimc.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/exynos4-is directory.
20 --------------
22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210
25 ------------------
27 - camera parallel interface capture (ITU-R.BT601/565);
28 - camera serial interface capture (MIPI-CSI2);
29 - memory-to-memory processing (color space conversion, scaling, mirror
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
[all …]
|
| D | building.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 distribution-specific source file or via the Kernel's main git tree\ [1]_.
12 - you're a braveheart and want to experiment with new stuff;
13 - if you want to report a bug;
14 - if you're developing new patches
23 https://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
50 Device Drivers --->
51 <M> Remote Controller support --->
54 [*] HDMI CEC drivers --->
55 <*> Multimedia support --->
[all …]
|
| /kernel/linux/linux-4.19/Documentation/media/v4l-drivers/ |
| D | qcom_camss.rst | 7 ------------
23 ----------------------------------
28 - 2 / 3 CSIPHY modules. They handle the Physical layer of the CSI2 receivers.
30 - 2 / 4 CSID (CSI Decoder) modules. They handle the Protocol and Application
34 - ISPIF (ISP Interface) module. Handles the routing of the data streams from
36 - 1 / 2 VFE (Video Front End) module(s). Contain a pipeline of image processing
46 -----------------------
50 - Input from camera sensor via CSIPHY;
51 - Generation of test input data by the TG in CSID;
52 - RDI interface of VFE
[all …]
|
| D | fimc.rst | 6 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
15 drivers/media/platform/exynos4-is directory.
18 --------------
20 S5PC100 (mem-to-mem only), S5PV210, EXYNOS4210
23 ------------------
25 - camera parallel interface capture (ITU-R.BT601/565);
26 - camera serial interface capture (MIPI-CSI2);
27 - memory-to-memory processing (color space conversion, scaling, mirror
29 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
30 instance to any parallel video input or any MIPI-CSI front-end);
[all …]
|
| /kernel/linux/linux-5.10/scripts/ |
| D | export_report.pl | 2 # SPDX-License-Identifier: GPL-2.0-only
7 # Usage: export_report.pl -k Module.symvers [-o report_file ] -f *.mod.c
14 sub numerically {
20 sub alphabetically {
26 sub print_depends_on {
30 my $list = $href->{$mod};
34 printf("\t\t%-25s\n", $symbol);
42 sub usage {
43 print "Usage: @_ -h -k Module.symvers [ -o outputfile ] \n",
44 "\t-f: treat all the non-option argument as .mod.c files. ",
[all …]
|
| /kernel/linux/linux-4.19/drivers/media/dvb-frontends/ |
| D | tc90522.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
9 * The demod has 4 input (2xISDB-T and 2xISDB-S),
10 * and provides independent sub modules for each input.
11 * As the sub modules work in parallel and have the separate i2c addr's,
12 * this driver treats each sub module as one demod device.
|
| /kernel/linux/linux-5.10/drivers/media/dvb-frontends/ |
| D | tc90522.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
9 * The demod has 4 input (2xISDB-T and 2xISDB-S),
10 * and provides independent sub modules for each input.
11 * As the sub modules work in parallel and have the separate i2c addr's,
12 * this driver treats each sub module as one demod device.
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/ |
| D | keystone-netcp.txt | 6 switch sub-module to send and receive packets. NetCP also includes a packet
13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates
16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
17 sub-modules exist as a loadable kernel module which plug in to the netcp core.
18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is
19 mandatory to have the ethernet switch sub-module for the ethernet interface to
20 be operational. Any other sub-module like the PA is optional.
24 -----------------------------
26 -----------------------------
28 |-> NetCP Devices -> |
[all …]
|
| /kernel/linux/linux-4.19/scripts/kconfig/ |
| D | streamline_config.pl | 3 # Copyright 2005-2009 - Steven Rostedt
12 # that turns on way too many modules than you need, and
13 # you only want the modules you use, then this program
16 # It gives you the ability to turn off all the modules that are
25 # 4. Have all your devices that you need modules for connected and
26 # operational (make sure that their corresponding modules are loaded)
33 # Now your kernel is ready to be built with only the modules that
38 # cd /usr/src/linux-2.6.10
39 # cp /boot/config-2.6.10-1-686-smp .config
54 sub dprint {
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | keystone-netcp.txt | 6 switch sub-module to send and receive packets. NetCP also includes a packet
13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates
16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
17 sub-modules exist as a loadable kernel module which plug in to the netcp core.
18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is
19 mandatory to have the ethernet switch sub-module for the ethernet interface to
20 be operational. Any other sub-module like the PA is optional.
24 -----------------------------
26 -----------------------------
28 |-> NetCP Devices -> |
[all …]
|
| /kernel/linux/linux-5.10/scripts/kconfig/ |
| D | streamline_config.pl | 2 # SPDX-License-Identifier: GPL-2.0
4 # Copyright 2005-2009 - Steven Rostedt
12 # that turns on way too many modules than you need, and
13 # you only want the modules you use, then this program
16 # It gives you the ability to turn off all the modules that are
25 # 4. Have all your devices that you need modules for connected and
26 # operational (make sure that their corresponding modules are loaded)
33 # Now your kernel is ready to be built with only the modules that
38 # cd /usr/src/linux-2.6.10
39 # cp /boot/config-2.6.10-1-686-smp .config
[all …]
|
| /kernel/linux/linux-4.19/scripts/ |
| D | export_report.pl | 7 # Usage: export_report.pl -k Module.symvers [-o report_file ] -f *.mod.c
14 sub numerically {
20 sub alphabetically {
26 sub print_depends_on {
30 my $list = $href->{$mod};
34 printf("\t\t%-25s\n", $symbol);
42 sub usage {
43 print "Usage: @_ -h -k Module.symvers [ -o outputfile ] \n",
44 "\t-f: treat all the non-option argument as .mod.c files. ",
46 "\t-h: print detailed help\n",
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/amd/display/ |
| D | Makefile | 23 # Makefile for the DAL (Display Abstract Layer), which is a sub-component
29 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/dc/inc/
30 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/dc/inc/hw
31 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/dc/clk_mgr
32 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/inc
33 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/freesync
34 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/color
35 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/info_packet
36 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/power
37 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/dmub/inc
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/Documentation/ |
| D | perf-script-perl.txt | 1 perf-script-perl(1)
5 ----
6 perf-script-perl - Process trace data with a Perl script
9 --------
11 'perf script' [-s [Perl]:script[.pl] ]
14 -----------
17 built-in Perl interpreter. It reads and processes the input file and
22 ---------------
25 -g perl' in the same directory as an existing perf.data trace file.
31 ~/libexec/perf-core/scripts/perl for typical examples showing how to
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-script-perl.txt | 1 perf-script-perl(1)
5 ----
6 perf-script-perl - Process trace data with a Perl script
9 --------
11 'perf script' [-s [Perl]:script[.pl] ]
14 -----------
17 built-in Perl interpreter. It reads and processes the input file and
22 ---------------
25 -g perl' in the same directory as an existing perf.data trace file.
31 ~/libexec/perf-core/scripts/perl for typical examples showing how to
[all …]
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/amd/display/ |
| D | Makefile | 23 # Makefile for the DAL (Display Abstract Layer), which is a sub-component
29 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/dc/inc/
30 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/dc/inc/hw
31 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/inc
32 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/freesync
33 subdir-ccflags-y += -I$(FULL_AMD_DISPLAY_PATH)/modules/color
36 subdir-ccflags-y += -DBUILD_FEATURE_TIMING_SYNC=0
38 DAL_LIBS = amdgpu_dm dc modules/freesync modules/color
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | open.rst | 1 .. 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/ti/ |
| D | ti,pruss.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 TI Programmable Real-Time Unit and Industrial Communication Subsystem
11 - Suman Anna <s-anna@ti.com>
15 The Programmable Real-Time Unit and Industrial Communication Subsystem
16 (PRU-ICSS a.k.a. PRUSS) is present on various TI SoCs such as AM335x, AM437x,
17 Keystone 66AK2G, OMAP-L138/DA850 etc. A PRUSS consists of dual 32-bit RISC
18 cores (Programmable Real-Time Units, or PRUs), shared RAM, data and
19 instruction RAMs, some internal peripheral modules to facilitate industrial
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,omap-remoteproc.yaml | 1 # 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
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
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
[all …]
|
| /kernel/linux/linux-5.10/ |
| D | Makefile | 1 # SPDX-License-Identifier: GPL-2.0
24 # Most importantly: sub-Makefiles should only ever modify files in
27 # unavoidable when linking the built-in.a targets which finally
28 # turn into vmlinux), we will call a sub make in that other dir, and
39 # Do not use make's built-in rules and variables
40 # (this increases performance and avoids hard-to-debug behaviour)
41 MAKEFLAGS += -rR
53 # ---------------------------------------------------------------------------
60 # cmd_cc_o_c = $(CC) $(c_flags) -c -o $@ $<
67 # A simple variant is to prefix commands with $(Q) - that's useful
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/ |
| D | perf-with-kcore.sh | 2 # SPDX-License-Identifier: GPL-2.0-only
3 # perf-with-kcore: use perf with a copy of kcore
7 set -e
11 …echo "Usage: perf-with-kcore <perf sub-command> <perf.data directory> [<sub-command options> [ -- …
12 echo " <perf sub-command> can be record, script, report or inject" >&2
13 echo " or: perf-with-kcore fix_buildid_cache_permissions" >&2
19 if [ -n "$PERF" ] ; then
23 if [ -z "$PERF" ] ; then
27 if [ ! -x "$PERF" ] ; then
39 if [ $EUID -eq 0 ] ; then
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/ |
| D | gpio-eic-sprd.txt | 6 controller contains 4 sub-modules: EIC-debounce, EIC-latch, EIC-async and
7 EIC-sync. But the PMIC EIC controller contains only one EIC-debounce sub-
10 The EIC-debounce sub-module provides up to 8 source input signal
12 stable status (millisecond resolution) and a single-trigger mechanism
13 is introduced into this sub-module to enhance the input event detection
14 reliability. In addition, this sub-module's clock can be shut off
19 The EIC-latch sub-module is used to latch some special power down signals
20 and generate interrupts, since the EIC-latch does not depend on the APB
23 The EIC-async sub-module uses a 32kHz clock to capture the short signals
26 The EIC-sync is similar with GPIO's input function, which is a synchronized
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/gpio/ |
| D | gpio-eic-sprd.txt | 6 controller contains 4 sub-modules: EIC-debounce, EIC-latch, EIC-async and
7 EIC-sync. But the PMIC EIC controller contains only one EIC-debounce sub-
10 The EIC-debounce sub-module provides up to 8 source input signal
12 stable status (millisecond resolution) and a single-trigger mechanism
13 is introduced into this sub-module to enhance the input event detection
14 reliability. In addition, this sub-module's clock can be shut off
19 The EIC-latch sub-module is used to latch some special power down signals
20 and generate interrupts, since the EIC-latch does not depend on the APB
23 The EIC-async sub-module uses a 32kHz clock to capture the short signals
26 The EIC-sync is similar with GPIO's input function, which is a synchronized
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,davinci-rproc.txt | 4 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
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'.
30 the parent node's '#address-cells' and '#size-cells' values.
[all …]
|
12345678910>>...14