drivers: i2s: max32: Driver with TX/RX Support

[cx-anuj-pathak]

Description

Adds I2S driver for MAX32655 MCU. It was only tested on MAX32655FTHR board using samples/i2s/echo sample.
Theoretically it should work on most MAS32 MCU (except MAX32650/MAX32660 which uses SPIMSS peripheral), given same MXC_I2S_* APIs and config structure are used internally. But due to lack of hardware it is not tested and dts of other mcu/board is also not updated.

Testing

• checkout to branch and west update
• build using west build -b max32655fthr/max32655/m4 ..\zephyr\samples\drivers\i2s\echo\
• flash using openocd.exe -f interface/cmsis-dap.cfg -f target/max32655.cfg -c "init" -c "reset" -c "halt" -c "flash write_image erase build/zephyr/zephyr.hex" -c "reset" -c "exit" (note: use openocd from msdk)
• speaking into max32655fthr will be echoed to the speaker through the jack.

[github-actions]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff

✅ All manifest checks OK

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

[ubieda]

@cx-anuj-pathak Please add PR description and Testing evidence

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[bricle]

@cx-anuj-pathak Thanks for your excellent work, any plans to move this forward? thanks.

[cx-anuj-pathak]

@cx-anuj-pathak Thanks for your excellent work, any plans to move this forward? thanks.

@bricle Yes, I'm active and will iterate over it as soon as dependencies in adi_hal projects are merged. I guess it got paused due to 4.2 release, and hopeful it will resume soon.

Right it forces custom branch in manifest, and causes PR Metadata check fail. That can only be resolved once adi_hal PRs are merged.

[bricle]

@cx-anuj-pathak Thanks for your excellent work, any plans to move this forward? thanks.

@bricle Yes, I'm active and will iterate over it as soon as dependencies in adi_hal projects are merged. I guess it got paused due to 4.2 release, and hopeful it will resume soon.

Right it forces custom branch in manifest, and causes PR Metadata check fail. That can only be resolved once adi_hal PRs are merged.

Very glad to hear this! But it seems no one have noticed these two PRs, maybe you could try to directly ping some regular reviewers from ADI to come into the spotlight. Thanks again for your reply.

[MaureenHelm]

@cx-anuj-pathak Thanks for your excellent work, any plans to move this forward? thanks.

@bricle Yes, I'm active and will iterate over it as soon as dependencies in adi_hal projects are merged. I guess it got paused due to 4.2 release, and hopeful it will resume soon.
Right it forces custom branch in manifest, and causes PR Metadata check fail. That can only be resolved once adi_hal PRs are merged.

Very glad to hear this! But it seems no one have noticed these two PRs, maybe you could try to directly ping some regular reviewers from ADI to come into the spotlight. Thanks again for your reply.

Thanks for the PR. The adi_hal module is a downstream fork of https://github.com/analogdevicesinc/msdk. Could you please send the hal changes upstream?

[cx-anuj-pathak]

@cx-anuj-pathak Thanks for your excellent work, any plans to move this forward? thanks.

@bricle Yes, I'm active and will iterate over it as soon as dependencies in adi_hal projects are merged. I guess it got paused due to 4.2 release, and hopeful it will resume soon.
Right it forces custom branch in manifest, and causes PR Metadata check fail. That can only be resolved once adi_hal PRs are merged.

Very glad to hear this! But it seems no one have noticed these two PRs, maybe you could try to directly ping some regular reviewers from ADI to come into the spotlight. Thanks again for your reply.

Thanks for the PR. The adi_hal module is a downstream fork of https://github.com/analogdevicesinc/msdk. Could you please send the hal changes upstream?

Filed PRs pointing to msdk repo at
analogdevicesinc/msdk#1425
analogdevicesinc/msdk#1426

let me know further coarse of actions

[cx-anuj-pathak]

@MaureenHelm PR to msdk are merged, let me know further course of actions

[leiche-cid]

@MaureenHelm @ubieda @ozersa Hi, very thanks for your efforts! Politely asking, any plans to move this forward?

[ubieda]

I believe this is blocked by #85205

[ttmut]

Filed PRs pointing to msdk repo at analogdevicesinc/msdk#1425 analogdevicesinc/msdk#1426

let me know further coarse of actions

These two PRs are already part of upstream MSDK and also included in the current hal_adi revision. So, I assume this can move forward.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cx-anuj-pathak]

@MaureenHelm @ttmut @ubieda PR is now ready for review