public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] clk: rockchip: add binding ID for DMC (memory controller) clocks on rk3288
Date: Wed, 26 Nov 2014 01:45:12 +0100	[thread overview]
Message-ID: <1717801.sWHeWsmqUi@diego> (raw)
In-Reply-To: <1416960783-25119-1-git-send-email-dianders@chromium.org>

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

  parent reply	other threads:[~2014-11-26  0:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  0:13 [PATCH 1/2] clk: rockchip: add binding ID for DMC (memory controller) clocks on rk3288 Doug Anderson
2014-11-26  0:13 ` [PATCH 2/2] clk: rockchip: use clock ID for DMC (memory controller) " Doug Anderson
2014-11-26  0:45 ` Heiko Stübner [this message]
2014-11-26  0:49   ` [PATCH 1/2] clk: rockchip: add binding ID for DMC (memory controller) clocks " Doug Anderson
2014-11-26 17:43     ` Heiko Stübner

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=1717801.sWHeWsmqUi@diego \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox