public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] 2.4.21 Interrupt polarity fix
Date: Tue, 05 Aug 2003 22:16:07 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106012193812192@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105962723421294@msgid-missing>

On Wednesday 30 July 2003 10:53 pm, Takayoshi Kochi wrote:
> It seems that acpi_register_intr (in arch/ia64/kernel/acpi.c)
> takes an interrupt polarity/trigger in opposite way.
> Attached patch fixes this.  Please apply.

Thanks.  This was indeed very confusing.  I applied the
following patch for 2.4.  The corresponding patch you
posted on August 4 for 2.6 appears functionally identical
but reverses the sense of the polarity test for no good
reason.  Can you send David a revised patch that does
it the same was as the one below?

Bjorn

#### AUTHOR kochi@hpc.bs1.fc.nec.co.jp
#### COMMENT START
### Comments for ChangeSet
ia64: Fix ACPI interrupt polarity/trigger interpretation

It seems that acpi_register_intr (in arch/ia64/kernel/acpi.c)
takes an interrupt polarity/trigger in opposite way.
Attached patch fixes this.  Please apply.

drivers/acpi/resource/rsirq.c decodes ACPI extended irq
resource and stores in edge_level and active_high_low members
of a structure (BTW, I think the names of these members
are source of confusion ;).

And this logic in acpi.c inverts both polarity and trigger.

vector = iosapic_register_intr(gsi,
        polarity ? IOSAPIC_POL_HIGH : IOSAPIC_POL_LOW,
        mode ? IOSAPIC_EDGE : IOSAPIC_LEVEL);

       ACPI -> rsirq.c -> serial.c -> acpi.c            -> iosapic.c
High      0         0           0      IOSAPIC_POL_LOW
Low       1         1           1      IOSAPIC_POL_HIGH
Edge      1         0           0      IOSAPIC_LEVEL
Level     0         1           1      IOSAPIC_EDGE

As ACPI_ACTIVE_{HIGH,LOW} and ACPI_{LEVEL,EDGE}_SENSITIVE are
defined in acpi subsystem, it should be safer to use these symbols.
### Comments for arch/ia64/kernel/acpi.c
Fix ACPI interrupt polarity/trigger interpretation
#### COMMENT END

# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
#	           ChangeSet	1.1060  -> 1.1061 
#	arch/ia64/kernel/acpi.c	1.16    -> 1.17   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/08/05	bjorn.helgaas@hp.com	1.1061
# find intrs
# --------------------------------------------
#
diff -Nru a/arch/ia64/kernel/acpi.c b/arch/ia64/kernel/acpi.c
--- a/arch/ia64/kernel/acpi.c	Tue Aug  5 17:00:35 2003
+++ b/arch/ia64/kernel/acpi.c	Tue Aug  5 17:00:35 2003
@@ -643,8 +643,9 @@
 		return 0;
 
 	/* Turn it on */
-	vector = iosapic_register_intr(gsi, polarity ? IOSAPIC_POL_HIGH : IOSAPIC_POL_LOW,
-			mode ? IOSAPIC_EDGE : IOSAPIC_LEVEL);
+	vector = iosapic_register_intr(gsi,
+		       	(polarity = ACPI_ACTIVE_HIGH) ? IOSAPIC_POL_HIGH : IOSAPIC_POL_LOW,
+			(mode = ACPI_EDGE_SENSITIVE) ? IOSAPIC_EDGE : IOSAPIC_LEVEL);
 	return vector;
 }
 


  reply	other threads:[~2003-08-05 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31  4:53 [PATCH] 2.4.21 Interrupt polarity fix Takayoshi Kochi
2003-08-05 22:16 ` Bjorn Helgaas [this message]
2003-08-06  1:22 ` Takayoshi Kochi

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=marc-linux-ia64-106012193812192@msgid-missing \
    --to=bjorn.helgaas@hp.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox