search

zephyrproject-rtos / zephyr

Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
https://docs.zephyrproject.org
Apache License 2.0
10.66k stars 6.52k forks source link

Reenable 1.8V SD card signalling on RT600 Platform #38575

Open danieldegrasse opened 3 years ago

danieldegrasse commented 3 years ago

Is your enhancement proposal related to a problem? Please describe. The current USDHC driver for the NXP RT600 evaluation kit does not properly support operating SD cards at 1.8V signalling, and will fail to mount an SD card that attempts to utilize 1.8V signalling instead of the standard 3.3V.

Describe the solution you'd like PR #38507 fixes this issue temporarily by disabling 1.8V signalling within the driver when running on this board. However, 1.8V signalling support would be preferable for power consumption. The evaluation board controls the signalling voltage level via a PMIC, which Zephyr does not support interfacing with.

Ideally, the PMIC should be accessible within Zephyr to enable utilizing SD cards at 1.8V on this evaluation board. This could be accomplished via adding board-specific code to interface with the PMIC, or via creating a driver api for PMIC devices and integrating the existing PMIC driver into Zephyr.

Describe alternatives you've considered The simplest solution is likely to add board-specific code for this PMIC. The only alternative I've considered is creating a driver API, but this would likely be a secondary step after fixing the initial issue with 1.8V signalling on this board given how large of a change it requires.

danieldegrasse commented 3 years ago

PR #38580 should fix this issue correctly, by enabling the RT685 PMIC and interfacing with it to reduce the voltage

zephyrbot commented 8 months ago

Hi @dleach02,

This issue, marked as an Enhancement, was opened a while ago and did not get any traction. It was just assigned to you based on the labels. If you don't consider yourself the right person to address this issue, please re-assing it to the right person.

Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.

@danieldegrasse you are also encouraged to help moving this issue forward by providing additional information and confirming this request/issue is still relevant to you.

Thanks!