From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Georgi Djakov <georgi.djakov@linaro.org>, sboyd@codeaurora.org
Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v7 1/2] clk: qcom: Add support for SMD-RPM Clocks
Date: Wed, 24 Feb 2016 10:18:02 +0000 [thread overview]
Message-ID: <56CD835A.1010608@linaro.org> (raw)
In-Reply-To: <1456243999-22652-2-git-send-email-georgi.djakov@linaro.org>
On 23/02/16 16:13, Georgi Djakov wrote:
> +/* msm8916 */
> +#define RPM_XO_CLK_SRC 0
> +#define RPM_XO_A_CLK_SRC 1
> +#define RPM_PCNOC_CLK 2
> +#define RPM_PCNOC_A_CLK 3
> +#define RPM_SNOC_CLK 4
> +#define RPM_SNOC_A_CLK 5
> +#define RPM_BIMC_CLK 6
> +#define RPM_BIMC_A_CLK 7
> +#define RPM_QDSS_CLK 8
> +#define RPM_QDSS_A_CLK 9
> +#define RPM_BB_CLK1 10
> +#define RPM_BB_CLK1_A 11
> +#define RPM_BB_CLK2 12
> +#define RPM_BB_CLK2_A 13
> +#define RPM_RF_CLK1 14
> +#define RPM_RF_CLK1_A 15
> +#define RPM_RF_CLK2 16
> +#define RPM_RF_CLK2_A 17
> +#define RPM_BB_CLK1_PIN 18
> +#define RPM_BB_CLK1_A_PIN 19
> +#define RPM_BB_CLK2_PIN 20
> +#define RPM_BB_CLK2_A_PIN 21
> +#define RPM_RF_CLK1_PIN 22
> +#define RPM_RF_CLK1_A_PIN 23
> +#define RPM_RF_CLK2_PIN 24
> +#define RPM_RF_CLK2_A_PIN 25
> +
These names are more generic, and offsets are specific to the 8916 chip,
adding soc prefix to these would make more sense and also set a rule for
the next soc support patches too.
Thanks,
srini
next prev parent reply other threads:[~2016-02-24 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 16:13 [PATCH v7 0/2] Add initial support for RPM clocks Georgi Djakov
2016-02-23 16:13 ` [PATCH v7 1/2] clk: qcom: Add support for SMD-RPM Clocks Georgi Djakov
2016-02-24 10:18 ` Srinivas Kandagatla [this message]
2016-02-24 19:15 ` Stephen Boyd
2016-02-26 16:50 ` Georgi Djakov
2016-02-23 16:13 ` [PATCH v7 2/2] clk: qcom: Add support for RPM Clocks Georgi Djakov
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=56CD835A.1010608@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.