From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 580CAC433E3 for ; Mon, 24 Aug 2020 10:29:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1207C2074D for ; Mon, 24 Aug 2020 10:29:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1598264940; bh=NDhUf/nP2mxoHfjf7T44MWooQOLOp+W6Th3UihAUPk4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:List-ID:From; b=UmSjVL/SGQufJvVb74JfBJewfUFDiGzepuvIm3KfAZ0cKz8eaZzklTfqVRx4zGDC8 9lGw/0mctmYI5A2wIC09AH5h2JkMumG4YVNsZUL4aCxUHkYgVyEIoqqJTJ+7iVrWj8 OmGBJNtM9hOMceyyfwWM0eZQcB5kOW2I6jwwG78I= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725968AbgHXK27 (ORCPT ); Mon, 24 Aug 2020 06:28:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:53140 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726241AbgHXK24 (ORCPT ); Mon, 24 Aug 2020 06:28:56 -0400 Received: from [192.168.0.50] (89-70-52-201.dynamic.chello.pl [89.70.52.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 175D520738; Mon, 24 Aug 2020 10:28:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1598264935; bh=NDhUf/nP2mxoHfjf7T44MWooQOLOp+W6Th3UihAUPk4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=XggvhdR1Szz+C2VO8HTTOPRjAqIa/TDcdPlm3E0ODNfUDDzq80nm0vsPxh/bijYYz 0s9qhiZjWcMR+YLzOfBBWI4Jjc9ut5S6FXpd0bQ5R7pwiFvsAfRwKwYNcYYOh/if3v 0BQiTaxKX1ofkzOdDD6XfgBPzaHHWWIedzfyu5MQ= Subject: Re: [PATCH v2] clk: samsung: Keep top BPLL mux on Exynos542x enabled To: Stephen Boyd Cc: linux-samsung-soc@vger.kernel.org, Marek Szyprowski , linux-clk@vger.kernel.org, linux-pm@vger.kernel.org, Chanwoo Choi , Krzysztof Kozlowski , Bartlomiej Zolnierkiewicz , Lukasz Luba References: <20200807133143.22748-1-m.szyprowski@samsung.com> <159780685238.334488.5802955284004610550@swboyd.mtv.corp.google.com> From: Sylwester Nawrocki Message-ID: Date: Mon, 24 Aug 2020 12:28:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-pm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On 8/23/20 12:12, Sylwester Nawrocki wrote: > On 8/19/20 05:14, Stephen Boyd wrote: >> Quoting Marek Szyprowski (2020-08-07 06:31:43) >>> BPLL clock must not be disabled because it is needed for proper DRAM >>> operation. This is normally handled by respective memory devfreq driver, >>> but when that driver is not yet probed or its probe has been deferred >>> the >>> clock might got disabled what causes board hang. Fix this by calling >>> clk_prepare_enable() directly from the clock provider driver. >>> >>> Signed-off-by: Marek Szyprowski >>> Reviewed-by: Lukasz Luba >>> Tested-by: Lukasz Luba >>> Acked-by: Krzysztof Kozlowski >>> --- >> >> Can I pick this up for clk-fixes? > > Sure, thanks for taking care of this. OTOH, I planned to queue that patch for next merged window, together with a patch that depends on that one, since the fix is not for an issue introduced in the last merge window. I guess it's better to avoid pulling (part of) the clk-fixes branch to the clk/samsung tree for next merge window?