From: Samuel Ortiz <sameo@linux.intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
Michel JAOUEN <michel.jaouen@stericsson.com>,
Maxime Coquelin <maxime.coquelin@stericsson.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 5/6] mfd/ab8500: support of hierachical interrupt
Date: Tue, 1 May 2012 13:31:30 +0200 [thread overview]
Message-ID: <20120501113130.GE20224@sortiz-mobl> (raw)
In-Reply-To: <1334647849-1773-1-git-send-email-linus.walleij@stericsson.com>
Hi Linus,
On Tue, Apr 17, 2012 at 09:30:49AM +0200, Linus Walleij wrote:
> +static irqreturn_t ab8500_hierarchical_irq(int irq, void *dev)
> +{
> + struct ab8500 *ab8500 = dev;
> + int i;
> +
> + dev_vdbg(ab8500->dev, "interrupt\n");
> +
> + /* Hierarchical interrupt version */
> + for (i = 0; i < AB8500_IT_LATCHHIER_NUM; i++) {
> + int status;
> + u8 hier_val;
> +
> + status = get_register_interruptible(ab8500, AB8500_INTERRUPT,
> + AB8500_IT_LATCHHIER1_REG + i, &hier_val);
> + if (status < 0 || hier_val == 0)
> + continue;
> +
> + do {
> + int latch_bit = __ffs(hier_val);
> + u8 offset = i * 8 + latch_bit;
> + u8 latch_val;
> +
> + /* Fix inconsistent ITFromLatch25 bit mapping... */
> + if (unlikely(offset == 17))
> + offset = 24;
> +
> + status = get_register_interruptible(ab8500,
> + AB8500_INTERRUPT,
> + AB8500_IT_LATCH1_REG + offset,
> + &latch_val);
> + if (status < 0 || latch_val == 0)
> + goto discard;
> +
> + do {
> + int int_bit = __ffs(latch_val);
> + int line;
> + int j;
> +
> + for (j = 0; j < ab8500->mask_size; j++)
> + if (ab8500->irq_reg_offset[j] == offset)
> + break;
> +
> + if (j >= ab8500->mask_size) {
> + dev_err(ab8500->dev,
> + "Register offset 0x%2x not declared\n",
> + offset);
> + return IRQ_HANDLED;
> + }
> +
> + line = j * 8 + int_bit;
> +
> + handle_nested_irq(ab8500->irq_base + line);
> + latch_val &= ~(1 << int_bit);
> + } while (latch_val);
> +discard:
> + hier_val &= ~(1 << latch_bit);
> + } while (hier_val);
> + }
> + return IRQ_HANDLED;
> +}
With 4 nested loops, this one is getting difficult to read. Have you
considered splitting the loops into separate routines ?
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-05-01 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 7:30 [PATCH 5/6] mfd/ab8500: support of hierachical interrupt Linus Walleij
2012-05-01 11:31 ` Samuel Ortiz [this message]
2012-05-01 22:18 ` Linus Walleij
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=20120501113130.GE20224@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@stericsson.com \
--cc=michel.jaouen@stericsson.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