Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753221AbdCOKMm (ORCPT ); Wed, 15 Mar 2017 06:12:42 -0400 Received: from mail-io0-f177.google.com ([209.85.223.177]:34903 "EHLO mail-io0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752358AbdCOKMk (ORCPT ); Wed, 15 Mar 2017 06:12:40 -0400 MIME-Version: 1.0 In-Reply-To: <1078eff36a2507d1aa5130cc0a9b28d520aabf31.1489015238.git.julia@ni.com> References: <1078eff36a2507d1aa5130cc0a9b28d520aabf31.1489015238.git.julia@ni.com> From: Linus Walleij Date: Wed, 15 Mar 2017 11:12:37 +0100 Message-ID: Subject: Re: [PATCH 17/19] pinctrl: amd: make use of raw_spinlock variants To: Julia Cartwright Cc: "linux-kernel@vger.kernel.org" , Thomas Gleixner , "linux-gpio@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 668 Lines: 17 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. 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 Patch applied. Yours, Linus Walleij