Skip to content

MERU800BIA/BFA: Initialize PSUs with write-protect#474

Open
aalamsi22 wants to merge 3 commits into
facebook:mainfrom
aalamsi22:meru_pmbus_wp
Open

MERU800BIA/BFA: Initialize PSUs with write-protect#474
aalamsi22 wants to merge 3 commits into
facebook:mainfrom
aalamsi22:meru_pmbus_wp

Conversation

@aalamsi22

Copy link
Copy Markdown
Contributor

Description

Some registers when read, cause the psu to raise an error through the status_cml register at 0x7e. This is normal for some PSUs with unsupported registers. However, problems arise when the write-protect is disabled, the linux pmbus driver sees the status register reporting an error and decides to ignore the valid values it reads.

Motivation

While this issue shouldn't hit because the WP register is enabled by default when the PSU turns on, this change ensures that WP is enabled in the rare cases where a WP may have been disabled manually or by another process prior to setting up fboss on the system.

Testing

Manually disabled WP and confirmed platform manager enables it again. All expected psu sensors are read successfully.

@joancaneus

Copy link
Copy Markdown
Contributor

@aalamsi22 Does this PR change require BSP version 0.7.10 ?

I am just trying to understand if the same comments in #441 also apply to it.

@aalamsi22

Copy link
Copy Markdown
Contributor Author

@aalamsi22 Does this PR change require BSP version 0.7.10 ?

I am just trying to understand if the same comments in #441 also apply to it.

No, this is independent of the bsp.

@facebook-github-bot

Copy link
Copy Markdown
Contributor

@joancaneus has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot

Copy link
Copy Markdown
Contributor

@aalamsi22 has updated the pull request. You must reimport the pull request before landing.

@facebook-github-bot

Copy link
Copy Markdown
Contributor

@joancaneus has imported this pull request. If you are a Meta employee, you can view this in D76944650.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

3 participants