[sx126x] Wio sx1262 support

[HattoriHanzo031]

No description provided.

[deadprogram]

Anything else needed on this PR @HattoriHanzo031 ?

Ignore my IRL questions about the wireless repo migration for the moment.

[HattoriHanzo031]

Anything else needed on this PR @HattoriHanzo031 ?

Ignore my IRL questions about the wireless repo migration for the moment.

I just did one last minute change to use new pin.Output abstraction instead of machine pin.
If everyone is fine with breaking change in New function, I don't have anything more to add.

[deadprogram]

🥇

[Escalion]

I'll volunteer to test this as I'm working with this hardware right now, but the PR looks good.

[HattoriHanzo031]

I'll volunteer to test this as I'm working with this hardware right now, but the PR looks good.

@Escalion Thank you, this would be very helpful. Please report any bugs or improvements that could be implemented.

P.S. what is the exact hardware you are using (MCU/module combination)?

[jwetzell]

I've got a couple of the sx1262 boards coming in (LILYGO T3S3) that I could use to test. I saw another issue related to this driver in searching (#703) and brought up there that it would probably be nice (although a bit breaking) if the base _pins driver only has support for what the base sx126x chips have. Right now it looks like it is setup for some specific module that has some sort of RF switch alongside the sx126x. I think renaming the _pins file to reflect whatever kind of module that is and having a more basic _pins that actually reflects just the base sx126x chip would be a more accurate implementation.

As well as the base driver doesn't expose DIO pins 2 and 3 (likely because whatever module was being used only has DIO1 connected) and the specific modules could simply use NoPins to reflect that they don't have that connection.