From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
To: "Zheng, Lv" <lv.zheng@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Mario Limonciello <Mario_Limonciello@dell.com>
Subject: Re: Unwanted delayed execution of _Qxx EC methods
Date: Fri, 06 Mar 2015 13:42:21 +0100 [thread overview]
Message-ID: <2027555.2ZAulqKXKg@xps13> (raw)
In-Reply-To: <1AE640813FDE7649BE1B193DEA596E88026D986B@SHSMSX101.ccr.corp.intel.com>
On Friday 06 March 2015 01:52:48 Zheng, Lv wrote:
> Hi, Gabriele
>
>
> I couldn't find this in my mail box, but saw it in the spinics.net.
>
> For EC query, there is no spec definitions around its behavior.
> Some EC firmware will have events queued (like edge triggering) while the others will keeps on reporting events when a condition is set (like level triggering).
> I think this case is a "level triggering like events", it is very useful for us to learn.
> We should be able to handle both firmware variations using one software architecture.
> Supporting this becomes possible now because we are able to switch EC handling between polling/interrupt modes using enhanced ACPICA GPE APIs.
> So we are able to switch EC into polling mode when SCI_EVT is detected and blocks further events and handles all transactions in polling mode.
> After completing the _Qxx evaluation we then can switch back to the interrupt mode and unblock further events.
>
> Could you please open a kernel Bugzilla entry at: https://bugzilla.kernel.org
> So we can discuss there with more test cases considered.
>
> Thanks and best regards
> -Lv
Hi,
thanks for the explanation.
I opened a bug report as requested, here the address:
https://bugzilla.kernel.org/show_bug.cgi?id=94411
Regards,
Gabriele
prev parent reply other threads:[~2015-03-06 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:20 Unwanted delayed execution of _Qxx EC methods Gabriele Mazzotta
[not found] ` <CAC=cRTM=F38k7m5y6OjSLaxwit_rRLeRSHO8W-BzgD9bLUzztw@mail.gmail.com>
2015-03-06 1:52 ` Zheng, Lv
2015-03-06 12:42 ` Gabriele Mazzotta [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=2027555.2ZAulqKXKg@xps13 \
--to=gabriele.mzt@gmail.com \
--cc=Mario_Limonciello@dell.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
/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