From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: devel@driverdev.osuosl.org,
Manivannan Sadhasivam <mani@kernel.org>,
linuxarm@huawei.com, linux-kernel@vger.kernel.org,
John Stultz <john.stultz@linaro.org>,
mauro.chehab@huawei.com
Subject: Re: [PATCH 1/6] staging: hikey9xx: fix Kconfig dependency chain
Date: Tue, 18 Aug 2020 17:07:04 +0200 [thread overview]
Message-ID: <20200818150704.GA665815@kroah.com> (raw)
In-Reply-To: <1b7e23500e7449593393115cc0954af441b0c730.1597762400.git.mchehab+huawei@kernel.org>
On Tue, Aug 18, 2020 at 04:58:53PM +0200, Mauro Carvalho Chehab wrote:
> Both the SPMI controller and the SPMI PMIC driver
> depends on the SPMI bus support.
>
> The dependency for the regulator is also wrong:
> it should depends on the SPMI version of the HiSilicon 6421,
> and not on the normal one.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> drivers/staging/hikey9xx/Kconfig | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/hikey9xx/Kconfig b/drivers/staging/hikey9xx/Kconfig
> index 76267b9be562..a004839e8fa9 100644
> --- a/drivers/staging/hikey9xx/Kconfig
> +++ b/drivers/staging/hikey9xx/Kconfig
> @@ -5,6 +5,7 @@ config SPMI_HISI3670
> tristate "Hisilicon 3670 SPMI Controller"
> select IRQ_DOMAIN_HIERARCHY
> depends on HAS_IOMEM
> + depends on SPMI
> help
> If you say yes to this option, support will be included for the
> built-in SPMI PMIC Arbiter interface on Hisilicon 3670
> @@ -14,6 +15,7 @@ config SPMI_HISI3670
> config MFD_HI6421_SPMI
> tristate "HiSilicon Hi6421v600 SPMI PMU/Codec IC"
> depends on OF
> + depends on SPMI
> select MFD_CORE
> help
> Add support for HiSilicon Hi6421v600 SPMI PMIC. Hi6421 includes
> @@ -28,7 +30,7 @@ config MFD_HI6421_SPMI
> # to be placed at drivers/regulator
> config REGULATOR_HI6421V600
> tristate "HiSilicon Hi6421v600 PMIC voltage regulator support"
> - depends on MFD_HI6421_PMIC && OF
> + depends on MFD_HI6421_SPMI && OF
> help
> This driver provides support for the voltage regulators on
> HiSilicon Hi6421v600 PMU / Codec IC.
Better, but now I get the following build error:
ERROR: modpost: "regulator_map_voltage_iterate" [drivers/staging/hikey9xx/hi6421v600-regulator.ko] undefined!
ERROR: modpost: "regulator_list_voltage_table" [drivers/staging/hikey9xx/hi6421v600-regulator.ko] undefined!
ERROR: modpost: "of_get_regulator_init_data" [drivers/staging/hikey9xx/hi6421v600-regulator.ko] undefined!
ERROR: modpost: "regulator_register" [drivers/staging/hikey9xx/hi6421v600-regulator.ko] undefined!
ERROR: modpost: "regulator_unregister" [drivers/staging/hikey9xx/hi6421v600-regulator.ko] undefined!
ERROR: modpost: "rdev_get_drvdata" [drivers/staging/hikey9xx/hi6421v600-regulator.ko] undefined!
Someone need CONFIG_REGULATOR enabled?
Another follow-on patch? :)
thanks,
greg k-h
next prev parent reply other threads:[~2020-08-18 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 14:58 [PATCH 0/6] Do some cleanups at the HiSilicon 6421 regulator Mauro Carvalho Chehab
2020-08-18 14:58 ` [PATCH 1/6] staging: hikey9xx: fix Kconfig dependency chain Mauro Carvalho Chehab
2020-08-18 15:07 ` Greg Kroah-Hartman [this message]
2020-08-18 16:07 ` Mauro Carvalho Chehab
2020-08-18 17:15 ` Greg Kroah-Hartman
2020-08-18 14:58 ` [PATCH 2/6] staging: mfd: hi6421-spmi-pmic: get rid of interrupt properties Mauro Carvalho Chehab
2020-08-18 14:58 ` [PATCH 3/6] staging: spmi: hisi-spmi-controller: change compatible string Mauro Carvalho Chehab
2020-08-18 14:58 ` [PATCH 4/6] staging: mfd: hi6421-spmi-pmic: Simplify the " Mauro Carvalho Chehab
2020-08-18 14:58 ` [PATCH 5/6] dt: document HiSilicon SPMI controller and mfd/regulator properties Mauro Carvalho Chehab
2020-08-18 14:58 ` [PATCH 6/6] MAINTAINERS: add an entry for HiSilicon 6421v600 drivers Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200818150704.GA665815@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mani@kernel.org \
--cc=mauro.chehab@huawei.com \
--cc=mchehab+huawei@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.