Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758282Ab3DYL5y (ORCPT ); Thu, 25 Apr 2013 07:57:54 -0400 Received: from mail-ia0-f174.google.com ([209.85.210.174]:58224 "EHLO mail-ia0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757389Ab3DYL5v (ORCPT ); Thu, 25 Apr 2013 07:57:51 -0400 MIME-Version: 1.0 In-Reply-To: <20130419122226.GB3432@gmail.com> References: <1366280825-31136-1-git-send-email-lee.jones@linaro.org> <1366280825-31136-5-git-send-email-lee.jones@linaro.org> <20130419122226.GB3432@gmail.com> Date: Thu, 25 Apr 2013 13:57:50 +0200 Message-ID: Subject: Re: [PATCH 4/9 v2] crypto: ux500/cryp - Prepare clock before enabling it From: Linus Walleij To: Lee Jones Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Linus WALLEIJ , Herbert Xu , "David S. Miller" , Andreas Westin , "linux-crypto@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1135 Lines: 35 On Fri, Apr 19, 2013 at 2:22 PM, Lee Jones wrote: > Slight change of plan for v2. > > Now we're doing a seperate clk_prepare(), as the clk_enable() in the > previous patch turned out to be called inside a spin_lock(). > > Arnd, can you confirm your Ack please? > > ---- > > crypto: ux500/cryp - Prepare clock before enabling it > > If we fail to prepare the ux500-cryp clock before enabling it the > platform will fail to boot. Here we insure this happens. > > Cc: Herbert Xu > Cc: David S. Miller > Cc: Andreas Westin > Cc: linux-crypto@vger.kernel.org > Acked-by: Arnd Bergmann > Signed-off-by: Lee Jones Same formatting problems as the other prepare/enable patch. Include Ulf Hansson. (Apart from this it looks OK.) Yours, Linus Walleij -- 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/