From: Bjorn Helgaas <helgaas@kernel.org>
To: "Raj, Ashok" <ashok.raj@intel.com>
Cc: Lukas Wunner <lukas@wunner.de>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] pci: pciehp: Handle MRL interrupts to enable slot for hotplug.
Date: Thu, 19 Nov 2020 16:27:41 -0600 [thread overview]
Message-ID: <20201119222741.GA206150@bjorn-Precision-5520> (raw)
In-Reply-To: <20201119220807.GB102444@otc-nc-03>
Hi Ashok,
When you update this patch, can you run "git log --oneline
drivers/pci/hotplug/pciehp*" and make yours match? It is a severe
character defect of mine, but seeing subject lines that are obviously
different than the convention is a disincentive to look at the patch.
On Thu, Nov 19, 2020 at 02:08:07PM -0800, Raj, Ashok wrote:
> On Thu, Nov 19, 2020 at 08:51:20AM +0100, Lukas Wunner wrote:
> > Hi Ashok,
> >
> > my sincere apologies for the delay.
>
> No worries..
>
> >
> > On Fri, Sep 25, 2020 at 04:01:38PM -0700, Ashok Raj wrote:
> > > When Mechanical Retention Lock (MRL) is present, Linux doesn't process
> > > those change events.
> > >
> > > The following changes need to be enabled when MRL is present.
> > >
> > > 1. Subscribe to MRL change events in SlotControl.
> > > 2. When MRL is closed,
> > > - If there is no ATTN button, then POWER on the slot.
> > > - If there is ATTN button, and an MRL event pending, ignore
> > > Presence Detect. Since we want ATTN button to drive the
> > > hotplug event.
next prev parent reply other threads:[~2020-11-19 22:27 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 [this message]
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
-- 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=20201119222741.GA206150@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=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