modules: hal_nxp: osa: Remove unused OSA API

[Radimli]

• Deleted file fsl_os_abstraction.h is unused and deprecated
• Location of current OSA API available in modules/hal/nxp/mcux/mcux-sdk/components/osa

[github-actions]

Hello @Radimli, and thank you very much for your first pull request to the Zephyr project!
Our Continuous Integration pipeline will execute a series of checks on your Pull Request commit messages and code, and you are expected to address any failures by updating the PR. Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request. If you haven't already, please make sure to review the project's Contributor Expectations and update (by amending and force-pushing the commits) your pull request if necessary.
If you are stuck or need help please join us on Discord and ask your question there. Additionally, you can escalate the review when applicable. 😊

[danieldegrasse]

Thanks for this change- please take a look at your git configuration. There are a few issues the compliance script is flagging (you can view these by clicking "Details" on the failed compliance check)

• Commit author does not match the signed-off entry: You can update the author of this commit with git commit --amend --author "Radim.Lipka@nxp.com"
• Commit body is too long (>75 characters on one line)- just add a line break in the commit body to fix this, editors like vim will do this for you automatically

Edit: we will also need to look at the failing twister tests- these point to places where the OSA API might still be used. It looks like this PR has some USB sample build failures.

[Radimli]

Thanks for this change- please take a look at your git configuration. There are a few issues the compliance script is flagging (you can view these by clicking "Details" on the failed compliance check)

• Commit author does not match the signed-off entry: You can update the author of this commit with git commit --amend --author "Radim.Lipka@nxp.com"
• Commit body is too long (>75 characters on one line)- just add a line break in the commit body to fix this, editors like vim will do this for you automatically

Edit: we will also need to look at the failing twister tests- these point to places where the OSA API might still be used. It looks like this PR has some USB sample build failures.

Hello @danieldegrasse,

yes, cmake regarding USB MW should be modified. Already discussing it with @MarkWangChinese

[Radimli]

@danieldegrasse @MarkWangChinese
It should be solved in
zephyrproject-rtos/hal_nxp#433

[MarkWangChinese]

Hi @Radimli You can update this PR (changing the west.yml) to contain the zephyrproject-rtos/hal_nxp#433 like: https://github.com/zephyrproject-rtos/zephyr/pull/77973/files#diff-d7f4082837dc3cb270fcf1abd68188216fdadee294e01611b8ca59ddea7fdbb3R201, then let the CI to check it.

[zephyrbot]

The following west manifest projects have been modified in this Pull Request:

Name	Old Revision	New Revision	Diff
hal_nxp	zephyrproject-rtos/hal_nxp@78b3972	zephyrproject-rtos/hal_nxp@74a7735 (master)	zephyrproject-rtos/hal_nxp@78b3972e..74a7735b

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[danieldegrasse]

Build tests look good, but you still have a compliance error. If you want to check this locally rather than waiting on CI (and are using Linux) you can run ./scripts/ci/check_compliance.py -c $(git merge-base HEAD main)...HEAD from your zephyr repo, with this branch checked out.

[danieldegrasse]

Please address merge conflict when you get a chance

[danieldegrasse]

@Radimli ping to fix merge conflict

[dleach02]

@Radimli we are working to sequence the HAL PRs

[dleach02]

@Radimli HAL side merged and this PR has been updated to point to the new SHA.

[github-actions]

Hi @Radimli!
Congratulations on getting your very first Zephyr pull request merged 🎉🥳. This is a fantastic achievement, and we're thrilled to have you as part of our community!

To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge.

Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁