| Age | Commit message (Collapse) | Author |
|---|
|
Open Kconfig will not fail if using osource,
This way can make SoC Kconfig to DM easy.
Link: ecb89b1370ec27be650a0a2fae7c6802b4246933
Signed-off-by: GuEe-GUI <[email protected]>
|
|
Signed-off-by: GuEe-GUI <[email protected]>
|
|
Don't use `irq` as a var when clear MSI global
irq map, the irq which alloc before will rewrite.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
Signed-off-by: GuEe-GUI <[email protected]>
|
|
1. remove gpt.
2. remove block device custom.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
1. Disk and blk device management.
2. Support partitions probe auto.
3. Support DFS and user mode fops, ioctl.
4. Add a cmd for blk info.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
MFD (Multifunction device) with System Controller Register Read/Write.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
Signed-off-by: GuEe-GUI <[email protected]>
|
|
1. Default return OK when input NULL (if is not necessary in device).
2. Support object parse in OFW.
3. Support CLK depends fix auto.
4. Fixup rt_clk_array_prepare_enable and rt_clk_array_disable_unprepare.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
old phy bus is too simple add phy_bus is not adapt rt_bus framework,so writer a stronger phy bus framework.
here is my commit message:
add mdio bus and phy bus to kernel,the phy bus use rt_bus framewok ,driver writer can write phy_driver first .when mac driver need to use phy they can register phy_device and pjhy_devie will serach for driver which match by uid and mask,if no driver match with the device that you register,phy_bus will return the genphy to you device,the genphy driver is the general driver for phy,so you can use it but it can not support the capcity of chip it may be cause performance is not up to peak
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Signed-off-by: GuEe-GUI <[email protected]>
|
|
We need a API to fix the driver load auto when
a second driver get it in probe process that
we can not be careful of the driver-to-driver's
depends in different SoC.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
Signed-off-by: GuEe-GUI <[email protected]>
|
|
The drivers will support OFW and name probe both.
We should make build OK when OFW is disable.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
Drivers can manage their own IDs without having to concern
themselves with the register/unregister in system
Link: https://github.com/RT-Thread/rt-thread/issues/9534
Signed-off-by: GuEe-GUI <[email protected]>
|
|
|
|
mac address
|
|
|
|
This reverts commit ea75800d5b3be3e63c6304afed8b06a3fdeae289.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fix milkv-duos-sd cann't startup big-core kernel
milkv-duos-sd use cv1813h folder store ld file
Signed-off-by: flyingcys <[email protected]>
|
|
Improved README document
- Unified the usage process of Standard Edition and Smart Edition.
- Deleted the description of running RTT in Machine Mode. Currently,
both Standard Edition and Smart Edition RTT run in S-mode by default.
At the same time, some unnecessary scripts were cleaned up.
Signed-off-by: Chen Wang <[email protected]>
|
|
initliz… (#9643)
* add spi custom configuration function and enhance muti object initlization and setting
* update changelog
* submit ci files
* fix ci file
* update
* formatting
* delete yaml files
* fix ble ci file
* fix undefined reference to app_main error
* update
|
|
|
|
导致异常
|
|
POSIX.1 says:
> read() attempts to read up to count bytes from file descriptor fd
> into the buffer starting at buf.
On the other hand, for rt_device_read, the `@size` is defined as the
number of unit (block size for blk device, otherwise one byte).
Changes:
- Transferred unit size from POSIX R/W(in bytes) to rt_device_R/W during
request of file R/W operations.
Signed-off-by: Shell <[email protected]>
|
|
* [bsp][nxp][mcxa153] add more UART channels
|
|
|
|
The `struct stat` object used inside mount(2) is uninitialized, which
can lead to undefined behavior during running
Changes:
- Set zero to buffer before calling to stat()
Signed-off-by: Shell <[email protected]>
|
|
|
|
* [tools] fix the SDK path issue in env script.
* [tools] add project.json generation in vsc.py.
* [tools] provide correct and clear comments in vsc.py
|
|
|
|
|
|
|
|
|
