From: "Raj, Ashok" <ashok.raj@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>,
linux-kernel@vger.kernel.org, Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH 1/1] pci: pciehp: Handle MRL interrupts to enable slot for hotplug.
Date: Sat, 21 Nov 2020 17:31:33 -0800 [thread overview]
Message-ID: <20201122013133.GA22190@araj-mobl1.jf.intel.com> (raw)
In-Reply-To: <20201121111050.GA6854@wunner.de>
On Sat, Nov 21, 2020 at 12:10:50PM +0100, Lukas Wunner wrote:
>
> > > > + /*
> > > > + * If ATTN is present and MRL is triggered
> > > > + * ignore the Presence Change Event.
> > > > + */
> > > > + if (ATTN_BUTTN(ctrl) && (events & PCI_EXP_SLTSTA_MRLSC))
> > > > + events &= ~PCI_EXP_SLTSTA_PDC;
> > >
> > > An Attention Button press results in a synthesized PDC event after
> > > 5 seconds, which may get lost due to the above if-statement.
> >
> > When its synthesized you don't get the MRLSC? So we won't nuke the PDC then
> > correct?
>
> I just meant to say, pciehp_queue_pushbutton_work() will synthesize
> a PDC event after 5 seconds and with the above code snippet, if an
> MRL event happens simultaneously, that synthesized PDC event would
> be lost. So I'd just drop the above code snippet. I think you
> just need to subscribe to MRL events and propagate them to
> pciehp_handle_presence_or_link_change(). There, you'd bring down
> the slot if an MRL event has occurred (same as DLLSC or PDC).
> Then, check whether MRL is closed. If so, and if presence or link
> is up, try to bring up the slot.
>
> If the MRL is open when slot or presence has gone up, the slot is not
> brought up. But once MRL is closed, there'll be another MRL event and
> *then* the slot is brought up.
>
Sounds good.. I'll send the update patch.
next prev parent reply other threads:[~2020-11-22 1:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 23:01 [PATCH 1/1] pci: pciehp: Handle MRL interrupts to enable slot for hotplug Ashok Raj
2020-10-16 23:43 ` Raj, Ashok
2020-11-19 7:51 ` Lukas Wunner
2020-11-19 22:08 ` Raj, Ashok
2020-11-19 22:27 ` Bjorn Helgaas
2020-11-19 22:37 ` Raj, Ashok
2020-11-20 19:33 ` Kuppuswamy, Sathyanarayanan
2020-11-21 11:10 ` Lukas Wunner
2020-11-22 1:31 ` Raj, Ashok [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-25 22:54 Ashok Raj
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=20201122013133.GA22190@araj-mobl1.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--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