Re: [PATCH 17/19] pinctrl: amd: make use of raw_spinlock variants

2017-03-15 Thread Linus Walleij
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote: > The amd pinctrl drivers currently implement an irq_chip for handling > interrupts; due to how irq_chip handling is done, it's necessary for the > irq_chip methods to be invoked from hardirq context, even on a a > real-time

Re: [PATCH 17/19] pinctrl: amd: make use of raw_spinlock variants

2017-03-15 Thread Linus Walleij
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote: > The amd pinctrl drivers currently implement an irq_chip for handling > interrupts; due to how irq_chip handling is done, it's necessary for the > irq_chip methods to be invoked from hardirq context, even on a a > real-time kernel.

[PATCH 17/19] pinctrl: amd: make use of raw_spinlock variants

2017-03-09 Thread Julia Cartwright
The amd pinctrl drivers currently implement an irq_chip for handling interrupts; due to how irq_chip handling is done, it's necessary for the irq_chip methods to be invoked from hardirq context, even on a a real-time kernel. Because the spinlock_t type becomes a "sleeping" spinlock w/ RT kernels,

[PATCH 17/19] pinctrl: amd: make use of raw_spinlock variants

2017-03-09 Thread Julia Cartwright
The amd pinctrl drivers currently implement an irq_chip for handling interrupts; due to how irq_chip handling is done, it's necessary for the irq_chip methods to be invoked from hardirq context, even on a a real-time kernel. Because the spinlock_t type becomes a "sleeping" spinlock w/ RT kernels,