From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Grant Likely <grant.likely@secretlab.ca>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, mathias.nyman@linux.intel.com,
mika.westerberg@linux.intel.com
Subject: Re: [PATCH] irq_domain: Standardise legacy/linear domain selection
Date: Thu, 5 Jul 2012 13:02:15 +0100 [thread overview]
Message-ID: <20120705120215.GS4111@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAHp75Vesp7KrYvQrNXK=fGOH5y+jk9AMHVJkGyu8o+72F9LSrg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
On Thu, Jul 05, 2012 at 02:43:42PM +0300, Andy Shevchenko wrote:
> The issue is in plain array of the numbers that are assigned to the devices.
> Somehow looks better to have real namespaces, or even hide irq number in the API
> struct device, request_irq(), but keep reference between driver and PIC via some
> object.
> So, given solution just hides an issue, but doesn't resolve it fully
> from my p.o.v.
This is unrelated to what you're talking about. The devices concerned
are mostly MFDs which use their own interrupts. Where other things need
to use the interrupt numbers then legacy mappings should still be used
and IRQ domains have no effect at all on the situation.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-05 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 11:19 [PATCH] irq_domain: Standardise legacy/linear domain selection Mark Brown
2012-07-05 11:43 ` Andy Shevchenko
2012-07-05 12:02 ` Mark Brown [this message]
2012-07-11 14:06 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2012-05-19 12:02 Mark Brown
2012-05-19 20:22 ` Grant Likely
2012-05-19 20:54 ` Mark Brown
2012-05-19 20:59 ` Grant Likely
2012-05-19 22:39 ` Mark Brown
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=20120705120215.GS4111@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=andy.shevchenko@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=tglx@linutronix.de \
/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