From: Thierry Reding <thierry.reding@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/6] PCI: tegra: Fixes and Tegra124 support
Date: Tue, 26 Aug 2014 17:08:14 +0200 [thread overview]
Message-ID: <20140826150812.GA26603@ulmo> (raw)
In-Reply-To: <1409065064-17617-1-git-send-email-thierry.reding@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]
On Tue, Aug 26, 2014 at 04:57:38PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> This series implements various fixes and adds support for Tegra124 to the
> Tegra PCIe controller driver.
>
> Patches 1 and 2 were already sent out separately earlier on but haven't been
> applied yet, so I'm including them here for convenience.
>
> Patches 3 to 5 are various fixes that should make the driver more reliable,
> though they don't (except maybe for patch 4) fix any known issues.
>
> Patch 6 finally adds support for Tegra124.
>
> Thierry
>
> Eric Yuen (1):
> PCI: tegra: Make sure the PCIe PLL is really reset
>
> Peter Daifuku (1):
> PCI: tegra: Fix extended configuration space mapping
>
> Thierry Reding (4):
> resource: Add device-managed request/release_resource()
> PCI: tegra: Implement a proper resource hierarchy
> PCI: tegra: Clear CLKREQ# enable on port disable
> PCI: tegra: Add Tegra124 support
>
> .../bindings/pci/nvidia,tegra20-pcie.txt | 25 +-
> Documentation/driver-model/devres.txt | 2 +
> drivers/pci/host/pci-tegra.c | 257 ++++++++++++++++++---
> include/linux/ioport.h | 5 +
> kernel/resource.c | 70 ++++++
> 5 files changed, 323 insertions(+), 36 deletions(-)
Hi Bjorn,
Right after sending this out I noticed that this series is missing a
change to the device tree binding that I've only had in my local tree,
so please don't apply this. I'll send out a v3 with that fixed shortly.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-08-26 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 14:57 [PATCH v2 0/6] PCI: tegra: Fixes and Tegra124 support Thierry Reding
2014-08-26 14:57 ` [PATCH v2 1/6] resource: Add device-managed request/release_resource() Thierry Reding
2014-08-26 14:57 ` [PATCH v2 2/6] PCI: tegra: Implement a proper resource hierarchy Thierry Reding
2014-08-26 14:57 ` [PATCH v2 3/6] PCI: tegra: Clear CLKREQ# enable on port disable Thierry Reding
2014-08-26 14:57 ` [PATCH v2 4/6] PCI: tegra: Fix extended configuration space mapping Thierry Reding
2014-08-26 14:57 ` [PATCH v2 5/6] PCI: tegra: Make sure the PCIe PLL is really reset Thierry Reding
2014-08-26 14:57 ` [PATCH v2 6/6] PCI: tegra: Add Tegra124 support Thierry Reding
2014-08-26 15:08 ` Thierry Reding [this message]
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=20140826150812.GA26603@ulmo \
--to=thierry.reding@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.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 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.