netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Roger Chen <roger.chen@rock-chips.com>
Cc: peppe.cavallaro@st.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
	kever.yang@rock-chips.com, eddie.cai@rock-chips.com
Subject: Re: [PATCH v2 2/6] GMAC: define clock ID used for GMAC
Date: Sun, 28 Dec 2014 21:51:14 +0100	[thread overview]
Message-ID: <1490915.LqZ81LD0Jb@phil> (raw)
In-Reply-To: <1417056766-3678-1-git-send-email-roger.chen@rock-chips.com>

Hi Roger,

patches modifying the rockchip clock parts should have a subject like
	clk: rockchip: .....

Same for the following patch

Am Donnerstag, 27. November 2014, 10:52:46 schrieb Roger Chen:
> Signed-off-by: Roger Chen <roger.chen@rock-chips.com>
> ---
>  include/dt-bindings/clock/rk3288-cru.h |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/include/dt-bindings/clock/rk3288-cru.h
> b/include/dt-bindings/clock/rk3288-cru.h index 100a08c..f9496f5 100644
> --- a/include/dt-bindings/clock/rk3288-cru.h
> +++ b/include/dt-bindings/clock/rk3288-cru.h
> @@ -72,6 +72,10 @@
>  #define SCLK_HEVC_CABAC		111
>  #define SCLK_HEVC_CORE		112
> 
> +#define SCLK_MAC_PLL		150

Why do you need to export the mac pll source selection?
I understand SCLK_MAC below, as you will want to select ext_gmac explicitly if 
available. But otherwise, why would you need to explicitly select the pll 
source?

The clock framework is intelligent enough that when you do a 
clk_set_rate(sclk_mac, 50000000) for example that it will select the best pll 
source + best divider to provide the most accurate frequency for this, so 
there should be no need to handle the pll source manually.


Heiko

> +#define SCLK_MAC		151
> +#define SCLK_MACREF_OUT		152
> +
>  #define DCLK_VOP0		190
>  #define DCLK_VOP1		191

  reply	other threads:[~2014-12-28 20:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  2:49 [PATCH v2 0/6] support GMAC driver for RK3288 Roger Chen
2014-11-27  2:51 ` Roger Chen
2014-11-27  2:52 ` [PATCH v2 1/6] GMAC: add driver for Rockchip RK3288 SoCs integrated GMAC Roger Chen
2014-12-01 23:44   ` Heiko Stübner
2014-12-03  7:57     ` Roger
2014-12-25  0:46       ` Roger
2014-12-28 20:28         ` Heiko Stübner
2014-12-25  2:32       ` Chen-Yu Tsai
2014-11-27  2:52 ` [PATCH v2 2/6] GMAC: define clock ID used for GMAC Roger Chen
2014-12-28 20:51   ` Heiko Stübner [this message]
2014-11-27  2:52 ` [PATCH v2 3/6] GMAC: modify CRU config for Rockchip RK3288 SoCs integrated GMAC Roger Chen
2014-11-27  2:53 ` [PATCH v2 4/6] ARM: dts: rockchip: add gmac info for rk3288 Roger Chen
2014-11-27  2:53 ` [PATCH v2 5/6] ARM: dts: rockchip: enable gmac on RK3288 evb board Roger Chen
2014-11-27  2:53 ` [PATCH v2 6/6] GMAC: add document for Rockchip RK3288 GMAC Roger Chen

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=1490915.LqZ81LD0Jb@phil \
    --to=heiko@sntech.de \
    --cc=eddie.cai@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=roger.chen@rock-chips.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).