Thermal drivers offer a generic mechanism for thermal management.
Usually it's made up of one or more thermal zones and cooling devices.
Each thermal zone contains its own temperature, trip points, and cooling devices.
All platforms with ACPI or OFW thermal support can use this driver.
Signed-off-by: GuEe-GUI <2991707448@qq.com>
1. There is only one GPIO device in System.
2. For Pin API input is pin number
3. Add sets pin debounce time API.
So we need a virtual pin for multi gpio chip.
Signed-off-by: GuEe-GUI <2991707448@qq.com>
1. Add the regulator driver framework.
2. Add the generic voltage and current regulator API support
for drivers.
Signed-off-by: GuEe-GUI <2991707448@qq.com>
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>
README.md: add introduction about how to make rootfs(fat) and
booting kernel with it.
Plus some cleanup for this documentation.
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
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>
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>
When RT_DEBUGING_AUTO_INIT is enabled, kenrel will add more
print message for auto init. However, the original format
easily causes the kernel printing and the init function printing
to be connected together, resulting in a confusing display
format.
For exmaple:
```
initialize lwip_system_initlwIP-2.0.3 initialized!
:0 done
```
Or
```
initialize sal_init[I/sal.skt] Socket Abstraction Layer initialize success.
:0 done
```
Solution: Add a carriage return to separate the kernel
printing and the init function printing.
After changing, the output will be:
```
initialize lwip_system_init
lwIP-2.0.3 initialized!
:0 done
```
Or
```
initialize sal_init
[I/sal.skt] Socket Abstraction Layer initialize success.
:0 done
```
Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
liuchao
Supper Thomas
Chasel
zhujiale
wumingzi
wdfk-prog
wycwyhwyq
yangpeng
flyingcys
hywing
kurisaw
ligr
Meco Man
GuEe-GUI
liminghui12
heyuanjie87
Chen Wang
GUI