From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: ACPI: EC: Fix logspam in "GPE storm avoidance" code
Date: Tue, 28 Oct 2008 21:25:18 +0300 [thread overview]
Message-ID: <4907590E.4070104@suse.de> (raw)
In-Reply-To: <49071C33.7030308@tuffmail.co.uk>
Alan Jenkins wrote:
> <http://bugzilla.kernel.org/show_bug.cgi?id=11841>
> "plenty of line "ACPI: EC: non-query interrupt received,
> switching to interrupt mode" in dmesg"
Probably, it is better to make pr_debug().
>
> GPE storm avoidance involves disabling the EC GPE during transactions.
> Unfortunately we forget to re-enable EC_FLAGS_GPE_MODE afterwards.
"We" don't forget it, "we" just use same mechanism as driver init. Thus if
for some reason interrupts do not start to arrive after we issue enable_gpe(),
we will not fall to timeouts.
>
> This happens to work because we re-enable it anyway when we detect
> the first confirmation interrupt of the next transaction. However,
> this causes lots of bogus "switching to interrupt mode" messages.
they are not "bogus", it is really switching the mode...
>
> Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
>
> diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
> index 7f0d81c..ba47c7c 100644
> --- a/drivers/acpi/ec.c
> +++ b/drivers/acpi/ec.c
> @@ -285,6 +285,7 @@ static int acpi_ec_transaction_unlocked(struct acpi_ec *ec, u8 command,
> /* check if we received SCI during transaction */
> ec_check_sci(ec, acpi_ec_read_status(ec));
> /* it is safe to enable GPE outside of transaction */
> + set_bit(EC_FLAGS_GPE_MODE, &ec->flags);
> acpi_enable_gpe(NULL, ec->gpe, ACPI_NOT_ISR);
> } else if (test_bit(EC_FLAGS_GPE_MODE, &ec->flags) &&
> t.irq_count > ACPI_EC_STORM_THRESHOLD) {
>
>
next prev parent reply other threads:[~2008-10-28 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 14:05 ACPI: EC: Fix logspam in "GPE storm avoidance" code Alan Jenkins
2008-10-28 18:25 ` Alexey Starikovskiy [this message]
2008-10-28 20:18 ` Alan Jenkins
2008-10-29 0:12 ` Henrique de Moraes Holschuh
2008-10-29 9:51 ` Alan Jenkins
2008-10-29 15:08 ` Henrique de Moraes Holschuh
2008-10-29 16:35 ` Alan Jenkins
2008-10-29 19:00 ` Alexey Starikovskiy
2008-11-01 11:03 ` Alan Jenkins
2008-10-30 1:47 ` Zhao Yakui
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=4907590E.4070104@suse.de \
--to=astarikovskiy@suse.de \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=linux-acpi@vger.kernel.org \
/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.