Make SPI Error support defmt::Format

[henrikssn]

Summary

Make SPI Error support the defmt::Format trait (behind the defmt feature)

Checklist

• CHANGELOG.md for the BSP or HAL updated
• All new or modified code is well documented, especially public items
• No new warnings or clippy suggestions have been introduced (see CI or check locally)

[TDHolmes]

Can we do this for thumbv7em too, as well as perhaps other peripheral's Error enums?

[bradleyharden]

#467 will unify the implementation for the different chips, so that won't be an issue anymore. It might make sense to merge that one, since it's ready, and apply this PR to the new code.

[henrikssn]

#467 will unify the implementation for the different chips, so that won't be an issue anymore. It might make sense to merge that one, since it's ready, and apply this PR to the new code.

Sure, I'll rebase when that is merged.

Can we do this for thumbv7em too, as well as perhaps other peripheral's Error enums?

Let's keep this to SPI for now (since that is what I need), we can open separate PR(s) for the rest on an as-needed basis.

[bradleyharden]

@henrikssn, you probably won't be able to rebase. Might be easier to just add it fresh. But #467 has been merged now

[henrikssn]

@henrikssn, you probably won't be able to rebase. Might be easier to just add it fresh. But #467 has been merged now

Done, please take another look.

@TDHolmes now also added this for v1 SPI, thumbv7m and I2C.

[bradleyharden]

@henrikssn, I think you didn't pull the latest changes when you updated this PR, because your commits modify files in the thumbv6m/sercom/v2 and thumbv7em/sercom/v2 directories, which no longer exist.

If you update it, we can merge

[henrikssn]

@henrikssn, I think you didn't pull the latest changes when you updated this PR, because your commits modify files in the thumbv6m/sercom/v2 and thumbv7em/sercom/v2 directories, which no longer exist.

If you update it, we can merge

I have lots of things going on right now, I'll try to get to it "soon". Please bare with me :)

[bradleyharden]

No worries. I didn't even notice this PR for the past 6 weeks, so...

[bradleyharden]

@henrikssn, still interested in following up with this? We're all busy, so 9 months isn't that long of a wait :p