[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1717801.sWHeWsmqUi@diego>
Date: Wed, 26 Nov 2014 01:45:12 +0100
From: Heiko Stübner <heiko@...ech.de>
To: Doug Anderson <dianders@...omium.org>
Cc: cym@...k-chips.com, Mike Turquette <mturquette@...aro.org>,
Derek Basehore <dbasehore@...omium.org>,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
kever.yang@...k-chips.com, mark.yao@...k-chips.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] clk: rockchip: add binding ID for DMC (memory controller) clocks on rk3288
Am Dienstag, 25. November 2014, 16:13:02 schrieb Doug Anderson:
> From: Jeff Chen <cym@...k-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@...k-chips.com>
> [dianders: split into two patches; adjusted commit msg]
> Signed-off-by: Doug Anderson <dianders@...omium.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists