[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1601270933560.3886@nanos>
Date: Wed, 27 Jan 2016 09:35:22 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Cao jin <caoj.fnst@...fujitsu.com>
cc: Bjorn Helgaas <helgaas@...nel.org>,
Chen Fan <chen.fan.fnst@...fujitsu.com>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
rjw@...ysocki.net, lenb@...nel.org, izumi.taku@...fujitsu.com,
wency@...fujitsu.com, ddaney.cavm@...il.com, okaya@...eaurora.org,
bhelgaas@...gle.com, jiang.liu@...ux.intel.com,
linux-pci@...r.kernel.org
Subject: Re: [PATCH v2] pci: fix unavailable irq number 255 reported by
BIOS
On Wed, 27 Jan 2016, Cao jin wrote:
> How about using IRQ_BITMAP_BITS as that "irq_valid" flag? because it is the
> ceiling of struct irq_desc irq_desc[], and request_irq() will return -EINVAL
> in case of the ceiling.
>
> #ifdef CONFIG_SPARSE_IRQ
> # define IRQ_BITMAP_BITS (NR_IRQS + 8196)
> #else
> # define IRQ_BITMAP_BITS NR_IRQS
> #endif
No. This is a core internal implementation detail.
Thanks,
tglx
Powered by blists - more mailing lists