linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] soc/tegra: Add generic PM domain support
Date: Fri, 29 Apr 2016 18:21:06 +0200	[thread overview]
Message-ID: <1461946869-26124-1-git-send-email-thierry.reding@gmail.com> (raw)

Hi ARM-SoC maintainers,

The following changes since commit 605aa5e48bfc3dbf0272bc4aac8674e06c19c1b3:

  dt-bindings: Update NVIDIA PMC for Tegra (2016-04-05 15:22:54 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.7-genpd

for you to fetch changes up to a38045121bf42110e6043d07315a7626b021a0db:

  soc/tegra: pmc: Add generic PM domain support (2016-04-29 17:17:47 +0200)

Thanks,
Thierry

----------------------------------------------------------------
soc/tegra: Add generic PM domain support

Implements generic PM domain support on top of the existing Tegra power-
gate API. Drivers are thus allowed to move away from the Tegra-specific
API and towards using generic power domains directly.

----------------------------------------------------------------
Jon Hunter (2):
      dt-bindings: Add power domain info for NVIDIA PMC
      soc/tegra: pmc: Add generic PM domain support

Thierry Reding (1):
      Merge branch 'for-4.7/soc' into for-4.7/genpd

 .../bindings/arm/tegra/nvidia,tegra20-pmc.txt      |  80 ++++
 drivers/soc/tegra/pmc.c                            | 485 ++++++++++++++++++---
 include/soc/tegra/pmc.h                            |   1 +
 3 files changed, 505 insertions(+), 61 deletions(-)

             reply	other threads:[~2016-04-29 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 16:21 Thierry Reding [this message]
2016-05-09 14:29 ` [GIT PULL] soc/tegra: Add generic PM domain support Arnd Bergmann

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=1461946869-26124-1-git-send-email-thierry.reding@gmail.com \
    --to=thierry.reding@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).