From: Sinan Kaya <okaya@codeaurora.org>
To: Timur Tabi <timur@codeaurora.org>,
linux-acpi@vger.kernel.org, cov@codeaurora.org, jcm@redhat.com
Cc: agross@codeaurora.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi: add support for extended IRQ to PCI link
Date: Sun, 8 Nov 2015 19:04:05 -0500 [thread overview]
Message-ID: <563FE2F5.3050802@codeaurora.org> (raw)
In-Reply-To: <563F7418.4050203@codeaurora.org>
On 11/8/2015 11:11 AM, Timur Tabi wrote:
> Sinan Kaya wrote:
>> -#define ACPI_MAX_IRQS 256
>> +#define ACPI_MAX_IRQS 1020
>
> Why 1020? Why not 1024?
>
1020 is the maximum interrupt ID that can be directed to an ARM SPI
interrupt according to ARM architecture.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] acpi: add support for extended IRQ to PCI link
Date: Sun, 8 Nov 2015 19:04:05 -0500 [thread overview]
Message-ID: <563FE2F5.3050802@codeaurora.org> (raw)
In-Reply-To: <563F7418.4050203@codeaurora.org>
On 11/8/2015 11:11 AM, Timur Tabi wrote:
> Sinan Kaya wrote:
>> -#define ACPI_MAX_IRQS 256
>> +#define ACPI_MAX_IRQS 1020
>
> Why 1020? Why not 1024?
>
1020 is the maximum interrupt ID that can be directed to an ARM SPI
interrupt according to ARM architecture.
--
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
next prev parent reply other threads:[~2015-11-09 0:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 16:07 [PATCH] acpi: add support for extended IRQ to PCI link Sinan Kaya
2015-11-08 16:07 ` Sinan Kaya
2015-11-08 16:11 ` Timur Tabi
2015-11-08 16:11 ` Timur Tabi
2015-11-09 0:04 ` Sinan Kaya [this message]
2015-11-09 0:04 ` Sinan Kaya
2015-11-09 0:05 ` Timur Tabi
2015-11-09 0:05 ` Timur Tabi
2015-11-09 21:49 ` Rafael J. Wysocki
2015-11-09 21:49 ` Rafael J. Wysocki
2015-11-08 20:35 ` Andy Shevchenko
2015-11-08 20:35 ` Andy Shevchenko
2015-11-09 22:29 ` Sinan Kaya
2015-11-09 22:29 ` Sinan Kaya
2015-11-09 22:29 ` Sinan Kaya
2015-11-09 5:24 ` Jiang Liu
2015-11-09 5:24 ` Jiang Liu
2015-11-09 5:45 ` Sinan Kaya
2015-11-09 5:45 ` Sinan Kaya
2015-11-09 8:45 ` Jiang Liu
2015-11-09 8:45 ` Jiang Liu
2015-11-09 13:50 ` Timur Tabi
2015-11-09 13:50 ` Timur Tabi
2015-11-09 16:28 ` Sinan Kaya
2015-11-09 16:28 ` Sinan Kaya
2015-11-12 6:14 [PATCH V2] " Sinan Kaya
2015-11-12 6:14 ` [PATCH] " Sinan Kaya
2015-11-12 9:56 ` Andy Shevchenko
2015-11-12 15:04 ` Sinan Kaya
2015-11-12 15:17 ` Andy Shevchenko
2015-11-12 15:54 ` okaya
2015-11-12 15:58 ` Timur Tabi
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=563FE2F5.3050802@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=agross@codeaurora.org \
--cc=cov@codeaurora.org \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@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.