mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Yi Zhang <yizhang@marvell.com>
Cc: qiaozhou@marvell.com, zhangwm@marvell.com,
	yizhang.mrvl@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: irq: clear status when disable irq
Date: Mon, 14 Oct 2013 12:09:08 +0100	[thread overview]
Message-ID: <20131014110908.GP2443@sirena.org.uk> (raw)
In-Reply-To: <1381724633-29586-1-git-send-email-yizhang@marvell.com>

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

On Mon, Oct 14, 2013 at 12:23:53PM +0800, Yi Zhang wrote:

> Change-Id: I371201f365c5a8470073a393068cfeb4e3d14a03

Don't include noise like this in upstream submissions.

> +		/* Ack masked but set interrupts */
> +		reg = d->chip->status_base +
> +			(i * map->reg_stride * d->irq_reg_stride);
> +		ret = regmap_read(d->map, reg, &d->status_buf[i]);
> +		if (ret != 0)
> +			dev_err(d->map->dev, "Failed to read IRQ status: %d\n",
> +				ret);

No, this isn't good - it'll read the hardware interrupt status again.
This will break any devices that are clear on read since enabled
interrupts will also be read.  I'd suggest unconditionally acknowledging
all masked interrupts as the simplest approach, obviously it'd be better
to only acknowledge newly masked interrupts but that is more complex to
implement.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-10-14 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14  4:23 Yi Zhang
2013-10-14 11:09 ` Mark Brown [this message]
2013-10-14 11:55   ` Yi Zhang
2013-10-15  5:03 Yi Zhang
2013-10-15 11:48 ` Mark Brown
2013-10-15 12:03   ` Yi Zhang

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=20131014110908.GP2443@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiaozhou@marvell.com \
    --cc=yizhang.mrvl@gmail.com \
    --cc=yizhang@marvell.com \
    --cc=zhangwm@marvell.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

all inboxes | Powered by JetHome®