On Thu, 15 Jan 2015, Rob Herring wrote:
> On Thu, Jan 15, 2015 at 3:11 AM, Thomas Gleixner wrote:
> > On Wed, 14 Jan 2015, Rob Herring wrote:
>
> > We do not change shared interrupts in any way. We provide an
> > alternative mechanism for braindead hardware. And if the at91 folks
> > are fine
On Thu, 15 Jan 2015, Rob Herring wrote:
On Thu, Jan 15, 2015 at 3:11 AM, Thomas Gleixner t...@linutronix.de wrote:
On Wed, 14 Jan 2015, Rob Herring wrote:
We do not change shared interrupts in any way. We provide an
alternative mechanism for braindead hardware. And if the at91 folks
are
On Thu, Jan 15, 2015 at 3:11 AM, Thomas Gleixner wrote:
> On Wed, 14 Jan 2015, Rob Herring wrote:
>> On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner wrote:
>> > All attempts to work around that have resulted in horrible bandaids so
>> > far. That's why I guided Boris to implement this dummy
Le 14/01/2015 23:55, Boris Brezillon a écrit :
> Hi Rob,
>
> On Wed, 14 Jan 2015 16:24:32 -0600
> Rob Herring wrote:
>
>> On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner wrote:
>>> On Tue, 13 Jan 2015, Rob Herring wrote:
On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
wrote:
Le 15/01/2015 10:11, Thomas Gleixner a écrit :
> On Wed, 14 Jan 2015, Rob Herring wrote:
>> On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner wrote:
>>> All attempts to work around that have resulted in horrible bandaids so
>>> far. That's why I guided Boris to implement this dummy demultiplexing
On Wed, 14 Jan 2015, Rob Herring wrote:
> On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner wrote:
> > All attempts to work around that have resulted in horrible bandaids so
> > far. That's why I guided Boris to implement this dummy demultiplexing
> > mechanism. It solves the problem at hand
On Thu, Jan 15, 2015 at 3:11 AM, Thomas Gleixner t...@linutronix.de wrote:
On Wed, 14 Jan 2015, Rob Herring wrote:
On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner t...@linutronix.de wrote:
All attempts to work around that have resulted in horrible bandaids so
far. That's why I guided Boris
On Wed, 14 Jan 2015, Rob Herring wrote:
On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner t...@linutronix.de wrote:
All attempts to work around that have resulted in horrible bandaids so
far. That's why I guided Boris to implement this dummy demultiplexing
mechanism. It solves the problem at
Le 14/01/2015 23:55, Boris Brezillon a écrit :
Hi Rob,
On Wed, 14 Jan 2015 16:24:32 -0600
Rob Herring robherri...@gmail.com wrote:
On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner t...@linutronix.de wrote:
On Tue, 13 Jan 2015, Rob Herring wrote:
On Tue, Jan 13, 2015 at 12:46 PM, Boris
Le 15/01/2015 10:11, Thomas Gleixner a écrit :
On Wed, 14 Jan 2015, Rob Herring wrote:
On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner t...@linutronix.de wrote:
All attempts to work around that have resulted in horrible bandaids so
far. That's why I guided Boris to implement this dummy
Hi Rob,
On Wed, 14 Jan 2015 16:24:32 -0600
Rob Herring wrote:
> On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner wrote:
> > On Tue, 13 Jan 2015, Rob Herring wrote:
> >> On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
> >> wrote:
> >> > Some interrupt controllers are multiplexing several
On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner wrote:
> On Tue, 13 Jan 2015, Rob Herring wrote:
>> On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
>> wrote:
>> > Some interrupt controllers are multiplexing several peripheral IRQs on
>> > a single interrupt line.
>> > While this is not a
Le 14/01/2015 15:03, Boris Brezillon a écrit :
> On Wed, 14 Jan 2015 14:36:42 +0100
> Nicolas Ferre wrote:
>
>> Le 13/01/2015 19:46, Boris Brezillon a écrit :
>>> Some interrupt controllers are multiplexing several peripheral IRQs on
>>> a single interrupt line.
>>> While this is not a problem
On Wed, 14 Jan 2015 14:36:42 +0100
Nicolas Ferre wrote:
> Le 13/01/2015 19:46, Boris Brezillon a écrit :
> > Some interrupt controllers are multiplexing several peripheral IRQs on
> > a single interrupt line.
> > While this is not a problem for most IRQs (as long as all peripherals
> > request
Le 13/01/2015 19:46, Boris Brezillon a écrit :
> Some interrupt controllers are multiplexing several peripheral IRQs on
> a single interrupt line.
> While this is not a problem for most IRQs (as long as all peripherals
> request the interrupt with IRQF_SHARED flag set), multiplexing timers and
>
On Tue, 13 Jan 2015, Rob Herring wrote:
> On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
> wrote:
> > Some interrupt controllers are multiplexing several peripheral IRQs on
> > a single interrupt line.
> > While this is not a problem for most IRQs (as long as all peripherals
> > request the
Hi Thomas,
On Tue, 13 Jan 2015 22:00:55 +0100 (CET)
Thomas Gleixner wrote:
> On Tue, 13 Jan 2015, Boris Brezillon wrote:
> > + ret = irq_set_handler_data(irq, demux);
> > + if (ret) {
> > + pr_err("Failed to assign handler data\n");
> > + goto err_free_domain;
> > + }
Hi Rob,
On Tue, 13 Jan 2015 21:26:42 -0600
Rob Herring wrote:
> On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
> wrote:
> > Some interrupt controllers are multiplexing several peripheral IRQs on
> > a single interrupt line.
> > While this is not a problem for most IRQs (as long as all
On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner t...@linutronix.de wrote:
On Tue, 13 Jan 2015, Rob Herring wrote:
On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
boris.brezil...@free-electrons.com wrote:
Some interrupt controllers are multiplexing several peripheral IRQs on
a single
Hi Rob,
On Wed, 14 Jan 2015 16:24:32 -0600
Rob Herring robherri...@gmail.com wrote:
On Wed, Jan 14, 2015 at 4:36 AM, Thomas Gleixner t...@linutronix.de wrote:
On Tue, 13 Jan 2015, Rob Herring wrote:
On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
boris.brezil...@free-electrons.com
Le 14/01/2015 15:03, Boris Brezillon a écrit :
On Wed, 14 Jan 2015 14:36:42 +0100
Nicolas Ferre nicolas.fe...@atmel.com wrote:
Le 13/01/2015 19:46, Boris Brezillon a écrit :
Some interrupt controllers are multiplexing several peripheral IRQs on
a single interrupt line.
While this is not a
Hi Rob,
On Tue, 13 Jan 2015 21:26:42 -0600
Rob Herring robherri...@gmail.com wrote:
On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
boris.brezil...@free-electrons.com wrote:
Some interrupt controllers are multiplexing several peripheral IRQs on
a single interrupt line.
While this is
Hi Thomas,
On Tue, 13 Jan 2015 22:00:55 +0100 (CET)
Thomas Gleixner t...@linutronix.de wrote:
On Tue, 13 Jan 2015, Boris Brezillon wrote:
+ ret = irq_set_handler_data(irq, demux);
+ if (ret) {
+ pr_err(Failed to assign handler data\n);
+ goto err_free_domain;
+
On Wed, 14 Jan 2015 14:36:42 +0100
Nicolas Ferre nicolas.fe...@atmel.com wrote:
Le 13/01/2015 19:46, Boris Brezillon a écrit :
Some interrupt controllers are multiplexing several peripheral IRQs on
a single interrupt line.
While this is not a problem for most IRQs (as long as all
Le 13/01/2015 19:46, Boris Brezillon a écrit :
Some interrupt controllers are multiplexing several peripheral IRQs on
a single interrupt line.
While this is not a problem for most IRQs (as long as all peripherals
request the interrupt with IRQF_SHARED flag set), multiplexing timers and
other
On Tue, 13 Jan 2015, Rob Herring wrote:
On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
boris.brezil...@free-electrons.com wrote:
Some interrupt controllers are multiplexing several peripheral IRQs on
a single interrupt line.
While this is not a problem for most IRQs (as long as all
On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
wrote:
> Some interrupt controllers are multiplexing several peripheral IRQs on
> a single interrupt line.
> While this is not a problem for most IRQs (as long as all peripherals
> request the interrupt with IRQF_SHARED flag set), multiplexing
On Tue, 13 Jan 2015, Boris Brezillon wrote:
> + ret = irq_set_handler_data(irq, demux);
> + if (ret) {
> + pr_err("Failed to assign handler data\n");
> + goto err_free_domain;
> + }
> +
> + irq_set_chained_handler(irq, irq_dumb_demux_handler);
> +
> + /*
Some interrupt controllers are multiplexing several peripheral IRQs on
a single interrupt line.
While this is not a problem for most IRQs (as long as all peripherals
request the interrupt with IRQF_SHARED flag set), multiplexing timers and
other type of peripherals will generate a WARNING (mixing
On Tue, Jan 13, 2015 at 12:46 PM, Boris Brezillon
boris.brezil...@free-electrons.com wrote:
Some interrupt controllers are multiplexing several peripheral IRQs on
a single interrupt line.
While this is not a problem for most IRQs (as long as all peripherals
request the interrupt with
Some interrupt controllers are multiplexing several peripheral IRQs on
a single interrupt line.
While this is not a problem for most IRQs (as long as all peripherals
request the interrupt with IRQF_SHARED flag set), multiplexing timers and
other type of peripherals will generate a WARNING (mixing
On Tue, 13 Jan 2015, Boris Brezillon wrote:
+ ret = irq_set_handler_data(irq, demux);
+ if (ret) {
+ pr_err(Failed to assign handler data\n);
+ goto err_free_domain;
+ }
+
+ irq_set_chained_handler(irq, irq_dumb_demux_handler);
+
+ /*
+ *
32 matches
Mail list logo
