From: Wei Xu <xuwei5@hisilicon.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
Linus Walleij <linus.walleij@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <lenb@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linuxarm <linuxarm@huawei.com>,
<shameerali.kolothum.thodi@huawei.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
John Garry <john.garry@huawei.com>, <salil.mehta@huawei.com>,
<shiju.jose@huawei.com>, <jinying@hisilicon.com>,
<zhangyi.ac@huawei.com>, <liguozhu@hisilicon.com>,
<tangkunshan@huawei.com>, huangdaode <huangdaode@hisilicon.com>
Subject: Re: [PATCH v2] gpio: pl061: Fix the issue failed to register the ACPI interrtupion
Date: Mon, 19 Aug 2019 20:59:47 +0800 [thread overview]
Message-ID: <5D5A9D43.4040508@hisilicon.com> (raw)
In-Reply-To: <CAHp75VfjE4V7yY1b3JYd_Mk9-8RTok2WCN=-MMrUBw5NN90o2A@mail.gmail.com>
Hi Andy,
Thanks!
On 2019/8/16 21:40, Andy Shevchenko wrote:
> On Fri, Aug 16, 2019 at 12:07 PM Wei Xu <xuwei5@hisilicon.com> wrote:
>> Invoke acpi_gpiochip_request_interrupts after the acpi data has been
>> attached to the pl061 acpi node to register interruption.
>>
>> Otherwise it will be failed to register interruption for the ACPI case.
>> Because in the gpiochip_add_data_with_key, acpi_gpiochip_add is invoked
>> after gpiochip_add_irqchip but at that time the acpi data has not been
>> attached yet.
>> 2. cat /proc/interrupts in the guest console:
>>
>> estuary:/$ cat /proc/interrupts
>> CPU0
>> 2: 3228 GICv3 27 Level arch_timer
>> 4: 15 GICv3 33 Level uart-pl011
>> 42: 0 GICv3 23 Level arm-pmu
>> IPI0: 0 Rescheduling interrupts
>> IPI1: 0 Function call interrupts
>> IPI2: 0 CPU stop interrupts
>> IPI3: 0 CPU stop (for crash dump) interrupts
>> IPI4: 0 Timer broadcast interrupts
>> IPI5: 0 IRQ work interrupts
>> IPI6: 0 CPU wake-up interrupts
>> Err: 0
>>
>> But on QEMU v3.0.0 and Linux kernel v5.2.0-rc7, pl061 interruption is
>> there as below:
>>
>> estuary:/$ cat /proc/interrupts
>> CPU0
>> 2: 2648 GICv3 27 Level arch_timer
>> 4: 12 GICv3 33 Level uart-pl011
>> 42: 0 GICv3 23 Level arm-pmu
>> 43: 0 ARMH0061:00 3 Edge ACPI:Event
>> IPI0: 0 Rescheduling interrupts
>> IPI1: 0 Function call interrupts
>> IPI2: 0 CPU stop interrupts
>> IPI3: 0 CPU stop (for crash dump) interrupts
>> IPI4: 0 Timer broadcast interrupts
>> IPI5: 0 IRQ work interrupts
>> IPI6: 0 CPU wake-up interrupts
>> Err: 0
> In above show only affected line.
OK. Will update it in v3.
>> And the whole dmesg log on Linux kernel v5.2.0-rc7 is as below:
> NO!
> Please, remove this huge noise!
Sorry for the noise!
I will drop it in v3.
Best Regards,
Wei
WARNING: multiple messages have this Message-ID (diff)
From: Wei Xu <xuwei5@hisilicon.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: salil.mehta@huawei.com, jinying@hisilicon.com,
tangkunshan@huawei.com, liguozhu@hisilicon.com,
Linus Walleij <linus.walleij@linaro.org>,
John Garry <john.garry@huawei.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
shameerali.kolothum.thodi@huawei.com,
Linuxarm <linuxarm@huawei.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
huangdaode <huangdaode@hisilicon.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
shiju.jose@huawei.com,
Mika Westerberg <mika.westerberg@linux.intel.com>,
zhangyi.ac@huawei.com,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v2] gpio: pl061: Fix the issue failed to register the ACPI interrtupion
Date: Mon, 19 Aug 2019 20:59:47 +0800 [thread overview]
Message-ID: <5D5A9D43.4040508@hisilicon.com> (raw)
In-Reply-To: <CAHp75VfjE4V7yY1b3JYd_Mk9-8RTok2WCN=-MMrUBw5NN90o2A@mail.gmail.com>
Hi Andy,
Thanks!
On 2019/8/16 21:40, Andy Shevchenko wrote:
> On Fri, Aug 16, 2019 at 12:07 PM Wei Xu <xuwei5@hisilicon.com> wrote:
>> Invoke acpi_gpiochip_request_interrupts after the acpi data has been
>> attached to the pl061 acpi node to register interruption.
>>
>> Otherwise it will be failed to register interruption for the ACPI case.
>> Because in the gpiochip_add_data_with_key, acpi_gpiochip_add is invoked
>> after gpiochip_add_irqchip but at that time the acpi data has not been
>> attached yet.
>> 2. cat /proc/interrupts in the guest console:
>>
>> estuary:/$ cat /proc/interrupts
>> CPU0
>> 2: 3228 GICv3 27 Level arch_timer
>> 4: 15 GICv3 33 Level uart-pl011
>> 42: 0 GICv3 23 Level arm-pmu
>> IPI0: 0 Rescheduling interrupts
>> IPI1: 0 Function call interrupts
>> IPI2: 0 CPU stop interrupts
>> IPI3: 0 CPU stop (for crash dump) interrupts
>> IPI4: 0 Timer broadcast interrupts
>> IPI5: 0 IRQ work interrupts
>> IPI6: 0 CPU wake-up interrupts
>> Err: 0
>>
>> But on QEMU v3.0.0 and Linux kernel v5.2.0-rc7, pl061 interruption is
>> there as below:
>>
>> estuary:/$ cat /proc/interrupts
>> CPU0
>> 2: 2648 GICv3 27 Level arch_timer
>> 4: 12 GICv3 33 Level uart-pl011
>> 42: 0 GICv3 23 Level arm-pmu
>> 43: 0 ARMH0061:00 3 Edge ACPI:Event
>> IPI0: 0 Rescheduling interrupts
>> IPI1: 0 Function call interrupts
>> IPI2: 0 CPU stop interrupts
>> IPI3: 0 CPU stop (for crash dump) interrupts
>> IPI4: 0 Timer broadcast interrupts
>> IPI5: 0 IRQ work interrupts
>> IPI6: 0 CPU wake-up interrupts
>> Err: 0
> In above show only affected line.
OK. Will update it in v3.
>> And the whole dmesg log on Linux kernel v5.2.0-rc7 is as below:
> NO!
> Please, remove this huge noise!
Sorry for the noise!
I will drop it in v3.
Best Regards,
Wei
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-19 12:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 9:05 [PATCH v2] gpio: pl061: Fix the issue failed to register the ACPI interrtupion Wei Xu
2019-08-16 9:05 ` Wei Xu
2019-08-16 13:40 ` Andy Shevchenko
2019-08-16 13:40 ` Andy Shevchenko
2019-08-19 12:59 ` Wei Xu [this message]
2019-08-19 12:59 ` Wei Xu
2019-08-18 12:58 ` kbuild test robot
2019-08-18 12:58 ` kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2019-08-16 8:58 Wei Xu
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=5D5A9D43.4040508@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=andy.shevchenko@gmail.com \
--cc=huangdaode@hisilicon.com \
--cc=jinying@hisilicon.com \
--cc=john.garry@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=lenb@kernel.org \
--cc=liguozhu@hisilicon.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=salil.mehta@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tangkunshan@huawei.com \
--cc=zhangyi.ac@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.