Skip to content
New issue

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

Add the S3MUA to the 1189 RAL #56

Merged
merged 2 commits into from
Jan 25, 2025
Merged

Add the S3MUA to the 1189 RAL #56

merged 2 commits into from
Jan 25, 2025

Conversation

mciantyre
Copy link
Member

Haven't tested this on hardware, and I haven't studied the imxrt-ral block. But the starting addresses match the reference manual contents.

This requires us to relax the code generation requirements in raltool to permit un-numbered instance groups. See the commit message for details and alternatives.

We can still emit the `number` function if there's just one instance.
We've been doing this for sole instance types, so this maintains
backwards compatibility.

If there are multiple peripherals associated with the same block, and if
they're not numbered, then we can treat them as distinct. We abuse the
const generics to stamp out unique type aliases, and we start counting
backwards from 255. We signal through documentation that this const
generic is meaningless.

There's other ways to do this; one way is to introduce a unique type
state to the generic `Instance`. By default, use `()`. Then let
implementations define their own type state when they specify their
instance aliases, thus generating unique types with the same "sole
instance" const generic. It's more code to take this approach, and I'm
time limited.
Depends on the previous commit to relax raltool code generation
requirements. Haven't tested this on hardware, and I barely studied the
SVD contents. The starting addresses match the reference manual
contents, and the smoke test passes.
@mciantyre mciantyre merged commit 601e576 into master Jan 25, 2025
48 checks passed
@mciantyre mciantyre deleted the 1180-s3mua branch January 25, 2025 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant