linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Alex_Gagniuc@Dellteam.com>
To: <lukas@wunner.de>, <mr.nuke.me@gmail.com>
Cc: <bhelgaas@google.com>, <Austin.Bolen@dell.com>,
	<keith.busch@intel.com>, <Shyam.Iyer@dell.com>,
	<okaya@kernel.org>, <linux-pci@vger.kernel.org>,
	<rafael.j.wysocki@intel.com>, <andy.shevchenko@gmail.com>,
	<mika.westerberg@linux.intel.com>, <poza@codeaurora.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC v2 1/4] PCI: hotplug: Add support for disabling in-band presence
Date: Thu, 21 Feb 2019 18:05:22 +0000	[thread overview]
Message-ID: <842e01310e894fd695b213652efdede7@ausx13mps321.AMER.DELL.COM> (raw)
In-Reply-To: 20190221071946.poqwdilfijpafhvb@wunner.de

On 2/21/19 1:20 AM, Lukas Wunner wrote:
> 
> [EXTERNAL EMAIL]
> 
> On Tue, Feb 19, 2019 at 07:20:27PM -0600, Alexandru Gagniuc wrote:
>> @@ -846,6 +846,9 @@ struct controller *pcie_init(struct pcie_device *dev)
>>   	if (pdev->is_thunderbolt)
>>   		slot_cap |= PCI_EXP_SLTCAP_NCCS;
>>   
>> +	if (pdev->no_in_band_presence)
>> +		ctrl->inband_presence_disabled = 1;
>> +
>>   	ctrl->slot_cap = slot_cap;
>>   	mutex_init(&ctrl->ctrl_lock);
>>   	mutex_init(&ctrl->state_lock);
> 
> The above hunk belongs in patch 4.
> 
> 
>> --- a/include/linux/pci.h
>> +++ b/include/linux/pci.h
>> @@ -413,6 +413,7 @@ struct pci_dev {
>>   	unsigned int	non_compliant_bars:1;	/* Broken BARs; ignore them */
>>   	unsigned int	is_probed:1;		/* Device probing in progress */
>>   	unsigned int	link_active_reporting:1;/* Device capable of reporting link active */
>> +	unsigned int	no_in_band_presence:1;	/* Device does not report in-band presence */
>>   	unsigned int	no_vf_scan:1;		/* Don't scan for VFs after IOV enablement */
>>   	pci_dev_flags_t dev_flags;
>>   	atomic_t	enable_cnt;	/* pci_enable_device has been called */
> 
> Same here.

:)

> Thanks,
> 
> Lukas
> 


  reply	other threads:[~2019-02-21 18:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  1:20 [PATCH RFC v2 0/4] PCI: pciehp: Do not turn off slot if presence comes up after link Alexandru Gagniuc
2019-02-20  1:20 ` [PATCH RFC v2 1/4] PCI: hotplug: Add support for disabling in-band presence Alexandru Gagniuc
2019-02-21  7:19   ` Lukas Wunner
2019-02-21 18:05     ` Alex_Gagniuc [this message]
2019-02-20  1:20 ` [PATCH RFC v2 2/4] PCI: pciehp: Do not turn off slot if presence comes up after link Alexandru Gagniuc
2019-02-21  7:36   ` Lukas Wunner
2019-02-22 19:56     ` Alex_Gagniuc
2019-02-23  6:49       ` Lukas Wunner
2019-02-24 22:27         ` Alex_Gagniuc
2019-02-20  1:20 ` [PATCH RFC v2 3/4] PCI: hotplug: Wait for PDS when in-band presence is disabled Alexandru Gagniuc
2019-02-20  1:20 ` [PATCH RFC v2 4/4] PCI: hotplug: Add quirk For Dell nvme pcie switches Alexandru Gagniuc
2019-02-21  7:56   ` Lukas Wunner
2019-02-21 18:35     ` Alex_Gagniuc
2019-02-22  1:20       ` Joe Perches
2019-02-22  2:04       ` Oliver
2019-02-22 19:19         ` Alex_Gagniuc
2019-02-21 15:38 ` [PATCH RFC v2 0/4] PCI: pciehp: Do not turn off slot if presence comes up after link Lukas Wunner
2019-02-21 18:17   ` Alex_Gagniuc
2019-04-19  0:01 ` Bjorn Helgaas
2019-04-19 15:22   ` [PATCH v3 " Alexandru Gagniuc
2019-04-19 15:22     ` [PATCH v3 1/4] PCI: hotplug: Add support for disabling in-band presence Alexandru Gagniuc
2019-04-19 15:22     ` [PATCH v3 2/4] PCI: pciehp: Do not turn off slot if presence comes up after link Alexandru Gagniuc
2019-04-19 15:22     ` [PATCH v3 3/4] PCI: hotplug: Wait for PDS when in-band presence is disabled Alexandru Gagniuc
2019-04-19 15:22     ` [PATCH v3 4/4] PCI: hotplug: Add quirk For Dell nvme pcie switches Alexandru Gagniuc
2019-04-19 21:00       ` Alan J. Wylie

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=842e01310e894fd695b213652efdede7@ausx13mps321.AMER.DELL.COM \
    --to=alex_gagniuc@dellteam.com \
    --cc=Austin.Bolen@dell.com \
    --cc=Shyam.Iyer@dell.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mr.nuke.me@gmail.com \
    --cc=okaya@kernel.org \
    --cc=poza@codeaurora.org \
    --cc=rafael.j.wysocki@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).