Home
last modified time | relevance | path

Searched refs:SPU (Results 1 – 25 of 25) sorted by relevance

/OK3568_Linux_fs/kernel/Documentation/filesystems/spufs/
H A Dspu_run.rst27 ate(2) to address a specific SPU context. When the context gets sched-
28 uled to a physical SPU, it starts execution at the instruction pointer
31 Execution of SPU code happens synchronously, meaning that spu_run does
32 not return while the SPU is still running. If there is a need to exe-
33 cute SPU code in parallel with other code on either the main CPU or
37 When spu_run returns, the current value of the SPU instruction pointer
63 on the SPU. The bit masks for the status codes are:
66 SPU was stopped by stop-and-signal.
69 SPU was stopped by halt.
72 SPU is waiting for a channel.
[all …]
H A Dspufs.rst10 spufs - the SPU file system
16 The SPU file system is used on PowerPC machines that implement the Cell
22 can use spu_create(2) to establish SPU contexts in the spufs root.
24 Every SPU context is represented by a directory containing a predefined
26 logical SPU. Users can change permissions on those files, but not actu-
63 the contents of the local storage memory of the SPU. This can be
65 data in the address space of the SPU. The possible operations on an
71 file. The file size is the size of the local storage of the SPU,
76 SPU local storage within the process address space. Only
81 The first SPU to CPU communication mailbox. This file is read-only and
[all …]
H A Dspu_create.rst26 Processor Units (SPUs). It creates a new logical context for an SPU in
28 point to a non-existing directory in the mount point of the SPU file
36 descriptor is closed, the logical SPU context is destroyed.
42 Allow mapping of some of the hardware registers of the SPU into
67 EEXIST An SPU context already exists at the given path name.
87 ENOSPC There are not enough SPU resources available to create a new
88 context or the user specific limit for the number of SPU con-
H A Dindex.rst4 SPU Filesystem
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/crypto/
H A Dbrcm,spu-crypto.txt1 The Broadcom Secure Processing Unit (SPU) hardware supports symmetric
2 cryptographic offload for Broadcom SoCs. A SoC may have multiple SPU hardware
7 brcm,spum-crypto - for devices with SPU-M hardware
11 brcm,spum-nsp-crypto - for the Northstar Plus variant of the SPU-M hardware
13 - reg: Should contain SPU registers location and length.
14 - mboxes: The mailbox channel to be used to communicate with the SPU.
/OK3568_Linux_fs/kernel/arch/powerpc/platforms/cell/
H A DKconfig44 tristate "SPU file system"
50 The SPU file system is used to access Synergistic Processing
94 tristate "CBE frequency scaling based on SPU usage"
/OK3568_Linux_fs/kernel/arch/sh/kernel/cpu/sh4a/
H A Dsetup-sh7724.c894 DMAC1B, DMAC0B, I2C0, I2C1, SDHI0, SDHI1, SPU, MMCIF, enumerator
1011 INTC_GROUP(SPU, SPU_SPUI0, SPU_SPUI1),
1061 TMU1_TUNI2, SPU } },
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A Dvf610-zii-ssmb-spu3.dts7 * SPU - Seat Power Unit
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/dvb/
H A Dvideo_types.rst244 /* can the driver also handle SPU, NAVI and CSS encoded data?
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/info/
H A Dld.info5899 * SPU ELF:: 'ld' and SPU ELF Support
6699 File: ld.info, Node: S/390 ELF, Next: SPU ELF, Prev: PowerPC64 ELF64, Up: Machine Dependent
6710 File: ld.info, Node: SPU ELF, Next: TI COFF, Prev: S/390 ELF, Up: Machine Dependent
6712 5.14 'ld' and SPU ELF Support
6734 'ld' usually checks that a final executable for SPU fits in the
6739 SPU local store space is limited. Over-allocation of stack space
6766 File: ld.info, Node: TI COFF, Next: WIN32, Prev: SPU ELF, Up: Machine Dependent
8320 * --emit-stack-syms: SPU ELF. (line 46)
8323 * --emit-stub-syms <2>: SPU ELF. (line 15)
8345 * --extra-overlay-stubs: SPU ELF. (line 19)
[all …]
H A Dbfd.info3928 SPU Relocations.
8151 bfd_arch_spu, /* PowerPC SPU. */
H A Dgccint.info5352 PowerPC target supports PowerPC SPU.
34856 needed for the SPU, which passes 'char' and 'short' arguments in
41287 For example, the SPU port uses the '__ea' address space to refer to
41288 memory in the host processor, rather than memory local to the SPU
41293 switches (native SPU pointers are always 32 bits).
41301 example, the SPU port uses the following to declare '__ea' as the
48233 * Trevor Smigiel for contributing the SPU port.
H A Dgcc.info59925 * Trevor Smigiel for contributing the SPU port.
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/info/
H A Dld.info5899 * SPU ELF:: 'ld' and SPU ELF Support
6699 File: ld.info, Node: S/390 ELF, Next: SPU ELF, Prev: PowerPC64 ELF64, Up: Machine Dependent
6710 File: ld.info, Node: SPU ELF, Next: TI COFF, Prev: S/390 ELF, Up: Machine Dependent
6712 5.14 'ld' and SPU ELF Support
6734 'ld' usually checks that a final executable for SPU fits in the
6739 SPU local store space is limited. Over-allocation of stack space
6766 File: ld.info, Node: TI COFF, Next: WIN32, Prev: SPU ELF, Up: Machine Dependent
8320 * --emit-stack-syms: SPU ELF. (line 46)
8323 * --emit-stub-syms <2>: SPU ELF. (line 15)
8345 * --extra-overlay-stubs: SPU ELF. (line 19)
[all …]
H A Dbfd.info3928 SPU Relocations.
8151 bfd_arch_spu, /* PowerPC SPU. */
H A Dgccint.info5352 PowerPC target supports PowerPC SPU.
34856 needed for the SPU, which passes 'char' and 'short' arguments in
41287 For example, the SPU port uses the '__ea' address space to refer to
41288 memory in the host processor, rather than memory local to the SPU
41293 switches (native SPU pointers are always 32 bits).
41301 example, the SPU port uses the following to declare '__ea' as the
48233 * Trevor Smigiel for contributing the SPU port.
H A Dgcc.info59925 * Trevor Smigiel for contributing the SPU port.
/OK3568_Linux_fs/kernel/drivers/crypto/
H A DKconfig822 Secure Processing Unit (SPU). The SPU driver registers skcipher,
/OK3568_Linux_fs/kernel/Documentation/driver-api/media/drivers/
H A Dcx2341x-devel.rst81 3 processors on chip, Java ones, VPU, SPU, APU, maybe these are the
124 - 0x9050: SPU control
192 - Write 0x00000001 to register 0x9050 to stop the SPU.
202 re-enable the SPU.
/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A Dproc.rst785 SPU
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/lib/gcc/aarch64-none-linux-gnu/10.3.1/plugin/include/
H A Dtarget.def4815 This is needed for the SPU, which passes @code{char} and @code{short}\n\
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/lib/gcc/arm-none-linux-gnueabihf/10.3.1/plugin/include/
H A Dtarget.def4815 This is needed for the SPU, which passes @code{char} and @code{short}\n\
/OK3568_Linux_fs/kernel/
H A DMAINTAINERS16569 SPU FILE SYSTEM
/OK3568_Linux_fs/device/rockchip/common/images/userdata/userdata_normal/media/
H A Dyuv420_p352x288.yuv7618 …�.6����������������������������������|}��������������������������~{wrme\SPU;1=7#R���1�*?/'…
/OK3568_Linux_fs/recovery/
HDrootfs.cpio.gz107070100A8AEB0000041ED0000000000000000000000116841B48100000000000000FD0000000200000000000000000000000200000000.�07070100A8B07C000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000900000000.gitkeep��07070100A8B07D000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000B00000000.skip_fsck����07070100A8AEB10000A1FF0000000000000000000000016841B0B600000007000000FD0000000200000000000000000000000400000000bin���usr/bin�07070100A8B07E000081A400000000000000000000000168412635000001CC000000FD0000000200000000000000000000001100000000busybox. ...