From mboxrd@z Thu Jan 1 00:00:00 1970 From: heiko@sntech.de (Heiko =?ISO-8859-1?Q?St=FCbner?=) Date: Wed, 26 Nov 2014 18:43:40 +0100 Subject: [PATCH 1/2] clk: rockchip: add binding ID for DMC (memory controller) clocks on rk3288 In-Reply-To: References: <1416960783-25119-1-git-send-email-dianders@chromium.org> <1717801.sWHeWsmqUi@diego> Message-ID: <3545025.lFcuKWk0o9@diego> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am Dienstag, 25. November 2014, 16:49:08 schrieb Doug Anderson: > Heiko, > > On Tue, Nov 25, 2014 at 4:45 PM, Heiko St?bner wrote: > > Am Dienstag, 25. November 2014, 16:13:02 schrieb Doug Anderson: > >> From: Jeff Chen > >> > >> 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 > >> [dianders: split into two patches; adjusted commit msg] > >> Signed-off-by: Doug Anderson > > > > 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