Re: [PATCH -next] regulator: qcom-rpmh: fix build after QCOM_COMMAND_DB is tristate

[Lina Iyer]

On Fri, Dec 25 2020 at 11:50 -0700, Randy Dunlap wrote:
> Restrict REGULATOR_QCOM_RPMH to QCOM_COMMAND_DB it the latter is enabled.
>
> Fixes this build error:
>  microblaze-linux-ld: drivers/regulator/qcom-rpmh-regulator.o: in function `rpmh_regulator_probe':
>  (.text+0x354): undefined reference to `cmd_db_read_addr'
>
> Fixes: 778279f4f5e4 ("soc: qcom: cmd-db: allow loading as a module")
> Reported-by: kernel test robot <lkp@xxxxxxxxx>
> Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
> Cc: Lina Iyer <ilina@xxxxxxxxxxxxxx>
> Cc: Liam Girdwood <lgirdwood@xxxxxxxxx>
> Cc: Mark Brown <broonie@xxxxxxxxxx>
Reviewed-by: Lina Iyer <ilina@xxxxxxxxxxxxxx>

> ---
> drivers/regulator/Kconfig |    1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-next-20201223.orig/drivers/regulator/Kconfig
> +++ linux-next-20201223/drivers/regulator/Kconfig
> @@ -881,6 +881,7 @@ config REGULATOR_QCOM_RPM
> config REGULATOR_QCOM_RPMH
> 	tristate "Qualcomm Technologies, Inc. RPMh regulator driver"
> 	depends on QCOM_RPMH || (QCOM_RPMH=n && COMPILE_TEST)
> +	depends on QCOM_COMMAND_DB || !QCOM_COMMAND_DB
> 	help
> 	  This driver supports control of PMIC regulators via the RPMh hardware
> 	  block found on Qualcomm Technologies Inc. SoCs.  RPMh regulator