usbdev/rndis.c: In function 'rndis_allocnetreq':
usbdev/rndis.c:761:10: error: implicit declaration of function 'nxmutex_lock'; did you mean 'net_mutex_lock'? [-Werror=implicit-function-declaration]
761 | while (nxmutex_lock(&priv->lock) < 0);
| ^~~~~~~~~~~~
| net_mutex_lock
usbdev/rndis.c:767:7: error: implicit declaration of function 'nxmutex_unlock' [-Werror=implicit-function-declaration]
767 | nxmutex_unlock(&priv->lock);
| ^~~~~~~~~~~~~~
usbdev/rndis.c: In function 'usbclass_classobject':
usbdev/rndis.c:2890:3: error: implicit declaration of function 'nxmutex_init'; did you mean 'nxsem_init'? [-Werror=implicit-function-declaration]
2890 | nxmutex_init(&priv->lock);
| ^~~~~~~~~~~~
| nxsem_init
usbdev/rndis.c: In function 'usbclass_uninitialize':
usbdev/rndis.c:2939:3: error: implicit declaration of function 'nxmutex_destroy'; did you mean 'nxsem_destroy'? [-Werror=implicit-function-declaration]
2939 | nxmutex_destroy(&drvr->dev->lock);
| ^~~~~~~~~~~~~~~
| nxsem_destroy
cc1: all warnings being treated as errors
Signed-off-by: v-tangmeng <v-tangmeng@xiaomi.com>
error: implicit declaration of function 'enter_critical_section'
[-Werror=implicit-function-declaration]
error: implicit declaration of function 'leave_critical_section'
[-Werror=implicit-function-declaration]
Signed-off-by: v-tangmeng <v-tangmeng@xiaomi.com>
This commit provided a better recursive spinlock implementation with
less memory-overhead and better performance.
Signed-off-by: ouyangxiangzhen <ouyangxiangzhen@xiaomi.com>
Modify the kernel to use only atomic_xx and atomic64_xx interfaces,
avoiding the use of sizeof or typeof to determine the type of
atomic operations, thereby simplifying the kernel's atomic
interface operations.
Signed-off-by: zhangyuan29 <zhangyuan29@xiaomi.com>
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>
currently, nuttx implements readv/writev on the top of read/write.
while it might work for the simplest cases, it's broken by design.
for example, it's impossible to make it work correctly for files
which need to preserve data boundaries without allocating a single
contiguous buffer. (udp socket, some character devices, etc)
this change is a start of the migration to a better design.
that is, implement read/write on the top of readv/writev.
to avoid a single huge change, following things will NOT be done in
this commit:
* fix actual bugs caused by the original readv-based-on-read design.
(cf. https://github.com/apache/nuttx/pull/12674)
* adapt filesystems/drivers to actually benefit from the new interface.
(except a few trivial examples)
* eventually retire the old interface.
* retire read/write syscalls. implement them in libc instead.
* pread/pwrite/preadv/pwritev (except the introduction of struct uio,
which is a preparation to back these variations with the new
interface.)
input/aw86225.c: In function 'aw86225_ram_work_routine':
input/aw86225.c:1976:27: warning: 'rtp_file.data' may be used uninitialized [-Wmaybe-uninitialized]
1976 | struct aw86225_firmware rtp_file;
| ^~~~~~~~
In function 'aw86225_ram_loaded',
inlined from 'aw86225_ram_work_routine' at input/aw86225.c:1982:3:
input/aw86225.c:1445:17: warning: 'rtp_file.size' may be used uninitialized [-Wmaybe-uninitialized]
1445 | for (i = 2; i < cont->size; i++)
| ~~^~~~~~~~~~~~
input/aw86225.c: In function 'aw86225_ram_work_routine':
input/aw86225.c:1976:27: note: 'rtp_file.size' was declared here
1976 | struct aw86225_firmware rtp_file;
Signed-off-by: fangpeina <fangpeina@xiaomi.com>
For resource-constrained devices, simulate RTP
playback effects using preset custom RAMLOOP
combinations instead of using RTP files to play
custom vibration effects.
Signed-off-by: fangpeina <fangpeina@xiaomi.com>
1. The -c parameter should not be added during the link phase, otherwise the link will fail.
2. If it is the clang compiler, its toolchain library should use --print-file-name to find it, otherwise an error will occur
Signed-off-by: wangmingrong1 <wangmingrong1@xiaomi.com>
This patch fixed userspace headers conflict. Architecture-related definition and API should not be exposed to users.
Signed-off-by: ouyangxiangzhen <ouyangxiangzhen@xiaomi.com>
Change syslog API naming more reasonable:
1. rename syslog_channel() to syslog_channel_register()
2. rename syslog_channel_remove() to syslog_channel_unregister()
Signed-off-by: chao an <anchao@lixiang.com>
hujun5
v-tangmeng