summaryrefslogtreecommitdiffstats
path: root/drivers/regulator/s5m8767.c
diff options
context:
space:
mode:
authorMarkus Pargmann <mpa@pengutronix.de>2014-10-08 15:47:05 +0200
committerMark Brown <broonie@kernel.org>2014-10-20 12:23:45 +0100
commit76f439df50aba1838e06dd01e5f20dada7473f57 (patch)
treea35a98029f817fa4663b71dc62db7d4fe5ca1f4f /drivers/regulator/s5m8767.c
parentf114040e3ea6e07372334ade75d1ee0775c355e1 (diff)
downloadlinux-76f439df50aba1838e06dd01e5f20dada7473f57.tar.gz
linux-76f439df50aba1838e06dd01e5f20dada7473f57.tar.bz2
linux-76f439df50aba1838e06dd01e5f20dada7473f57.zip
regulator: Add ena_gpio_initialized to regulator_config
Most drivers do not set the ena_gpio field of struct regulator_config before passing it to the regulator core. This is fine as long as the gpio identifier that is passed is a positive integer. But the gpio identifier 0 is also valid. So we are not able to decide wether we got a real gpio identifier or not based on a 0 in ena_gpio. To be able to decide if it is a valid gpio that got passed, this patch adds a ena_gpio_initialized field that should be set if was initialized with a correct value, either a gpio >= 0 or a negative error number. The core then checks if ena_gpio or ena_gpio_initialized before handling it as a gpio. This way we maintain backwards compatibility and fix the behaviour for gpio number 0. Signed-off-by: Markus Pargmann <mpa@pengutronix.de> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/regulator/s5m8767.c')
0 files changed, 0 insertions, 0 deletions