From: Robin Murphy <robin.murphy@arm.com>
To: Ezequiel Garcia <ezequiel@collabora.com>,
Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org
Cc: mylene.josserand@collabora.com, sboyd@kernel.org,
Heiko Stuebner <heiko.stuebner@theobroma-systems.com>,
mturquette@baylibre.com, linux-kernel@vger.kernel.org,
jagan@amarulasolutions.com, linux-clk@vger.kernel.org
Subject: Re: [PATCH] clk: rockchip: use separate compatibles for rk3288w-cru
Date: Fri, 3 Jul 2020 17:19:30 +0100 [thread overview]
Message-ID: <2e331af7-6565-5f88-4f12-94468a4214ce@arm.com> (raw)
In-Reply-To: <00aaa4c4087b56cb4c2580e90f18c84055e105c9.camel@collabora.com>
On 2020-07-03 16:38, Ezequiel Garcia wrote:
> On Fri, 2020-07-03 at 17:28 +0200, Heiko Stuebner wrote:
>> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>>
>> Commit 1627f683636d ("clk: rockchip: Handle clock tree for rk3288w variant")
>> added the check for rk3288w-specific clock-tree changes but in turn would
>> require a double-compatible due to re-using the main rockchip,rk3288-cru
>> compatible as entry point.
>>
>> The binding change actually describes the compatibles as one or the other
>> so adapt the code accordingly and add a real second entry-point for the
>> clock controller.
>>
>> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>> ---
>> drivers/clk/rockchip/clk-rk3288.c | 15 +++++++++++++--
>> 1 file changed, 13 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/clk/rockchip/clk-rk3288.c b/drivers/clk/rockchip/clk-rk3288.c
>> index 204976e2d0cb..a39ca9809cc3 100644
>> --- a/drivers/clk/rockchip/clk-rk3288.c
>> +++ b/drivers/clk/rockchip/clk-rk3288.c
>> @@ -922,7 +922,7 @@ static struct syscore_ops rk3288_clk_syscore_ops = {
>> .resume = rk3288_clk_resume,
>> };
>>
>> -static void __init rk3288_clk_init(struct device_node *np)
>> +static void __init rk3288_common_init(struct device_node *np, bool is_w)
>
> From an API standpoint, avoid boolean arguments
> in favor of a simple enum.
And if the enum's just a selector between different data, consider
simply passing the data directly ;)
Robin.
>
> This case is trivial, but I think it's useful to avoid
> the anti pattern.
>
> Thanks for quickly working on this :)
>
> Ezequiel
>
>> {
>> struct rockchip_clk_provider *ctx;
>>
>> @@ -945,7 +945,7 @@ static void __init rk3288_clk_init(struct device_node *np)
>> rockchip_clk_register_branches(ctx, rk3288_clk_branches,
>> ARRAY_SIZE(rk3288_clk_branches));
>>
>> - if (of_device_is_compatible(np, "rockchip,rk3288w-cru"))
>> + if (is_w)
>> rockchip_clk_register_branches(ctx, rk3288w_hclkvio_branch,
>> ARRAY_SIZE(rk3288w_hclkvio_branch));
>> else
>> @@ -970,4 +970,15 @@ static void __init rk3288_clk_init(struct device_node *np)
>>
>> rockchip_clk_of_add_provider(np, ctx);
>> }
>> +
>> +static void __init rk3288_clk_init(struct device_node *np)
>> +{
>> + rk3288_common_init(np, false);
>> +}
>> CLK_OF_DECLARE(rk3288_cru, "rockchip,rk3288-cru", rk3288_clk_init);
>> +
>> +static void __init rk3288w_clk_init(struct device_node *np)
>> +{
>> + rk3288_common_init(np, true);
>> +}
>> +CLK_OF_DECLARE(rk3288w_cru, "rockchip,rk3288w-cru", rk3288w_clk_init);
>
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
prev parent reply other threads:[~2020-07-03 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 15:28 [PATCH] clk: rockchip: use separate compatibles for rk3288w-cru Heiko Stuebner
2020-07-03 15:38 ` Ezequiel Garcia
2020-07-03 16:19 ` Robin Murphy [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=2e331af7-6565-5f88-4f12-94468a4214ce@arm.com \
--to=robin.murphy@arm.com \
--cc=ezequiel@collabora.com \
--cc=heiko.stuebner@theobroma-systems.com \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=mylene.josserand@collabora.com \
--cc=sboyd@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 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).