From: Guodong Xu <guodong.xu@linaro.org>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Catalin Marinas <catalin.marinas@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
damm+renesas@opensource.se, "xuwei (O)" <xuwei5@hisilicon.com>,
Thierry Reding <treding@nvidia.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>,
Gregory Clement <gregory.clement@free-electrons.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Eric Anholt <eric@anholt.net>, Riku Voipio <riku.voipio@lina>
Subject: Re: [PATCH 4/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator
Date: Sat, 27 May 2017 17:42:01 +0800 [thread overview]
Message-ID: <CAFGCpxw3orr+4OO2_YVj2DrAJsvo9O+WiGeVv6GAk26HLzAnRw@mail.gmail.com> (raw)
In-Reply-To: <CABxcv=kP7XLDhUifwDBEfnayfgjGJFf7v9kUkPS6pcLKiaLP-g@mail.gmail.com>
On Fri, May 26, 2017 at 8:13 PM, Javier Martinez Canillas
<javier@dowhile0.org> wrote:
> Hello Guodong,
>
> On Fri, May 26, 2017 at 8:35 AM, Guodong Xu <guodong.xu@linaro.org> wrote:
>> From: Wang Xiaoyin <hw.wangxiaoyin@hisilicon.com>
>>
>
> [snip]
>
>>
>> +config REGULATOR_HI6421V530
>> + tristate "HiSilicon Hi6421v530 PMIC voltage regulator support"
>
> The Kconfig symbol is tristate so the driver can be built as a module...
>
>> +
>> +static struct platform_driver hi6421v530_regulator_driver = {
>> + .driver = {
>> + .name = "hi6421v530-regulator",
>> + },
>> + .probe = hi6421v530_regulator_probe,
>> +};
>> +module_platform_driver(hi6421v530_regulator_driver);
>
> ... but the driver doesn't have a platform device ID table nor export
> it as a module alias using MODULE_DEVICE_TABLE().
>
I will add that.
Thanks for your review.
-Guodong
> That means that if built as a module, it won't be autoloaded when the
> "hi6421v530-regulator" device is registered by the MFD driver.
>
>> +
>> +MODULE_AUTHOR("Wang Xiaoyin <hw.wangxiaoyin@hisilicon.com>");
>> +MODULE_DESCRIPTION("Hi6421v530 regulator driver");
>> +MODULE_LICENSE("GPL v2");
>
> Alternative you can add a MODULE_ALIAS().
>
> Best regards,
> Javier
next prev parent reply other threads:[~2017-05-27 9:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 6:35 [PATCH 0/6] MFD: add driver for HiSilicon Hi6421v530 PMIC Guodong Xu
[not found] ` <20170526063518.21246-1-guodong.xu-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-05-26 6:35 ` [PATCH 1/6] dt-bindings: mfd: Add hi6421v530 bindings Guodong Xu
[not found] ` <20170526063518.21246-2-guodong.xu-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-05-31 18:07 ` Rob Herring
2017-06-02 9:01 ` Guodong Xu
2017-05-26 6:35 ` [PATCH 4/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator Guodong Xu
2017-05-26 11:38 ` Mark Brown
[not found] ` <20170526113822.xsmk5lsrvzmqyljm-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-05-27 9:47 ` Guodong Xu
2017-05-26 12:13 ` Javier Martinez Canillas
2017-05-27 9:42 ` Guodong Xu [this message]
2017-05-26 6:35 ` [PATCH 5/6] arm64: dts: hikey960: add device node for pmic and regulators Guodong Xu
2017-05-26 6:35 ` [PATCH 6/6] arm64: defconfig: enable hi6421v530 MFD and regulator Guodong Xu
2017-05-26 6:35 ` [PATCH 2/6] mfd: hi6421-pmic: move hi6421_regmap_config definition to header file Guodong Xu
2017-05-26 8:33 ` Arnd Bergmann
2017-05-27 3:08 ` Guodong Xu
2017-05-26 6:35 ` [PATCH 3/6] mfd: hi6421v530: add support for HiSilicon Hi6421v530 Guodong Xu
2017-05-30 7:36 ` Lee Jones
2017-06-02 9:35 ` Guodong Xu
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=CAFGCpxw3orr+4OO2_YVj2DrAJsvo9O+WiGeVv6GAk26HLzAnRw@mail.gmail.com \
--to=guodong.xu@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=damm+renesas@opensource.se \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=geert+renesas@glider.be \
--cc=gregory.clement@free-electrons.com \
--cc=javier@dowhile0.org \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=riku.voipio@lina \
--cc=thomas.petazzoni@free-electrons.com \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.com \
--cc=yamada.masahiro@socionext.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).