From: Sinan Kaya <okaya@codeaurora.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-acpi@vger.kernel.org, timur@codeaurora.org,
cov@codeaurora.org, jcm@redhat.com,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V7] ACPI, PCI, irq: support IRQ numbers greater than 256
Date: Tue, 1 Dec 2015 11:30:21 -0500 [thread overview]
Message-ID: <565DCB1D.7030308@codeaurora.org> (raw)
In-Reply-To: <20151201153031.GD9306@localhost>
On 12/1/2015 10:30 AM, Bjorn Helgaas wrote:
> Not sure whether you saw my earlier response about this:
>
Sorry, I missed it.
> ACPI_MAX_IRQS is only used to size the acpi_irq_penalty[] table (and
> after your patch, to validate IRQ numbers from ACPI). But I think
> the acpi_irq_penalty[] table is a design we've outgrown. I *think*
> we only care about penalties for IRQs 0-15, so even a 256-entry
> table is more than we need.
>
> If we could make acpi_irq_penalty[] a fixed size of 16 entries or
> replace it with a linked list, I think we could get rid of
> ACPI_MAX_IRQS completely. Then the validation checks you add below
> would be unnecessary and we could handle any interrupt number
> supplied from ACPI.
>
> I think it would be really nice to get rid of the arbitrary maximum
> interrupt ID (1020).
Let me look and do some testing. I'll try to do less damage by using a
link list rather than 16 and try to replicate the existing functionality.
--
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-12-01 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 23:39 [PATCH V7] ACPI, PCI, irq: support IRQ numbers greater than 256 Sinan Kaya
2015-12-01 15:30 ` Bjorn Helgaas
2015-12-01 16:30 ` Sinan Kaya [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=565DCB1D.7030308@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=cov@codeaurora.org \
--cc=helgaas@kernel.org \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=timur@codeaurora.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.