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
Is your enhancement proposal related to a problem? Please describe.
There are no protections against simultaneous i2c transactions colliding on the same bus. Identical to #29239.
Describe the solution you'd like
It seems like consensus from issues like #24511 is that a global i2c lock is the way to go, but I don't know what the status of that is.
Proposed change
Implement a locking semaphore for i2c_sam0_configure and i2c_sam0_transfer.
The text was updated successfully, but these errors were encountered:
Is your enhancement proposal related to a problem? Please describe.
There are no protections against simultaneous i2c transactions colliding on the same bus. Identical to #29239.
Describe the solution you'd like
It seems like consensus from issues like #24511 is that a global i2c lock is the way to go, but I don't know what the status of that is.
Proposed change
Implement a locking semaphore for
i2c_sam0_configure
andi2c_sam0_transfer
.The text was updated successfully, but these errors were encountered: