Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp4146399imm; Mon, 15 Oct 2018 09:48:02 -0700 (PDT) X-Google-Smtp-Source: ACcGV63FSyqEkD+vvyyPn8RggpLFXE6/pdf+YPKUh8Ri0lWE2DqOC41lTtcVCOnVTIyIFhH4AB5j X-Received: by 2002:a62:5fc5:: with SMTP id t188-v6mr9144754pfb.84.1539622081961; Mon, 15 Oct 2018 09:48:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539622081; cv=none; d=google.com; s=arc-20160816; b=hvf2BKGk/bSeFu/ZHuC6xoVXjP0kFRxafUaA7kfzbr2INFajrurYRdgxiQRK1ctV+0 V5qbuN9Y2OiiK73Fe7oUhPeDYUEhAsA+bvev5wYG0Pv8jsZKvX+WiUyBzVJjYK94xhWY jGAT6jEnYWjz2ILRFuFXP5jBy0nBNaY7sawqVuqG6ofHFMAI2hHyxhYhcp327EeRC/pb kIb9XJY6tO8PCuqwiHTOsnb8FO4/zKaWsxn8NxeHH+hTsSGABDpbwdyHN8HIUUbsSzva OeQ2M5+Vi3JUxTvLQwDt1JsXjRyoTGhMXc25kS1jMbSKlrmS7SIhzRWNJ+rs277wBCL7 UyHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:subject:user-agent:message-id :references:cc:in-reply-to:from:to:content-transfer-encoding :mime-version:dkim-signature; bh=729qZ7IhqGix8Y9+mNSNwCGe24G6QW+RYwfMIlNBjkc=; b=gWegBOsHrwBKHZ/MTS3eHuwjr1HgIfwP8fuiqF8v9qkd7I3a1lkegRhItnjbS0NeSM AN6/cPPDcy4YLlfaUODThD0B8sCKUttigrI+7TxJMwbMR/GyAuMx7r8FOu8RM4dn95af RIAqXBkZJMAY3GQ69W6oCT+RcHTrbcaw4geQuiQgLEkypGfwonlt3SbeVrprxAaK9eF/ 1772YHNgTYqplJZ2cqBTlgW1yZNvm9UCE1YJDipFLrHTtU/5jzNyTYGvQyxjH7sobnE9 L7z1T0zJ6dLUv8JWC4Tkg1o5Qo9/ZfYzvZoaXu6c3HntduEhi4bfqDyvzChqnZ8TqyB+ mNTQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="K/YbPpk+"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a7-v6si11031379pgb.301.2018.10.15.09.47.45; Mon, 15 Oct 2018 09:48:01 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="K/YbPpk+"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726768AbeJPAcA (ORCPT + 99 others); Mon, 15 Oct 2018 20:32:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:37872 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726691AbeJPAcA (ORCPT ); Mon, 15 Oct 2018 20:32:00 -0400 Received: from localhost (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 773622064A; Mon, 15 Oct 2018 16:45:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1539621958; bh=729qZ7IhqGix8Y9+mNSNwCGe24G6QW+RYwfMIlNBjkc=; h=To:From:In-Reply-To:Cc:References:Subject:Date:From; b=K/YbPpk+4B4ZHYIU1c0av9EJZNgoAyFKdx/EOn0+dBicj/vtsfQPlK58azZ1M8ggI seQp+c93t2sfoD1IekQw1Q28j8WVxk+gfJYADTF2jecXBqnlCfEE0Xv259XmWW1ddm cuyNa+21Co7nm3S06OqTu/LP9pwiVSkmeuOSDlQU= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable To: "kernel@pengutronix.de" , "linux-arm-kernel@lists.infradead.org" , "linux-clk@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mturquette@baylibre.com" , "s.hauer@pengutronix.de" , "shawnguo@kernel.org" , Anson Huang , Fabio Estevam , Jerome Forissier , Peng Fan , Rob Herring From: Stephen Boyd In-Reply-To: Cc: dl-linux-imx References: <1533703167-26583-1-git-send-email-Anson.Huang@nxp.com> <153567894721.93865.4092113232222931488@swboyd.mtv.corp.google.com> <153573827629.93865.6200966443862432044@swboyd.mtv.corp.google.com> <153898445180.119890.15025812558797341532@swboyd.mtv.corp.google.com> <153937368201.5275.2313781259297807972@swboyd.mtv.corp.google.com> Message-ID: <153962195779.5275.17500455384946496344@swboyd.mtv.corp.google.com> User-Agent: alot/0.7 Subject: RE: [PATCH 2/2] clk: imx: imx7d: remove clks_init_on array Date: Mon, 15 Oct 2018 09:45:57 -0700 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Anson Huang (2018-10-15 02:33:35) > > > > > > > > > > > > > Why can't we add clks to the op-tee node in DT's /firmware containe= r? > > > > Then any clks in there can be turned on forever and left enabled by > > > > the linux driver? > > > > > > I did NOT run op-tee with Linux-next kernel before, can you advise mo= re? > > = > > Neither have I, so I can't advise more. > > = > > > And I think if op-tee has such requirement, can we have another patch > > > to cover it? > > = > > Yes. > > = > > = > > > I believe all other i.MX platforms also have same requirements if > > > considering op-tee support, so I think it should be another topic, wh= at do you > > think? > > > > > = > > I'm going to drop these patches from my review queue. Please resend them > > and please include the op-tee patches too. > = > = > I do NOT know how to include the op-tee patch to meet special requirement= , should > the op-tee related patch be added later when someone actually add the op-= tee support for i.MX7? > It should NOT block this patch set, do you think we can add this patch se= t first? > = Please resend the two patches. In the commit text for the second patch, describe the plan to remove CLK_IS_CRITICAL from these clks by adding an OP-TEE device/driver to the kernel to keep these clks enabled. My understanding is that there isn't an OP-TEE driver right now, but these clks are used by the firmware and can't be turned off in Linux. If in the future we want to be able to turn them on and off, we'll need to add them to an OP-TEE device node and have that driver manage the clks. How that will work when a system doesn't enable the OP-TEE driver I'm not sure. We may need to develop some system whereby clks like this are handed from the clk controller to the consumer driver when it's enabled for further power managment, but if they're never handed off, they're kept on forever like is done here. Anyway, please resend with a note about why these are marked CLK_IS_CRITICAL.