Home
last modified time | relevance | path

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

12345678910>>...12

/openbmc/openbmc/meta-security/recipes-perl/perl/files/
H A Dlibwhisker2.patch8 Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com>
9 ---
10 Upstream-Status: Pending
12 Makefile.pl | 12 +++++++-----
13 1 file changed, 7 insertions(+), 5 deletions(-)
15 diff --git a/Makefile.pl b/Makefile.pl
17 --- a/Makefile.pl
19 @@ -131,6 +131,8 @@ foreach (keys %MODULES){
28 @@ -171,7 +173,7 @@ sub command_install_pod {
29 command_build() if(!-e $TARGET);
[all …]
/openbmc/linux/Documentation/admin-guide/media/
H A Dqcom_camss.rst1 .. 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 …]
H A Dfimc.rst1 .. SPDX-License-Identifier: GPL-2.0
8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
17 drivers/media/platform/samsung/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 …]
H A Dbuilding.rst1 .. 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 …]
/openbmc/linux/scripts/
H A Dexport_report.pl2 # 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 …]
/openbmc/linux/drivers/media/dvb-frontends/
H A Dtc90522.h1 /* 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.
/openbmc/linux/Documentation/devicetree/bindings/net/
H A Dkeystone-netcp.txt6 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 …]
/openbmc/u-boot/scripts/kconfig/
H A Dstreamline_config.pl3 # 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 …]
/openbmc/linux/scripts/kconfig/
H A Dstreamline_config.pl2 # 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 …]
/openbmc/qemu/storage-daemon/qapi/
H A Dqapi-schema.json1 # -*- Mode: Python -*-
4 # Note that modules are shared with the QEMU main schema under the assumption
6 # modules, no code is generated here, but we reuse the code files generated
11 # modules are only generated if an array of the respective type is already used
18 # Documentation generated with qapi-gen.py is in source order, with
19 # included sub-schemas inserted at the first include directive
21 # stable order, it's best to include each sub-schema just once, or
32 { 'include': '../../qapi/block-core.json' }
33 { 'include': '../../qapi/block-export.json' }
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/opencv/opencv/
H A D0008-Do-not-embed-build-directory-in-binaries.patch7 https://salsa.debian.org/science-team/opencv/-/raw/master/debian/patches/0008-Do-not-embed-build-di…
8 Upstream-Status: Backport
9 Signed-off-by: Chee Yang Lee <chee.yang.lee@intel.com>
10 ---
11 modules/core/CMakeLists.txt | 10 ------
12 modules/core/include/opencv2/core/private.hpp | 4 +--
13 modules/core/include/opencv2/core/utility.hpp | 4 +--
14 modules/core/src/utils/datafile.cpp | 48 +--------------------------
15 4 files changed, 5 insertions(+), 61 deletions(-)
17 diff --git a/modules/core/CMakeLists.txt b/modules/core/CMakeLists.txt
[all …]
/openbmc/linux/drivers/gpu/drm/amd/display/
H A DMakefile23 # 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 …]
/openbmc/linux/tools/perf/Documentation/
H A Dperf-script-perl.txt1 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 …]
/openbmc/openbmc-test-automation/pldm/
H A Dtest_pldm_bios.robot26 # "Response": "2020-11-07 07:10:10"
34 # Date format example: 2022-10-12 16:31:17
36 # Example : ['2022-10-12', '16:31:17']
54 # 2020-11-25 07:34:30
57 ${upgrade_date}= Evaluate re.sub(r'-* *:*', "", '${date}') modules=re
60 ${upgrade_time}= Evaluate re.sub(r'-* *:*', "", '${time}') modules=re
98 # pldmtool bios GetBIOSAttributeCurrentValueByHandle -a pvm_fw_boot_side
106 ${cur_attr}= Pldmtool bios GetBIOSAttributeCurrentValueByHandle -a ${i}
118 ${pldm_output}= Pldmtool bios GetBIOSTable --type AttributeTable
130 ${current_date_time}= Evaluate re.sub(r'-* *:*', "", '${result}') modules=re
[all …]
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A 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 …]
/openbmc/linux/Documentation/devicetree/bindings/remoteproc/
H A 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
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 …]
H A 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
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 …]
/openbmc/qemu/hw/misc/
H A Dmchp_pfsoc_ioscb.c33 * named as "System Port 0 (AXI-D0)".
43 * There are many sub-modules in the IOSCB module.
47 * The following are sub-modules offsets that are of concern.
92 /* All PLL modules in IOSCB have the same register layout */
188 qemu_irq_raise(s->irq); in mchp_pfsoc_ctrl_write()
209 memory_region_init(&s->container, OBJECT(s), in mchp_pfsoc_ioscb_realize()
211 sysbus_init_mmio(sbd, &s->container); in mchp_pfsoc_ioscb_realize()
213 /* add subregions for all sub-modules in IOSCB */ in mchp_pfsoc_ioscb_realize()
215 memory_region_init_io(&s->lane01, OBJECT(s), &mchp_pfsoc_dummy_ops, s, in mchp_pfsoc_ioscb_realize()
217 memory_region_add_subregion(&s->container, IOSCB_LANE01_BASE, &s->lane01); in mchp_pfsoc_ioscb_realize()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/soc/ti/
H A Dti,pruss.yaml1 # 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 …]
/openbmc/phosphor-mrw-tools/
H A DInventory.pm14 #Chips that are modeled as modules (card-chip together)
22 sub getInventory
45 sub findItems
49 for my $target (sort keys %{$targetObj->getAllTargets()}) {
53 if (!$targetObj->isBadAttribute($target, "TYPE")) {
54 $type = $targetObj->getAttribute($target, "TYPE");
57 if (!$targetObj->isBadAttribute($target, "RU_TYPE")) {
58 $ruType = $targetObj->getAttribute($target, "RU_TYPE");
73 #is a card-chip instance that plugs into a connector on the
78 #For example, we'll already have .../module-0/proc-0 so we don't
[all …]
/openbmc/linux/Documentation/devicetree/bindings/gpio/
H A Dsprd,gpio-eic.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/gpio/sprd,gpio-eic.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>
19 controller contains 4 sub-modules, i.e. EIC-debounce, EIC-latch, EIC-async and
20 EIC-sync. But the PMIC EIC controller contains only one EIC-debounce sub-
23 The EIC-debounce sub-module provides up to 8 source input signal
[all …]
/openbmc/linux/arch/arm/include/asm/
H A Dinsn.h1 /* SPDX-License-Identifier: GPL-2.0 */
9 * appropriate relocations. The combined sequence has a range of -/+ 256 MiB,
10 * which should be sufficient for the core kernel as well as modules loaded
18 "10: sub " #reg ", pc, #8 \n\t" \
19 "11: sub " #reg ", " #reg ", #4 \n\t" \
/openbmc/linux/
H A DMakefile1 # SPDX-License-Identifier: GPL-2.0
28 # Most importantly: sub-Makefiles should only ever modify files in
31 # unavoidable when linking the built-in.a targets which finally
32 # turn into vmlinux), we will call a sub make in that other dir, and
41 this-makefile := $(lastword $(MAKEFILE_LIST))
42 export abs_srctree := $(realpath $(dir $(this-makefile)))
47 # Do not use make's built-i
1463 modules: vmlinux global() target
1466 modules: modules_prepare global() target
1812 modules modules_install: __external_modules_error global() target
1852 modules: modpost global() target
1863 modules: global() target
[all...]
/openbmc/linux/Documentation/devicetree/bindings/arm/freescale/
H A Dfsl,vf610-mscm-cpucfg.txt1 Freescale Vybrid Miscellaneous System Control - CPU Configuration
3 The MSCM IP contains multiple sub modules, this binding describes the first
7 - compatible: "fsl,vf610-mscm-cpucfg", "syscon"
8 - reg: the register range of the MSCM CPU configuration registers
12 compatible = "fsl,vf610-mscm-cpucfg", "syscon";
/openbmc/openbmc/poky/meta/classes/
H A Dgo-vendor.bbclass7 # When importing Go modules, Go downloads the imported modules using
9 # the yocto build concept of fetching every source ahead of build-time
13 # downloaded during the fetch-phase and unpacked into the modules 'vendor'
17 inherit go-mod
71 # Nothing to do except re-establish link to actual vendor folder
78 modules = {}
106 if not (repo, version) in modules:
107 modules[(repo, version)] = {
113 for module_key, module in modules.items():
131 # https://go.dev/ref/mod#modules-overview
[all …]

12345678910>>...12