From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Prashant Gaikwad <pgaikwad@nvidia.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
Stephen Warren <swarren@wwwdotorg.org>,
Russell King <linux@arm.linux.org.uk>,
Simon Glass <sjg@chromium.org>,
Mike Turquette <mturquette@linaro.org>,
Joseph Lo <josephl@nvidia.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 09/10] clk: tegra: Implement clocks for Tegra114
Date: Mon, 4 Feb 2013 12:45:31 +0200 [thread overview]
Message-ID: <20130204104531.GQ2364@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <510F5E87.90801@nvidia.com>
On Mon, Feb 04, 2013 at 08:08:55AM +0100, Prashant Gaikwad wrote:
...
> > +#define RST_DEVICES_L 0x004
> > +#define RST_DEVICES_H 0x008
> > +#define RST_DEVICES_U 0x00C
> > +#define RST_DEVICES_V 0x358
> > +#define RST_DEVICES_W 0x35C
> > +#define RST_DEVICES_X 0x28C
> > +#define RST_DEVICES_SET_L 0x300
> > +#define RST_DEVICES_CLR_L 0x304
> > +#define RST_DEVICES_SET_H 0x308
> > +#define RST_DEVICES_CLR_H 0x30c
> > +#define RST_DEVICES_SET_U 0x310
> > +#define RST_DEVICES_CLR_U 0x314
> > +#define RST_DEVICES_SET_V 0x430
> > +#define RST_DEVICES_CLR_V 0x434
> > +#define RST_DEVICES_SET_W 0x438
> > +#define RST_DEVICES_CLR_W 0x43c
> > +#define RST_DEVICES_NUM 5
>
> RST_DEVICES_SET/CLR_X?
>
For all I can see (from the not yet public TRM), this is not actually used?
So I decided to not mention it here.
> > +
> > +#define CLK_OUT_ENB_L 0x010
> > +#define CLK_OUT_ENB_H 0x014
> > +#define CLK_OUT_ENB_U 0x018
> > +#define CLK_OUT_ENB_V 0x360
> > +#define CLK_OUT_ENB_W 0x364
> > +#define CLK_OUT_ENB_X 0x280
> > +#define CLK_OUT_ENB_SET_L 0x320
> > +#define CLK_OUT_ENB_CLR_L 0x324
> > +#define CLK_OUT_ENB_SET_H 0x328
> > +#define CLK_OUT_ENB_CLR_H 0x32c
> > +#define CLK_OUT_ENB_SET_U 0x330
> > +#define CLK_OUT_ENB_CLR_U 0x334
> > +#define CLK_OUT_ENB_SET_V 0x440
> > +#define CLK_OUT_ENB_CLR_V 0x444
> > +#define CLK_OUT_ENB_SET_W 0x448
> > +#define CLK_OUT_ENB_CLR_W 0x44c
> > +#define CLK_OUT_ENB_SET_X 0x284
> > +#define CLK_OUT_ENB_CLR_X 0x288
> > +#define CLK_OUT_ENB_NUM 6
>
> <snip>
>
> > +
> > + /* dsia */
> > + clk = clk_register_mux(NULL, "dsia_mux", mux_plld_out0_plld2_out0,
> > + ARRAY_SIZE(mux_plld_out0_plld2_out0), 0,
> > + clk_base + PLLD_BASE, 25, 1, 0, &pll_d_lock);
> > + clks[dsia_mux] = clk;
> > + clk = tegra_clk_register_periph_gate("dsia", "dsia_mux", 0, clk_base,
> > + 0, 48, &periph_h_regs,
> > + periph_clk_enb_refcnt);
> > + clk_register_clkdev(clk, "dsia", "tegradc.0");
> > + clks[dsia] = clk;
> > +
> > + /* dsib */
> > + clk = clk_register_mux(NULL, "dsib_mux", mux_plld_out0_plld2_out0,
> > + ARRAY_SIZE(mux_plld_out0_plld2_out0), 0,
> > + clk_base + PLLD2_BASE, 25, 1, 0, &pll_d2_lock);
> > + clks[dsib_mux] = clk;
> > + clk = tegra_clk_register_periph_gate("dsib", "dsib_mux", 0, clk_base,
> > + 0, 82, &periph_u_regs,
> > + periph_clk_enb_refcnt);
> > + clk_register_clkdev(clk, "dsib", "tegradc.1");
> > + clks[dsib] = clk;
> > +
>
> Can we use periph no div clock here for dsia and dsib?
>
Will check.
> > + /* xusb_hs_src */
> > + val = readl(clk_base + CLK_SOURCE_XUSB_SS_SRC);
> > + val |= BIT(25); /* always select PLLU_60M */
> > + writel(val, clk_base + CLK_SOURCE_XUSB_SS_SRC);
> > +
> > + clk = clk_register_fixed_factor(NULL, "xusb_hs_src", "pll_u_60M", 0,
> > + 1, 1);
> > + clks[xusb_hs_src] = clk;
> > +
>
> With device tree we can directly use pll_u_60M, no need to register
> clock with fixed factor 1.
This is true for now. In the future these clocks will need to be dvfs aware
though. I think it makes sense to have a separate clock then?
> Same comment for dis1-fixed, dsi2-fixed and mipi-cal-fast clocks.
>
Those might not need to become dvfs aware.
> > + /* xusb_host */
> > + clk = tegra_clk_register_periph_gate("xusb_host", "xusb_host_src", 0,
> > + clk_base, 0, 89, &periph_u_regs,
> > + periph_clk_enb_refcnt);
> > + clk_register_clkdev(clk, "tegra_xhci", "host");
> > + clks[xusb_host] = clk;
> > +
> > + /* xusb_ss */
> > + clk = tegra_clk_register_periph_gate("xusb_ss", "xusb_ss_src", 0,
> > + clk_base, 0, 156, &periph_w_regs,
> > + periph_clk_enb_refcnt);
> > + clk_register_clkdev(clk, "tegra_xhci", "ss");
> > + clks[xusb_host] = clk;
> > +
> > + /* xusb_dev */
> > + clk = tegra_clk_register_periph_gate("xusb_dev", "xusb_dev_src", 0,
> > + clk_base, 0, 95, &periph_u_regs,
> > + periph_clk_enb_refcnt);
> > + clk_register_clkdev(clk, "tegra_xhci", "dev");
>
> clks[xusb_dev] = clk;
>
Missing indeed.
Cheers,
Peter.
next prev parent reply other threads:[~2013-02-04 10:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 10:18 [PATCH v5 00/10] Tegra114 clockframework Peter De Schrijver
2013-02-01 10:18 ` [PATCH v5 01/10] clk: tegra: Refactor PLL programming code Peter De Schrijver
2013-02-04 6:06 ` Prashant Gaikwad
2013-02-04 14:32 ` Peter De Schrijver
2013-02-05 5:42 ` Prashant Gaikwad
2013-02-05 13:23 ` Peter De Schrijver
2013-02-06 12:32 ` Peter De Schrijver
2013-02-04 21:57 ` Stephen Warren
2013-02-01 10:18 ` [PATCH v5 02/10] clk: tegra: Add TEGRA_PLL_BYPASS flag Peter De Schrijver
2013-02-04 6:13 ` Prashant Gaikwad
2013-02-01 10:18 ` [PATCH v5 03/10] clk: tegra: Add PLL post divider table Peter De Schrijver
2013-02-04 6:28 ` Prashant Gaikwad
2013-02-01 10:18 ` [PATCH v5 04/10] clk: tegra: Add new fields and PLL types for Tegra114 Peter De Schrijver
2013-02-01 19:40 ` Rhyland Klein
2013-02-04 6:35 ` Prashant Gaikwad
2013-02-04 10:37 ` Peter De Schrijver
2013-02-01 10:18 ` [PATCH v5 05/10] clk: tegra: Add flags to tegra_clk_periph() Peter De Schrijver
2013-02-04 6:33 ` Prashant Gaikwad
2013-02-01 10:18 ` [PATCH v5 06/10] clk: tegra: Workaround for Tegra114 MSENC problem Peter De Schrijver
2013-02-04 6:39 ` Prashant Gaikwad
2013-02-01 10:18 ` [PATCH v5 07/10] ARM: tegra: Define Tegra114 CAR binding Peter De Schrijver
2013-02-04 21:16 ` Stephen Warren
2013-02-01 10:18 ` [PATCH v5 08/10] ARM: dt: Add references to tegra_car clocks Peter De Schrijver
2013-02-04 6:45 ` Prashant Gaikwad
2013-02-01 10:18 ` [PATCH v5 09/10] clk: tegra: Implement clocks for Tegra114 Peter De Schrijver
2013-02-04 7:08 ` Prashant Gaikwad
2013-02-04 10:45 ` Peter De Schrijver [this message]
2013-02-04 14:07 ` Peter De Schrijver
2013-02-04 21:01 ` Stephen Warren
2013-02-07 16:18 ` Peter De Schrijver
2013-02-04 14:34 ` Peter De Schrijver
2013-02-05 5:36 ` Prashant Gaikwad
2013-02-01 10:18 ` [PATCH v5 10/10] clk: tegra: devicetree match for nvidia,tegra114-car Peter De Schrijver
2013-02-04 7:10 ` Prashant Gaikwad
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=20130204104531.GQ2364@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=josephl@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=pgaikwad@nvidia.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sjg@chromium.org \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®