From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Grant Likely <grant.likely@linaro.org>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>, "Jin, Yao" <yao.jin@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Krogerus, Heikki" <heikki.krogerus@intel.com>
Subject: Re: [PATCH] pinctrl-baytrail: workaround for irq descriptor conflict on ASUS T100TA
Date: Thu, 24 Apr 2014 09:25:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1404240918110.4704@ionos.tec.linutronix.de> (raw)
In-Reply-To: <CACRpkdYztACye5Xht3f4UuaWDA0gB7t2rgRmpTaL330YcxYhfQ@mail.gmail.com>
On Wed, 23 Apr 2014, Linus Walleij wrote:
> However this is a first time for an embedded irqchip (coupled
> with GPIO ACPI) creeping into the x86 world, so it needs some
> attention I think, do we have a direction forward for peaceful
> coexistence of several irq controllers picking some IRQ
> numbers/descriptors dynamically as they probe, also on
> x86 systems?
The issue on x86 is, that we have basically two classes of interrupts.
- The hardwired ones (in the chipset and we have no way to
change that except with MSI)
- The dynamic ones, i.e. MSI[X]
So for allocating the MSI interrupts we use the range above the
possible hardwired interrupts.
Unfortunaly the information where the reserved/hardwired range ends is
not available to drivers, but it should be simple to do so.
I'm traveling until friday, so please wait before you commit that
fugly hack. I'll have a closer look how we can handle that at the core
level.
Thanks,
tglx
next prev parent reply other threads:[~2014-04-24 7:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1397443272-31467-1-git-send-email-yao.jin@linux.intel.com>
2014-04-14 2:48 ` [PATCH] pinctrl-baytrail: workaround for irq descriptor conflict on ASUS T100TA Jin, Yao
2014-04-22 13:18 ` Linus Walleij
2014-04-23 2:04 ` Jin, Yao
2014-04-23 11:35 ` Mathias Nyman
2014-04-23 14:28 ` Linus Walleij
2014-04-24 7:25 ` Thomas Gleixner [this message]
2014-04-24 13:19 ` Linus Walleij
2014-04-24 14:40 ` Thomas Gleixner
2014-04-25 9:45 ` Mika Westerberg
2014-04-28 10:25 ` [tip:irq/urgent] genirq: x86: Ensure that dynamic irq allocation does not conflict tip-bot for Thomas Gleixner
2014-04-23 15:33 ` [PATCH] pinctrl-baytrail: workaround for irq descriptor conflict on ASUS T100TA Andy Shevchenko
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=alpine.DEB.2.02.1404240918110.4704@ionos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=grant.likely@linaro.org \
--cc=heikki.krogerus@intel.com \
--cc=hpa@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=mingo@elte.hu \
--cc=rafael.j.wysocki@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=yao.jin@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).