| /openbmc/linux/drivers/media/platform/mediatek/mdp/ |
| H A D | mtk_mdp_core.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copyright (c) 2015-2016 MediaTek Inc.
12 #include <media/v4l2-ctrls.h>
13 #include <media/v4l2-device.h>
14 #include <media/v4l2-mem2mem.h>
15 #include <media/videobuf2-core.h>
16 #include <media/videobuf2-dma-contig.h>
22 #define MTK_MDP_MODULE_NAME "mtk-mdp"
34 * struct mtk_mdp_pix_align - alignment of image
48 * struct mtk_mdp_fmt - the driver's internal color format data
[all …]
|
| /openbmc/linux/drivers/remoteproc/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 bool "Support for Remote Processor subsystem"
33 processor framework.
44 processor framework.
54 This can be either built-in or a loadable module.
62 Say y here to support Mediatek's System Companion Processor (SCP) via
63 the remote processor framework.
75 and DSP on OMAP4) via the remote processor framework.
80 use-cases to run on your platform (multimedia codecs are
102 Say y here to support Wakeup M3 remote processor on TI AM33xx
[all …]
|
| H A D | remoteproc_elf_loader.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Remote Processor Framework ELF loader
8 * Ohad Ben-Cohen <ohad@wizery.com>
12 * Suman Anna <s-anna@ti.com>
29 * rproc_elf_sanity_check() - Sanity Check for ELF32/ELF64 firmware image
30 * @rproc: the remote processor handle
31 * @fw: the ELF firmware image
33 * Make sure this fw image is sane (ie a correct ELF32/ELF64 file).
35 * Return: 0 on success and -EINVAL upon any failure
39 const char *name = rproc->firmware;
[all …]
|
| /openbmc/u-boot/cmd/ |
| H A D | remoteproc.c | 1 // SPDX-License-Identifier: GPL-2.0+
4 * Texas Instruments Incorporated - http://www.ti.com/
14 * print_remoteproc_list() - print all the remote processor devices
27 printf("Cannot find Remote processor class\n"); in print_remoteproc_list()
37 switch (uc_pdata->mem_type) { in print_remoteproc_list()
45 printf("%d - Name:'%s' type:'%s' supports: %s%s%s%s%s%s\n", in print_remoteproc_list()
46 dev->seq, in print_remoteproc_list()
47 uc_pdata->name, in print_remoteproc_list()
49 ops->load ? "load " : "", in print_remoteproc_list()
50 ops->start ? "start " : "", in print_remoteproc_list()
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | remoteproc.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
4 * Texas Instruments Incorporated - http://www.ti.com/
16 #include <dm/platdata.h> /* For platform data support - non dt world */
19 * enum rproc_mem_type - What type of memory model does the rproc use
20 * @RPROC_INTERNAL_MEMORY_MAPPED: Remote processor uses own memory and is memory
21 * mapped to the host processor over an address range.
32 * struct dm_rproc_uclass_pdata - platform data for a CPU
33 * @name: Platform-specific way of naming the Remote proc
48 * struct dm_rproc_ops - Operations that are provided by remote proc driver
50 * Return 0 on success, -ve error on fail
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A 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 …]
|
| H A D | ti,k3-dsp-rproc.yaml | 1 # 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,
17 These processor sub-systems usually contain additional sub-modules like
19 controller, a dedicated local power/sleep controller etc. The DSP processor
20 cores in the K3 SoCs are usually either a TMS320C66x CorePac processor or a
[all …]
|
| /openbmc/u-boot/board/freescale/p2041rdb/ |
| H A D | README | 3 The P2041 Processor combines four Power Architecture processor cores
4 with high-performance datapath acceleration architecture(DPAA), CoreNet
9 P2041RDB board is a quad core platform supporting the P2041 processor
14 1. Build image
18 2. Program image
19 => tftp 1000000 u-boot.bin
36 5. Change DIP-switch
37 SW1[1-5] = 10110
42 1. Build image
47 Use PE tool to produce a image used to be programed to
[all …]
|
| /openbmc/linux/drivers/media/platform/renesas/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
18 tristate "R-Car Image Signal Processor (ISP)"
27 Support for Renesas R-Car Image Signal Processor (ISP).
28 Enable this to support the Renesas R-Car Image Signal
29 Processor (ISP).
32 module will be called rcar-isp.
43 source "drivers/media/platform/renesas/rcar-vin/Kconfig"
44 source "drivers/media/platform/renesas/rzg2l-cru/Kconfig"
49 tristate "Renesas Frame Compression Processor"
54 This is a driver for the Renesas Frame Compression Processor (FCP).
[all …]
|
| /openbmc/u-boot/arch/arm/mach-omap2/am33xx/ |
| H A D | Kconfig | 63 an AM335x processor subsystem.
105 The BAV335x OEM Network Processor integrates all the functions of an
107 incorporates the popular Texas Instruments Sitara 32bit ARM Coretex-A8
108 processor, with fast DDR3 512MB SDRAM, 4GB of embedded MMC and a Gigabit
213 The PDU001 is a processor and display unit developed around
214 the Computing-Module m2 from bytes at work AG.
253 an AM43xx processor subsystem.
263 prompt "Enable RTC-DDR ONLY Support"
265 If you want RTC-DDR ONLY Support, say Y. RTC Only with DDR in
266 self-refresh mode is a special power saving mode where in all
[all …]
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | x32-psabi.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
6 x32 processor-specific Application Binary Interface (`x32
7 psABI <https://software.intel.com/en-us/node/628948>`__) is a native
8 32-bit processor-specific ABI for Intel 64 (x86-64) architectures. An
13 Some processing environments prefer using 32-bit applications even when
14 running on Intel 64-bit platforms. Consider the i386 psABI, which is a
15 very old 32-bit ABI for Intel 64-bit platforms. The i386 psABI does not
16 provide efficient use and access of the Intel 64-bit processor
18 psABI. This ABI is newer and uses 64-bits for data sizes and program
29 - You can create packages and images in x32 psABI format on x86_64
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/documentation/corstone1000/ |
| H A D | user-guide.rst | 2 # Copyright (c) 2022-2024, Arm Limited.
4 # SPDX-License-Identifier: MIT
11 ------
12 The Corstone-1000 software stack uses the `Yocto Project <https://www.yoctoproject.org/>`__ to build
13 a tiny Linux distribution suitable for the Corstone-1000 platform (kernel and initramfs filesystem …
14 The Yocto Project relies on the `BitBake <https://docs.yoctoproject.org/bitbake.html#bitbake-docume…
19 -------------
26 - Git 1.8.3.1 or greater.
27 - Python 3.8.0 or greater.
28 - GNU Tar 1.28 or greater.
[all …]
|
| H A D | software-architecture.rst | 2 # Copyright (c) 2022-2024, Arm Limited.
4 # SPDX-License-Identifier: MIT
12 Arm Corstone-1000
15 Arm Corstone-1000 is a reference solution for IoT devices. It is part of
19 Corstone-1000 software plus hardware reference solution is PSA Level-2 ready
21 More information on the Corstone-1000 subsystem product and design can be
23 `Arm Corstone-1000 Software`_ and `Arm Corstone-1000 Technical Overview`_.
28 present in the user-guide document.
34 The software architecture of Corstone-1000 platform is a reference
43 .. image:: images/CorstoneSubsystems.png
[all …]
|
| /openbmc/u-boot/board/armltd/integrator/ |
| H A D | README | 2 U-Boot for ARM Integrator Development Platforms
8 Manuals available from :-
12 --------
13 There are two Integrator variants - Integrator/AP and Integrator/CP.
15 Each CM consists of a ARM processor core and associated hardware e.g
24 ------------
25 Integrator platforms can be configured to use U-Boot in at least three ways :-
26 a) Run ARM boot monitor, manually run U-Boot image from flash
27 b) Run ARM boot monitor, automatically run U-Boot image from flash
28 c) Run U-Boot image direct from flash.
[all …]
|
| /openbmc/u-boot/board/freescale/mpc8572ds/ |
| H A D | README | 2 --------
3 MPC8572DS is a high-performance computing, evaluation and development platform
4 supporting the mpc8572 PowerTM processor.
6 Building U-Boot
7 -----------
12 -----------
14 locations can be swapped using the dip-switch SW9[1:2].
20 ----------
22 0xe800_0000 - 0xebff_ffff Alternate bank 64MB
23 0xec00_0000 - 0xefff_ffff Boot bank 64MB
[all …]
|
| /openbmc/u-boot/doc/imx/mkimage/ |
| H A D | imximage.txt | 1 ---------------------------------------------
2 Imximage Boot Image generation using mkimage
3 ---------------------------------------------
5 This document describes how to set up a U-Boot image that can be booted
13 Booting from NOR flash does not require to use this image type.
15 For more details refer Chapter 2 - System Boot and section 2.14
16 (flash header description) of the processor's manual.
19 --------------
20 ./tools/mkimage -l <mx u-boot_file>
21 to list the imx image file details
[all …]
|
| /openbmc/u-boot/drivers/remoteproc/ |
| H A D | k3_rproc.c | 1 // SPDX-License-Identifier: GPL-2.0+
5 * Copyright (C) 2018 Texas Instruments Incorporated - http://www.ti.com/
17 #include <power-domain.h>
26 * struct k3_rproc_privdata - Structure representing Remote processor data.
31 * @proc_id: TISCI processor ID
32 * @host_id: TISCI host id to which the processor gets assigned to.
45 * k3_rproc_load() - Load up the Remote processor image
47 * @addr: Address at which image is available
48 * @size: size of the image
55 const struct ti_sci_proc_ops *pops = &rproc->sci->ops.proc_ops; in k3_rproc_load()
[all …]
|
| H A D | ti_power_proc.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * (C) Copyright 2015-2016
4 * Texas Instruments Incorporated - http://www.ti.com/
17 * struct ti_powerproc_privdata - power processor private data
18 * @loadaddr: base address for loading the power processor
27 * ti_of_to_priv() - generate private data from device tree
28 * @dev: corresponding ti remote processor device
31 * Return: 0 if all went ok, else corresponding -ve error
37 const void *blob = gd->fdt_blob; in ti_of_to_priv()
41 debug("'%s' no dt?\n", dev->name); in ti_of_to_priv()
[all …]
|
| /openbmc/linux/drivers/staging/media/sunxi/sun6i-isp/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Allwinner A31 Image Signal Processor (ISP) Driver"
14 Support for the Allwinner A31 Image Signal Processor (ISP), also
|
| /openbmc/u-boot/arch/x86/ |
| H A D | Kconfig | 8 prompt "Run U-Boot in 32/64-bit mode"
11 U-Boot can be built as a 32-bit binary which runs in 32-bit mode
12 even on 64-bit machines. In this case SPL is not used, and U-Boot
13 runs directly from the reset vector (via 16-bit start-up).
15 Alternatively it can be run as a 64-bit binary, thus requiring a
16 64-bit machine. In this case SPL runs in 32-bit mode (via 16-bit
17 start-up) then jumps to U-Boot in 64-bit mode.
19 For now, 32-bit mode is recommended, as 64-bit is still
23 bool "32-bit"
25 Build U-Boot as a 32-bit binary with no SPL. This is the currently
[all …]
|
| /openbmc/linux/arch/sh/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
78 The SuperH is a RISC processor targeted for use in embedded systems
81 <http://www.linux-sh.org/>.
152 # Processor families
214 prompt "Processor sub-type selection"
217 # Processor subtypes
220 # SH-2 Processor Support
223 bool "Support SH7619 processor"
228 bool "Support J2 processor"
233 # SH-2A Processor Support
[all …]
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | remoteproc-framework.txt | 1 # SPDX-License-Identifier: GPL-2.0+
4 # Texas Instruments Incorporated - http://www.ti.com/
7 Remote Processor Framework
11 2. How does it work - The driver
18 This is an introduction to driver-model for Remote Processors found
19 on various System on Chip(SoCs). The term remote processor is used to
20 indicate that this is not the processor on which U-Boot is operating
22 the processor on which we are functional.
24 The simplified model depends on a single UCLASS - UCLASS_REMOTEPROC
27 - drivers/remoteproc/rproc-uclass.c
[all …]
|
| /openbmc/u-boot/board/qualcomm/dragonboard820c/ |
| H A D | readme.txt | 1 # SPDX-License-Identifier: GPL-2.0+
3 # (C) Copyright 2017 Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
8 - UART
9 - SD card
10 - PSCI reset
11 - Environment in EXT4 partition 1 in SD card (check defconfig for details)
25 CROSS_COMPILE="ccache aarch64-linux-gnu-"
27 3) cd to the u-boot tree
30 $ make -j `nproc`
38 $ dtbTool -o dt.img arch/arm/dts
[all …]
|
| /openbmc/linux/drivers/firmware/efi/libstub/ |
| H A D | arm64.c | 1 // SPDX-License-Identifier: GPL-2.0
12 #include <asm/image.h>
28 * via the type 4 SMBIOS records. Otherwise, test the processor version in system_needs_vamap()
29 * field. eMAG systems all appear to have the processor version field in system_needs_vamap()
36 socid = (u32 *)record->processor_id; in system_needs_vamap()
38 static char const altra[] = "Ampere(TM) Altra(TM) Processor"; in system_needs_vamap()
42 version = efi_get_smbios_string(&record->header, 4, in system_needs_vamap()
44 if (!version || (strncmp(version, altra, sizeof(altra) - 1) && in system_needs_vamap()
45 strncmp(version, emag, sizeof(emag) - 1))) in system_needs_vamap()
109 size -= lsize; in efi_cache_sync_image()
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/remoteproc/ |
| H A D | k3-rproc.txt | 1 Texas Instruments' K3 Remote processor driver
4 In K3 generation Socs, loading an image on any processing entity
5 cannot be done directly from U-Boot. In order to load an image,
10 --------------------
11 - compatible: Shall be: "ti,am654-rproc"
12 - reg: base address of the remoteproc timer.
13 - power-domains: Should contain two sets of entries:
18 doc/device-tree-bindings/power/ti,sci-pm-domain.txt
19 - resets: Should contain a phandle to a reset controller node
22 doc/device-tree-bindings/reset/ti,sci-reset.txt
[all …]
|