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

2020-12-28 Thread Mark Brown
On Fri, 25 Dec 2020 10:50:04 -0800, 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

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

2020-12-27 Thread 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

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

2020-12-25 Thread Randy Dunlap
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: