Add device MCIMX6X and MCIMX7D and related i.mx drivers

[mcuxsusan]

• This files are copied from https://github.com/zephyrproject-rtos/hal_nxp/tree/master/imx
  and re-organized according to current folder structure.

• Device headers and device specific files goes to devices/{device}
  folder, common drivers are put in the drivers/xx_imx driver folder
  according to IP.

Signed-off-by: Susan Su [email protected]

Prerequisites

• I have checked latest main branch and the issue still exists.
• I did not see it is stated as known-issue in release notes.
• No similar GitHub issue is related to this change.
• My code follows the commit guidelines of this project.
• I have performed a self-review of my own code.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.

Describe the pull request

A clear and concise description for the change in this Pull Request and which issue is fixed.

Fixes # (issue)

Type of change (please delete options that are not relevant):

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Tests

• Test configuration (please complete the following information):
  • Hardware setting:
  • Toolchain:
  • Test Tool preparation:
  • Any other dependencies:
• Test executed
  Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
  • Build Test
  • Run Test

[mcuxsusan]

Hi @dleach02, @mmahadevan108 please help review if the organize way of these i.mx stuff is OK and feel free to suggest, thanks in advance.

[mcuxsusan]

Hi @mmahadevan108, @dleach02, kind reminder, please help check the PR.

[mmahadevan108]

device_imx.h duplicated and put in 2 locations. Is there a common place we can add this file?

[mmahadevan108]

@mcuxsusan. Any thoughts on avoiding device_imx.h duplication?

[mcuxsusan]

Hi @mmahadevan108 , sorry for my late response. Per my understanding, this device_imx.h header file is similar as our fsl_device_registers.h, just used to include the needed header file for this specific device. So, I was wondering we should have individual device_imx.h, just like our fsl_device_registers.h.

I could make the content only specified for this device, is that acceptable for your side?

[mmahadevan108]

I think that should work. Thank you

[mmahadevan108]

@mcuxsusan Getting back to this PR. Can it be update per the above discussion.

[mcuxsusan]

Hi @mmahadevan108, sorry for my late action. I will try to update this tomorrow, appreciate for your patience.

[mcuxsusan]

@mmahadevan108, please check the updated PR, thanks a lot.

[mmahadevan108]

@mcuxsusan , restarting this thread as there are some PR's in Zephyr that could benefit from adding this support in the SDK. Does this PR need to be updated for the current version of the SDK?

[mcuxsusan]

Hello @mmahadevan108, checking with the NPI team, these two devices are not in SDK support scope now. So, we are not able to add the two devices into the mcux-sdk repo. Not sure if you would like to have these two devices support maintain in hal_nxp.