Page MenuHomeFreeBSD

Allow setting of GPIO pin names.
ClosedPublic

Authored by loos on Mar 3 2015, 1:59 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 12 2024, 1:57 AM
Unknown Object (File)
Mar 12 2024, 1:57 AM
Unknown Object (File)
Mar 12 2024, 1:57 AM
Unknown Object (File)
Mar 12 2024, 1:57 AM
Unknown Object (File)
Mar 8 2024, 4:22 AM
Unknown Object (File)
Jan 8 2024, 11:24 AM
Unknown Object (File)
Jan 4 2024, 10:11 AM
Unknown Object (File)
Jan 4 2024, 10:11 AM
Subscribers

Details

Summary

Add two new gpiobus methods to get and set GPIO pin names.

When a pin name is set, we do a lazy allocation and store the user supplied string.

When a pin name is read, the gpiobus getname method will return the stored value if any, and the default name otherwise.

Make the necessary modifications to libgpio and gpioctl.

When a gpiobus child is added, use its name to identify the gpio pin name.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

loos retitled this revision from to Allow setting of GPIO pin names..
loos updated this object.
loos edited the test plan for this revision. (Show Details)
rpaulo added inline comments.
lib/libgpio/gpio.c
122 ↗(On Diff #4088)

I'm thinking it might be better to just write this function with a (gpio_handle_t, unsigned int pin, const char *name) instead of passing the gpio config.

sys/dev/gpio/gpiobus.c
691 ↗(On Diff #4088)

This can probably be M_WAITOK.

Change the parameters of libgpio's function gpio_pin_set_name().

Change the memory allocation of GPIO pin name to M_WAITOK.

rpaulo added a reviewer: rpaulo.
rpaulo added inline comments.
lib/libgpio/gpio.c
124 ↗(On Diff #4109)

Should we bzero this variable?

This revision is now accepted and ready to land.Mar 5 2015, 4:36 AM

Thanks Rui!

lib/libgpio/gpio.c
124 ↗(On Diff #4109)

Yes, it is better to bzero it first. I'll fix it before commit.

loos updated this revision to Diff 4145.

Closed by commit rS279761 (authored by @loos).