From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: Andy Gross <agross@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 7/7] clk: qcom: add camera clock controller driver for SM8450 SoC
Date: Tue, 12 Apr 2022 21:51:49 -0500 [thread overview]
Message-ID: <YlY6xYvy+Zzo9Bmm@builder.lan> (raw)
In-Reply-To: <20220314114252.1636683-1-vladimir.zapolskiy@linaro.org>
On Mon 14 Mar 06:42 CDT 2022, Vladimir Zapolskiy wrote:
> diff --git a/drivers/clk/qcom/camcc-sm8450.c b/drivers/clk/qcom/camcc-sm8450.c
[..]
> +static struct pll_vco lucid_evo_vco[] = {
const
> + { 249600000, 2000000000, 0 },
> +};
> +
> +static struct pll_vco rivian_evo_vco[] = {
const
> + { 864000000, 1056000000, 0 },
> +};
> +
> +static const struct alpha_pll_config cam_cc_pll0_config = {
> + .l = 0x3E,
Please use lowercase hex digits throughout the patch.
> + .alpha = 0x8000,
> + .config_ctl_val = 0x20485699,
> + .config_ctl_hi_val = 0x00182261,
> + .config_ctl_hi1_val = 0x32AA299C,
> + .user_ctl_val = 0x00008400,
> + .user_ctl_hi_val = 0x00000805,
> +};
> +
[..]
> +static struct platform_driver cam_cc_sm8450_driver = {
> + .probe = cam_cc_sm8450_probe,
> + .driver = {
> + .name = "cam_cc-sm8450",
> + .of_match_table = cam_cc_sm8450_match_table,
> + },
> +};
> +
> +static int __init cam_cc_sm8450_init(void)
> +{
> + return platform_driver_register(&cam_cc_sm8450_driver);
> +}
> +subsys_initcall(cam_cc_sm8450_init);
Camera isn't critical to boot the system, so I think you can replace
this with just module_platform_driver(cam_cc_sm8450_driver);
Rest looks good to me.
Thanks,
Bjorn
> +
> +static void __exit cam_cc_sm8450_exit(void)
> +{
> + platform_driver_unregister(&cam_cc_sm8450_driver);
> +}
> +module_exit(cam_cc_sm8450_exit);
> +
> +MODULE_DESCRIPTION("QTI CAMCC SM8450 Driver");
> +MODULE_LICENSE("GPL v2");
> --
> 2.33.0
>
prev parent reply other threads:[~2022-04-13 2:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 11:42 [PATCH v2 0/7] clk: qcom: add camera clock controller driver for SM8450 SoC Vladimir Zapolskiy
2022-03-14 11:42 ` [PATCH v2 1/7] dt-bindings: clock: add QCOM SM8450 camera clock bindings Vladimir Zapolskiy
2022-03-14 14:42 ` Rob Herring
2022-04-13 2:53 ` Bjorn Andersson
2022-03-14 11:42 ` [PATCH v2 2/7] arm64: dts: qcom: sm8450: Add description of camera clock controller Vladimir Zapolskiy
2022-03-14 11:42 ` [PATCH v2 3/7] clk: qcom: clk-alpha-pll: fix clk_trion_pll_configure description Vladimir Zapolskiy
2022-03-14 11:42 ` [PATCH v2 4/7] clk: qcom: clk-alpha-pll: limit exported symbols to GPL licensed code Vladimir Zapolskiy
2022-04-13 2:45 ` Bjorn Andersson
2022-03-14 11:42 ` [PATCH v2 5/7] clk: qcom: clk-alpha-pll: export lucid evo PLL configuration interfaces Vladimir Zapolskiy
2022-04-13 2:44 ` Bjorn Andersson
2022-03-14 11:42 ` [PATCH v2 6/7] clk: qcom: clk-alpha-pll: add rivian " Vladimir Zapolskiy
2022-03-14 11:42 ` [PATCH v2 7/7] clk: qcom: add camera clock controller driver for SM8450 SoC Vladimir Zapolskiy
2022-04-13 2:51 ` Bjorn Andersson [this message]
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=YlY6xYvy+Zzo9Bmm@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=vladimir.zapolskiy@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox