public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: Disabling an interrupt in the handler locks the system up
Date: Fri, 21 Oct 2016 21:49:35 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1610212147420.4855@nanos> (raw)
In-Reply-To: <580A70B9.8060507@free.fr>

On Fri, 21 Oct 2016, Mason wrote:
> On 21/10/2016 21:14, Marc Zyngier wrote:
> > If connecting a device that signals its interrupt as level low to an
> > input line configured as level high doesn't strike you as a major
> > issue, nothing will. At that point, you can put anything you want in
> > your DT.
> 
> If I understand correctly, you are saying that I should have
> specified IRQ_TYPE_LEVEL_LOW, instead of IRQ_TYPE_LEVEL_HIGH?
> 
> If the HW outputs 1 when idle, and 0 when busy, that
> is level low? (Sorry if this is obvious, I'm absolutely
> clueless in this subject matter.)

We describe the level which is raising the interrupt. So in your case the
line goes to 0 when the interrupt is active, so the level is LOW.

Thanks,

	tglx

  reply	other threads:[~2016-10-21 19:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 16:37 Disabling an interrupt in the handler locks the system up Mason
2016-10-21 17:46 ` Marc Zyngier
2016-10-21 18:39   ` Mason
2016-10-21 19:14     ` Marc Zyngier
2016-10-21 19:47       ` Mason
2016-10-21 19:49         ` Thomas Gleixner [this message]
2016-10-21 20:27           ` Mason
2016-10-22 11:37             ` Marc Zyngier
2016-10-22 23:10               ` Mason
2016-10-24  8:17                 ` Marc Zyngier
2016-10-24 16:12                 ` Mason
2016-10-24 16:55                   ` Thomas Gleixner
2016-10-25  8:29                     ` Sebastian Frias
2016-10-25  8:36                       ` Mason
2016-10-25 10:45                         ` Marc Zyngier
2016-10-25 13:56                           ` Mason
2016-10-25 13:56                             ` Thomas Gleixner
2016-10-25  9:20                       ` 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.1610212147420.4855@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