rt-thread.git/bsp/cvitek/drivers, branch v5.2.2Unnamed repository; edit this file 'description' to name the repository.http://cgit.235523.xyz/rt-thread.git/atom/bsp/cvitek/drivers?h=v5.2.22025-10-28T06:13:56Zfeat:clang format ignore migration2025-10-28T06:13:56Zache11971248+zhou-strontium-qi@user.noreply.gitee.com2025-10-21T14:36:53Zurn:sha1:36bf8f656b230e4c3f8fd4ee8a6ac16ac958a077Fix the crash of the SPI driver under the smart mode2025-07-04T12:51:04Zflyingcysflyingcys@163.com2025-07-01T14:58:40Zurn:sha1:f4168669a71449133184167987595a56591d4bdf
Signed-off-by: flyingcys flyingcys@163.com
bsp: cvitek: fix build warnings for spi2025-03-24T12:38:08ZChen Wangunicorn_wang@outlook.com2025-03-24T02:16:32Zurn:sha1:5b88c8c207268cb74d5cc69654787d2c26c2f1a9
See https://github.com/RT-Thread/rt-thread/issues/10138.
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
[bsp][cvitek] fix spi driver build error2025-03-24T01:24:11Zimcuign7798540@gmail.com2025-03-21T06:25:06Zurn:sha1:6073200d2e9978b1180cabca28cdd307a8da9de9
Build error: 'struct _device_spi' has no member named 'base_addr'
Analyze: the name should be dws.regs
Solution: change base_addr to dws.regs
Signed-off-by: zdtyuiop4444 <ign7798540@gmail.com>
bsp: cvitek: remove support for spinor/spinand2025-01-08T22:54:14ZChen Wangunicorn_wang@outlook.com2025-01-08T02:59:11Zurn:sha1:2322f0154ecc0736e75750af74d403ca76b17576
Confirmed with milkv, only the sd card version is sold
by default for duo in the market. The spi pins are
provided through stamp holes, so that users can solder
the corresponding components on their baseboard during
secondary development.
In order to simplify maintenance work, the mainline
will only support the sd-card version and no longer
support spinor/spinand.
Updated config files the same in this patch.
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
bsp: cvitek: use ioremap for arm64 core2024-12-30T03:32:10ZChen Wangunicorn_wang@outlook.com2024-12-25T05:39:40Zurn:sha1:b774c9b9388aee64922761afb1e4af471e8173b1
For ARM, RT-smart and RT-standard both enable mmc (see
rt_hw_board_init() in bsp/cvitek/cv18xx_aarch64/board/board.c,
rt_hw_mmu_setup is called both for smart or standard).
So ioremap is must to do for ARM.
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
bsp: cvitek: remove GPL license declaration2024-12-19T14:39:47ZChen Wangunicorn_wang@outlook.com2024-12-19T08:13:14Zurn:sha1:6a7e797712ff7b297a2dd9367942656bfc42e460
GPL is conflict with Apache, which is used by RTT.
See <https://www.apache.org/licenses/GPL-compatibility.html>
Also clean up and remove some words such "LINUX".
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
bsp: cvitek: fix warning on rtc driver2024-11-27T02:45:00ZChen Wangunicorn_wang@outlook.com2024-11-26T06:57:15Zurn:sha1:16475b3c9231305a929d98ebd27e1ea77b33284d
When RTC is enabled, a warning appear during compiling:
warning: implicit declaration of function 'rtc_alarm_enable' [-Wimplicit-function-declaration]
366 | rtc_alarm_enable(alarm->enable);
| ^~~~~~~~~~~~~~~~
It's due to _rtc_set_alarm is not covered by RT_USING_ALARM. It's wrong.
Solution: cover all functions including _rtc_get_alarm & _rtc_set_alarm
under RT_USING_ALARM macro conditional defintion.
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
bsp: cvitek: support mount fat/ext rootfs for rt-smart2024-11-27T02:45:00ZChen Wangunicorn_wang@outlook.com2024-11-26T02:37:43Zurn:sha1:032fe9c3a3dbfdcb338ef7ff5f0023c8f20d6b30
Support mount rootfs automaticly during booting up.
First try ext, then fat.
Plus some code cleanup, such as remove BSP_USING_ON_CHIP_FLASH_FS,
which is not defined and unused.
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
bsp: cvitek: 906b: romfs -> diskfs2024-11-27T02:45:00ZChen Wangunicorn_wang@outlook.com2024-11-26T01:23:01Zurn:sha1:1052f99537c31c38dc1aad39cec3d8fd38a06a2c
ROMFS is Read-Only Memory Filesystem. But ext4/fat are not read-only.
So renamed:
- mnt_romfs.c -> mnt_diskfs.c
- BSP_ROOTFS_TYPE_ROMFS -> BSP_ROOTFS_TYPE_DISKFS
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>