Rmt: Don't use the paste macro

[wisp3rwind]

Thank you for your contribution!

We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:

Submission Checklist 📝

• I have updated existing examples or added new ones (if applicable).
• I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
• My changes were added to the CHANGELOG.md in the proper section.
• I have added necessary changes to user code to the Migration Guide.
• My changes are in accordance to the esp-rs API guidelines

Extra:

• I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖

Description

This replaces constructs of the form

• old: rmt.int_raw().read().[< ch $ch_num _tx_thr_event >]().bit()
• new: rmt.int_raw().read().ch_tx_thr_event($ch_num).bit()

which removes the need for the paste! macro and its somewhat unwieldy [< ... >] syntax, since the PACs have indexed accessors for all registers and fields.

Github doesn't format the diff very well, it's much easier to review with git diff -b.

Note that this PR is relative to #2960, only the last commit is new.

Testing

• Checked that the riscv rmt examples compile.
• Ran a heavily modified RMT driver, including this change, on an ESP Rust Board in tx mode.
• I didn't test xtensa, since I don't have a toolchain set up.

[wisp3rwind]

Just rebased on main, with #2960 merged.

[bugadani]

Github doesn't format the diff very well, it's much easier to review with git diff -b.

Github's "Hide whitespace" option also gives a decent diff :) It's a bit hidden, but very useful in my experience.

[bugadani]

Thank you so much for taking care of this!

[bjoernQ]

Thanks! This might even pave the way to move things out of the macro but it's a nice improvement on it's own

[wisp3rwind]

Thanks! This might even pave the way to move things out of the macro but it's a nice improvement on it's own

Actually, I've done something like that locally, but I'm not sure whether it's really in a good form to upstream, yet. I'll probably push some other changes first.