From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: ipu: Make sure the interrupt routine checks all interrupts.
Date: Mon, 2 Jan 2017 10:49:19 +0530 [thread overview]
Message-ID: <20170102051918.GR3573@localhost> (raw)
In-Reply-To: <1482354838-22615-1-git-send-email-lilja.magnus@gmail.com>
On Wed, Dec 21, 2016 at 10:13:58PM +0100, Magnus Lilja wrote:
> Commit 3d8cc00073d6 ("dmaengine: ipu: Consolidate duplicated irq handlers")
> consolidated the two interrupts routines into one, but the remaining
> interrupt routine only checks the status of the error interrupts, not the
> normal interrupts.
>
> This patch fixes that problem (tested on i.MX31 PDK board).
Applied thnx
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Magnus Lilja <lilja.magnus@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
"# 4 . 1 . x" <stable@vger.kernel.org>
Subject: Re: [PATCH] dmaengine: ipu: Make sure the interrupt routine checks all interrupts.
Date: Mon, 2 Jan 2017 10:49:19 +0530 [thread overview]
Message-ID: <20170102051918.GR3573@localhost> (raw)
In-Reply-To: <1482354838-22615-1-git-send-email-lilja.magnus@gmail.com>
On Wed, Dec 21, 2016 at 10:13:58PM +0100, Magnus Lilja wrote:
> Commit 3d8cc00073d6 ("dmaengine: ipu: Consolidate duplicated irq handlers")
> consolidated the two interrupts routines into one, but the remaining
> interrupt routine only checks the status of the error interrupts, not the
> normal interrupts.
>
> This patch fixes that problem (tested on i.MX31 PDK board).
Applied thnx
--
~Vinod
next prev parent reply other threads:[~2017-01-02 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 21:13 [PATCH] dmaengine: ipu: Make sure the interrupt routine checks all interrupts Magnus Lilja
2016-12-21 21:13 ` Magnus Lilja
2017-01-02 5:19 ` Vinod Koul [this message]
2017-01-02 5:19 ` Vinod Koul
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=20170102051918.GR3573@localhost \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.