From: Phil Edworthy <phil.edworthy@renesas.com>
To: Simon Horman <horms@verge.net.au>, Bjorn Helgaas <bhelgaas@google.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linux-sh@vger.kernel.org>,
Phil Edworthy <phil.edworthy@renesas.com>
Subject: [PATCH 0/4] Various R-Car PCIe patches
Date: Thu, 17 Dec 2015 13:22:33 +0000 [thread overview]
Message-ID: <1450358557-28376-1-git-send-email-phil.edworthy@renesas.com> (raw)
The first patch removes code that is no longer used. The next two allow us to
use runtim PM. The last patch is for PHY setup in order to get PCIe compliance
apparently. For that last patch, I've been told that this is what I must set.
Phil Edworthy (4):
PCI: rcar: remove unused pci_sys_data structure in pcie-rcar
PCI: rcar: Support runtime PM link state L1 handling in pcie-rcar
PCI: rcar: Add runtime PM support to pcie-rcar
PCI: rcar: Add Gen2 PHY setup to pcie-rcar
drivers/pci/host/pcie-rcar.c | 105 +++++++++++++++++++++++++++++++++----------
1 file changed, 81 insertions(+), 24 deletions(-)
--
2.5.0
next reply other threads:[~2015-12-17 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 13:22 Phil Edworthy [this message]
2015-12-17 13:22 ` [PATCH 1/4] PCI: rcar: remove unused pci_sys_data structure in pcie-rcar Phil Edworthy
2015-12-17 13:22 ` [PATCH 2/4] PCI: rcar: Support runtime PM link state L1 handling " Phil Edworthy
2015-12-17 13:30 ` Wolfram Sang
2015-12-17 13:41 ` Geert Uytterhoeven
2015-12-18 13:44 ` Phil Edworthy
2015-12-18 13:42 ` Phil Edworthy
2015-12-18 14:04 ` Wolfram Sang
2015-12-18 15:25 ` Phil Edworthy
2015-12-21 10:52 ` Phil Edworthy
2015-12-21 13:16 ` Geert Uytterhoeven
2016-01-04 14:18 ` Phil Edworthy
2016-01-04 14:56 ` Geert Uytterhoeven
2015-12-17 13:22 ` [PATCH 3/4] PCI: rcar: Add runtime PM support to pcie-rcar Phil Edworthy
2015-12-17 13:22 ` [PATCH 4/4] PCI: rcar: Add Gen2 PHY setup " Phil Edworthy
2015-12-17 13:33 ` Wolfram Sang
2015-12-18 13:43 ` Phil Edworthy
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=1450358557-28376-1-git-send-email-phil.edworthy@renesas.com \
--to=phil.edworthy@renesas.com \
--cc=bhelgaas@google.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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
all inboxes | Powered by JetHome®