From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>,
Paul Walmsley <pwalmsley@nvidia.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-tegra@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: [PATCH 3/5] clk: tegra124: Add common clk IDs to clk-id.h
Date: Fri, 4 Oct 2013 12:12:42 +0300 [thread overview]
Message-ID: <1380878014-22088-4-git-send-email-pdeschrijver@nvidia.com> (raw)
In-Reply-To: <1380878014-22088-1-git-send-email-pdeschrijver@nvidia.com>
Tegra124 introduces a number of a new clocks. Introduce the corresponding
the IDs for them.
Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
---
drivers/clk/tegra/clk-id.h | 27 +++++++++++++++++++++++++++
1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/tegra/clk-id.h b/drivers/clk/tegra/clk-id.h
index b2a4d45..4ac3017 100644
--- a/drivers/clk/tegra/clk-id.h
+++ b/drivers/clk/tegra/clk-id.h
@@ -191,6 +191,33 @@ enum clk_id {
tegra_clk_clk_out_3_mux,
tegra_clk_dsia_mux,
tegra_clk_dsib_mux,
+
+ tegra124_clk_isp,
+ tegra_clk_uarte,
+ tegra_clk_entropy,
+ tegra_clk_i2c6,
+ tegra_clk_hdmi_audio,
+ tegra_clk_clk72Mhz,
+ tegra_clk_vic03,
+ tegra_clk_adx1,
+ tegra_clk_amx1,
+ tegra_clk_sor0,
+ tegra_clk_sata_oob,
+ tegra_clk_sata,
+ tegra_clk_vi_sensor2,
+ tegra_clk_ispb,
+ tegra_clk_vim2_clk,
+ tegra_clk_pcie,
+ tegra_clk_afi,
+ tegra_clk_sata_cold,
+ tegra_clk_dpaux,
+ tegra_clk_gpu,
+ tegra_clk_pll_p_out5,
+ tegra_clk_cml0,
+ tegra_clk_cml1,
+ tegra_clk_pll_c4,
+ tegra_clk_pll_dp,
+
tegra_clk_max,
};
--
1.7.7.rc0.72.g4b5ea.dirty
next prev parent reply other threads:[~2013-10-04 9:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 9:12 [PATCH 0/5] Tegra124 clock support Peter De Schrijver
2013-10-04 9:12 ` [PATCH 1/5] clk: tegra: Add support for PLLSS Peter De Schrijver
2013-10-10 10:39 ` Thierry Reding
2013-10-10 10:59 ` Peter De Schrijver
2013-10-14 15:03 ` Peter De Schrijver
2013-10-04 9:12 ` [PATCH 2/5] clk: tegra: Add periph regs bank X Peter De Schrijver
2013-10-10 10:43 ` Thierry Reding
2013-10-10 11:00 ` Peter De Schrijver
2013-10-04 9:12 ` Peter De Schrijver [this message]
2013-10-08 22:29 ` [PATCH 3/5] clk: tegra124: Add common clk IDs to clk-id.h Stephen Warren
2013-10-04 9:12 ` [PATCH 4/5] clk: tegra124: Add new peripheral clocks Peter De Schrijver
2013-10-08 22:31 ` Stephen Warren
2013-10-09 8:11 ` Peter De Schrijver
2013-10-09 16:00 ` Stephen Warren
2013-10-10 8:51 ` Peter De Schrijver
2013-10-04 9:12 ` [PATCH 5/5] clk: tegra124: Add support for Tegra124 clocks Peter De Schrijver
2013-10-08 22:31 ` [PATCH 0/5] Tegra124 clock support Stephen Warren
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=1380878014-22088-4-git-send-email-pdeschrijver@nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=pawel.moll@arm.com \
--cc=pgaikwad@nvidia.com \
--cc=pwalmsley@nvidia.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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®