[FEATURE] Switch to Zephyr native drivers on i.MX platforms

[dbaluta]

Is your feature request related to a problem? Please describe.

Completely switch to Zephyr native drivers on i.MX platforms.

Supported boards:

• i.MX8QM
• i.MX8QXP
• i.MX8MP
• i.MX8ULP
• i.MX93

Issue tracking overall work from community is here: #5794

Describe the solution you'd like

IPs drivers:

• DMA
  • SDMA
  • EDMA
• DAI
  • SAI
  • ESAI
• IRQSteer - drivers: interrupt_controller: Add driver for NXP's irqsteer zephyrproject-rtos/zephyr#62776
• Messaging Unit / IPC

Open questions:

• should we use IPC3 or IPC4?

[lgirdwood]

Open questions:

• should we use IPC3 or IPC4?

I would recommend IPC4 as that's what's had most integration, validation and testing effort. i.e. most APIs around IP integration already have glue to IPC4.

[lgirdwood]

Adding @nashif and @andyross

[kv2019i]

@dbaluta Ok to bump this to v2.10 ? I think lot of progress has been done, so maybe add the ticket with current status and then bump the milestone tag...?

[dbaluta]

@kv2019i do we have a timeline for v2.9 ? I think we are in the final steps of merging support for imx8/8x/8ulp and later 8mp for this. We estimate around 1 month for this.

No problem for us to bump this for v2.10. I will post a table with the progress here.

[kv2019i]

@dbaluta #8696 ... target for stable-v2.9 branch was last week, so we are running a bit behind, but I did the branch today. Now going through feature items that were not ready by the stable branch cutoff. We can still cherry-pick/backport fixes for the release.

[dbaluta]

OK, bump this to v2.10

[kv2019i]

@dbaluta v2.10 branched today, can you give a status update and move to 2.11 if there's work left?

[dbaluta]

Move to v2.11 for now.

[kv2019i]

@dbaluta To v2.12? Stable branch is today (#9360).

[dbaluta]

@kv2019i yes, moved it.