From: Bjorn Helgaas <helgaas@kernel.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Jon Derrick <jonathan.derrick@intel.com>,
linux-pci@vger.kernel.org, Ashok Raj <ashok.raj@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Subject: Re: [PATCH] PCI: pciehp: Ignore spurious link inactive change when off
Date: Tue, 25 May 2021 15:17:44 -0500 [thread overview]
Message-ID: <20210525201744.GA1226059@bjorn-Precision-5520> (raw)
In-Reply-To: <20210525192512.GA3450@wunner.de>
On Tue, May 25, 2021 at 09:25:12PM +0200, Lukas Wunner wrote:
> On Mon, May 24, 2021 at 05:42:18PM -0500, Bjorn Helgaas wrote:
> > On Fri, Apr 09, 2021 at 02:59:35PM -0600, Jon Derrick wrote:
> > > When a specific x8 CEM card is bifurcated into x4x4 mode, and the
> > > upstream ports both support hotplugging on each respective x4 device, a
> > > slot management system for the CEM card requires both x4 devices to be
> > > sysfs removed from the OS before it can safely turn-off physical power.
> > > The implications are that Slot Control will display Powered Off status
> > > for the device where the device is actually powered until both ports
> > > have powered off.
> > >
> > > When power is removed from the first half, the link remains active to
> > > provide clocking while waiting for the second half to have power
> > > removed. When power is then removed from the second half, the first half
> > > starts shutdown sequence and will trigger a link status change event.
> > > This is misinterpreted as an enabling event due to positive presence
> > > detect and causes the first half to be re-enabled.
> > >
> > > The spurious enable can be resolved by ignoring link status change
> > > events when no link is active when in the off state.
>
> Sorry for not responding earlier, I missed this patch.
>
>
> > > --- a/drivers/pci/hotplug/pciehp_ctrl.c
> > > +++ b/drivers/pci/hotplug/pciehp_ctrl.c
> > > @@ -265,6 +265,11 @@ void pciehp_handle_presence_or_link_change(struct controller *ctrl, u32 events)
> > > cancel_delayed_work(&ctrl->button_work);
> > > fallthrough;
> > > case OFF_STATE:
> > > + if ((events & PCI_EXP_SLTSTA_DLLSC) && !link_active) {
> > > + mutex_unlock(&ctrl->state_lock);
> > > + break;
> > > + }
> > > +
>
> I think this change will inadvertently ignore events that shouldn't be
> ignored: E.g., a DLLSC event may have been triggered by replacement of
> the card in the slot and while Presence Detect State is 1, the link may
> not yet be active. The change above will cause not only the DLLSC but
> also the PDC event to be ignored.
>
> There are also reports of link flaps on card insertion and the above
> change may result in the slot not being brought up even though it should.
>
> The commit message sounds like powering down the CEM card takes longer
> than expected. We wait 1 second in set_slot_off() after disabling
> slot power and that's apparently not sufficient. The 1 second delay
> is mandated by section 6.7.1.8 of the PCIe Base Spec. If this card
> needs a longer delay, a quirk should be added rather than changing
> the algorithm for everyone.
I dropped this patch for now, thanks for taking a look, Lukas.
Bjorn
prev parent reply other threads:[~2021-05-25 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 20:59 [PATCH] PCI: pciehp: Ignore spurious link inactive change when off Jon Derrick
2021-04-09 21:38 ` Raj, Ashok
2021-05-24 22:42 ` Bjorn Helgaas
2021-05-25 19:25 ` Lukas Wunner
2021-05-25 20:17 ` Bjorn Helgaas [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=20210525201744.GA1226059@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=ashok.raj@intel.com \
--cc=dan.j.williams@intel.com \
--cc=jonathan.derrick@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sathyanarayanan.kuppuswamy@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).