Apply this change to 2.0.9

[SuGlider]

Description of Change

This change is missing in 2.0.9 (master).
Fixes F_CPU for all SoC.

Tests scenarios

Related links

#Fix #8005
#7913

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ SuGlider
❌ devrim-oguz
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[SuGlider]

@me-no-dev -
This PR should be also in 2.0.9, but not for 3.0.0 which has another PR for fixing it ( #8007 ).
It is already in release/2.x branch ( #7913 )
Not sure what is the right way to do it. Please advise.

[me-no-dev]

@SuGlider if it's in release/v2.x then it will be in 2.0.9. No need to PR master, because it will go into 3.0.0 also that way.

[SuGlider]

@SuGlider if it's in release/v2.x then it will be in 2.0.9. No need to PR master, because it will go into 3.0.0 also that way.

It was already in release/v2.x and it didn't go to 2.0.8, when it was released...
That is the reason I think that it doesn't happen automatically.

[mrengineer7777]

@SuGlider you have an extra contributor that is blocking the license agreement

[me-no-dev]

@SuGlider if it's in release/v2.x then it will be in 2.0.9. No need to PR master, because it will go into 3.0.0 also that way.

It was already in release/v2.x and it didn't go to 2.0.8, when it was released... That is the reason I think that it doesn't happen automatically.

I might have an idea of what went wrong... 2.0.9 will be fine

[VojtechBartoska]

@SuGlider can we change a PR title to something more specific? Right now, it's without any meaning for e.g. Release notes, thanks.

[mrengineer7777]

Suggested title: "Fix F_CPU for all SoCs".
If me-no-dev wants to merge this (likely not, see above), then suglider also needs to fix the contributor.