From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Deepak Sikri <deepak.sikri@st.com>
Cc: spear-devel@list.st.com, netdev@vger.kernel.org
Subject: Re: [PATCH 3/6] stmmac: Add support for CPU freq notifiers.
Date: Tue, 06 Mar 2012 09:04:14 +0100 [thread overview]
Message-ID: <4F55C4FE.7010607@st.com> (raw)
In-Reply-To: <4F54D62B.2080502@st.com>
On 3/5/2012 4:05 PM, Giuseppe CAVALLARO wrote:
[snip]
>> +#ifdef CONFIG_CPU_FREQ
>> +static inline void stmmac_clk_csr_set(struct stmmac_priv *priv, int clk_rate)
>> +{
>> +
>> + if ((clk_rate >= CSR_F_20M) && (clk_rate < CSR_F_35M))
>> + priv->plat->clk_csr = STMMAC_CLK_RANGE_20_35M;
>> + else if ((clk_rate >= CSR_F_35M) && (clk_rate < CSR_F_60M))
>> + priv->plat->clk_csr = STMMAC_CLK_RANGE_35_60M;
>> + else if ((clk_rate >= CSR_F_60M) && (clk_rate < CSR_F_100M))
>> + priv->plat->clk_csr = STMMAC_CLK_RANGE_60_100M;
>> + else if ((clk_rate >= CSR_F_100M) && (clk_rate < CSR_F_150M))
>> + priv->plat->clk_csr = STMMAC_CLK_RANGE_100_150M;
>> + else if ((clk_rate >= CSR_F_150M) && (clk_rate < CSR_F_250M))
>> + priv->plat->clk_csr = STMMAC_CLK_RANGE_150_250M;
>> + else if ((clk_rate >= CSR_F_250M) && (clk_rate < CSR_F_300M))
>> + priv->plat->clk_csr = STMMAC_CLK_RANGE_250_300M;
>> + else
>> + priv->plat->clk_csr = STMMAC_CLK_RANGE_150_250M;
Another note is that you are overriding the priv->plat->clk_csr that was
passed through the platform and used in some case on other architectures.
peppe
next prev parent reply other threads:[~2012-03-06 8:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:55 [PATCH 0/6] stmmac: Driver Updates Deepak Sikri
2012-03-02 12:55 ` [PATCH 1/6] stmmac: Define CSUM offload engine Types Deepak Sikri
2012-03-02 12:55 ` [PATCH 2/6] stmmac: Define MDC clock selection macros Deepak Sikri
2012-03-02 12:55 ` [PATCH 3/6] stmmac: Add support for CPU freq notifiers Deepak Sikri
2012-03-02 12:55 ` [PATCH 4/6] stmmac: Update stmmac descriptor checks for stmmac core prior to Rev-3.5 Deepak Sikri
2012-03-02 12:55 ` [PATCH 5/6] stmmac: configure burst related GMAC DMA parameters Deepak Sikri
2012-03-02 12:55 ` [PATCH 6/6] stmmac: Replace infinite loops by timeouts in mdio r/w Deepak Sikri
2012-03-06 7:55 ` Giuseppe CAVALLARO
2012-03-05 1:52 ` [PATCH 5/6] stmmac: configure burst related GMAC DMA parameters David Miller
2012-03-07 5:39 ` deepaksi
2012-03-06 7:43 ` Giuseppe CAVALLARO
2012-03-07 6:18 ` deepaksi
2012-03-05 1:51 ` [PATCH 4/6] stmmac: Update stmmac descriptor checks for stmmac core prior to Rev-3.5 David Miller
2012-03-05 4:01 ` Shiraz Hashim
2012-03-05 4:59 ` David Miller
2012-03-07 8:26 ` deepaksi
2012-03-06 7:10 ` Giuseppe CAVALLARO
2012-03-07 8:25 ` deepaksi
2012-03-07 8:45 ` Giuseppe CAVALLARO
2012-03-05 1:50 ` [PATCH 3/6] stmmac: Add support for CPU freq notifiers David Miller
2012-03-07 7:18 ` deepaksi
2012-03-05 15:05 ` Giuseppe CAVALLARO
2012-03-06 8:04 ` Giuseppe CAVALLARO [this message]
2012-03-07 8:28 ` deepaksi
2012-03-07 7:17 ` deepaksi
2012-03-05 14:34 ` [PATCH 2/6] stmmac: Define MDC clock selection macros Giuseppe CAVALLARO
2012-03-07 6:55 ` deepaksi
2012-03-07 7:19 ` Giuseppe CAVALLARO
2012-03-07 8:30 ` deepaksi
2012-03-05 14:13 ` [PATCH 1/6] stmmac: Define CSUM offload engine Types Giuseppe CAVALLARO
2012-03-07 6:50 ` deepaksi
2012-03-05 15:31 ` [PATCH 0/6] stmmac: Driver Updates Giuseppe CAVALLARO
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=4F55C4FE.7010607@st.com \
--to=peppe.cavallaro@st.com \
--cc=deepak.sikri@st.com \
--cc=netdev@vger.kernel.org \
--cc=spear-devel@list.st.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;
as well as URLs for NNTP newsgroup(s).