The Qualcomm MMIO-mapped reference voltage regulator is only present on
Qualcomm SoCs. Hence add a dependency on ARCH_QCOM, to prevent asking
the user about this driver when configuring a kernel without Qualcomm
SoC support.
Fixes: 7cbfbe23796086fd ("regulator: Introduce Qualcomm REFGEN regulator driver")
Signed-off-by: Geert Uytterhoeven <[email protected]>
---
drivers/regulator/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
index 542a7b4279949700..94f44736473e0d2e 100644
--- a/drivers/regulator/Kconfig
+++ b/drivers/regulator/Kconfig
@@ -1001,6 +1001,7 @@ config REGULATOR_PWM
config REGULATOR_QCOM_REFGEN
tristate "Qualcomm REFGEN regulator driver"
+ depends on ARCH_QCOM || COMPILE_TEST
depends on HAS_IOMEM
depends on REGMAP
help
--
2.34.1
On Tue, 25 Jul 2023 17:47:43 +0200, Geert Uytterhoeven wrote:
> The Qualcomm MMIO-mapped reference voltage regulator is only present on
> Qualcomm SoCs. Hence add a dependency on ARCH_QCOM, to prevent asking
> the user about this driver when configuring a kernel without Qualcomm
> SoC support.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: REGULATOR_QCOM_REFGEN should depend on ARCH_QCOM
commit: 6b677c1ae8e4096c84fbcbe1b7fd300dab0b381b
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark