-
Notifications
You must be signed in to change notification settings - Fork 7.3k
drivers: eeprom: bflb efuses #89108
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
base: main
Are you sure you want to change the base?
drivers: eeprom: bflb efuses #89108
Conversation
This sets revision to the one with vendor headers from final hal version Signed-off-by: Camille BAUD <mail@massdriver.space>
This introduces a driver used to access bouffalolab efuses via eeprom API Signed-off-by: Camille BAUD <mail@massdriver.space>
This enables the driver by default, it will be needed at init in the future Signed-off-by: Camille BAUD <mail@massdriver.space>
The following west manifest projects have changed revision in this Pull Request:
⛔ DNM label due to: 1 impostor SHA Note: This message is automatically posted and updated by the Manifest GitHub Action. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the EEPROM API really the correct one to use here?
That is one of the main questions yea, what alternatives is there? |
If you are just reading the eFUSE settings, perhaps the syscon API is better suited? |
It looks like it would fit yea... Is there any example driver for it that doesnt just read memory actually? Or would that be a first driver for a syscon interface? |
This introduces bflb efuse access via eeprom api.
This is not used at the moment but will be in the next steps of integration (for clock_control and things like DAC and ADC).