All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sanchayan Maity <maitysanchayan@gmail.com>
To: a.zummo@towertech.it, rtc-linux@googlegroups.com
Cc: stefan@agner.ch, shawn.guo@linaro.org,
	linux-kernel@vger.kernel.org,
	Sanchayan Maity <maitysanchayan@gmail.com>
Subject: [RESEND PATCHv2] Add SNVS clock support to rtc-snvs driver
Date: Wed,  3 Dec 2014 11:28:54 +0530	[thread overview]
Message-ID: <cover.1417585458.git.maitysanchayan@gmail.com> (raw)

For v2:
As such this patch remains the same, but is being resend
and in isolation after the previous discussions here.
https://lkml.org/lkml/2014/11/7/295

Since the changes on rtc-snvs.c will need to go through
the rtc subsystem tree and the DT changes cannot be applied
by Shawn, till this driver patch gets mainlined, this driver
patch I am sending by itself without the DT changes send
earlier.

The first version of the patches were send quiet a 
while back. 
https://lkml.org/lkml/2014/9/26/492

The reason for sending this v2 of the patches late was to
prevent any changes midway to the VF dts patches being tried
with the below commit.
https://lkml.org/lkml/2014/10/22/605

Changes since v1:
The clock enable and disable functions for the SNVS are
now optional and only enable/disable it, if it has been
defined in the device tree node. Instead of failing and 
returning error as in the earlier set of patches, this
makes sure that the driver does not break for the other
i.MX devices for which the clock has not been defined and
enabled elsewhere.

Sanchayan Maity (1):
  drivers/rtc/rtc-snvs: Add clock support

 drivers/rtc/rtc-snvs.c |   34 ++++++++++++++++++++++++++++++++--
 1 file changed, 32 insertions(+), 2 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2014-12-03  5:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03  5:58 Sanchayan Maity [this message]
2014-12-03  5:58 ` [RESEND PATCHv2] drivers/rtc/rtc-snvs: Add clock support Sanchayan Maity
2014-12-04  9:36   ` Stefan Agner
2014-12-04 10:05   ` Alessandro Zummo
2014-12-04 12:29     ` Stefan Agner
2014-12-04 16:54       ` Alessandro Zummo
2014-12-05  0:12   ` Andrew Morton
2014-12-05 14:54     ` Stefan Agner
2014-12-05 21:44       ` Andrew Morton

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.1417585458.git.maitysanchayan@gmail.com \
    --to=maitysanchayan@gmail.com \
    --cc=a.zummo@towertech.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=shawn.guo@linaro.org \
    --cc=stefan@agner.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.