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

Configure clock switch via IPMI and save it to the FRU EEPROM #123

Closed
augustofg opened this issue Mar 7, 2022 · 2 comments · Fixed by #165
Closed

Configure clock switch via IPMI and save it to the FRU EEPROM #123

augustofg opened this issue Mar 7, 2022 · 2 comments · Fixed by #165

Comments

@augustofg
Copy link
Member

The clock switch configuration shouldn't be hard-coded to the MMC firmware. Instead, it should be loaded from the EEPROM and configured via IPMI. The AFCv3.1 port supports changing the adn4604 configuration via IPMI, but it doesn't expose a way to read the current configuration and store it in the EEPROM.

If possible, design an agnostic IPMI message API that can be used for adn4604 and idt_8v54816.

@augustofg
Copy link
Member Author

For the IPMI / EEPROM API I propose using the 8V54816ANLG register layout as it is very simple and direct to the point, then for the AFCv3.1 translate it to something that makes sense:
screenshot-2023-08-02_14-35-31

@augustofg
Copy link
Member Author

augustofg commented Aug 2, 2023

So, for the AFCv3.1 (ADN4604ASVZ) boards I've come with the following scheme:

  • Port I/O (bit 7): Ignored, input and outputs are fixed Use it to enable or disable the output, '0' output disabled, '1' output enabled;
  • Termination On/Off (bit 6): Ignored, ADN4604ASVZ doesn't have individual port termination control (one bit controls 8 ports). All inputs will have its terminators ON;
  • Polarity (bit 5): ADN4604ASVZ only allow changing the polarity of input ports, so this will only apply its inputs;
  • Output Port Signal Source (bits 0 to 3): Select the input port for the respective output port.

@gustavosr8 gustavosr8 linked a pull request Aug 16, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants