[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1392173573-59844-1-git-send-email-wangyijing@huawei.com>
Date: Wed, 12 Feb 2014 10:52:46 +0800
From: Yijing Wang <wangyijing@...wei.com>
To: Bjorn Helgaas <bhelgaas@...gle.com>
CC: <linux-kernel@...r.kernel.org>, <linux-pci@...r.kernel.org>,
Yijing Wang <wangyijing@...wei.com>,
Hanjun Guo <guohanjun@...wei.com>
Subject: [PATCH part1 v6 0/7] Introduce PCIe Device Serial Number capability support
v5->v6: Add is_frozen flag to protect pci bus from double frozen.
This series is based on Bjorn's pci-next branch.
Currently, more and more PCIe devices support PCIe DSN(Device Serial Number)
capability, we can use this cap to identify device. In some platform,
when we hotplug PCIe device, no interrupts will be received in system.
So we can not identify the device whether is changed during suspend.
PCIe DSN can help to identify this.
Legacy PCI device can achieve it by PCI Vital Product Data capability.
We can use its SN keyword to report the unique number.
But in my platform, PCI devices which support VPD SN cap report the
meaningless same string "0123456789".
Rework PCI VPD code to support device identification is not an easy work.
Plan to do it in part2.
Yijing Wang (7):
PCI: rework pci_find_next_ext_capability()
PCI: introduce pci_bus_find_ext_capability()
PCI: Add support for Device Serial Number capability
PCI: Introduce pci_serial_number_changed()
PCI: Add pci_dummy_ops to isolate pci device temporarily
PCI: Check pci device serial number when scan device
PCI: pciehp: Don't enable/disable slot on resume unless status
changed
drivers/pci/hotplug/pciehp_core.c | 10 ++-
drivers/pci/pci.c | 169 +++++++++++++++++++++++++++++++++++--
drivers/pci/pci.h | 2 +-
drivers/pci/probe.c | 15 +++-
include/linux/pci.h | 10 ++-
5 files changed, 192 insertions(+), 14 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists