Searched full:messaging (Results 1 – 25 of 142) sorted by relevance
123456
2 RapidIO subsystem Channelized Messaging character device driver (rio_cm.c)15 messaging capabilities of RapidIO endpoint devices (mports) directly20 RapidIO mailbox messaging resources.23 messaging mailboxes in case of multi-packet message (up to 4KB) and26 have reduced number of messaging mailboxes. RapidIO aware applications must27 therefore share the messaging resources of a RapidIO endpoint.29 Main purpose of this device driver is to provide RapidIO mailbox messaging31 operations using a single messaging mailbox. This allows applications to32 use the limited RapidIO messaging hardware resources efficiently.43 support messaging operations (number of entries up to RIO_MAX_MPORTS).[all …]
10 doorbells, inbound maintenance port-writes and RapidIO messaging.16 RapidIO messaging support uses dedicated messaging channels for each mailbox.18 into the corresponding message queue. Messaging callbacks are implemented to be19 fully compatible with RIONET driver (Ethernet over RapidIO messaging services).58 - RIO messaging MBOX selection mask. This is a bitmask that defines59 messaging MBOXes are managed by this device driver. Mask bits 0 - 3
75 *messaging*::79 Options of *messaging*97 Example of *messaging*101 % perf bench sched messaging # run with default107 % perf bench sched messaging -t -g 20 # be multi-thread, with 20 groups
83 tristate "RapidIO Channelized Messaging driver"86 This option includes RapidIO channelized messaging driver which88 messaging mailbox between multiple user-space applications.
7 title: Freescale/NXP i.MX Messaging Unit (MU) work as msi controller13 The Messaging Unit module enables two processors within the SoC to19 Because the MU manages the messaging between processors, the MU uses
325 * Messaging definitions339 * Outbound Messaging Engine Registers400 * Inbound Messaging Engine Registers473 * Messaging Engine Interrupts552 * Inbound Messaging Descriptor580 * Outbound Messaging Descriptor627 /* Descriptor types for BDMA and Messaging blocks */633 DTYPE5 = 5, /* OB Messaging Block Pointer Descriptor */634 DTYPE6 = 6 /* Inbound Messaging Descriptor */895 /* Inbound Messaging */[all …]
39 "RIO Messaging MBOX Selection Mask (default: 0x0f = all)");498 * Service channel interrupts from Messaging Engine in tsi721_irqhandler()605 * tsi721_omsg_msix - MSI-X interrupt handler for outbound messaging609 * Handles outbound messaging interrupts signaled using MSI-X.622 * tsi721_imsg_msix - MSI-X interrupt handler for inbound messaging626 * Handles inbound messaging interrupts signaled using MSI-X.690 * immediately after mport initialization. Messaging interrupt service routines731 * Initialize MSI-X entries for Messaging Engine: in tsi721_enable_msix()1536 /* Enable Inbound Messaging Interrupts */1546 /* Clear pending Inbound Messaging interrupts */ in tsi721_imsg_interrupt_enable()[all …]
118 Messaging:122 The header file <linux/slimbus.h> has more documentation about messaging APIs.124 Messaging APIs: argument126 .. kernel-doc:: drivers/slimbus/messaging.c
7 title: NXP i.MX Messaging Unit (MU)13 The Messaging Unit module enables two processors within the SoC to18 Because the MU manages the messaging between processors, the MU uses
33 base_cycles=$(perf stat --no-big-num -e cycles -- perf bench sched messaging -g 1 -l 100 -t 2>&1 | …38 bpf_cycles=$(perf stat --no-big-num --bpf-counters -e cycles -- perf bench sched messaging -g 1 -l …
40 perf lock record -o ${perfdata} -- perf bench sched messaging > /dev/null 2>&160 perf lock con -a -b -E 1 -q -- perf bench sched messaging > /dev/null 2> ${result}
66 # perf bench sched messaging creates 400 processes68 perf bench sched messaging -g 10 > /dev/null 2&>1
3 * Remote processor messaging - sample client driver95 MODULE_DESCRIPTION("Remote processor messaging sample client driver");
9 * PF<->VF Gen2 Messaging format59 * PF<->VF Gen4 Messaging format61 * Similarly to the gen2 messaging format, 32-bit long registers are used for
4 * sched-messaging.c6 * messaging: Benchmark for scheduler and IPC mechanisms257 "perf bench sched messaging <options>",
1 perf-y += sched-messaging.o
10 the VCHIQ messaging interface between the kernel and the firmware
11 ecryptfs-$(CONFIG_ECRYPT_FS_MESSAGING) += messaging.o miscdev.o
6 slimbus-y := core.o messaging.o sched.o stream.o
34 communicating with slave HW directly over the bus using messaging
339 /* Register messaging address. Block transaction is not allowed. */ in snd_tscm_transaction_reregister()355 /* Turn on messaging. */ in snd_tscm_transaction_reregister()383 /* Turn off messaging. */ in snd_tscm_transaction_unregister()
13 * Bootloader Messaging Interface (BMI)15 * BMI is a very simple messaging interface used during initialization
114 /* Enable VF2PF Messaging Ints - VFs 0 through 15 per vf_mask[15:0] */ in enable_vf2pf_interrupts()121 /* Enable VF2PF Messaging Ints - VFs 16 through 31 per vf_mask[31:16] */ in enable_vf2pf_interrupts()
22 * Bootloader Messaging Interface (BMI)24 * BMI is a very simple messaging interface used during initialization
21 * @K3_RINGACC_RING_MODE_MESSAGE: Messaging mode. Messaging mode requires
