[1/2] clk: rockchip: add binding ID for DMC (memory controller) clocks on rk3288
diff mbox

Message ID 1416960783-25119-1-git-send-email-dianders@chromium.org
State New, archived
Headers show

Commit Message

Doug Anderson Nov. 26, 2014, 12:13 a.m. UTC
From: Jeff Chen <cym@rock-chips.com>

The DMC clocks need to be turned off at runtime, so we should have IDs
so we can export them.

Signed-off-by: Jeff Chen <cym@rock-chips.com>
[dianders: split into two patches; adjusted commit msg]
Signed-off-by: Doug Anderson <dianders@chromium.org>
---
 include/dt-bindings/clock/rk3288-cru.h | 4 ++++
 1 file changed, 4 insertions(+)

Comments

Heiko Stuebner Nov. 26, 2014, 12:45 a.m. UTC | #1
Am Dienstag, 25. November 2014, 16:13:02 schrieb Doug Anderson:
> From: Jeff Chen <cym@rock-chips.com>
> 
> The DMC clocks need to be turned off at runtime, so we should have IDs
> so we can export them.
> 
> Signed-off-by: Jeff Chen <cym@rock-chips.com>
> [dianders: split into two patches; adjusted commit msg]
> Signed-off-by: Doug Anderson <dianders@chromium.org>

both patches look ok to me and I'll probably pick them up tomorrow.

Just as handling question, do you plan on sending dts changes using these 
clocks in time for 3.19 [i.e. in the next couple of days]?

We have currently three clock patches/series adding new clock ids [this one, 
the mmc phases and Sonny's i2s_clkout] and I'm trying to dertermine if I need 
a shared branch for those.

Currently it doesn't look like the others will provide dts patches using the 
clocks in time, so it looks like I can skip the shared branch and we can use 
the clock ids regularly after the merge-window. Some true for your clocks?


Thanks
Heiko
Doug Anderson Nov. 26, 2014, 12:49 a.m. UTC | #2
Heiko,

On Tue, Nov 25, 2014 at 4:45 PM, Heiko Stübner <heiko@sntech.de> wrote:
> Am Dienstag, 25. November 2014, 16:13:02 schrieb Doug Anderson:
>> From: Jeff Chen <cym@rock-chips.com>
>>
>> The DMC clocks need to be turned off at runtime, so we should have IDs
>> so we can export them.
>>
>> Signed-off-by: Jeff Chen <cym@rock-chips.com>
>> [dianders: split into two patches; adjusted commit msg]
>> Signed-off-by: Doug Anderson <dianders@chromium.org>
>
> both patches look ok to me and I'll probably pick them up tomorrow.

OK, thanks!


> Just as handling question, do you plan on sending dts changes using these
> clocks in time for 3.19 [i.e. in the next couple of days]?

There's pretty much zero chance.  Maybe negative.


> We have currently three clock patches/series adding new clock ids [this one,
> the mmc phases and Sonny's i2s_clkout] and I'm trying to dertermine if I need
> a shared branch for those.
>
> Currently it doesn't look like the others will provide dts patches using the
> clocks in time, so it looks like I can skip the shared branch and we can use
> the clock ids regularly after the merge-window. Some true for your clocks?

Yup, no problem for me.  I provided this as two patches to you just in
case it was convenient, since I saw that as feedback in previous
submissions.

Thanks!

-Doug
Heiko Stuebner Nov. 26, 2014, 5:43 p.m. UTC | #3
Am Dienstag, 25. November 2014, 16:49:08 schrieb Doug Anderson:
> Heiko,
> 
> On Tue, Nov 25, 2014 at 4:45 PM, Heiko Stübner <heiko@sntech.de> wrote:
> > Am Dienstag, 25. November 2014, 16:13:02 schrieb Doug Anderson:
> >> From: Jeff Chen <cym@rock-chips.com>
> >> 
> >> The DMC clocks need to be turned off at runtime, so we should have IDs
> >> so we can export them.
> >> 
> >> Signed-off-by: Jeff Chen <cym@rock-chips.com>
> >> [dianders: split into two patches; adjusted commit msg]
> >> Signed-off-by: Doug Anderson <dianders@chromium.org>
> > 
> > both patches look ok to me and I'll probably pick them up tomorrow.
> 
> OK, thanks!

I've now added both patches to my clk branch.


> > We have currently three clock patches/series adding new clock ids [this
> > one, the mmc phases and Sonny's i2s_clkout] and I'm trying to dertermine
> > if I need a shared branch for those.
> > 
> > Currently it doesn't look like the others will provide dts patches using
> > the clocks in time, so it looks like I can skip the shared branch and we
> > can use the clock ids regularly after the merge-window. Some true for
> > your clocks?
> Yup, no problem for me.  I provided this as two patches to you just in
> case it was convenient, since I saw that as feedback in previous
> submissions.

Yep, I think it is the sanest of doing it in one way all the time, so we have 
the option of easily creating shared branches depending on what is needed.


Heiko

Patch
diff mbox

diff --git a/include/dt-bindings/clock/rk3288-cru.h b/include/dt-bindings/clock/rk3288-cru.h
index 100a08c..8e19ed5 100644
--- a/include/dt-bindings/clock/rk3288-cru.h
+++ b/include/dt-bindings/clock/rk3288-cru.h
@@ -141,6 +141,10 @@ 
 #define PCLK_VIO2_H2P		361
 #define PCLK_CPU		362
 #define PCLK_PERI		363
+#define PCLK_DDRUPCTL0		364
+#define PCLK_PUBL0		365
+#define PCLK_DDRUPCTL1		366
+#define PCLK_PUBL1		367
 
 /* hclk gates */
 #define HCLK_GPS		448