Home
last modified time | relevance | path

Searched full:cfe (Results 1 – 25 of 71) sorted by relevance

123

/linux-6.14.4/drivers/media/platform/raspberrypi/rp1-cfe/
Dcfe.c44 #include "cfe-fmts.h"
45 #include "cfe.h"
50 #include "cfe-trace.h"
52 #define CFE_MODULE_NAME "rp1-cfe"
55 #define cfe_dbg(cfe, fmt, arg...) dev_dbg(&(cfe)->pdev->dev, fmt, ##arg) argument
56 #define cfe_info(cfe, fmt, arg...) dev_info(&(cfe)->pdev->dev, fmt, ##arg) argument
57 #define cfe_err(cfe, fmt, arg...) dev_err(&(cfe)->pdev->dev, fmt, ##arg) argument
262 struct cfe_device *cfe; member
312 static inline bool is_fe_enabled(struct cfe_device *cfe) in is_fe_enabled() argument
314 return cfe->fe_csi2_channel != -1; in is_fe_enabled()
[all …]
DMakefile5 rp1-cfe-objs := cfe.o csi2.o pisp-fe.o dphy.o
6 obj-$(CONFIG_VIDEO_RP1_CFE) += rp1-cfe.o
DKconfig4 tristate "Raspberry Pi RP1 Camera Front End (CFE) video capture driver"
15 called rp1-cfe.
Dcfe-trace.h8 #define TRACE_SYSTEM cfe
201 #define TRACE_INCLUDE_FILE ../../drivers/media/platform/raspberrypi/rp1-cfe/cfe-trace
/linux-6.14.4/Documentation/admin-guide/media/
Draspberrypi-rp1-cfe.rst4 Raspberry Pi PiSP Camera Front End (rp1-cfe)
10 The PiSP Camera Front End (CFE) is a module which combines a CSI-2 receiver with
13 The CFE has four DMA engines and can write frames from four separate streams
25 The rp1-cfe driver
28 The Raspberry Pi PiSP Camera Front End (rp1-cfe) driver is located under
29 drivers/media/platform/raspberrypi/rp1-cfe. It uses the `V4L2 API` to register
34 The media topology registered by the `rp1-cfe` driver, in this particular
37 .. _rp1-cfe-topology:
39 .. kernel-figure:: raspberrypi-rp1-cfe.dot
45 - rp1-cfe-csi2-ch0: capture device for the first CSI-2 stream
[all …]
Draspberrypi-rp1-cfe.dot18 n00000011 [label="rp1-cfe-csi2-ch0\n/dev/video0", shape=box, style=filled, fillcolor=yellow]
19 n00000015 [label="rp1-cfe-csi2-ch1\n/dev/video1", shape=box, style=filled, fillcolor=yellow]
20 n00000019 [label="rp1-cfe-csi2-ch2\n/dev/video2", shape=box, style=filled, fillcolor=yellow]
21 n0000001d [label="rp1-cfe-csi2-ch3\n/dev/video3", shape=box, style=filled, fillcolor=yellow]
22 n00000021 [label="rp1-cfe-fe-image0\n/dev/video4", shape=box, style=filled, fillcolor=yellow]
23 n00000025 [label="rp1-cfe-fe-image1\n/dev/video5", shape=box, style=filled, fillcolor=yellow]
24 n00000029 [label="rp1-cfe-fe-stats\n/dev/video6", shape=box, style=filled, fillcolor=yellow]
25 n0000002d [label="rp1-cfe-fe-config\n/dev/video7", shape=box, style=filled, fillcolor=yellow]
/linux-6.14.4/Documentation/devicetree/bindings/mtd/partitions/
Dbrcm,bcm947xx-cfe-partitions.yaml4 $id: http://devicetree.org/schemas/mtd/partitions/brcm,bcm947xx-cfe-partitions.yaml#
11 home routers. Their BCM947xx boards using CFE bootloader have several
24 1) Bootloader with Broadcom's CFE (Common Firmware Environment)
33 CFE's environment variable "bootpartition" is used.
42 const: brcm,bcm947xx-cfe-partitions
49 compatible = "brcm,bcm947xx-cfe-partitions";
Dbrcm,bcm963xx-cfe-nor-partitions.txt1 Broadcom BCM963XX CFE Loader NOR Flash Partitions
5 NOR. The first erase block used for the CFE bootloader, the last for an
12 - compatible : must be "brcm,bcm963xx-cfe-nor-partitions"
22 compatible = "brcm,bcm963xx-cfe-nor-partitions";
Dbrcm,trx.txt6 supported by the CFE bootloader.
14 device executable binary (e.g. a kernel) as it's what the CFE bootloader starts
/linux-6.14.4/arch/mips/bcm63xx/boards/
Dboard_bcm963xx.c731 u8 *boot_addr, *cfe; in board_prom_init() local
748 /* dump cfe version */ in board_prom_init()
749 cfe = boot_addr + BCM963XX_CFE_VERSION_OFFSET; in board_prom_init()
750 if (strstarts(cfe, "cfe-")) { in board_prom_init()
751 if(cfe[4] == 'v') { in board_prom_init()
752 if(cfe[5] == 'd') in board_prom_init()
754 (char *) &cfe[5]); in board_prom_init()
755 else if (cfe[10] > 0) in board_prom_init()
757 "%u.%u.%u-%u.%u-%u", cfe[5], cfe[6], in board_prom_init()
758 cfe[7], cfe[8], cfe[9], cfe[10]); in board_prom_init()
[all …]
/linux-6.14.4/drivers/mtd/parsers/
Dbcm63xxpart.c3 * BCM63XX CFE image tag parser
27 #include <asm/fw/cfe/cfe_api.h>
101 parts[curpart].name = "CFE"; in bcm63xx_parse_cfe_nor_partitions()
155 { .compatible = "brcm,bcm963xx-cfe-nor-partitions" },
171 MODULE_DESCRIPTION("MTD partitioning for BCM63XX CFE bootloaders");
Dparser_imagetag.c3 * BCM63XX CFE image tag parser
48 pr_info("%s: CFE image tag found at 0x%llx with version %s, board type %s\n", in bcm963xx_read_imagetag()
54 pr_warn("%s: CFE image tag at 0x%llx CRC invalid (expected %08x, actual %08x)\n", in bcm963xx_read_imagetag()
63 /* CFE, NVRAM and global Linux are always present */ in bcm963xx_parse_imagetag_partitions()
221 MODULE_DESCRIPTION("MTD parser for BCM963XX CFE Image Tag partitions");
DKconfig10 bool "BCM63XX CFE partitioning parser"
15 This provides partition parsing for BCM63xx devices with CFE
92 using CFE environment variable.
130 was named after it. Later it was adapted to CFE and U-Boot
/linux-6.14.4/arch/mips/sibyte/common/
Dcfe.c20 #include <asm/fw/cfe/cfe_api.h>
21 #include <asm/fw/cfe/cfe_error.h>
58 printk("Passing control back to CFE...\n"); in cfe_linux_exit()
222 * what CFE gives us (handle, 0, EPT and EPTSEAL) in prom_init()
251 printk("CFE's entrypoint seal doesn't match. Spinning."); in prom_init()
264 printk("LINUX_CMDLINE not defined in cfe."); in prom_init()
Dcfe_console.c8 #include <asm/fw/cfe/cfe_api.h>
9 #include <asm/fw/cfe/cfe_error.h>
68 .name = "cfe",
/linux-6.14.4/Documentation/devicetree/bindings/media/
Draspberrypi,rp1-cfe.yaml4 $id: http://devicetree.org/schemas/media/raspberrypi,rp1-cfe.yaml#
28 - const: raspberrypi,rp1-cfe
76 compatible = "raspberrypi,rp1-cfe";
/linux-6.14.4/arch/mips/include/asm/fw/cfe/
Dcfe_api.h6 * Broadcom Common Firmware Environment (CFE)
9 * cfe from an application. It should be the only header
24 /* Seal indicating CFE's presence, passed to user program. */
Dcfe_error.h7 * Broadcom Common Firmware Environment (CFE)
9 * CFE's global error code list is here.
/linux-6.14.4/arch/arm/boot/dts/broadcom/
Dbcm53016-dlink-dwl-8610ap.dts111 /* This is named nflash1.trx in CFE */
118 /* This is named nflash1.trx2 in CFE */
125 /* This is named nflash1.rwfs in CFE */
/linux-6.14.4/arch/mips/fw/cfe/
Dcfe_api.c8 * Broadcom Common Firmware Environment (CFE)
11 * call the standard "iocb" interface entry point to CFE).
20 #include <asm/fw/cfe/cfe_api.h>
37 * passed in two registers each, and CFE expects one.
442 /* disable XKS01 so that CFE can access the registers */ in cfe_die()
/linux-6.14.4/Documentation/userspace-api/media/v4l/
Dmetafmt-pisp-fe.rst14 `rp1-cfe-fe-config` output video device node using the
32 by writing to a buffer provided via the `rp1-cfe-fe-stats` capture video device
/linux-6.14.4/arch/mips/sibyte/sb1250/
Dsmp.c15 #include <asm/fw/cfe/cfe_api.h>
109 * Use CFE to find out how many CPUs are available, setting up
/linux-6.14.4/include/linux/
Dbcm963xx_tag.h61 /* 72-83: Address in memory of CFE */
63 /* 84-93: Size of CFE */
/linux-6.14.4/arch/mips/sibyte/bcm1480/
Dsmp.c15 #include <asm/fw/cfe/cfe_api.h>
120 * Use CFE to find out how many CPUs are available, setting up
/linux-6.14.4/drivers/media/platform/raspberrypi/
DMakefile4 obj-y += rp1-cfe/

123