From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anthony Olech <anthony.olech.opensource@diasemi.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Anthony Olech <anthony.olech@diasemi.com>,
Dajun Chen <david.chen@diasemi.com>
Subject: Re: [PATCH] regmap-irq: allow auto-allocated IRQs to be mapped
Date: Sat, 4 Aug 2012 11:54:24 +0100 [thread overview]
Message-ID: <20120804105424.GB10523@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201208020805.q72858Yj003147@latitude.olech.com>
On Wed, Aug 01, 2012 at 07:05:15PM +0100, Anthony Olech wrote:
> if the irq_base is set to -1 when calling regmap_add_irq_chip()
> then allow the IRQ to be mapped even if the allocated irq_base
> is actually zero.
> This restores the behaviour seen in v3.4, and I assume that the
> tidy-ups just made in v3.5 INADVERTENTLY introduce this change
> in behaviour.
Please pay MORE attention to the changelog - obviously there's no
problem mapping automatically allocated IRQs, there's only any effect if
they happen to GET allocated at zero.
The only real issue I see with the current code is that if the user
explicitly wants to statically allocate an IRQ range at zero they can't.
The current intended behaviour is that we use a linear domain unless a
positive IRQ base is specified, though we're not quite doing that right
now as a transitional measure until drivers are updated.
The current da9052 driver usage seems to have quite a few problems, I do
recall having to fix some problems that make me doubt if it ever worked
well. Looking at the code now I see it's using hard coded references to
absolute IRQ numbers which is an issue... It should be being converted
to use regmap_irq_get_virq().
next parent reply other threads:[~2012-08-04 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201208020805.q72858Yj003147@latitude.olech.com>
2012-08-04 10:54 ` Mark Brown [this message]
2012-08-05 19:57 ` [PATCH] regmap-irq: allow auto-allocated IRQs to be mapped Opensource [Anthony Olech]
2012-08-06 12:20 ` Mark Brown
2012-08-07 11:18 ` Opensource [Anthony Olech]
2012-08-07 14:03 ` Mark Brown
2012-08-07 14:37 ` Opensource [Anthony Olech]
2012-08-07 17:02 ` Mark Brown
2012-08-08 8:30 ` Opensource [Anthony Olech]
2012-08-01 18:05 Anthony Olech
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=20120804105424.GB10523@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anthony.olech.opensource@diasemi.com \
--cc=anthony.olech@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox