Home
last modified time | relevance | path

Searched full:vchiq (Results 1 – 25 of 28) sorted by relevance

12

/linux/drivers/platform/raspberrypi/
H A DMakefile3 obj-$(CONFIG_BCM2835_VCHIQ) += vchiq.o
5 vchiq-objs := \
6 vchiq-interface/vchiq_core.o \
7 vchiq-interface/vchiq_arm.o \
8 vchiq-interface/vchiq_bus.o \
9 vchiq-interface/vchiq_debugfs.o \
12 vchiq-objs += vchiq-interface/vchiq_dev.o
15 obj-$(CONFIG_BCM2835_VCHIQ_MMAL) += vchiq-mmal/
H A DKconfig16 tristate "BCM2835 VCHIQ"
21 This config enables the VCHIQ driver, which implements a
24 the VPU. More specifically, the VCHIQ driver is used by
35 bool "VCHIQ Character Driver"
37 Enable the creation of VCHIQ character driver. The cdev exposes
39 with VideoCore, via the VCHIQ core driver (Check BCM2835_VCHIQ
50 source "drivers/platform/raspberrypi/vchiq-mmal/Kconfig"
/linux/Documentation/devicetree/bindings/soc/bcm/
H A Dbrcm,bcm2835-vchiq.yaml4 $id: http://devicetree.org/schemas/soc/bcm/brcm,bcm2835-vchiq.yaml#
7 title: Broadcom VCHIQ firmware services
13 The VCHIQ communication channel can be provided by BCM283x and Capri SoCs,
22 - brcm,bcm2835-vchiq
27 - brcm,bcm2836-vchiq
28 - const: brcm,bcm2835-vchiq
48 compatible = "brcm,bcm2835-vchiq";
/linux/drivers/platform/raspberrypi/vchiq-interface/
H A DTESTING1 This document contains some hints to test the function of the VCHIQ driver
6 Testing the VCHIQ driver requires a Raspberry Pi with one of the following SoC:
14 There are no specific requirements to the VideoCore firmware to get VCHIQ
26 Just use bcm2835_defconfig which already has VCHIQ enabled.
30 Use the multi_v7_defconfig as a base and then enable all VCHIQ options.
34 Use the defconfig which has most of the VCHIQ options enabled.
40 Check the driver is probed and /dev/vchiq is created
86 Command: cat /sys/kernel/debug/vchiq/state
H A Dvchiq_arm.c40 #define DEVICE_NAME "vchiq"
61 * The devices implemented in the VCHIQ firmware are not discoverable,
79 * The keepalive mechanism was retro-fitted to VCHIQ to allow active
108 * Flag to indicate that the first vchiq connect has made it through.
141 * This function is called by the vchiq stack once it has been connected to
160 * This function is used to defer initialization until the vchiq stack is
259 "VCHIQ doorbell", state); in vchiq_platform_init()
1035 snprintf(entity, sizeof(entity), "VCHIQ: "); in vchiq_use_internal()
1300 dev_warn(state->dev, "suspend: VCHIQ use count %d\n", peer_count); in vchiq_dump_service_use_state()
1301 dev_warn(state->dev, "suspend: Overall vchiq instance use count %d\n", vc_use_count); in vchiq_dump_service_use_state()
[all …]
H A Dvchiq_bus.c3 * vchiq_device.c - VCHIQ generic device and bus-type
30 return add_uevent_var(env, "MODALIAS=vchiq:%s", dev_name(&device->dev)); in vchiq_bus_uevent()
51 .name = "vchiq-bus",
H A Dvchiq_debugfs.c16 /* Global 'vchiq' debugfs and clients entry used by all instances */
126 vchiq_dbg_dir = debugfs_create_dir("vchiq", NULL); in vchiq_debugfs_init()
H A Dvchiq_dev.c513 /* This must be a VCHIQ-style service */ in vchiq_ioc_await_completion()
628 "arm: vchiq: connect: could not lock mutex for state %d: %d\n", in vchiq_ioctl()
640 "arm: vchiq: could not connect: %d\n", status); in vchiq_ioctl()
1181 dev_dbg(state->dev, "arm: vchiq open\n"); in vchiq_open()
1184 dev_dbg(state->dev, "arm: vchiq has no connection to VideoCore\n"); in vchiq_open()
1329 .name = "vchiq",
1334 * vchiq_register_chrdev - Register the char driver for vchiq
1349 * vchiq_deregister_chrdev - Deregister and cleanup the vchiq char
H A Dvchiq_ioctl.h8 #include <linux/raspberrypi/vchiq.h>
/linux/drivers/platform/raspberrypi/vchiq-mmal/
H A DMakefile2 bcm2835-mmal-vchiq-objs := mmal-vchiq.o
4 obj-$(CONFIG_BCM2835_VCHIQ_MMAL) += bcm2835-mmal-vchiq.o
H A DKconfig2 tristate "BCM2835 MMAL VCHIQ service"
5 Enables the MMAL API over VCHIQ interface as used for the
H A Dmmal-vchiq.c13 * V4L2 driver MMAL vchiq interface code
25 #include <linux/raspberrypi/vchiq.h>
32 #include "mmal-vchiq.h"
182 /* handle for a vchiq instance */
249 * we do this because it is important we do not call any other vchiq
1320 * list, and we should get the relevant callbacks via VCHIQ in port_disable()
1843 pr_err("mmal-vchiq: VCHIQ close failed\n"); in vchiq_mmal_finalise()
1917 instance->bulk_wq = alloc_ordered_workqueue("mmal-vchiq", in vchiq_mmal_init()
1947 MODULE_DESCRIPTION("BCM2835 MMAL VCHIQ interface");
H A Dmmal-msg.h40 #include "mmal-vchiq.h"
91 u32 status; /* The status of the vchiq operation */
H A Dmmal-vchiq.h13 * MMAL interface to VCHIQ message passing
/linux/arch/arm/boot/dts/broadcom/
H A Dbcm2836-rpi.dtsi5 &vchiq {
6 compatible = "brcm,bcm2836-vchiq", "brcm,bcm2835-vchiq";
H A Dbcm2835-rpi.dtsi23 vchiq: mailbox@7e00b840 {
24 compatible = "brcm,bcm2835-vchiq";
21 vchiq: mailbox@7e00b840 { global() label
H A Dbcm2711-rpi.dtsi108 &vchiq {
/linux/include/linux/raspberrypi/
H A Dvchiq_bus.h50 * module_vchiq_driver() - Helper macro for registering a vchiq driver
51 * @__vchiq_driver: vchiq driver struct
53 * Helper macro for vchiq drivers which do not do anything special in
H A Dvchiq_core.h18 #include "vchiq.h"
175 * VCHIQ is a reliable connection-oriented datagram protocol.
177 * A VCHIQ service is equivalent to a TCP connection, except:
508 short version; /* The version of VCHIQ */
509 short version_min; /* The minimum compatible version of VCHIQ */
H A Dvchiq_cfg.h8 /* The version of VCHIQ - change with any non-trivial change */
/linux/drivers/staging/vc04_services/bcm2835-audio/
H A DMakefile3 snd-bcm2835-objs := bcm2835.o bcm2835-ctl.o bcm2835-pcm.o bcm2835-vchiq.o
H A Dbcm2835-pcm.c136 /* minimum 16 bytes alignment (for vchiq bulk transfers) */ in snd_bcm2835_playback_open_generic()
203 /* notify the vchiq that it should enter spdif passthrough mode by in snd_bcm2835_pcm_prepare()
H A Dbcm2835-vchiq.c17 struct mutex vchi_mutex; /* Serialize vchiq access */
26 MODULE_PARM_DESC(force_bulk, "Force use of vchiq bulk for audio");
H A Dbcm2835.h8 #include <linux/raspberrypi/vchiq.h>
H A Dbcm2835.c319 MODULE_DEVICE_TABLE(vchiq, device_id_table);

12