Oopenvela-robotrpmsgdev.c: use shmem buf to replace local variables
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
drivers/misc/optee: Add SMC backend for arm archs So far NuttX has supported OP-TEE interfacing over local and RPMsg sockets. This commit introduces support for direct invocation of OP-TEE through arm SMCs. The SMC transport is enabled through CONFIG_DEV_OPTEE_SMC. This SMC implementation has been tested only with arm64, OP-TEE rev 4.4. Note that it does not support reverse direction RPCs, i.e. from the Secure World to the Normal World to something like optee supplicant. A basic RPC handling skeleton is provided with implementation for some basic functions (alloc/free mem, and foreign interrupts) but no supplicant command handling. (+one minor change s/parm/param in arch/arm64/include/syscall to satisfy the spellchecker during PR) Signed-off-by: George Poulios <gpoulios@census-labs.com> Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
drivers/misc/optee: Add OPTEE_OPENVELA_COMPAT temporarily Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
drivers/misc/optee: Add SMC backend for arm archs So far NuttX has supported OP-TEE interfacing over local and RPMsg sockets. This commit introduces support for direct invocation of OP-TEE through arm SMCs. The SMC transport is enabled through CONFIG_DEV_OPTEE_SMC. This SMC implementation has been tested only with arm64, OP-TEE rev 4.4. Note that it does not support reverse direction RPCs, i.e. from the Secure World to the Normal World to something like optee supplicant. A basic RPC handling skeleton is provided with implementation for some basic functions (alloc/free mem, and foreign interrupts) but no supplicant command handling. (+one minor change s/parm/param in arch/arm64/include/syscall to satisfy the spellchecker during PR) Signed-off-by: George Poulios <gpoulios@census-labs.com> Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
kasan: fix the virtio transport write address error caused by kasan tag Signed-off-by: Yongrong Wang <wangyongrong@xiaomi.com> | 2 个月前 | |
drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> | 2 个月前 | |
driver/dev_mem: Support seek function Use filep->f_pos to record the offset instead of the memory address Signed-off-by: wangmingrong1 <wangmingrong1@xiaomi.com> | 2 个月前 | |
uio api tweaks VELAPLATFO-60135:VELAPLATFO-60136 * Make readv/writev implementations update struct uio This can simplify partial result handling. * change the error number on the overflow from EOVERFLOW to EINVAL to match NetBSD * add a commented out uio_offset field. I used "#if 0" here as C comments can't nest. * add a few helper functions Note on uio_copyfrom/uio_copyto: although i'm not quite happy with the "offset" functionality, it's necessary to simplify the adaptation of some drivers like drivers/serial/serial.c, which (ab)uses the user-supplied buffer as a line-buffer. Signed-off-by: Yongrong Wang <wangyongrong@xiaomi.com> | 2 个月前 | |
uio api tweaks VELAPLATFO-60135:VELAPLATFO-60136 * Make readv/writev implementations update struct uio This can simplify partial result handling. * change the error number on the overflow from EOVERFLOW to EINVAL to match NetBSD * add a commented out uio_offset field. I used "#if 0" here as C comments can't nest. * add a few helper functions Note on uio_copyfrom/uio_copyto: although i'm not quite happy with the "offset" functionality, it's necessary to simplify the adaptation of some drivers like drivers/serial/serial.c, which (ab)uses the user-supplied buffer as a line-buffer. Signed-off-by: Yongrong Wang <wangyongrong@xiaomi.com> | 2 个月前 | |
drivers: Avoid causing a busy loop in the program due to context switching induced by sem_post. examples: There are two threads involved: thread A with a priority of 100 and thread B with a priority of 101. Here's how they interact: When thread A releases a semaphore, thread B is scheduled to execute some code and may reacquire the semaphore. If no other tasks are ready, thread A will be scheduled to run. This continuous process can lead to a busy loop. Thread A: Thread B: while (nxsem_get_value(&priv->wait, &semcount) >= 0 && <--- semcount <= 0) | 2)context switch { 1)contex switch | nxsem_post(&priv->wait); -------------> run some code and nxsem_wait again } Signed-off-by: dongjiuzhu1 <dongjiuzhu1@xiaomi.com> | 2 个月前 | |
drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> | 2 个月前 | |
drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> | 2 个月前 | |
fs/vfs: Separate file descriptors from file descriptions This patch is a rework of the NuttX file descriptor implementation. The goal is two-fold: 1. Improve POSIX compliance. The old implementation tied file description to inode only, not the file struct. POSIX however dictates otherwise. 2. Fix a bug with descriptor duplication (dup2() and dup3()). There is an existing race condition with this POSIX API that currently results in a kernel side crash. The crash occurs when a partially open / closed file descriptor is duplicated. The reason for the crash is that even if the descriptor is closed, the file might still be in use by the kernel (due to e.g. ongoing write to file). The open file data is changed by file_dup3() and this causes a crash in the device / drivers themselves as they lose access to the inode and private data. The fix is done by separating struct file into file and file descriptor structs. The file struct can live on even if the descriptor is closed, fixing the crash. This also fixes the POSIX issue, as two descriptors can now point to the same file. Signed-off-by: Ville Juven <ville.juven@unikie.com> Signed-off-by: dongjiuzhu1 <dongjiuzhu1@xiaomi.com> | 2 个月前 | |
drivers/misc/optee: Fix non-registered memory ref passing So far the NuttX implementation of OP-TEE has been using registered memory references to pass non-registered memory to OP-TEE OS, passing the physical address of the memory in what is normally used as a 'cookie'. This was compatible with the Openvela framework, but no other OP-TEE OS. Fix this by passing temporary memory instead with the standard non-contiguous (OPTEE_MSG_ATTR_NONCONTIG) flag. Signed-off-by: George Poulios <gpoulios@census-labs.com> Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
Remove @ and % tag from all comments and format the multiple line comments Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com> | 2 个月前 | |
drivers/misc/optee: Rename optee_shm_entry to optee_shm This is no longer (exactly) the linked list entry that it used to be, but rather an associated pointer in an idr tree entry. Plain 'optee_shm' is more concise, and more appropriate. Changes also reg_pair_to_uintptr() to reg_pair_to_ptr() for better readability in invocations. Signed-off-by: George Poulios <gpoulios@census-labs.com> Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
drivers/misc/optee: Add SMC backend for arm archs So far NuttX has supported OP-TEE interfacing over local and RPMsg sockets. This commit introduces support for direct invocation of OP-TEE through arm SMCs. The SMC transport is enabled through CONFIG_DEV_OPTEE_SMC. This SMC implementation has been tested only with arm64, OP-TEE rev 4.4. Note that it does not support reverse direction RPCs, i.e. from the Secure World to the Normal World to something like optee supplicant. A basic RPC handling skeleton is provided with implementation for some basic functions (alloc/free mem, and foreign interrupts) but no supplicant command handling. (+one minor change s/parm/param in arch/arm64/include/syscall to satisfy the spellchecker during PR) Signed-off-by: George Poulios <gpoulios@census-labs.com> Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
drivers/misc/optee.c: Add shm registration support Adds support for SHM_REGISTER IOCTL. Registration can be requested both against the driver (for automatic cleanup) and against the secure OS (for sharing). Introduces also optee_{msg,free}_alloc() to allocate aligned memory for message arguments depending on the alignment specified in the driver's private data. For alignment greater than word size, memory is allocated on the heap, otherwise it's allocated on the stack (similar to the previous implementation but using alloca() instead). Signed-off-by: George Poulios <gpoulios@census-labs.com> Signed-off-by: hujun5 <hujun5@xiaomi.com> | 2 个月前 | |
ramdisk.c: support ramdisk_unregister function. Signed-off-by: wangshaoxin <wangshaoxin@xiaomi.com> | 2 个月前 | |
misc/rpmsgblk: should wait the bound state in all operations Use rpmsgblk_get_tx_payload_buffer() in rpmsgblk_send_recv() to check the bound state, so all rpmsgblk operations will wait bound with peer. Signed-off-by: wangshaoxin <wangshaoxin@xiaomi.com> | 2 个月前 | |
drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> | 2 个月前 | |
Revert "rpmsg services: Add time consuming operation to rpmsg deferd work queue." This reverts commit f37afffbcc7664ccf6879822a076416b1773744a. Reason for revert: change rpmsg defer work logic Signed-off-by: Yongrong Wang <wangyongrong@xiaomi.com> | 2 个月前 | |
rpmsgdev.c: use shmem buf to replace local variables because user buffer maybe operate in other thread, when enable the stack MPU pretection, it will cause a crash Signed-off-by: Yongrong Wang <wangyongrong@xiaomi.com> | 2 个月前 | |
drivers/rpmsgdev: support rpmsgdev block read mode Signed-off-by: rongyichang <rongyichang@xiaomi.com> | 2 个月前 | |
sched/wqueue: Fix coverity, MISRA C-2012 Rule 10.1, 10.3, 11.1, 11.3, 11.4(Type conversion). Signed-off-by: jiangtao16 <jiangtao16@xiaomi.com> | 2 个月前 | |
drivers: migrate to SPDX identifier Most tools used for compliance and SBOM generation use SPDX identifiers This change brings us a step closer to an easy SBOM generation. Signed-off-by: Alin Jerpelea <alin.jerpelea@sony.com> | 2 个月前 |