> On Wed, 30 Oct 2013, "陈华才" wrote:
>
>> I use a Loongson-3(MIPS-series CPU) machine, there is a serial port
>> integrated in the CPU (but it iss buggy), and it use handle_percpu_irq()
>> as the irq handler. Maybe I should move the checking into
>> handle_percpu_irq()?
>
> Why is a device
On Wed, 30 Oct 2013, "陈华才" wrote:
> I use a Loongson-3(MIPS-series CPU) machine, there is a serial port
> integrated in the CPU (but it iss buggy), and it use handle_percpu_irq()
> as the irq handler. Maybe I should move the checking into
> handle_percpu_irq()?
Why is a device interrupt using
I use a Loongson-3(MIPS-series CPU) machine, there is a serial port
integrated in the CPU (but it iss buggy), and it use handle_percpu_irq()
as the irq handler. Maybe I should move the checking into
handle_percpu_irq()?
Huacai
> On Sat, 28 Sep 2013, Huacai Chen wrote:
>
>> Some devices (e.g.
I use a Loongson-3(MIPS-series CPU) machine, there is a serial port
integrated in the CPU (but it iss buggy), and it use handle_percpu_irq()
as the irq handler. Maybe I should move the checking into
handle_percpu_irq()?
Huacai
On Sat, 28 Sep 2013, Huacai Chen wrote:
Some devices (e.g. serial
On Wed, 30 Oct 2013, 陈华才 wrote:
I use a Loongson-3(MIPS-series CPU) machine, there is a serial port
integrated in the CPU (but it iss buggy), and it use handle_percpu_irq()
as the irq handler. Maybe I should move the checking into
handle_percpu_irq()?
Why is a device interrupt using
On Wed, 30 Oct 2013, 陈华才 wrote:
I use a Loongson-3(MIPS-series CPU) machine, there is a serial port
integrated in the CPU (but it iss buggy), and it use handle_percpu_irq()
as the irq handler. Maybe I should move the checking into
handle_percpu_irq()?
Why is a device interrupt using
On Sat, 28 Sep 2013, Huacai Chen wrote:
> Some devices (e.g. serial port) setup irq handler at dev open and free
> it at dev close. So, sometimes there is no irqaction for a specific
> irq. But some buggy devices may send irqs at any time. This patch avoid
> the NULL OOPS when irqaction isn't
On Sat, 28 Sep 2013, Huacai Chen wrote:
Some devices (e.g. serial port) setup irq handler at dev open and free
it at dev close. So, sometimes there is no irqaction for a specific
irq. But some buggy devices may send irqs at any time. This patch avoid
the NULL OOPS when irqaction isn't
Some devices (e.g. serial port) setup irq handler at dev open and free
it at dev close. So, sometimes there is no irqaction for a specific
irq. But some buggy devices may send irqs at any time. This patch avoid
the NULL OOPS when irqaction isn't registered.
Signed-off-by: Huacai Chen
---
Some devices (e.g. serial port) setup irq handler at dev open and free
it at dev close. So, sometimes there is no irqaction for a specific
irq. But some buggy devices may send irqs at any time. This patch avoid
the NULL OOPS when irqaction isn't registered.
Signed-off-by: Huacai Chen
10 matches
Mail list logo