Re: [RFC] ACPI IRQ proposal

[Bjorn Helgaas <bjorn.helgaas@hp.com>]

On Friday 26 March 2004 1:56 am, Takayoshi Kochi wrote:
> The polarity and trigger are programmed in iosapic when MADT
> parsing is done, so we don't want to force 'ACPI_ACTIVE_LOW,
> ACPI_LEVEL_SENSITIVE' when SCI is enabled.

Yup, I just completely threw out the MADT parsing, which was
a mistake.  Obviously we have to keep track of what's there.
It's a shame it's currently all in architecture code, even though
it should really be platform-independent.

> So maybe acpi_register_gsi() would take only one argument (u32 gsi)
> and the acpi_register_gsi() by itself will derive polarity and trigger
> from override table or iosapic_intr_info[]?

But it doesn't seem right to me to for the arch code to have to keep
track of the polarity/trigger stuff.  Ideally I think ACPI should extract
that from the PRT (as it does today) and from the static tables (as
the arch code does today), then tell the arch code once via
acpi_register_gsi().

But in the short term, I think I'll just leave the non-PRT stuff pretty
much as it is today, and focus on cleaning up the PRT handling a bit.