[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52262629.8010605@wwwdotorg.org>
Date: Tue, 03 Sep 2013 12:10:49 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: Peter De Schrijver <pdeschrijver@...dia.com>
CC: linux-tegra@...r.kernel.org,
Mike Turquette <mturquette@...aro.org>,
Joseph Lo <josephl@...dia.com>,
Paul Walmsley <pwalmsley@...dia.com>,
Prashant Gaikwad <pgaikwad@...dia.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] clk: tegra: convert Tegra114 gate clocks to table
On 09/03/2013 07:31 AM, Peter De Schrijver wrote:
> This patch converts the Tegra114 gate clock registration to be table driven
> like the periph clocks. The same struct tegra_periph_init_data is used for the
> table, but some fields are unused. This makes the code easier to read and also
> paves the way to share clock data between Tegra SoCs.
> diff --git a/drivers/clk/tegra/clk-tegra114.c b/drivers/clk/tegra/clk-tegra114.c
> +static const char *clk_32k[] = {
> + "clk_32k",
> +};
I think those new arrays of strings are only used ...
> @@ -2114,6 +2023,26 @@ static __init void tegra114_periph_clk_init(void __iomem *clk_base)
> + for (i = 0; i < ARRAY_SIZE(tegra_periph_gate_clk_list); i++) {
> + int reg_bank;
> +
> + data = &tegra_periph_gate_clk_list[i];
> + reg_bank = get_reg_bank(data->periph.gate.clk_num);
> +
> + if (reg_bank >= 0) {
> + clk = tegra_clk_register_periph_gate(data->name,
> + data->parent_names[0],
... here. If so, why make them arrays? Surely they could just be a const
char * inside tegra_periph_gate_clk_list[i]?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists