From: Stuart Hayes <stuart.w.hayes@gmail.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Austin Bolen <austin_bolen@dell.com>,
keith.busch@intel.com, Alexandru Gagniuc <mr.nuke.me@gmail.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"Gustavo A . R . Silva" <gustavo@embeddedor.com>,
Sinan Kaya <okaya@kernel.org>,
Oza Pawandeep <poza@codeaurora.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
lukas@wunner.de
Subject: Re: [PATCH v3 2/3] PCI: pciehp: Wait for PDS if in-band presence is disabled
Date: Mon, 21 Oct 2019 13:08:00 -0500 [thread overview]
Message-ID: <2ba3b9ea-488b-91ea-ba41-0602efaa21f4@gmail.com> (raw)
In-Reply-To: <20191021134111.GK2819@lahna.fi.intel.com>
On 10/21/19 8:41 AM, Mika Westerberg wrote:
> On Thu, Oct 17, 2019 at 03:32:55PM -0400, Stuart Hayes wrote:
>> From: Alexandru Gagniuc <mr.nuke.me@gmail.com>
>>
>> When inband presence is disabled, PDS may come up at any time, or not
>> at all. PDS being low may indicate that the card is still mating, and
>> we could expect contact bounce to bring down the link as well.
>>
>> It is reasonable to assume that most cards will mate in a hotplug slot
>> in about a second. Thus, when we know PDS only reflects out-of-band
>> presence, it's worthwhile to wait the extra second or so to make sure
>> the card is properly mated before loading the driver, and to prevent
>> the hotplug code from disabling a device if the presence detect change
>> goes active after the device is enabled.
>>
>> Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com>
>> Signed-off-by: Stuart Hayes <stuart.w.hayes@gmail.com>
>
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> One nit below.
>
>> ---
>> v2:
>> replace while(true) loop with do...while
>> v3
>> remove unused variable declaration (pds)
>> modify text of warning message
>>
>> drivers/pci/hotplug/pciehp_hpc.c | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/drivers/pci/hotplug/pciehp_hpc.c b/drivers/pci/hotplug/pciehp_hpc.c
>> index dc109d521f30..02eb811a014f 100644
>> --- a/drivers/pci/hotplug/pciehp_hpc.c
>> +++ b/drivers/pci/hotplug/pciehp_hpc.c
>> @@ -242,6 +242,22 @@ static bool pci_bus_check_dev(struct pci_bus *bus, int devfn)
>> return found;
>> }
>>
>> +static void pcie_wait_for_presence(struct pci_dev *pdev)
>> +{
>> + int timeout = 1250;
>> + u16 slot_status;
>> +
>> + do {
>> + pcie_capability_read_word(pdev, PCI_EXP_SLTSTA, &slot_status);
>> + if (!!(slot_status & PCI_EXP_SLTSTA_PDS))
>
> It is more readable if you write it like:
>
> if (slot_status & PCI_EXP_SLTSTA_PDS)
>
I agree, it is more readable, and the double bang shouldn't be needed for an
"if" condition. Thanks.
>> + return;
>> + msleep(10);
>> + timeout -= 10;
>> + } while (timeout > 0);
>> +
>> + pci_info(pdev, "Timeout waiting for Presence Detect state to be set\n");
>> +}
>> +
>> int pciehp_check_link_status(struct controller *ctrl)
>> {
>> struct pci_dev *pdev = ctrl_dev(ctrl);
>> @@ -251,6 +267,9 @@ int pciehp_check_link_status(struct controller *ctrl)
>> if (!pcie_wait_for_link(pdev, true))
>> return -1;
>>
>> + if (ctrl->inband_presence_disabled)
>> + pcie_wait_for_presence(pdev);
>> +
>> found = pci_bus_check_dev(ctrl->pcie->port->subordinate,
>> PCI_DEVFN(0, 0));
>>
>> --
>> 2.18.1
next prev parent reply other threads:[~2019-10-21 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 19:32 [PATCH v3 0/3] PCI: pciehp: Do not turn off slot if presence comes up after link Stuart Hayes
2019-10-17 19:32 ` [PATCH v3 1/3] PCI: pciehp: Add support for disabling in-band presence Stuart Hayes
2019-10-21 13:38 ` Mika Westerberg
2019-10-17 19:32 ` [PATCH v3 2/3] PCI: pciehp: Wait for PDS if in-band presence is disabled Stuart Hayes
2019-10-21 13:41 ` Mika Westerberg
2019-10-21 18:08 ` Stuart Hayes [this message]
2019-10-17 19:32 ` [PATCH v3 3/3] PCI: pciehp: Add dmi table for in-band presence disabled Stuart Hayes
2019-10-21 13:47 ` Mika Westerberg
2019-10-21 18:19 ` Stuart Hayes
2019-10-22 0:13 ` Alex G.
2019-10-22 9:42 ` Mika Westerberg
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=2ba3b9ea-488b-91ea-ba41-0602efaa21f4@gmail.com \
--to=stuart.w.hayes@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=austin_bolen@dell.com \
--cc=bhelgaas@google.com \
--cc=gustavo@embeddedor.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