From: Tony Lindgren <tony@atomide.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: Oleg Matcovschi <oleg.matcovschi@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux@arm.linux.org.uk, jarkko.nikula@bitmer.com
Subject: Re: [PATCH v2] omap: dma: Clear status registers on enable/disable irq.
Date: Mon, 4 Jun 2012 23:39:13 -0700 [thread overview]
Message-ID: <20120605063912.GB12766@atomide.com> (raw)
In-Reply-To: <2491206.Xgf8oVG38F@acer>
* Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [120604 15:01]:
> On Tue, 15 May 2012 14:35:08 Oleg Matcovschi wrote:
> > Use omap_disable_channel_irq() function instead of directly accessing CICR.
> > The omap_disable_chanel_irq() function clears pending interrupts
> > and disables interrupt on channel.
> > Functions omap2_enable_irq_lch()/omap2_disable_irq_lch() clear interrupt
> > status register.
> >
> >
> > Signed-off-by: Oleg Matcovschi <oleg.matcovschi@ti.com>
> > ---
> > v1 initial revision
> > v2 Review by Tony Lindgren
>
> My Tested-by: on OMAP1 still valid for v2 if you care.
OK good to hear, will add that.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] omap: dma: Clear status registers on enable/disable irq.
Date: Mon, 4 Jun 2012 23:39:13 -0700 [thread overview]
Message-ID: <20120605063912.GB12766@atomide.com> (raw)
In-Reply-To: <2491206.Xgf8oVG38F@acer>
* Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [120604 15:01]:
> On Tue, 15 May 2012 14:35:08 Oleg Matcovschi wrote:
> > Use omap_disable_channel_irq() function instead of directly accessing CICR.
> > The omap_disable_chanel_irq() function clears pending interrupts
> > and disables interrupt on channel.
> > Functions omap2_enable_irq_lch()/omap2_disable_irq_lch() clear interrupt
> > status register.
> >
> >
> > Signed-off-by: Oleg Matcovschi <oleg.matcovschi@ti.com>
> > ---
> > v1 initial revision
> > v2 Review by Tony Lindgren
>
> My Tested-by: on OMAP1 still valid for v2 if you care.
OK good to hear, will add that.
Regards,
Tony
next prev parent reply other threads:[~2012-06-05 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 21:35 [PATCH v2] omap: dma: Clear status registers on enable/disable irq Oleg Matcovschi
2012-05-15 21:35 ` Oleg Matcovschi
2012-06-01 7:36 ` Jarkko Nikula
2012-06-01 7:36 ` Jarkko Nikula
2012-06-04 6:13 ` Tony Lindgren
2012-06-04 6:13 ` Tony Lindgren
2012-06-05 18:28 ` Matcovschi, Oleg
2012-06-05 18:28 ` Matcovschi, Oleg
2012-06-04 21:53 ` Janusz Krzysztofik
2012-06-04 21:53 ` Janusz Krzysztofik
2012-06-05 6:39 ` Tony Lindgren [this message]
2012-06-05 6:39 ` Tony Lindgren
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=20120605063912.GB12766@atomide.com \
--to=tony@atomide.com \
--cc=jarkko.nikula@bitmer.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=oleg.matcovschi@ti.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 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.