From: Thomas Gleixner <tglx@linutronix.de>
To: jeffy <jeffy.chen@rock-chips.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
briannorris@chromium.org, dianders@chromium.org,
tfiga@chromium.org, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH] genirq: Check irq disabled & masked states in irq_shutdown
Date: Sat, 27 May 2017 10:16:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1705270950210.2329@nanos> (raw)
In-Reply-To: <592905F7.4010803@rock-chips.com>
On Sat, 27 May 2017, jeffy wrote:
> On 05/26/2017 09:20 PM, Thomas Gleixner wrote:
> > On Fri, 26 May 2017, Jeffy Chen wrote:
> >
> > > If irq is already disabled and masked, we would hit a unbalanced irq
> > > shutdown/disable/mask when freeing it.
> >
> > Errr? What exactly is unbalanced? None of the called functions has any
> > counter or whatever.
> >
> > Can you please explain what you are trying to fix?
>
> sorry, i'll try to rewrite the commit message.
>
> for example when a driver(drivers/net/wireless/marvell/mwifiex/main.c) try to
> do these:
>
> devm_request_irq->irq_startup->irq_enable
> disable_irq <-- disabled and masked
> devm_free_irq->irq_shutdown <-- disable it again
This driver is broken as hell. It requests the interrupt _BEFORE_ the whole
thing is initialized. If there is a pending interrupt on that line, it will
explode nicely before it is able to disable the irq. But that's a different
problem.
Thanks,
tglx
next prev parent reply other threads:[~2017-05-27 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 13:17 Jeffy Chen
2017-05-26 13:20 ` Thomas Gleixner
2017-05-27 4:52 ` jeffy
2017-05-27 8:16 ` Thomas Gleixner [this message]
2017-05-30 23:20 ` Brian Norris
2017-05-30 23:32 ` Brian Norris
2017-05-31 8:38 ` Thomas Gleixner
2017-05-31 9:22 ` Thomas Gleixner
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.20.1705270950210.2329@nanos \
--to=tglx@linutronix.de \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=jeffy.chen@rock-chips.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tfiga@chromium.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
all inboxes | Powered by JetHome®