On Tue, 4 Feb 2020 at 23:21, Heiko Schocher <h...@denx.de> wrote: > > dm_gpio_lookup_name() searches for a gpio through > the bank name. But we have also gpio labels, and it > makes sense to search for a gpio also in the labels > we have defined, if no gpio is found through the > bank name definition. > > This is useful for example if you have a wp pin on > different gpios on different board versions. > > If dm_gpio_lookup_name() searches also for the gpio labels, > you can give the gpio an unique label name and search > for this label, and do not need to differ between > board revisions. > > Signed-off-by: Heiko Schocher <h...@denx.de> > --- > > Example on the aristainetos board: > > => gpio clear wp_spi_nor.gpio-hog > gpio: pin wp_spi_nor.gpio-hog (gpio 47) value is 0 > => > > before this patch, you need to know where your > pin is: > > => gpio clear GPIO2_15 > gpio: pin GPIO2_15 (gpio 47) value is 0 > => > > travis build: > > Changes in v3: > - add comment from Simon Glass > make this new function configurable through Kconfig > option DM_GPIO_LOOKUP_LABEL > > Changes in v2: > - add comment from Simon Glass > move code into seperate function dm_gpio_lookup_label() > add test if dm_gpio_lookup_label() works > > drivers/gpio/Kconfig | 22 ++++++++++++++++++ > drivers/gpio/gpio-uclass.c | 47 ++++++++++++++++++++++++++++++++++++++ > test/dm/gpio.c | 7 ++++++ > 3 files changed, 76 insertions(+)
Reviewed-by: Simon Glass <s...@chromium.org>