Skip to content

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

VynDragon
Copy link
Collaborator

@VynDragon VynDragon commented Apr 25, 2025

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).

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>
Copy link

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff
hal_bouffalolab zephyrproject-rtos/hal_bouffalolab@c6c44b8 (main) ❌ Impostor SHA: zephyrproject-rtos/hal_bouffalolab@308356a zephyrproject-rtos/hal_bouffalolab@c6c44b87..308356a7

DNM label due to: 1 impostor SHA

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@github-actions github-actions bot added manifest manifest-hal_bouffalolab DNM (manifest) This PR should not be merged (controlled by action-manifest) labels Apr 25, 2025
Copy link
Member

@henrikbrixandersen henrikbrixandersen left a 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?

@VynDragon
Copy link
Collaborator Author

VynDragon commented Apr 26, 2025

Is the EEPROM API really the correct one to use here?

That is one of the main questions yea, what alternatives is there?

@henrikbrixandersen
Copy link
Member

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?

@VynDragon
Copy link
Collaborator Author

VynDragon commented Apr 26, 2025

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DNM (manifest) This PR should not be merged (controlled by action-manifest) manifest manifest-hal_bouffalolab
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants