linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	nm@ti.com, dianders@chromium.org, heiko@sntech.de,
	broonie@kernel.org
Subject: [GIT PULL] PM / AVS changes for v3.18 - v2
Date: Thu, 25 Sep 2014 12:05:42 -0700	[thread overview]
Message-ID: <7ha95nikqh.fsf@linaro.org> (raw)

Hi Rafael,

The first pull request was missing a dependency on a feature that went
in through Mark Brown's regulator tree, so it wouldn't actually compile
properly by itself.  This version pulls in that topic branch from Marks
tree (topic/voltage-ev branch, already part of -next), and now compiles fine.

Kevin

The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:

  Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux.git tags/avs-for-3.18

for you to fetch changes up to cd8caa18deff6d2d87a4e3161b4dd8c6da3c4f38:

  Merge branch 'topic/voltage-ev' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator into avs-next (2014-09-25 09:57:57 -0700)

----------------------------------------------------------------
PM / AVS changes for v3.18

- Add new driver for Rockchip IO voltage domains
- update MAINTAINERS to reflect maintenance of drivers/power/avs/*

----------------------------------------------------------------
Heiko Stübner (2):
      regulator: core: Add REGULATOR_EVENT_PRE_VOLTAGE_CHANGE (and ABORT)
      PM / AVS: rockchip-io: add driver handling Rockchip io domains

Kevin Hilman (2):
      MAINTAINERS: update entry for drivers/power/avs
      Merge branch 'topic/voltage-ev' of git://git.kernel.org/.../broonie/regulator into avs-next

 Documentation/devicetree/bindings/power/rockchip-io-domain.txt |  83 +++++++++++++++++++
 MAINTAINERS                                                    |   4 +-
 drivers/power/avs/Kconfig                                      |   8 ++
 drivers/power/avs/Makefile                                     |   1 +
 drivers/power/avs/rockchip-io-domain.c                         | 351 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 drivers/regulator/core.c                                       |  63 +++++++++++++--
 include/linux/regulator/consumer.h                             |  20 +++++
 7 files changed, 521 insertions(+), 9 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/power/rockchip-io-domain.txt
 create mode 100644 drivers/power/avs/rockchip-io-domain.c


             reply	other threads:[~2014-09-25 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 19:05 Kevin Hilman [this message]
2014-09-25 20:42 ` [GIT PULL] PM / AVS changes for v3.18 - v2 Rafael J. Wysocki
2014-09-26  8:15 ` Mark Brown
2014-09-26 13:40   ` Rafael J. Wysocki
2014-09-26 14:23   ` Kevin Hilman
2014-09-26 15:42     ` Kevin Hilman

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=7ha95nikqh.fsf@linaro.org \
    --to=khilman@deeprootsystems.com \
    --cc=broonie@kernel.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    /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).