devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 1/2] clk: rockchip: add clock ID for usbphy480m_src
@ 2014-11-13  7:22 Kever Yang
  2014-12-16 21:02 ` Doug Anderson
       [not found] ` <1415863357-15680-1-git-send-email-kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
  0 siblings, 2 replies; 3+ messages in thread
From: Kever Yang @ 2014-11-13  7:22 UTC (permalink / raw)
  To: Heiko Stuebner, Mike Turquette
  Cc: dianders, sonnyrao, addy.ke, cf, dkl, huangtao, linux-rockchip,
	Kever Yang, Rob Herring, Pawel Moll, Mark Rutland, Ian Campbell,
	Kumar Gala, Mark yao, devicetree, linux-kernel

There are 3 different parent clock from different usbphy,
all of them are fixed 480MHz, it is not able to auto select
by clock core to the 2nd and the 3rd parent.
For different use case for different board, we may need to
select different usbphy clock out as parent manually.

Add the clock ID for it so that we can use in dts.

Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
---

 include/dt-bindings/clock/rk3288-cru.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/dt-bindings/clock/rk3288-cru.h b/include/dt-bindings/clock/rk3288-cru.h
index 100a08c..3dcc906 100644
--- a/include/dt-bindings/clock/rk3288-cru.h
+++ b/include/dt-bindings/clock/rk3288-cru.h
@@ -71,6 +71,7 @@
 #define SCLK_HDMI_CEC		110
 #define SCLK_HEVC_CABAC		111
 #define SCLK_HEVC_CORE		112
+#define SCLK_USBPHY480M_SRC	113
 
 #define DCLK_VOP0		190
 #define DCLK_VOP1		191
-- 
1.9.1

^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-01-12 20:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-13  7:22 [PATCH 1/2] clk: rockchip: add clock ID for usbphy480m_src Kever Yang
2014-12-16 21:02 ` Doug Anderson
     [not found] ` <1415863357-15680-1-git-send-email-kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-01-12 20:47   ` Heiko Stübner

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).