Re: [PATCH 0/3] simulated interrupts

On Wed, Jul 19, 2017 at 4:19 PM, Marc Zyngier 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 >

Re: [PATCH 0/3] simulated interrupts

On Wed, Jul 19, 2017 at 4:19 PM, Marc Zyngier 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

Re: [PATCH 0/3] simulated interrupts

On Wed, Jul 19, 2017 at 5:53 PM, Thomas Gleixner wrote: > On Wed, 19 Jul 2017, Andy Shevchenko wrote: >> On Wed, Jul 19, 2017 at 5:19 PM, Marc Zyngier wrote: >> > echo 1 >/proc/irq/9/trigger >> > (or the corresponding /sys/kernel/debug/irq/irqs/

Re: [PATCH 0/3] simulated interrupts

On Wed, Jul 19, 2017 at 5:53 PM, Thomas Gleixner wrote: > On Wed, 19 Jul 2017, Andy Shevchenko wrote: >> On Wed, Jul 19, 2017 at 5:19 PM, Marc Zyngier wrote: >> > echo 1 >/proc/irq/9/trigger >> > (or the corresponding /sys/kernel/debug/irq/irqs/ interface if we want to >> > make sure that this

Re: [PATCH 0/3] simulated interrupts

On Wed, 19 Jul 2017, Andy Shevchenko wrote: > On Wed, Jul 19, 2017 at 5:19 PM, Marc Zyngier wrote: > > On 19/07/17 14:58, Thomas Gleixner wrote: > >> On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > > > echo 1 >/proc/irq/9/trigger > > (or the corresponding

Re: [PATCH 0/3] simulated interrupts

On Wed, 19 Jul 2017, Andy Shevchenko wrote: > On Wed, Jul 19, 2017 at 5:19 PM, Marc Zyngier wrote: > > On 19/07/17 14:58, Thomas Gleixner wrote: > >> On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > > > echo 1 >/proc/irq/9/trigger > > (or the corresponding /sys/kernel/debug/irq/irqs/ interface

Re: [PATCH 0/3] simulated interrupts

On Wed, Jul 19, 2017 at 5:19 PM, Marc Zyngier wrote: > On 19/07/17 14:58, Thomas Gleixner wrote: >> On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > echo 1 >/proc/irq/9/trigger > (or the corresponding /sys/kernel/debug/irq/irqs/ interface if we want to > make sure that

Re: [PATCH 0/3] simulated interrupts

On Wed, Jul 19, 2017 at 5:19 PM, Marc Zyngier wrote: > On 19/07/17 14:58, Thomas Gleixner wrote: >> On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > echo 1 >/proc/irq/9/trigger > (or the corresponding /sys/kernel/debug/irq/irqs/ interface if we want to > make sure that this > is really not for

Re: [PATCH 0/3] simulated interrupts

On 19/07/17 14:58, Thomas Gleixner wrote: > On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > >> 2017-07-19 14:25 GMT+02:00 Thomas Gleixner : >>> On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: >>> Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated

Re: [PATCH 0/3] simulated interrupts

On 19/07/17 14:58, Thomas Gleixner wrote: > On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > >> 2017-07-19 14:25 GMT+02:00 Thomas Gleixner : >>> On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: >>> Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated interrupts that

Re: [PATCH 0/3] simulated interrupts

On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > 2017-07-19 14:25 GMT+02:00 Thomas Gleixner : > > On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > > > >> Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated > >> interrupts that can be 'fired' from process

Re: [PATCH 0/3] simulated interrupts

On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > 2017-07-19 14:25 GMT+02:00 Thomas Gleixner : > > On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > > > >> Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated > >> interrupts that can be 'fired' from process context when needed

Re: [PATCH 0/3] simulated interrupts

2017-07-19 14:25 GMT+02:00 Thomas Gleixner : > On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > >> Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated >> interrupts that can be 'fired' from process context when needed and >> requested just like normal

Re: [PATCH 0/3] simulated interrupts

2017-07-19 14:25 GMT+02:00 Thomas Gleixner : > On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > >> Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated >> interrupts that can be 'fired' from process context when needed and >> requested just like normal interrupts. This is

Re: [PATCH 0/3] simulated interrupts

On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated > interrupts that can be 'fired' from process context when needed and > requested just like normal interrupts. This is useful for testing and > development purposes. > >

Re: [PATCH 0/3] simulated interrupts

On Wed, 19 Jul 2017, Bartosz Golaszewski wrote: > Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated > interrupts that can be 'fired' from process context when needed and > requested just like normal interrupts. This is useful for testing and > development purposes. > >

[PATCH 0/3] simulated interrupts

Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated interrupts that can be 'fired' from process context when needed and requested just like normal interrupts. This is useful for testing and development purposes. Currently this code is reimplemented by every user. This series

[PATCH 0/3] simulated interrupts

Some frameworks (e.g. iio, gpiolib) use irq_work to implement simulated interrupts that can be 'fired' from process context when needed and requested just like normal interrupts. This is useful for testing and development purposes. Currently this code is reimplemented by every user. This series