Update documented max PIN values, to accomodate RP2350B

[lurch]

No description provided.

[kilograham]

I know the old max was incorrect in some places, but I'm not sure in terms of helping the user that using NUM_BANK0_GPIOS-1 is useful. maybe we should use a pseudo value here like (highest GPIO) or (GPIO count) depending on the context...

Still on the fence though so open to thoughts (cc @liamfraser @will-v-pi @peterharperuk)

[peterharperuk]

Yes, it's a bit techy. What's a bank anyway?

[lurch]

Yes, it's a bit techy.

I don't know if what I've added here is any more "techy" than anything else in section 5.1 of https://datasheets.raspberrypi.com/pico/raspberry-pi-pico-c-sdk.pdf ? 🤔

What's a bank anyway?

I think it's a building where you used to get money from, before everything became card-only 💳

[kilograham]

Yes, it's a bit techy.

I don't know if what I've added here is any more "techy" than anything else in section 5.1 of https://datasheets.raspberrypi.com/pico/raspberry-pi-pico-c-sdk.pdf ? 🤔

well most of those actually refer to other configuration values whereas NUM_BANK0_GPIOS is a bit of an internal thing.

we are a bit more conversational on others, e.g "1 on RP2350", so I'd say either "highest GPIO number", or "47 on RP2350B, 31 otherwise"

[kilograham]

29 if you are being pedantic

edit: not pedantic actually, accurate (except in some cases - e.g. PIO where it is actually 32)

[lurch]

Thanks for the suggestion - I'm much happier with something specific like "47 on RP2350B, 31 otherwise" than with something vague like "highest GPIO". (That change has been pushed)

[kilograham]

presumably we can't have a comma in the middle of the max value though (oops)

[kilograham]

maybe / instead of ,

[lurch]

presumably we can't have a comma in the middle of the max value though (oops)

Yes we can, the hand-written parser for this is "clever" 😂 (and I also tested before submitting the PR)