drivers: cc: mcux: Fix incorrect clock source of FlexSPI2

[Finomnis]

Due to the following in line 45, FlexSPI2 actually returned the frequency of FlexSPI1:

peripheral = (clock_name & IMX_CCM_PERIPHERAL_MASK);

The fix is to adjust the switch case to match the #1 + instance scheme of the other clocks.

Needs backporting to 3.7.

Fixes ##79288

[danieldegrasse]

Thanks for the fix, you have a few compliance issues that need to be fixed (you can fix up this commit and force push over the branch you sent the PR from):

61de4a34fba4b0a6a7958a60bb3bc12411f2095a: author email (Martin Stumpf [email protected]) needs to match one of the signed-off-by entries.
Error: See https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines for more details

1: UC2 Commit message does not contain a 'Signed-off-by:' line
1: UC6 Commit message body is empty, should at least have 1 line(s).
3: B6 Body message is missing
Compliance error, check for error messages in the "Run Compliance Tests" step
You can run this step locally with the ./scripts/ci/check_compliance.py script.

As the error above hints, you can also run ./scripts/ci/check_compliance.py locally to test if you've fixed these errors (provided you install the python dependencies given in scripts/requirements-compliance.txt using pip)

[Finomnis]

Thanks for the fix, you have a few compliance issues that need to be fixed (you can fix up this commit and force push over the branch you sent the PR from):

61de4a34fba4b0a6a7958a60bb3bc12411f2095a: author email (Martin Stumpf [email protected]) needs to match one of the signed-off-by entries.
Error: See https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines for more details
1: UC2 Commit message does not contain a 'Signed-off-by:' line
1: UC6 Commit message body is empty, should at least have 1 line(s).
3: B6 Body message is missing
Compliance error, check for error messages in the "Run Compliance Tests" step
You can run this step locally with the ./scripts/ci/check_compliance.py script.

As the error above hints, you can also run ./scripts/ci/check_compliance.py locally to test if you've fixed these errors (provided you install the python dependencies given in scripts/requirements-compliance.txt using pip)

This script (on windows) gives me a segmentation fault :/

I hope it's correct now

[danieldegrasse]

This script (on windows) gives me a segmentation fault :/

I hope it's correct now

Ah yeah, sorry- I should have made that clear in my first message, the script is only tested in linux :/

[Finomnis]

@danieldegrasse Will this be backported to 3.7? We encountered this issue at work on the 3.7 LTS release, and would like to stay upstream if possible and not on our own fork.

[decsny]

@danieldegrasse Will this be backported to 3.7? We encountered this issue at work on the 3.7 LTS release, and would like to stay upstream if possible and not on our own fork.

to do that then you need to open a bug report issue and link it to this PR, and then have someone add the backport tag to this PR