-
Notifications
You must be signed in to change notification settings - Fork 2k
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
periph/i2c: added means to make I2C thread-safe #2323
Conversation
ACK |
@thomaseichinger did you link this PR in issue #2314? If so, do you want to change all other i2c implementations in here? I could also adapt some, just want to avoid that our work collides |
As discussed in RIOT-OS#2289 this changes provide means to use the i2c interface safely within multible threads.
98f3150
to
830b2b2
Compare
@PeterKietzmann I did, updated adopting all other existing i2c implementations. |
Ah haven't seen this. Ok I'll go through the commits |
@PeterKietzmann As the proposed concept doesn't break the current usage of the interface I decided to adopt i2c's uses separately. Would you mind taking over this task? |
@thomaseichinger. ACK for this PR. I could adapt the uses. Thanks for the list in #2314. I'll register my name to some , just to avoid collisions if someone else hops in. If not, i'll adapt all within the next days |
Everything is fine. ACK |
periph/i2c: added means to make I2C thread-safe
As discussed in #2289 this changes provide means to use the i2c interface safely within multiple threads. Missing implementations will be provided as the concept is accepted. Implementation is analog to #2290.