| Age | Commit message (Collapse) | Author |
|
* [sdio][dm] import Kconfig for DM
Signed-off-by: GuEe-GUI <[email protected]>
* [sdio] fixup IRQ and mmcsd threads' stack size default
Signed-off-by: GuEe-GUI <[email protected]>
* [sdio][dm] Support DM mode
1. Support features read by DM.
2. Support regulator API in drivers.
3. Support send tuning option CMD.
4. Replace `switch_uhs_voltage` by `signal_voltage_switch`.
Signed-off-by: GuEe-GUI <[email protected]>
* [dm][sdhci] Cleanup the SDHCI
Signed-off-by: GuEe-GUI <[email protected]>
* [sdio][dm] add new SDIO/SDHCI drivers
1. SDHCI support on PCI bus
2. Synopsys DesignWare MMC Family(MMIO/PCI)
Signed-off-by: GuEe-GUI <[email protected]>
---------
Signed-off-by: GuEe-GUI <[email protected]>
|
|
high-speed ddr mode #11037
|
|
|
|
|
|
1. remove gpt.
2. remove block device custom.
Signed-off-by: GuEe-GUI <[email protected]>
|
|
https://github.com/RT-Thread/rt-thread/pull/9420
|
|
- corrected the default value for max_data_rate variable
Signed-off-by: Fan YANG <[email protected]>
|
|
|
|
|
|
整理 components/drivers 的 Kconfig
|
|
Update sd.c
|
|
Update sd.c
|
|
- added SDR50, SDR104 and DDR50 support to SD driver
Signed-off-by: Fan YANG <[email protected]>
|
|
- added HS400 supprt (both eMMC5.0 and eMMC5.1 flavor are supported)
Signed-off-by: Fan YANG <[email protected]>
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Fan YANG <[email protected]>
|
|
|
|
|
|
|
|
rt_ssize_t can give negative error code, which follows the unix style correctly
|
|
|
|
|
|
* Synchronize the code of the rt mart branch to the master branch.
* TTY device
* Add lwP code from rt-smart
* Add vnode in DFS, but DFS will be re-write for rt-smart
* There are three libcpu for rt-smart:
* arm/cortex-a, arm/aarch64
* riscv64
Co-authored-by: Rbb666 <[email protected]>
Co-authored-by: zhkag <[email protected]>
|
|
修改SD检测线程函数里面的延时实现,将mmcsd_delay_ms改为rt_thread_mdelay. mmcsd_delay_ms过时且延时计算错误。
|
|
|
|
When detecting all SDIO devices fails, it is also necessary to return information
|
|
* [fix] Fix simulator compilation warnings
* Update bsp/simulator/rtconfig_project.h
Co-authored-by: Man, Jianting (Meco) <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
1. New naming rule for multiple cards: sdXpY. Ex: sd0, sd0p0, sd0p1, sd1, sd1p0, sd1p1, .... sdXpY.
2. Always create super-node for backward-compatible and fdisk-like utility. EX: sd0, sd1, ..... sdX.
3. Shrink code.
|
|
|
|
|
|
1. Issue on traveling latest node in list if multi-partitions on card.
|
|
|
|
|
|
|
|
|
|
Try a few times before switching to other data widths.
The original strategy (simply wait for 20ms ) failed on STM32H743 with an MTFC4GACAJCN-4M (4GB EMMC) when switching data width.
(unless the debugging info is enabled, which add more delays)
With this EMMC, the fixed delay was set to 50ms for it to be able to work.
Instead of a fixed delay, I think we better change to trying a few more times with smaller delays.
|
|
|
|
|
|
framework.
|
|
Currently RTT mmc stack only support Highspeed mode or
blow, which means the max speed should be 52MHz according
to JEDEC spec. Two problems show here:
(1) max_data_rate = (unsigned int)-1. The value of unsigned int
depends on compilers/arch. Moreover, it makes no sense to assume
cpu addressing width with IP clock rate limit.
(1)hs_max_data_rate was set to 200MHz.
So what should BSP drivers do if 52MHz < max_data_rate < 200MHz?
Either it blindly sets a spec-violated clock rate to drive a Highspeed
card, or just adjust the clock rate internally. Both cases are
really bad for practice.
If the card claims to support Highspeed, we set the clock to not
to exceed 52MHz. Otherwise it should be set according to
card->max_data_rate parsed by ext_csd. This patch fixes it as-is,
and also simplify the code a lot.
Signed-off-by: Shawn Lin <[email protected]>
|
|
It makes no sense to try bus width if not supported by drivers or BSP,
since we know it must be failed. It saves a lot for booting in time
critical environment.
Signed-off-by: Shawn Lin <[email protected]>
|
|
If the whole sd card was formatted as a partition, current
code break out the loop mistakenly, so it skips dfs_mount_device
later. Simply remove the broken 'break' to solve this problem.
Signed-off-by: Shawn Lin <[email protected]>
|