From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: xgene-dma: Fix double IRQ issue by setting IRQ_DISABLE_UNLAZY flag
Date: Wed, 6 Jan 2016 11:05:02 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1601061103000.3689@nanos> (raw)
In-Reply-To: <20160106093121.GB11778@localhost>
On Wed, 6 Jan 2016, Vinod Koul wrote:
> On Wed, Jan 06, 2016 at 02:51:07PM +0530, Rameshwar Sahu wrote:
> > >> @@ -1610,6 +1611,7 @@ static int xgene_dma_request_irqs(struct xgene_dma *pdma)
> > >> /* Register DMA channel rx irq */
> > >> for (i = 0; i < XGENE_DMA_MAX_CHANNEL; i++) {
> > >> chan = &pdma->chan[i];
> > >> + irq_set_status_flags(chan->rx_irq, IRQ_DISABLE_UNLAZY);
> > >
> > > Why not use irq_settings_disable_unlazy(), at least read the reference you
> > > pointed out!
> >
> > irq_settings_disable_unlazy() is helper function to test
> > IRQ_DISABLE_UNLAZY flag is set or not, it's not for setting this flag.
> > FYI...
> > +static inline bool irq_settings_disable_unlazy(struct irq_desc *desc)
> > +{
> > + return desc->status_use_accessors & _IRQ_DISABLE_UNLAZY;
> > +}
>
> Ah yes, I saw clear API and assumed there would be set. Then I think we
> should add a set helper as well as the usage is intended for drivers to
> set this flag
>
> Thomas,
>
> Any reason why you didn't add a set helper, only test and clear?
Why would I? Those helpers are core internal and not usable in random drivers.
Drivers have irq_set_status_flags()/irq_clear_status_flags() ...
Thanks,
tglx
next prev parent reply other threads:[~2016-01-06 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1450875495-2229-1-git-send-email-rsahu@apm.com>
2016-01-06 9:13 ` [PATCH] dmaengine: xgene-dma: Fix double IRQ issue by setting IRQ_DISABLE_UNLAZY flag Vinod Koul
2016-01-06 9:21 ` Rameshwar Sahu
2016-01-06 9:31 ` Vinod Koul
2016-01-06 9:32 ` Rameshwar Sahu
2016-01-06 10:05 ` Thomas Gleixner [this message]
[not found] ` <CAOHikRALt92uf598bH2hWq-QKOVRxd+OEjZ2pRkRj5-F8ApD5w@mail.gmail.com>
2016-01-06 10:12 ` Suman Tripathi
2016-01-06 10:12 ` Thomas Gleixner
2016-01-07 4:49 ` Vinod Koul
2016-01-07 5:40 ` Vinod Koul
2015-12-23 12:39 Rameshwar Prasad Sahu
-- strict thread matches above, loose matches on Subject: below --
2015-12-22 12:52 Rameshwar Prasad Sahu
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=alpine.DEB.2.11.1601061103000.3689@nanos \
--to=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox