Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1601212 > unrolled thread

Re: [PATCH 10/19] gpio: ws16c48: make use of raw_spinlock variants

Started byLinus Walleij <linus.walleij@linaro.org>
First post2017-03-15 11:10 +0100
Last post2017-03-15 11:10 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 10/19] gpio: ws16c48: make use of raw_spinlock variants Linus Walleij <linus.walleij@linaro.org> - 2017-03-15 11:10 +0100

#1601212 — Re: [PATCH 10/19] gpio: ws16c48: make use of raw_spinlock variants

FromLinus Walleij <linus.walleij@linaro.org>
Date2017-03-15 11:10 +0100
SubjectRe: [PATCH 10/19] gpio: ws16c48: make use of raw_spinlock variants
Message-ID<tle2t-689-5@gated-at.bofh.it>
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright <julia@ni.com> wrote:

> The ws16c48 gpio driver currently implements 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, it is not suitable to be used with irq_chips.
>
> A quick audit of the operations under the lock reveal that they do only
> minimal, bounded work, and are therefore safe to do under a raw spinlock.
>
> Signed-off-by: Julia Cartwright <julia@ni.com>

Patch applied with William's ACK.

Yours,
Linus Walleij

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web