linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Alex_Gagniuc@Dellteam.com>
To: <lukas@wunner.de>
Cc: <mr.nuke.me@gmail.com>, <bhelgaas@google.com>,
	<Austin.Bolen@dell.com>, <keith.busch@intel.com>,
	<Shyam.Iyer@dell.com>, <gustavo@embeddedor.com>,
	<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: pciehp: Do not turn off slot if presence comes up after link
Date: Thu, 14 Feb 2019 19:26:28 +0000	[thread overview]
Message-ID: <59479c08d4624ffdb00883813ce80729@ausx13mps321.AMER.DELL.COM> (raw)
In-Reply-To: 20190214070100.kvikmkkcrp2d32sm@wunner.de

On 2/14/19 1:01 AM, Lukas Wunner wrote:
> On Wed, Feb 13, 2019 at 06:55:46PM +0000, Alex_Gagniuc@Dellteam.com wrote:
>> On 2/13/19 2:36 AM, Lukas Wunner wrote:
>>>> (*) A bit hypothetical: There is no hardware yet implementing the ECN.
>>>
>>> Hm, this contradicts Austin Bolen's e-mail of Jan 25 that "Yes, this
>>> platform disables in-band presence" (when asked whether your host
>>> controller already adheres to the ECN).
>>
>> Both statements are true. The hardware does indeed disable in-band
>> presence, in a rudimentary way that is not compliant with the ECN -- it
>> doesn't implement the bits required by the ECN.
> 
> Ugh, can a BIOS update make those machines compliant to the ECN

No, that is not possible, I'm told.

> or do we need a quirk specifically for them?

We might have to.

> It should match the spec, which I have no access to.

I am as irritated as you that the spec is not readily available for 
public viewing.

Cheers,
Alex

      reply	other threads:[~2019-02-14 19:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 21:06 [PATCH] PCI: pciehp: Do not turn off slot if presence comes up after link Alexandru Gagniuc
2019-02-08 19:56 ` Bjorn Helgaas
2019-02-09 11:58 ` Lukas Wunner
2019-02-11 23:48   ` Alex_Gagniuc
2019-02-12  8:30     ` Lukas Wunner
2019-02-12 10:37       ` Lukas Wunner
2019-02-12 23:57       ` Alex_Gagniuc
2019-02-13  8:36         ` Lukas Wunner
2019-02-13 18:55           ` Alex_Gagniuc
2019-02-14  7:01             ` Lukas Wunner
2019-02-14 19:26               ` Alex_Gagniuc [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=59479c08d4624ffdb00883813ce80729@ausx13mps321.AMER.DELL.COM \
    --to=alex_gagniuc@dellteam.com \
    --cc=Austin.Bolen@dell.com \
    --cc=Shyam.Iyer@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=mr.nuke.me@gmail.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).