Oopenvela-robotfix the compilation error
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
drivers/usbdev/mtp: support build usb mtp with cmake Signed-off-by: yangsong8 <yangsong8@xiaomi.com> | 2 个月前 | |
driver/serial/cdcacm: config to enable or disable txbuf To be compatible with the previous method, add a buf between cdcacm and serial. Because when using usbreqbuf directly as the buf of serial, the amount of data sent may be insufficient due to the limit of the number of reqs. For example, when the number of reqs is 4, the number of data send through cdcacm is 5, and each data is a separate USB packet, if the host does not read in time, resulting in blocking send. Signed-off-by: yangsong8 <yangsong8@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 个月前 | |
driver/usbdev: fix cdcacm wr container missing issue in cdcacm_sndpacket, If if (priv->wrcontainer) is true, then priv->wrcontainer is set to NULL. If an interrupt occurs before priv->wrcontainer is reassigned after being NULL, priv->wrcontainer will be reassigned once during the interrupt, and nwrq-- will be called, but no data will be sent at this time. Only when data is sent by calling txint will priv->wrcontainer be reassigned and nwrq-- called again. This causes the issue. Signed-off-by: yangsong8 <yangsong8@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 个月前 | |
drivers/usbdev: replace critical_section with mutex_t Signed-off-by: zhanghongyu <zhanghongyu@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 个月前 | |
fix the compilation error error: implicit declaration of function 'nxmutex_lock' Signed-off-by: v-tangmeng <v-tangmeng@xiaomi.com> | 2 个月前 | |
driver/usbdev: Use small lock to protect composite device Use spin lock to replace enter_critical_section Signed-off-by: yangsong8 <yangsong8@xiaomi.com> | 2 个月前 | |
driver/usbdev: Use small lock to protect composite device Use spin lock to replace enter_critical_section Signed-off-by: yangsong8 <yangsong8@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 个月前 | |
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: fix compile error. 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> | 2 个月前 | |
fix the compilation error 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> | 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 个月前 | |
driver/usbdev: Use small lock to protect usbdev fs Use spin lock to replace enter_critical_section Signed-off-by: yangsong8 <yangsong8@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 个月前 | |
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/usbdev: Fix usbtrace lock unpaired issue Signed-off-by: yangsong8 <yangsong8@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/usbdev: Use small lock to protect usbdev msc Signed-off-by: yangsong8 <yangsong8@xiaomi.com> | 2 个月前 | |
drivers/usbdev: Use small lock to protect usbdev msc Signed-off-by: yangsong8 <yangsong8@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/usbdev: Use small lock to protect usbdev msc Signed-off-by: yangsong8 <yangsong8@xiaomi.com> | 2 个月前 |