public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yijing Wang <wangyijing@huawei.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Yijing Wang <wangyijing@huawei.com>,
	<linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>,
	Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH part1 v6 0/7] Introduce PCIe Device Serial Number capability support
Date: Mon, 17 Feb 2014 16:52:40 +0800	[thread overview]
Message-ID: <5301CDD8.5020808@huawei.com> (raw)
In-Reply-To: <1392173573-59844-1-git-send-email-wangyijing@huawei.com>

Hi Bjorn,
   Sorry to bother you, any comment about this series?

Thanks!
Yijing.

On 2014/2/12 10:52, Yijing Wang wrote:
> 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(-)
> 
> 
> 
> .
> 


-- 
Thanks!
Yijing


      parent reply	other threads:[~2014-02-17  8:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  2:52 [PATCH part1 v6 0/7] Introduce PCIe Device Serial Number capability support Yijing Wang
2014-02-12  2:52 ` [PATCH part1 v6 1/7] PCI: rework pci_find_next_ext_capability() Yijing Wang
2014-02-12  2:52 ` [PATCH part1 v6 2/7] PCI: introduce pci_bus_find_ext_capability() Yijing Wang
2014-02-12  2:52 ` [PATCH part1 v6 3/7] PCI: Add support for Device Serial Number capability Yijing Wang
2014-02-12  2:52 ` [PATCH part1 v6 4/7] PCI: Introduce pci_serial_number_changed() Yijing Wang
2014-02-12  7:26   ` Gu Zheng
2014-02-12  7:57     ` Yijing Wang
2014-02-12  2:52 ` [PATCH part1 v6 5/7] PCI: Add pci_dummy_ops to isolate pci device temporarily Yijing Wang
2014-02-12  7:46   ` Gu Zheng
2014-02-12  7:59     ` Yijing Wang
2014-02-12  2:52 ` [PATCH part1 v6 6/7] PCI: Check pci device serial number when scan device Yijing Wang
2014-02-12  2:52 ` [PATCH part1 v6 7/7] PCI: pciehp: Don't enable/disable slot on resume unless status changed Yijing Wang
2014-02-17  8:52 ` Yijing Wang [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=5301CDD8.5020808@huawei.com \
    --to=wangyijing@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.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