examples/leds_shell: use periph_gpio_mock on native

[krzysztof-cabaj]

Contribution description

In current version of the leds_shell when user uses gpio set or gpio clear command in the native program ends with segmentation fault error. This PR solves this problem by adding periph_gpio_mock module. Now, when user in native uses these commands program works without crach - of course as this is mockup - nothing really happens. I tested this PR in few real boards and everything works fine.

Testing procedure

Output from examples/leds_shell for native without this PR:

main(): This is RIOT! (Version: 2021.07-devel-10924-g4612c)
This board has 2 LEDs
> gpio set 0 0
gpio set 0 0
Set HIGH to PORT 0, PIN 0
Segmentation fault

and with this PR:

main(): This is RIOT! (Version: 2021.07-devel-10924-g4612c-examples-leds_shell-fix-segfault)
This board has 2 LEDs
> gpio set 0 0
gpio set 0 0
Set HIGH to PORT 0, PIN 0
> 

Issues/PRs references

See also #20431

[benpicco]

You also want to check for native64

[krzysztof-cabaj]

Till today, I never use native64- but it behave like native and crash without gpio_periph_mock.

Im not an exepert in Makfile but after reading few pages about or adding logical OR to ifeq (for example) i decided leave this "nasty" copy-paste code.

[benpicco]

Please squash

[krzysztof-cabaj]

Squashed!

Thanks for support!

[riot-ci]

Murdock results

✔️ PASSED

ca9835f examples/leds_shell: fix segfault

Success	Failures	Total	Runtime
19	0	19	01m:18s

Artifacts

• Documentation preview

[mguetschow]

Sorry to chime in late, but shouldn't the module periph_gpio depend on the feature with the same name, which shouldn't be present on native or native64 if not mocked?

[benpicco]

native has support for GPIOs, you can specify --gpio /dev/gpiochip0 to export GPIO port to RIOT, see #12451

[mguetschow]

Oh nice, didn't know about that! If that is the default, there is probably no way around manually specifying periph_gpio_mock in that example.

Still, I'm wondering if missing that module in a certain application on native could trigger an (run-time) error message instead of a segfault?