From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Zhengqiang <zhengqiang10@huawei.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH] Bug fix for PME interrupt handler, add Root Status check
Date: Fri, 29 Sep 2017 15:12:16 +0200 [thread overview]
Message-ID: <CAJZ5v0ii5CSzmnNqrgGTyAG-2ckc8cebJDWH6f+BU3__9umDDQ@mail.gmail.com> (raw)
In-Reply-To: <59CDE3E8.7050702@huawei.com>
On Fri, Sep 29, 2017 at 8:10 AM, Zhengqiang <zhengqiang10@huawei.com> wrote:
> Hi,Rafael, thanks for you reply.
> please see my comment.
>
> On 2017/9/29 7:13, Rafael J. Wysocki wrote:
>> On Thu, Sep 28, 2017 at 5:54 AM, Qiang <zhengqiang10@huawei.com> wrote:
>>> PCIe PME and hot plug share same interrupt number. In some special case,
>>> Link down event cause hot plug interrupt, devices is not disconnected,
>>> But read config will return 0xff.
>>>
>>> In that case, PME work function will run and not return Because
>>> Root Status PME bit always 1 and can not be cleared.
>>>
>>> This patch add Root Status check in PME interrupt handler,
>>> Just do same as pciehp isr Slot status check.
>>>
>>> Signed-off-by: Qiang Zheng <zhengqiang10@huawei.com>
>>> ---
>>> drivers/pci/pcie/pme.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/pci/pcie/pme.c b/drivers/pci/pcie/pme.c
>>> index fafdb16..67144f5 100644
>>> --- a/drivers/pci/pcie/pme.c
>>> +++ b/drivers/pci/pcie/pme.c
>>> @@ -273,7 +273,7 @@ static irqreturn_t pcie_pme_irq(int irq, void *context)
>>> spin_lock_irqsave(&data->lock, flags);
>>> pcie_capability_read_dword(port, PCI_EXP_RTSTA, &rtsta);
>>>
>>> - if (!(rtsta & PCI_EXP_RTSTA_PME)) {
>>> + if (rtsta == (u32)(~0) || !(rtsta & PCI_EXP_RTSTA_PME)) {
>>> spin_unlock_irqrestore(&data->lock, flags);
>>> return IRQ_NONE;
>>> }
>>
>> OK, but isn't there a symbol for all ones in u32? And if there isn't,
>> what about adding it?
>>
> Here is Root Status register definitions.
Well, that's not what I meant.
You have "rtsta == (u32)(~0)" in the patch above, but you could do
"rtsta == U32_MAX" instead.
Thanks,
Rafael
next prev parent reply other threads:[~2017-09-29 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 3:54 [PATCH] Bug fix for PME interrupt handler, add Root Status check Qiang
2017-09-28 23:13 ` Rafael J. Wysocki
2017-09-29 6:10 ` Zhengqiang
2017-09-29 13:12 ` Rafael J. Wysocki [this message]
2017-09-30 1:46 ` Zhengqiang
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=CAJZ5v0ii5CSzmnNqrgGTyAG-2ckc8cebJDWH6f+BU3__9umDDQ@mail.gmail.com \
--to=rafael@kernel.org \
--cc=gabriele.paoloni@huawei.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=zhengqiang10@huawei.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).