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 3/7] ARM: tegra: rework PCIe regulators
Date: Fri, 18 Jul 2014 16:45:36 +0200	[thread overview]
Message-ID: <1405694740-4090-3-git-send-email-thierry.reding@gmail.com> (raw)
In-Reply-To: <1405694740-4090-1-git-send-email-thierry.reding@gmail.com>

The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:

  Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-3.17-pcie-regulators

for you to fetch changes up to 122ee17dc2adb5c4a63d3a29af9f4e6e331087e5:

  ARM: tegra: Remove legacy PCIe power supply properties (2014-07-18 11:20:10 +0200)

----------------------------------------------------------------
ARM: tegra: rework PCIe regulators

This branch reworks the set of regulators that the Tegra PCIe driver
uses, so that the driver and DT bindings more correctly model what's
really going on in HW. For backwards-compatibility the driver will
fallback to using the old set of regulators if the new ones can't be
found.

I've made this a separate branch in case it needs to be pulled into the
PCIe tree to resolve any conflicts.

----------------------------------------------------------------
Thierry Reding (5):
      PCI: tegra: Overhaul regulator usage
      ARM: tegra: Add new PCIe regulator properties
      PCI: tegra: Implement accurate power supply scheme
      PCI: tegra: Remove deprecated power supply properties
      ARM: tegra: Remove legacy PCIe power supply properties

 .../bindings/pci/nvidia,tegra20-pcie.txt           |  30 ++-
 arch/arm/boot/dts/tegra20-harmony.dts              |   8 +-
 arch/arm/boot/dts/tegra20-tamonten.dtsi            |   7 +-
 arch/arm/boot/dts/tegra20-trimslice.dts            |   8 +-
 arch/arm/boot/dts/tegra30-beaver.dts               |  12 +-
 arch/arm/boot/dts/tegra30-cardhu.dtsi              |  11 +-
 drivers/pci/host/pci-tegra.c                       | 222 +++++++++++++++------
 7 files changed, 222 insertions(+), 76 deletions(-)

  parent reply	other threads:[~2014-07-18 14:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 14:45 [GIT PULL 1/7] ARM: tegra: move fuse code out of arch/arm Thierry Reding
2014-07-18 14:45 ` [GIT PULL 2/7] ARM: tegra: core code changes for 3.17 Thierry Reding
2014-07-19 19:31   ` Olof Johansson
2014-07-18 14:45 ` Thierry Reding [this message]
2014-07-19 19:44   ` [GIT PULL 3/7] ARM: tegra: rework PCIe regulators Olof Johansson
2014-07-18 14:45 ` [GIT PULL 4/7] ARM: tegra: Add XUSB pad controller support Thierry Reding
2014-07-19 19:50   ` Olof Johansson
2014-07-18 14:45 ` [GIT PULL 5/7] ARM: create a cros-ec-keyboard DT fragment Thierry Reding
2014-07-18 14:48   ` Thierry Reding
2014-07-18 14:45 ` [GIT PULL 6/7] ARM: tegra: device tree changes for 3.17 Thierry Reding
2014-07-19 19:52   ` Olof Johansson
2014-07-18 14:45 ` [GIT PULL 7/7] ARM: tegra: defconfig updates " Thierry Reding
2014-07-19 19:56   ` Olof Johansson
2014-07-19 19:29 ` [GIT PULL 1/7] ARM: tegra: move fuse code out of arch/arm Olof Johansson

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=1405694740-4090-3-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).