Add method to disable automatic retransmission

[epontan]

To support time-triggered communication as described in ISO 11898-1:2015, automatic retransmission can be disabled through the DynAux trait.

Thank you!

Thank you for your contribution.
Please make sure that your submission includes the following:

Must

• The code compiles without errors or warnings.
• All tests pass and in the best case you also added new tests.
• cargo +stable fmt was run.
• cargo +stable clippy yields no warnings.
• Your changes were added to the CHANGELOG.md in the proper section.
• You add a description of your work to this PR.
• You added proper docs (in code, rustdoc and README.md) for your
  newly added features and code.

[Ironedde]

Cool, I didn't know about this option in the CAN standard 👍
Are you expecting more changes in the future to allow you to make time-triggered communication work.

I'm mostly thinking about the SOF detection for time synchronization.
We have:

• message timestamp as part of the AnyMessage trait
• interrupt handling for TSW
• fetching the Timestamp counter from TSCV.

Maybe having the ability to reset the TSCV would be a good idea?
Or is interrupt handling of TSW the best approach?

[epontan]

Cool, I didn't know about this option in the CAN standard 👍 Are you expecting more changes in the future to allow you to make time-triggered communication work.

I have two changes upcoming, but those are more related to retrieval of the TX buffer index.

I'm mostly thinking about the SOF detection for time synchronization. We have:

• message timestamp as part of the AnyMessage trait
• interrupt handling for TSW
• fetching the Timestamp counter from TSCV.

Maybe having the ability to reset the TSCV would be a good idea? Or is interrupt handling of TSW the best approach?

I'm not sure, but mcan could probably support both.