fix STM I2C compiler inline issue

[hallard]

Summary of changes

fixed #15379

Documentation

removed inline that trigger link issues on STM32WL as @0xc0170 proposal in #15379

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

@0xc0170 @jeromecoutant

---

[0xc0170]

One slight improvement would be just mark it as static (it's internal helper as I understood

[0xc0170]

Let me know if you want to update it and we can test it afterwards

[hallard]

if static won't prevent compiler to optimize it as inline it's fine for me, anyway I like the MBED_FORCEINLINE option, works for some time on my side

[0xc0170]

it should work the same way as the funciton below (

mbed-os/targets/TARGET_STM/i2c_api.c

Line 909 in e55852c

static void prep_for_restart_if_needed(struct i2c_s *obj_s) {

).

[hallard]

sure but as it's just a var check and return, for performance and overhead I really prefer to see it as inline (as it was when created) and avoid potential "is the compiler his doing is job correctly", as this fix is needed because it don't.

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️