linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maitysanchayan@gmail.com (Sanchayan Maity)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Add SNVS clock gating and clock support to rtc-snvs driver
Date: Fri, 26 Sep 2014 18:43:58 +0530	[thread overview]
Message-ID: <cover.1411736171.git.maitysanchayan@gmail.com> (raw)

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

             reply	other threads:[~2014-09-26 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 13:13 Sanchayan Maity [this message]
2014-09-26 13:13 ` [PATCH 1/3] ARM: imx: clk-vf610: Add SNVS clock Sanchayan Maity
2014-09-26 13:14 ` [PATCH 2/3] ARM: dts: vf610: Add SNVS node Sanchayan Maity
2014-09-28  4:02   ` Shawn Guo
2014-09-26 13:14 ` [PATCH 3/3] drivers/rtc/rtc-snvs: Add clock support Sanchayan Maity
2014-09-28  3:56   ` Shawn Guo
2014-09-29 12:57     ` Stefan Agner
2014-09-29 13:05   ` Stefan Agner
2014-09-30  4:57     ` Sanchayan Maity

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=cover.1411736171.git.maitysanchayan@gmail.com \
    --to=maitysanchayan@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).