Closed rivos-eblot closed 1 year ago
Looks good to me. Can you give a little bit of context for why this is necessary? At the moment it seems that all the logic is still the otp earlgrey implementation, do you plans to make parts of the OTP generic and part of it platform specific?
This commit enables support other OTP mappings. As all RISC-V (hence OT) machines are built at the same time, we need an indirection so access platform-specific OTP data. OT components that do not depend on the OTP backend need to access to OTP content without a reference to a specific OTP implementation.
Looks good to me. Can you give a little bit of context for why this is necessary? At the moment it seems that all the logic is still the otp earlgrey implementation, do you plans to make parts of the OTP generic and part of it platform specific?