From: sathyanarayanan.kuppuswamy@linux.intel.com
To: bhelgaas@google.com, rjw@rjwysocki.net, lenb@kernel.org,
robert.moore@intel.com, erik.schmauss@intel.com,
ruscur@russell.cc
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, ashok.raj@intel.com,
keith.busch@intel.com,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: [PATCH v1 0/3] Add Error Disconnect Recover (EDR) support.
Date: Thu, 28 Feb 2019 12:49:46 -0800 [thread overview]
Message-ID: <cover.1551382061.git.sathyanarayanan.kuppuswamy@linux.intel.com> (raw)
From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
This patchset adds support for following features:
1. Error Disconnect Recover (EDR) support.
2. _OSC based negotiation support for DPC.
You can find EDR spec in the following link.
https://members.pcisig.com/wg/PCI-SIG/document/12614
Kuppuswamy Sathyanarayanan (3):
PCI/ACPI: Add _OSC based negotiation support for DPC
ACPI: Add Error Disconnect Recover (EDR) ACPI notifier support
PCI/DPC: Add Error Disconnect Recover (EDR) support
drivers/acpi/acpica/utdecode.c | 3 +-
drivers/acpi/bus.c | 5 +-
drivers/acpi/pci_root.c | 6 +
drivers/pci/pcie/Kconfig | 10 +
drivers/pci/pcie/dpc.c | 326 ++++++++++++++++++++++++++++++--
drivers/pci/pcie/portdrv_core.c | 8 +-
drivers/pci/probe.c | 1 +
include/acpi/actypes.h | 3 +-
include/linux/acpi.h | 3 +-
include/linux/pci.h | 1 +
10 files changed, 347 insertions(+), 19 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-28 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 20:49 sathyanarayanan.kuppuswamy [this message]
2019-02-28 20:49 ` [PATCH v1 1/3] PCI/ACPI: Add _OSC based negotiation support for DPC sathyanarayanan.kuppuswamy
2019-02-28 20:49 ` [PATCH v1 2/3] ACPI: Add Error Disconnect Recover (EDR) ACPI notifier support sathyanarayanan.kuppuswamy
2019-02-28 20:49 ` [PATCH v1 3/3] PCI/DPC: Add Error Disconnect Recover (EDR) support sathyanarayanan.kuppuswamy
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=cover.1551382061.git.sathyanarayanan.kuppuswamy@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=erik.schmauss@intel.com \
--cc=keith.busch@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=ruscur@russell.cc \
/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®