public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Nils Faerber
	<nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Interrupt routing problem
Date: Tue, 13 Jan 2004 10:00:03 +0100	[thread overview]
Message-ID: <20040113090003.GB3599@hell.org.pl> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720CC3-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

Thus wrote Yu, Luming:
> > (I believe
> > there was a patch I tested and found working).
> 
> What patch ?

I believe it was the one attached below -- my bookmarks went wild some time
ago and I can't tell the bugzilla no., but it's certainly there.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org

diff -Bru linux-2.6.0-test8/drivers/acpi/hardware/hwgpe.c patched/drivers/acpi/hardware/hwgpe.c
--- linux-2.6.0-test8/drivers/acpi/hardware/hwgpe.c     2003-10-18 05:42:53.000000000 +0800
+++ patched/drivers/acpi/hardware/hwgpe.c       2003-10-28 16:30:34.000000000 +0800
@@ -578,3 +578,38 @@

        return (status);
 }
+
+acpi_status
+acpi_hw_enable_ec_gpes(
+       void)
+{
+
+       struct acpi_gpe_block_info      *gpe_block;
+       struct acpi_gpe_event_info      *gpe_event_info;
+       acpi_status                     status = AE_OK;
+       acpi_native_uint                i,j;
+
+       ACPI_FUNCTION_ENTRY ();
+
+       status = acpi_ut_acquire_mutex(ACPI_MTX_EVENTS);
+
+       if(ACPI_FAILURE(status)){
+               return (status);
+       }
+
+       for (i = 0; i < ACPI_MAX_GPE_BLOCKS; i++) {
+               gpe_block = acpi_gbl_gpe_fadt_blocks[i];
+               if (gpe_block) {
+                       for ( j = 0; j < gpe_block->register_count*8; j++){
+                               gpe_event_info= &gpe_block->event_info[j];
+                               if (gpe_event_info->handler &&
+                                               gpe_event_info->context)
+                                       acpi_hw_enable_gpe(gpe_event_info);
+                       }
+               }
+       }
+
+       (void) acpi_ut_release_mutex(ACPI_MTX_EVENTS);
+
+       return (status);
+}
diff -Bru linux-2.6.0-test8/drivers/acpi/hardware/hwsleep.c patched/drivers/acpi/hardware/hwsleep.c
--- linux-2.6.0-test8/drivers/acpi/hardware/hwsleep.c   2003-10-18 05:42:54.000000000 +0800
+++ patched/drivers/acpi/hardware/hwsleep.c     2003-10-24 18:53:10.000000000 +0800
@@ -429,6 +429,9 @@
        if (ACPI_FAILURE (status)) {
                return_ACPI_STATUS (status);
        }
+
+
+       acpi_hw_enable_ec_gpes();

        /* Disable BM arbitration */
        status = acpi_set_register (ACPI_BITREG_ARB_DISABLE, 0, ACPI_MTX_LOCK);
diff -Bru linux-2.6.0-test8/include/acpi/achware.h patched/include/acpi/achware.h
--- linux-2.6.0-test8/include/acpi/achware.h    2003-10-18 05:43:18.000000000 +0800
+++ patched/include/acpi/achware.h      2003-10-24 19:01:17.000000000 +0800
@@ -156,6 +156,9 @@
 acpi_hw_enable_non_wakeup_gpes (
        void);

+acpi_status
+acpi_hw_enable_ec_gpes(
+       void);

 /* ACPI Timer prototypes */




-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html

  parent reply	other threads:[~2004-01-13  9:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  8:50 Interrupt routing problem Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720CC3-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13  9:00   ` Karol Kozimor [this message]
     [not found]     ` <20040113090003.GB3599-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-15 10:41       ` Nils Faerber
  -- strict thread matches above, loose matches on Subject: below --
2004-01-18  4:14 Yu, Luming
2004-01-13  9:08 Yu, Luming
2004-01-12  5:28 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720CA9-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-13  8:26   ` Karol Kozimor
2004-01-07  8:50 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C83-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-07  9:05   ` Karol Kozimor
     [not found]     ` <20040107090531.GA32086-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2004-01-07 15:34       ` Karol Kozimor
2004-01-05  2:17 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C75-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-01-06  4:10   ` Len Brown
     [not found]     ` <1073362251.2419.21.camel-D2Zvc0uNKG8@public.gmane.org>
2004-01-06  8:47       ` Karol Kozimor
2004-01-04 16:43 Nils Faerber

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=20040113090003.GB3599@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox