You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PCI-SIG defines the operation of bus with SMBus and I3C mixed
If a component with supporting SMBus only is connected to a bus with SMBus and I3C mixed, it must operate as SMBus protocol.
However, Caliptra's Recovery I/F supports only I3C connection and does not support SMBus. So Recovery I/F does not work on the environment with SMBus and I3C mixed.
Does Caliptra project have a plan to support SMBus on Recovery I/F?
The text was updated successfully, but these errors were encountered:
PCI-SIG defines the operation of bus with SMBus and I3C mixed
If a component with supporting SMBus only is connected to a bus with SMBus and I3C mixed, it must operate as SMBus protocol.
from PCI Express Base Specification Revision 6.3(https://pcisig.com/specifications)
![Image](https://private-user-images.githubusercontent.com/139826405/410848787-c993be15-6dd8-4dce-8997-053ca6911df1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk0Nzc5ODgsIm5iZiI6MTczOTQ3NzY4OCwicGF0aCI6Ii8xMzk4MjY0MDUvNDEwODQ4Nzg3LWM5OTNiZTE1LTZkZDgtNGRjZS04OTk3LTA1M2NhNjkxMWRmMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjEzJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxM1QyMDE0NDhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01Y2YyMWFlNmY3MTQxNDA4ZTNiOTM5NzRiYThmYjRjYjY1MTkxZThjMTJmNGUxN2Y0NDVhYzIzYWMzZDEzMzUxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.3kt-aLaeJ9Js9ogt3eQfwCaRZNx8X56OxYjrwjJKd2c)
However, Caliptra's Recovery I/F supports only I3C connection and does not support SMBus. So Recovery I/F does not work on the environment with SMBus and I3C mixed.
Does Caliptra project have a plan to support SMBus on Recovery I/F?
The text was updated successfully, but these errors were encountered: