On 11/12/2015 11:19 AM, Sebastian Andrzej Siewior wrote:
> On 11/06/2015 08:59 PM, Grygorii Strashko wrote:
>> Hi Sebastian,
>
> Hi Grygorii,
>
>> - IRQF_NO_THREAD is the first considered option for such kind of issues.
>>But: Now in LKML there are ~60 occurrences of IRQF_NO_THREAD - most of
On 11/06/2015 08:59 PM, Grygorii Strashko wrote:
> Hi Sebastian,
Hi Grygorii,
> - IRQF_NO_THREAD is the first considered option for such kind of issues.
> But: Now in LKML there are ~60 occurrences of IRQF_NO_THREAD - most of
> them are used by Arch code. And It's only used by 6 drivers
On 11/05/2015 07:43 PM, Grygorii Strashko wrote:
> diff --git a/drivers/pci/host/pci-dra7xx.c b/drivers/pci/host/pci-dra7xx.c
> index 6589e7e..31460f4 100644
> --- a/drivers/pci/host/pci-dra7xx.c
> +++ b/drivers/pci/host/pci-dra7xx.c
> @@ -302,8 +302,30 @@ static int __init
Hi Sebastian,
On 11/06/2015 10:53 AM, Sebastian Andrzej Siewior wrote:
> On 11/05/2015 07:43 PM, Grygorii Strashko wrote:
>> diff --git a/drivers/pci/host/pci-dra7xx.c b/drivers/pci/host/pci-dra7xx.c
>> index 6589e7e..31460f4 100644
>> --- a/drivers/pci/host/pci-dra7xx.c
>> +++
On -RT, TI DRA7 PCIe driver always produces below backtrace when the
first PCI interrupt is triggered:
[ cut here ]
WARNING: CPU: 1 PID: 82 at kernel/irq/handle.c:150
handle_irq_event_percpu+0x14c/0x174()
irq 460 handler irq_default_primary_handler+0x0/0x14 enabled
