Create I2S Configuration Class

[ikivanc]

Description

• Added I2S Configuration Class from low-level I2S reference

Motivation and Context

• Created I2S Configuration Class from low-level I2S reference

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• 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 change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (work on Unit Tests, has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[nfbot]

Hi @ikivanc,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉

[Ellerbach]

Few comments but all up, nice design :-)

[Ellerbach]

how is that different from mono and stereo?

[ikivanc]

For initializing I2S configuration I2sChannelFormat is required, We'll need mono and stereo when we use i2s_set_clk We can delete I2sChannel for now

[Ellerbach]

please simplify all this, there is no real reason to have multiple times the same elements with the same values.

[ikivanc]

These values are provided in the reference documentation for I2S communication standard format. Do you have any suggestion?

[Ellerbach]

Yes :-) Clean :-) Just keep one per value (those having the same value do have the same behavior)

[Ellerbach]

StandardI2s = 0X01,
Lsb = 0x02,
Msb = 0x03,
PcmShort = 0x04,
PcmLong = 0x0C, or 0x08?