Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1127905ybh; Thu, 23 Jul 2020 00:45:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzN9QFE31vRs8c9cYB9VZKCXyejJlywlZRbhZE5fZRHXk2sbaIavW4Os6W11Wad5+ZUmwIv X-Received: by 2002:a50:ab52:: with SMTP id t18mr3010354edc.195.1595490302291; Thu, 23 Jul 2020 00:45:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595490302; cv=none; d=google.com; s=arc-20160816; b=J1T4aNb9LxOPcydZN5OEtZpQIMaEoMGwLp/aVKsIKBFL2QJ096kau12MraNW9XZMa7 5W1USu0Lj4VHZv0Bc7UMGOgwn21NNgz1fZ0FFjSxEFr+Rbq8ScyLfWavciJXBfTIBPa+ 7m5baw25+VdvQRfu6x5r/lYs8M5ZMCWRkf0h5mL3t1tR+OJE6fBZj/4GeZEe0XLcZRGj 9cpJXxxu4neyEbUQ0lalRZ3wR/f8yT68Lw+yoEpRECoOOdqCiR+C+Fnav+4usxBobmzD A5lGTA6EUjQzyFMhXWBSEutfCBgynPVnA210jQco0wnmYZlM7UDYCK32lF3SozGuIuAJ CDMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=eZga/LiXStP5WOFM1p8mNax5fYkyirN5NcwYtvXxdbE=; b=WXh6RT6Oyv+yyKR20K1PWmhOeILbdeFMzzLhjzDY6JzlTJh9fx2FKEByuFBVN+3POa 0nTo98FEfcAXkGZ1YCDrRHsEG0PDKB8bwTRSRFOyWyhm3FJhQZENM+4jeK9ue1GKB8YZ dWahGDBLrDewPo7eQtddQu4noDnxeEdk0eZ8f97XmMEXkn7+RQmCQsDv0fM+rVq7CBIa PICETgvNvaKGW/jer/jDNHv10P8ByeYa4E82gQLZhZHW0/Sq0MRaTCTZ4gPsL4CoTPqH 7mGaP2kqzCi/SJygkghxyrW58PP8MMNJ7AD+bG+6K5lQ0DlRtyVfTNlZOoF9+vOHRFzP O/dw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k19si1532903ejk.27.2020.07.23.00.44.39; Thu, 23 Jul 2020 00:45:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727120AbgGWHnc (ORCPT + 99 others); Thu, 23 Jul 2020 03:43:32 -0400 Received: from inva020.nxp.com ([92.121.34.13]:37046 "EHLO inva020.nxp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726108AbgGWHnb (ORCPT ); Thu, 23 Jul 2020 03:43:31 -0400 Received: from inva020.nxp.com (localhost [127.0.0.1]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id 0B1C61A0083; Thu, 23 Jul 2020 09:43:29 +0200 (CEST) Received: from inva024.eu-rdc02.nxp.com (inva024.eu-rdc02.nxp.com [134.27.226.22]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id F1AD71A007B; Thu, 23 Jul 2020 09:43:28 +0200 (CEST) Received: from fsr-ub1864-014.ea.freescale.net (fsr-ub1864-014.ea.freescale.net [10.171.95.219]) by inva024.eu-rdc02.nxp.com (Postfix) with ESMTP id 593FB202B6; Thu, 23 Jul 2020 09:43:28 +0200 (CEST) From: =?UTF-8?q?Horia=20Geant=C4=83?= To: Herbert Xu , Dmitry Torokhov Cc: "David S. Miller" , Rob Herring , Shawn Guo , =?UTF-8?q?Andr=C3=A9=20Draszik?= , Robin Gong , Anson Huang , Fabio Estevam , Aymen Sghaier , Adam Ford , linux-input@vger.kernel.org, linux-crypto@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, NXP Linux Team Subject: [PATCH v3 1/3] dt-bindings: crypto: fsl-sec4: add snvs clock to pwrkey Date: Thu, 23 Jul 2020 10:43:12 +0300 Message-Id: <20200723074314.3304-2-horia.geanta@nxp.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20200723074314.3304-1-horia.geanta@nxp.com> References: <20200723074314.3304-1-horia.geanta@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org From: André Draszik On i.MX7 and i.MX8M, the SNVS requires a clock. This is similar to the clock bound to the SNVS RTC node, but if the SNVS RTC driver isn't enabled, then SNVS doesn't work, and as such the pwrkey driver doesn't work (i.e. hangs the kernel, as the clock isn't enabled). Also see commit ec2a844ef7c1 ("ARM: dts: imx7s: add snvs rtc clock") for a similar fix. Signed-off-by: André Draszik Acked-by: Rob Herring Reviewed-by: Horia Geantă Signed-off-by: Horia Geantă --- .../devicetree/bindings/crypto/fsl-sec4.txt | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt index 8f359f473ada..1800d57edb66 100644 --- a/Documentation/devicetree/bindings/crypto/fsl-sec4.txt +++ b/Documentation/devicetree/bindings/crypto/fsl-sec4.txt @@ -449,6 +449,19 @@ System ON/OFF key driver Value type: Definition: this is phandle to the register map node. + - clocks + Usage: optional, required if SNVS LP requires explicit + enablement of clocks + Value type: + Definition: a clock specifier describing the clock required for + enabling and disabling SNVS LP. + + - clock-names + Usage: optional, required if SNVS LP requires explicit + enablement of clocks + Value type: + Definition: clock name string should be "snvs-pwrkey". + EXAMPLE: snvs-pwrkey@020cc000 { compatible = "fsl,sec-v4.0-pwrkey"; @@ -456,6 +469,8 @@ EXAMPLE: interrupts = <0 4 0x4> linux,keycode = <116>; /* KEY_POWER */ wakeup-source; + clocks = <&clks IMX7D_SNVS_CLK>; + clock-names = "snvs-pwrkey"; }; ===================================================================== @@ -547,6 +562,8 @@ FULL EXAMPLE interrupts = <0 4 0x4>; linux,keycode = <116>; /* KEY_POWER */ wakeup-source; + clocks = <&clks IMX7D_SNVS_CLK>; + clock-names = "snvs-pwrkey"; }; }; -- 2.17.1