[Feature Request] Fully type erased pin

[jg2562]

Currently, there is only the ability to partially erase the pin's typing, meaning pins still must remain within the port they originated from. However, this restricts the usage if there requires an array that crosses port boundaries. I propose implementing a pin with the origin port type fully erased similar to how stm32f4xx-hal does it. How feasible would this be?

[mlamoore]

Looking at the reference manual for the STM32H742/743/750/753, the GPIO registers are arranged with uniform layouts and offsets so the same technique would be possible there. If you wanted to do this, I would recommend starting by looking through all the supported reference manuals and make sure they all use consecutive GPIO register blocks 0x400 apart in memory like the 742/743/750/753, then port this over.

…

On Fri, Feb 11, 2022 at 1:36 PM Jack ***@***.***> wrote: Currently, there is only the ability to partially erase the pin's typing, meaning pins still must remain within the port they originated from. However, this restricts the usage if there requires an array that crosses port boundaries. I propose implementing a pin with the origin port type fully erased similar to how stm32f4xx-hal does it <https://github.com/stm32-rs/stm32f4xx-hal/blob/8ab1f8fed69d8cded57f0b3a3b12a1e9c7d479be/src/gpio/erased.rs>. How feasible would this be? — Reply to this email directly, view it on GitHub <#315>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUS5FM63SZCZBSYOWO4LVDU2VQNFANCNFSM5OFFG4XA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jg2562]

Yeh, I will take a look at that, thank you for the direction!