Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759856Ab0FKJYP (ORCPT ); Fri, 11 Jun 2010 05:24:15 -0400 Received: from mail.karo-electronics.de ([81.173.242.67]:64996 "EHLO mail.karo-electronics.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755121Ab0FKJYO (ORCPT ); Fri, 11 Jun 2010 05:24:14 -0400 Message-ID: <19474.172.742782.972629@ipc1.ka-ro> Date: Fri, 11 Jun 2010 11:23:56 +0200 From: =?iso-8859-15?Q?Lothar_Wa=DFmann?= To: Jeremy Kerr Cc: Ben Dooks , Ben Herrenchmidt , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [RFC,PATCH 1/2] Add a common struct clk In-Reply-To: <201006111718.47426.jeremy.kerr@canonical.com> References: <1275636608.606606.450179637764.0.gpush@pororo> <201006111557.12249.jeremy.kerr@canonical.com> <19473.61547.684572.647641@ipc1.ka-ro> <201006111718.47426.jeremy.kerr@canonical.com> X-Mailer: VM 8.0.9 under Emacs 22.2.1 (i486-pc-linux-gnu) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1152 Lines: 30 Hi, > > Using a mutex in clk_enable()/clk_disable() is a bad idea, since that > > makes it impossible to call those functions in interrupt context. > > Do we do this at the moment? I know at least one implementation of clk_enable > uses a mutex for locking. > You are probably talking about the Freescale i.MX51 kernel, that won't even boot, if you enable CONFIG_DEBUG_KERNEL, CONFIG_DEBUG_SPINLOCK, CONFIG_DEBUG_LOCKDEP and CONFIG_DEBUG_SPINLOCK_SLEEP. The mutex in the clock implementation is one of the reasons. Lothar Wa?mann -- ___________________________________________________________ Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10 Gesch?ftsf?hrer: Matthias Kaussen Handelsregistereintrag: Amtsgericht Aachen, HRB 4996 www.karo-electronics.de | info@karo-electronics.de ___________________________________________________________ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/