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

drivers: stm32_i2c: use compatible st,stm32mp15-i2c-non-secure #7172

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

etienne-lms
Copy link
Contributor

Update STM32 I2C driver use st,stm32mp15-i2c-non-secure specific DT compatible property for when the I2C bus is non-secure. Update STM32MP15 based DH boards accordingly.

Update stm32mp15 based DH boards DTS file to explicitly use non-secure
I2C4 bus as set in the ETZPC node st,decprot property.

Signed-off-by: Etienne Carriere <[email protected]>
@GseoC
Copy link
Contributor

GseoC commented Dec 10, 2024

Edit: Some comments

core/drivers/stm32_i2c.c Outdated Show resolved Hide resolved
core/include/drivers/stm32_i2c.h Show resolved Hide resolved
@GseoC
Copy link
Contributor

GseoC commented Dec 10, 2024

Acked-by: Gatien Chevallier <[email protected]>

@etienne-lms
Copy link
Contributor Author

@jneuhauser, are you okay with this change?

Change STM32 I2C driver to rely on the compatible DT property of the
node to store whether the bus is expected assigned to secure or
non-secure world. Using a non-secure I2C bus in OP-TEE on stm32mp1
platforms is something expected only on STM32MP15 variant for
compatibility with platform already supported in upstream Linux/U-Boot
components, as defined by st,stm32mp15-i2c-non-secure specific
compatible string ID.

Signed-off-by: Etienne Carriere <[email protected]>
Acked-by: Gatien Chevallier <[email protected]>
@etienne-lms
Copy link
Contributor Author

Review tag applied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants