[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <cover.1411736171.git.maitysanchayan@gmail.com>
Date: Fri, 26 Sep 2014 18:43:58 +0530
From: Sanchayan Maity <maitysanchayan@...il.com>
To: kernel@...gutronix.de, a.zummo@...ertech.it
Cc: b35083@...escale.com, rtc-linux@...glegroups.com,
shawn.guo@...escale.com, stefan@...er.ch, linux@....linux.org.uk,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Sanchayan Maity <maitysanchayan@...il.com>
Subject: [PATCH 0/3] Add SNVS clock gating and clock support to rtc-snvs driver
The following series of patches:
(1) Enable clock gating for the SNVS peripheral
(2) Adds SNVS devicetree node for the VF610 platform
(3) Add clock enable and disable support for the
SNVS peripheral which is required by RTC.
I would like to ask whether the solution i am
opting for in these set of patches is ok? Is there
another more appropriate solution? I couldn't find
any other piece of code which was enabling the clock
gating for the SNVS peripheral explicitly. Is this
expected to be taken care of by uboot?
Sanchayan Maity (3):
ARM: imx: clk-vf610: Add SNVS clock
ARM: dts: vf610: Add SNVS node
drivers/rtc/rtc-snvs: Add clock support
arch/arm/boot/dts/vf610.dtsi | 15 ++++++++++
arch/arm/mach-imx/clk-vf610.c | 1 +
drivers/rtc/rtc-snvs.c | 48 +++++++++++++++++++++++++------
include/dt-bindings/clock/vf610-clock.h | 3 +-
4 files changed, 57 insertions(+), 10 deletions(-)
--
1.7.9.5
--
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