From: Paul Bolle <pebolle@tiscali.nl>
To: Jiancheng Xue <xuejiancheng@huawei.com>
Cc: mturquette@baylibre.com, sboyd@codeaurora.org,
p.zabel@pengutronix.de, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linux@arm.linux.org.uk, khilman@linaro.org,
arnd@arndb.de, olof@lixom.net, xuwei5@hisilicon.com,
haojian.zhuang@linaro.org, zhangfei.gao@linaro.org,
bintian.wang@huawei.com, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, yanhaifeng@hisilicon.com,
yanghongwei@hisilicon.com, suwenping@hisilicon.com,
raojun@hisilicon.com, ml.yang@hisilicon.com,
gaofei@hisilicon.com, zhangzhenxing@hisilicon.com,
xuejiancheng@hisilicon.com, lidongpo@hisilicon.com
Subject: Re: [PATCH v7 1/6] clk: hisilicon: add CRG driver for hi3519 soc
Date: Tue, 26 Jan 2016 02:17:43 +0100 [thread overview]
Message-ID: <1453771063.17181.56.camel@tiscali.nl> (raw)
In-Reply-To: <1453690883-31220-2-git-send-email-xuejiancheng@huawei.com>
On ma, 2016-01-25 at 11:01 +0800, Jiancheng Xue wrote:
> --- a/drivers/clk/hisilicon/Kconfig
> +++ b/drivers/clk/hisilicon/Kconfig
> +config COMMON_CLK_HI3519
> + bool "Hi3519 Clock Driver"
> + depends on ARCH_HISI
> + default y
> + help
> + Build the clock driver for hi3519.
> --- a/drivers/clk/hisilicon/Makefile
> +++ b/drivers/clk/hisilicon/Makefile
> +obj-$(CONFIG_COMMON_CLK_HI3519) += clk-hi3519.o
If I parsed the above correctly clk-hi3519.o can only be built-in,
right?
> --- /dev/null
> +++ b/drivers/clk/hisilicon/clk-hi3519.c
> +#include <linux/module.h>
So is this include actually needed?
> +static int hi3519_clk_probe(struct platform_device *pdev)
> +{
> + struct device_node *np = pdev->dev.of_node;
> + struct hisi_clock_data *clk_data;
> +
> + clk_data = hisi_clk_init(np, HI3519_NR_CLKS);
> + if (!clk_data)
> + return -ENODEV;
> +
> + hisi_clk_register_fixed_rate(hi3519_fixed_rate_clks,
> +
> ARRAY_SIZE(hi3519_fixed_rate_clks),
> + clk_data);
> + hisi_clk_register_mux(hi3519_mux_clks,
> ARRAY_SIZE(hi3519_mux_clks),
> + clk_data);
> + hisi_clk_register_gate(hi3519_gate_clks,
> + ARRAY_SIZE(hi3519_gate_clks), clk_data);
> +
> + return hisi_reset_init(np);
> +}
(evolution 3.16.5 makes replying to code quite a challenge.)
> +static const struct of_device_id hi3519_clk_match_table[] = {
> + { .compatible = "hisilicon,hi3519-crg" },
> + { }
> +};
> +MODULE_DEVICE_TABLE(of, hi3519_clk_match_table);
Last time I checked MODULE_DEVICE_TABLE is preprocessed away for built
-in code.
> +static void __exit hi3519_clk_exit(void)
> +{
> + platform_driver_unregister(&hi3519_clk_driver);
> +}
> +module_exit(hi3519_clk_exit);
Not needed for built-in only code.
> +MODULE_DESCRIPTION("HiSilicon Hi3519 Clock Driver");
Ditto.
> --- a/drivers/clk/hisilicon/clk.c
> +++ b/drivers/clk/hisilicon/clk.c
> +EXPORT_SYMBOL(hisi_clk_init);
What module uses this export?
> +EXPORT_SYMBOL(hisi_clk_register_fixed_rate);
Ditto.
> +EXPORT_SYMBOL(hisi_clk_register_fixed_factor);
Ditto.
> +EXPORT_SYMBOL(hisi_clk_register_mux);
Ditto.
> +EXPORT_SYMBOL(hisi_clk_register_divider);
Ditto.
> +EXPORT_SYMBOL(hisi_clk_register_gate);
Ditto.
> +EXPORT_SYMBOL(hisi_clk_register_gate_sep);
Ditto.
> --- /dev/null
> +++ b/drivers/clk/hisilicon/reset.c
> +int hisi_reset_init(struct device_node *np)
> +{
> + [...]
> +}
> +EXPORT_SYMBOL(hisi_reset_init);
Ditto.
> --- /dev/null
> +++ b/drivers/clk/hisilicon/reset.h
> +#ifdef CONFIG_RESET_CONTROLLER
> +int hisi_reset_init(struct device_node *np);
> +#else
> +static inline int hisi_reset_init(struct device_node *np)
> +{
> + return 0;
> +}
> +#endif
Thanks,
Paul Bolle
next prev parent reply other threads:[~2016-01-26 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 3:01 [PATCH v7 0/6] ARM: hisi: Add initial support including clock driver for Hi3519 soc Jiancheng Xue
2016-01-25 3:01 ` [PATCH v7 1/6] clk: hisilicon: add CRG driver for hi3519 soc Jiancheng Xue
2016-01-26 1:17 ` Paul Bolle [this message]
2016-01-27 3:28 ` xuejiancheng
2016-01-25 3:01 ` [PATCH v7 2/6] ARM: hisi: add compatible string for Hi3519 soc Jiancheng Xue
2016-01-25 3:01 ` [PATCH v7 3/6] ARM: config: hisi: enable CONFIG_RESET_CONTROLLER Jiancheng Xue
2016-01-25 3:01 ` [PATCH v7 4/6] ARM: debug: add hi3519 debug uart Jiancheng Xue
2016-01-26 3:07 ` xuejiancheng
2016-01-25 3:01 ` [PATCH v7 5/6] ARM: dt-bindings: add device tree bindings for Hi3519 sysctrl Jiancheng Xue
2016-01-25 3:01 ` [PATCH v7 6/6] ARM: dts: add dts files for Hi3519 Jiancheng Xue
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=1453771063.17181.56.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=arnd@arndb.de \
--cc=bintian.wang@huawei.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gaofei@hisilicon.com \
--cc=haojian.zhuang@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@linaro.org \
--cc=lidongpo@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=ml.yang@hisilicon.com \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=raojun@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=suwenping@hisilicon.com \
--cc=xuejiancheng@hisilicon.com \
--cc=xuejiancheng@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=yanghongwei@hisilicon.com \
--cc=yanhaifeng@hisilicon.com \
--cc=zhangfei.gao@linaro.org \
--cc=zhangzhenxing@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
all inboxes | Powered by JetHome®