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

What is the purpose of this commit #251

Open
Grubby0624 opened this issue Jul 29, 2024 · 2 comments
Open

What is the purpose of this commit #251

Grubby0624 opened this issue Jul 29, 2024 · 2 comments

Comments

@Grubby0624
Copy link

FAPI_TRY(mss::pmic::i2c::reg_write(i_pmic_target, TPS_REGS::RA3_BREADCRUMB, CLEAR_BREAD_CRUMBS));

I have a few questions about this commit: 43fd55aa243fe570b989da8f8ff9fcb893c7d218 "Added recovery procedure to DDR4 pmic_n_made_detect":
1. What is the purpose of this commit? If I don't add this commit and restart the machine after setting the PMIC output voltage bias, it can start up normally. However, if I add this commit, the I2C link to this PMIC will report an I2C No ACK error after booting up
2. I am using TPS53830 PMIC, and I understand that RA3 represents the I2C address for this model of PMIC. Why is its value changed to 0x00 here?
Thanks!!

@dcrowell77
Copy link
Collaborator

I think there was a typo in your commit hash above. Did you mean 43fd55a? If so, the commit is adding some logic to recover a dead PMIC at runtime. It has been working fine for us. Where in the IPL do you see the failure?

I'm asking around about the second question. If that is a different PMIC model than we use then our code may not support it. In our case RA3 seems to be just a scratch register with no functional use.

@dcrowell77
Copy link
Collaborator

Are you testing with DDIMMs or some other configuration? Do you have DDR4 or DDR5 memory? It appears that you are going down a DDR4 code path using a PMIC that we only support on the DDR5 DDIMMs. There are some implicit assumptions about which PMIC models are supported for which DDR versions that you seem to be violating.

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

No branches or pull requests

2 participants