summaryrefslogtreecommitdiff
path: root/include/xen/features.h
diff options
context:
space:
mode:
authorDinh Nguyen <dinguyen@kernel.org>2017-02-03 09:29:07 -0600
committerArnd Bergmann <arnd@arndb.de>2017-02-06 17:33:01 +0100
commit08b3b33f3e4dc0016ad878c1a48f094a74956277 (patch)
tree06fb52732838341e97a7e16f7838c199234c6841 /include/xen/features.h
parent36e854c3b8e17db0e9ace2c603d492b71d53b5cd (diff)
MAINTAINERS: socfpga: update email for Dinh Nguyen
My opensource.altera.com email will be going away soon. Signed-off-by: Dinh Nguyen <dinguyen@kernel.org> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'include/xen/features.h')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-01-24 18:23:29 +0000
to some pre-configured voltage. With recent progress in U-boot SPL support, this is no longer the case. In any case we should handle this quirk in the kernel driver as well. This invalid setting causes _regulator_get_voltage() to fail with -EINVAL which causes regulator registration to fail when constrains are used: [ 1.054181] vcc-pg: failed to get the current voltage(-22) [ 1.059670] axp20x-regulator axp20x-regulator.0: Failed to register ldo_io0 [ 1.069749] axp20x-regulator: probe of axp20x-regulator.0 failed with error -22 This commits makes the axp20x regulator driver accept the 0x1f register value, fixing this. The datasheet does not guarantee reliable operation above 3.3V, so on boards where this regulator is used the regulator-max-microvolt setting must be 3.3V or less. This is essentially the same as the commit f40d4896bf32 ("regulator: axp20x: Fix axp22x ldo_io registration error on cold boot") for AXP22x PMICs. Fixes: a51f9f4622a3 ("regulator: axp20x: support AXP809 variant") Signed-off-by: Chen-Yu Tsai <wens@csie.org> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'net/dns_resolver/Kconfig')