Hi, In v2 of this series I renamed the added regulator_config field 'ena_gpio_valid' to 'ena_gpio_initialized'. We have a gpio_is_valid check in the regulator core code, so no need to require a valid ena_gpio. It should avoid a lot of gpio_is_valid checks in regulator drivers.
v2 is also backward compatible now, so if ena_gpio_initialized is false, it will still handle gpios > 0. There are some more changes on the regulator driver patches, which now do not set ena_gpio_initialized for pdata code. This series fixes the handling of gpio 0 in the regulator framework. Best regards, Markus Markus Pargmann (4): regulator: Add ena_gpio_initialized to regulator_config regulator: Set ena_gpio_initialized in regulator drivers regulator: fixed: Use gpio_is_valid regulator: gpio: Use gpio_is_valid drivers/regulator/arizona-ldo1.c | 1 + drivers/regulator/core.c | 3 ++- drivers/regulator/fixed.c | 4 +++- drivers/regulator/gpio-regulator.c | 4 +++- drivers/regulator/max8952.c | 2 ++ drivers/regulator/s2mps11.c | 1 + drivers/regulator/s5m8767.c | 1 + drivers/regulator/tps65090-regulator.c | 1 + drivers/regulator/wm8994-regulator.c | 6 ++++-- include/linux/regulator/driver.h | 4 ++++ 10 files changed, 22 insertions(+), 5 deletions(-) -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
