From patchwork Fri Nov 18 09:14:13 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Marek Szyprowski X-Patchwork-Id: 82848 Delivered-To: patch@linaro.org Received: by 10.140.97.165 with SMTP id m34csp1236806qge; Fri, 18 Nov 2016 01:15:45 -0800 (PST) X-Received: by 10.129.152.211 with SMTP id p202mr7698165ywg.314.1479460545059; Fri, 18 Nov 2016 01:15:45 -0800 (PST) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v191si1462575ywv.399.2016.11.18.01.15.44; Fri, 18 Nov 2016 01:15:45 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-samsung-soc-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-samsung-soc-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-samsung-soc-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752817AbcKRJPn (ORCPT + 4 others); Fri, 18 Nov 2016 04:15:43 -0500 Received: from mailout2.samsung.com ([203.254.224.25]:51858 "EHLO mailout2.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752793AbcKRJPm (ORCPT ); Fri, 18 Nov 2016 04:15:42 -0500 Received: from epcpsbgm1new.samsung.com (epcpsbgm1 [203.254.230.26]) by mailout2.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0OGT02K5TZ23EWD0@mailout2.samsung.com>; Fri, 18 Nov 2016 18:15:39 +0900 (KST) X-AuditID: cbfee61a-f79916d0000062de-94-582ec6bba6d3 Received: from epmmp2 ( [203.254.227.17]) by epcpsbgm1new.samsung.com (EPCPMTA) with SMTP id 61.1D.25310.BB6CE285; Fri, 18 Nov 2016 18:15:39 +0900 (KST) Received: from AMDC2765.digital.local ([106.116.147.25]) by mmp2.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0OGT00LBHZ1SZW30@mmp2.samsung.com>; Fri, 18 Nov 2016 18:15:39 +0900 (KST) From: Marek Szyprowski To: linux-clk@vger.kernel.org, linux-samsung-soc@vger.kernel.org Cc: Marek Szyprowski , Sylwester Nawrocki , Krzysztof Kozlowski , Bartlomiej Zolnierkiewicz , Jaehoon Chung , Chanwoo Choi Subject: [PATCH] clk/samsung: exynos5433: mark some clocks as critical Date: Fri, 18 Nov 2016 10:14:13 +0100 Message-id: <1479460453-23620-1-git-send-email-m.szyprowski@samsung.com> X-Mailer: git-send-email 1.9.1 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsVy+t9jQd3dx/QiDH6t1rTYOGM9q8X1L89Z LW78amO1OH9+A7vFx557rBYzzu9jslh75C67xeE37awOHB6bVnWyefRtWcXo8XmTXABzlJtN RmpiSmqRQmpecn5KZl66rVJoiJuuhZJCXmJuqq1ShK5vSJCSQlliTimQZ2SABhycA9yDlfTt Etwyvm15wljwXa2ieWFSA+MXhS5GTg4JAROJ/pbpjBC2mMSFe+vZuhi5OIQEZjFKrF/zkxHC +cUocam1kQmkik3AUKLrbRcbiC0i4CDx+dNrsCJmgX4mif//ljODJIQF3CQmzu8Ga2ARUJU4 u2MtmM0r4CGx++NGqHVyEiePTWadwMi9gJFhFaNEakFyQXFSeq5hXmq5XnFibnFpXrpecn7u JkZwaD6T2sF4cJf7IUYBDkYlHt6Ia7oRQqyJZcWVuYcYJTiYlUR4RY7qRQjxpiRWVqUW5ccX leakFh9iNAU6YCKzlGhyPjBu8kriDU3MTcyNDSzMLS1NjJTEeRtnPwsXEkhPLEnNTk0tSC2C 6WPi4JRqYDzA9uT5Cb5f5aGHi/YllC6Yukaiq0Q44VvTeevW29f/mUQ08BiZNZ95aORYstD1 KF/qcoXpznn6D3hPhSsc26jr0dyYaBwvxMgbx/F11//nU7qXSbi1hr7b+sTtVvLPc6Urrj7V FGP6eCD8quuD/eqNq4LEOVPmrv6b5vfOiOf6MsWswL3PS5RYijMSDbWYi4oTAS4hQlNjAgAA X-MTR: 20000000000000000@CPGS Sender: linux-samsung-soc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-samsung-soc@vger.kernel.org Some parent clocks of the Exynos5433 CMUs must be always enabled to access any register in the given CMU or devices connected to it. For the time being, until a proper solution based on runtime PM is applied, mark those clocks as critical (instead of ignore unused) to prevent disabling them. Reported-by: Jaehoon Chung Signed-off-by: Marek Szyprowski --- drivers/clk/samsung/clk-exynos5433.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Reviewed-by: Chanwoo Choi