linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Cartwright <joshc@codeaurora.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Alessandro Zummo <a.zummo@towertech.it>,
	linux-kernel@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, rtc-linux@googlegroups.com
Subject: [PATCH v2 0/6] rtc: make the pm8xxx RTC driver usable
Date: Mon, 10 Mar 2014 13:44:43 -0500	[thread overview]
Message-ID: <1394477089-3996-1-git-send-email-joshc@codeaurora.org> (raw)

This patchset is based on Stephen Boyd's PM8921 modernization/cleanups[1], and
allows for this RTC driver to be usable again.

Changes since v1:
  * Further style cleanups as suggested by Stephen Boyd
  * Dropped the use of reg-names/interrupt-names properties entirely

[1]: http://lkml.kernel.org/g/1393441166-32692-1-git-send-email-sboyd@codeaurora.org

Josh Cartwright (6):
  rtc: pm8xxx: fixup checkpatch/style issues
  rtc: pm8xxx: use regmap API for register accesses
  rtc: pm8xxx: use devm_request_any_context_irq
  rtc: pm8xxx: add support for devicetree
  rtc: pm8xxx: move device_init_wakeup() before rtc_register
  documentation: bindings: document PMIC8921/8058 RTC

 .../devicetree/bindings/rtc/qcom,pm8xxx-rtc.txt    |  21 ++
 drivers/rtc/rtc-pm8xxx.c                           | 284 ++++++++++-----------
 include/linux/mfd/pm8xxx/rtc.h                     |  25 --
 3 files changed, 150 insertions(+), 180 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/rtc/qcom,pm8xxx-rtc.txt
 delete mode 100644 include/linux/mfd/pm8xxx/rtc.h

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

             reply	other threads:[~2014-03-10 18:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 18:44 Josh Cartwright [this message]
2014-03-10 18:44 ` [PATCH v2 1/6] rtc: pm8xxx: fixup checkpatch/style issues Josh Cartwright
2014-03-10 18:44 ` [PATCH v2 2/6] rtc: pm8xxx: use regmap API for register accesses Josh Cartwright
2014-03-10 20:47   ` Andrew Morton
2014-03-10 21:35     ` Josh Cartwright
2014-03-10 21:43       ` Andrew Morton
2014-03-10 23:32       ` Mark Brown
2014-03-10 18:44 ` [PATCH v2 3/6] rtc: pm8xxx: use devm_request_any_context_irq Josh Cartwright
2014-03-10 18:44 ` [PATCH v2 4/6] rtc: pm8xxx: add support for devicetree Josh Cartwright
2014-03-10 20:47   ` Andrew Morton
2014-03-10 21:56     ` Josh Cartwright
2014-03-10 18:44 ` [PATCH v2 5/6] rtc: pm8xxx: move device_init_wakeup() before rtc_register Josh Cartwright
2014-03-10 18:44 ` [PATCH v2 6/6] documentation: bindings: document PMIC8921/8058 RTC Josh Cartwright
2014-03-10 21:22   ` Rob Herring
     [not found]     ` <CAL_JsqJe7M6i0RKWVPHbvyHbHscMtZmW-xbJuaJTePqYRKWrUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-10 22:11       ` Josh Cartwright
2014-03-10 22:18         ` Andrew Morton
     [not found]           ` <20140310151807.7274d58d3c50b884585244b6-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2014-03-12 17:17             ` [PATCH v3 6/6] mfd: devicetree: bindings: add pm8xxx RTC description Josh Cartwright
2014-03-21  8:12               ` Lee Jones

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=1394477089-3996-1-git-send-email-joshc@codeaurora.org \
    --to=joshc@codeaurora.org \
    --cc=a.zummo@towertech.it \
    --cc=akpm@linux-foundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    /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).