Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update error handling for SDHCI tuning #181

Draft
wants to merge 3 commits into
base: nilrt/master/6.1
Choose a base branch
from

Conversation

erickshepherdNI
Copy link
Contributor

@erickshepherdNI erickshepherdNI commented Nov 13, 2024

This pull request reverts our previous commit to handle tuning interrupts in favor of the upstream commit that does the same thing.

This pull request also includes a fix for the sdhci_execute_tuning function, which was not actually returning the result of the underlying tuning function. This caused multiple retuning attempts for DDR50 cards, which cannot always be tuned, that led to an I/O error. This change updates sdhci_execute_tuning to return the error code which causes tuning to be disabled after the first attempt.

Testing

I built the kernel and installed it on two different setups that both use DDR50 SD cards. Previously only one setup reproduced the I/O error that resulted from repeated retuning. After installing the kernel both systems reported that the initial DDR50 tuning failed, but no other issues appeared in the dmesg logs and I was able to read and write to the SD cards on both systems.

The sdhci_execute_tuning function was not actually returning the result
of the underlying tuning function. This caused multiple retuning
attempts for DDR50 cards, which cannot always be tuned, that led to an
I/O error. This change updates sdhci_execute_tuning to return the error
code which causes tuning to be disabled after the first attempt.

Signed-off-by: Erick Shepherd <[email protected]>
@erickshepherdNI erickshepherdNI marked this pull request as draft November 13, 2024 22:16
@erickshepherdNI
Copy link
Contributor Author

I'm continuing to investigate this issue further and may need to make additional changes. I've converted this to a draft until it is ready to go in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant