From: Bintian <bintian.wang@huawei.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will.deacon@arm.com, devicetree@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
khilman@linaro.org, mturquette@linaro.org,
rob.herring@linaro.org, zhangfei.gao@linaro.org,
haojian.zhuang@linaro.org, xuwei5@hisilicon.com,
jh80.chung@samsung.com, olof@lixom.net, yanhaifeng@gmail.com,
sboyd@codeaurora.org, xuejiancheng@huawei.com,
sledge.yanwei@huawei.com, tomeu.vizoso@collabora.com,
linux@arm.linux.org.uk, guodong.xu@linaro.org,
jorge.ramirez-ortiz@linaro.org, tyler.baker@linaro.org,
xuyiping@hisilicon.com, wangbinghui@hisilicon.com,
zhenwei.wang@hisilicon.com, victor.lixin@hisilicon.com,
puck.chen@hisilicon.com, dan.zhao@hisilicon.c
Subject: Re: [PATCH v2 4/6] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC
Date: Mon, 13 Apr 2015 21:17:59 +0800 [thread overview]
Message-ID: <552BC207.40807@huawei.com> (raw)
In-Reply-To: <1428926202.11113.77.camel@x220>
Hello Paul,
Thank you very much for code review and testing on arm!
On 2015/4/13 19:56, Paul Bolle wrote:
> On Mon, 2015-04-13 at 17:17 +0800, Bintian Wang wrote:
>> --- /dev/null
>> +++ b/drivers/clk/hisilicon/Kconfig
>> @@ -0,0 +1,5 @@
>> +config COMMON_CLK_HI6220
>> + tristate "Hi6220 Clock Driver"
>> + depends on OF && ARCH_HISI
>> + help
>> + Build the Hisilicon Hi6220 clock driver based on the common clock framework.
>
> In 5/6 you make arm64's ARCH_HISI (a bool) select COMMON_CLK_HI6220. So
> for arm64 this driver will always be built-in.
>
> For arm's ARCH_HISI it's possible to set COMMON_CLK_HI6220 to 'm'.
Setting COMMON_CLK_HI6220 to a bool symbol is a good solution based on
current code base, I will fix it in next version.
>
>> --- a/drivers/clk/hisilicon/Makefile
>> +++ b/drivers/clk/hisilicon/Makefile
>> @@ -2,8 +2,9 @@
>> # Hisilicon Clock specific Makefile
>> #
>>
>> -obj-y += clk.o clkgate-separated.o
>> +obj-y += clk.o clkgate-separated.o clkdivider-hi6220.o
>
> These objects will always be built-in, right?
>
>> obj-$(CONFIG_ARCH_HI3xxx) += clk-hi3620.o
>> obj-$(CONFIG_ARCH_HIP04) += clk-hip04.o
>> obj-$(CONFIG_ARCH_HIX5HD2) += clk-hix5hd2.o
>> +obj-$(CONFIG_COMMON_CLK_HI6220) += clk-hi6220.o
>
> If CONFIG_COMMON_CLK_HI6220 is 'm' this will build a module named
> clk-hi6220.ko. If I try to do that I get:
> $ make -C ../../.. ARCH=arm CROSS_COMPILE=arm-linux-gnu- M=$PWD clk-hi6220.ko
> make: Entering directory `[...]'
> CC [M] [...]/drivers/clk/hisilicon/clk-hi6220.o
> MODPOST 1 modules
> WARNING: "hisi_clk_register_gate" [[...]/drivers/clk/hisilicon/clk-hi6220.ko] undefined!
> WARNING: "hi6220_clk_register_divider" [[...]/drivers/clk/hisilicon/clk-hi6220.ko] undefined!
> WARNING: "hisi_clk_register_mux" [[...]/drivers/clk/hisilicon/clk-hi6220.ko] undefined!
> WARNING: "hisi_clk_register_gate_sep" [[...]/drivers/clk/hisilicon/clk-hi6220.ko] undefined!
> WARNING: "hisi_clk_register_fixed_factor" [[...]/drivers/clk/hisilicon/clk-hi6220.ko] undefined!
> WARNING: "hisi_clk_register_fixed_rate" [[...]/drivers/clk/hisilicon/clk-hi6220.ko] undefined!
> WARNING: "hisi_clk_init" [[...]/drivers/clk/hisilicon/clk-hi6220.ko] undefined!
> CC [...]/drivers/clk/hisilicon/clk-hi6220.mod.o
> LDFINAL [M] [...]/drivers/clk/hisilicon/clk-hi6220.ko
> make: Leaving directory `[...]'
>
> That is, I think, because nothing exports these symbols.
[...]
> There's nothing module specific in this file. And the lack of a
> MODULE_LICENSE() macro is also telling. If this was built as a module
> loading that module - ignoring the undefined symbols - would taint the
> kernel.
>
> It seems to me that COMMON_CLK_HI6220 is meant to be a bool symbol.
You are right.
>
>
> Paul Bolle
>
> I wonder what checkpatch had to say about the length of the lines seen
> in this patch.
Yes, I ran this script before sending out this patch set, it reports
warnings about "line over 80 characters ", but I find it's easier to
read than shrinking one line to several lines, so just keep it, do I
need to fix it?
Thanks,
Bintian
>
> .
>
next prev parent reply other threads:[~2015-04-13 13:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 9:17 [PATCH v2 0/6] arm64,hi6220: Enable Hisilicon Hi6220 SoC Bintian Wang
[not found] ` <1428916660-25910-1-git-send-email-bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-13 9:17 ` [PATCH v2 1/6] arm64: Enable Hisilicon ARMv8 SoC family in Kconfig and defconfig Bintian Wang
2015-04-20 21:10 ` Kevin Hilman
[not found] ` <7hvbgqfqv5.fsf-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
2015-04-21 0:39 ` Bintian
2015-04-13 9:17 ` [PATCH v2 2/6] arm64: hi6220: Document devicetree bindings for Hisilicon hi6220 SoC Bintian Wang
2015-04-13 9:17 ` [PATCH v2 5/6] arm64: Kconfig: Add clock support to ARCH_HISI Bintian Wang
2015-04-13 9:17 ` [PATCH v2 3/6] clk: hi6220: Document devicetree bindings for hi6220 clock Bintian Wang
2015-04-13 15:32 ` Arnd Bergmann
2015-04-14 3:35 ` Bintian
[not found] ` <552C8AFE.9040907-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-14 10:19 ` Arnd Bergmann
2015-04-14 12:37 ` Bintian
[not found] ` <552D09F7.7080603-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-14 13:20 ` Arnd Bergmann
2015-04-14 14:37 ` Brent Wang
2015-04-13 9:17 ` [PATCH v2 4/6] clk: hi6220: Clock driver support for Hisilicon hi6220 SoC Bintian Wang
[not found] ` <1428916660-25910-5-git-send-email-bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-13 11:56 ` Paul Bolle
2015-04-13 13:17 ` Bintian [this message]
[not found] ` <552BC207.40807-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-13 14:15 ` Paul Bolle
2015-04-13 13:30 ` Arnd Bergmann
2015-04-13 13:57 ` Bintian
[not found] ` <552BCB5A.8010705-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-13 15:34 ` Arnd Bergmann
2015-04-14 8:53 ` YiPing Xu
2015-04-13 9:17 ` [PATCH v2 6/6] arm64: dts: Add dts files for Hisilicon Hi6220 SoC Bintian Wang
[not found] ` <1428916660-25910-7-git-send-email-bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-14 14:44 ` Arnd Bergmann
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=552BC207.40807@huawei.com \
--to=bintian.wang@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=dan.zhao@hisilicon.c \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=guodong.xu@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jh80.chung@samsung.com \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=olof@lixom.net \
--cc=pawel.moll@arm.com \
--cc=pebolle@tiscali.nl \
--cc=puck.chen@hisilicon.com \
--cc=rob.herring@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sledge.yanwei@huawei.com \
--cc=tomeu.vizoso@collabora.com \
--cc=tyler.baker@linaro.org \
--cc=victor.lixin@hisilicon.com \
--cc=wangbinghui@hisilicon.com \
--cc=will.deacon@arm.com \
--cc=xuejiancheng@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=xuyiping@hisilicon.com \
--cc=yanhaifeng@gmail.com \
--cc=zhangfei.gao@linaro.org \
--cc=zhenwei.wang@hisilicon.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).