We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This doesn't follow any of the sai_vx.yaml patterns. It is a new (and hopefully improved) SAI block.
If no one is working on this, I work on getting a PR ready.
The text was updated successfully, but these errors were encountered:
Correction. The STM32U5 uses the sai_v4. So no MR needed to add the yaml. I will still verify the register map matches V4 and add it to perimap.
sai_v4
perimap
Sorry, something went wrong.
The datasheet has a mismatch with sai_v4:
enum/CKSTR: bit_size: 1 variants: - name: FallingEdge description: Data strobing edge is falling edge of SCK value: 0 - name: RisingEdge description: Data strobing edge is rising edge of SCK value: 1
Some discussion here. The ST employee seems to confirm the datasheet is correct.
No branches or pull requests
This doesn't follow any of the sai_vx.yaml patterns. It is a new (and hopefully improved) SAI block.
If no one is working on this, I work on getting a PR ready.
The text was updated successfully, but these errors were encountered: