[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYRcsr16YBiooDn5D4p+4qB3yhAdE-+VgBBSD4kCCO-Hw@mail.gmail.com>
Date: Wed, 2 Aug 2017 13:32:48 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Marc Zyngier <marc.zyngier@....com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Bartosz Golaszewski <brgl@...ev.pl>,
Jonathan Corbet <corbet@....net>,
Bamvor Jian Zhang <bamvor.zhangjian@...aro.org>,
Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH 0/3] simulated interrupts
On Wed, Jul 19, 2017 at 4:19 PM, Marc Zyngier <marc.zyngier@....com> wrote:
> On a slightly tangential subject, there is another aspect that I thought
> of implementing for a while, but always ended up just relying on a quick
> hack: forcing the injection of an actual interrupt. A number of
> interrupt controllers have the ability to make an interrupt pending, for
> it to be handled as if a device had actually triggered it.
This would be especially useful for a class of embedded systems that
are woken up from deep sleep by an asynchronous interrupt controller.
Usually GPIO(-ish) lines are armed and the system put to sleep, and
when it comes up, the information of what line woke it up is there in a
special register, but the actual (synchronous) interrupt line is no longer
asserted or edge triggered, so an interrupt need to be inserted.
Yours,
Linus Walleij
Powered by blists - more mailing lists