Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp54314imm; Thu, 30 Aug 2018 08:09:42 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbuKn99J9Lm1d0eIY4IPVKaLWLR/m6mQ6yuMFpVDnRJ4TXI6evwBdiFl8ZL2dktM4q418do X-Received: by 2002:a17:902:14e:: with SMTP id 72-v6mr10474592plb.299.1535641782125; Thu, 30 Aug 2018 08:09:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535641782; cv=none; d=google.com; s=arc-20160816; b=VIYNY/3dIybpIsaz1NZSkaIjFaGcj/abkPglk5mnLlZ+Qq/IQ7+Q3Aq1K5oBQPagLD ASK7NFGQ6QsddLYtIXRHG84fVyTE6M+dENLjCxRrxivYoV99Rg6fcnPIfF/VfsCjq2xs nklNF0PyBsMuTj+imtz7VLm4WFGiiAHgMhVB5deOK8oWVqL8sxkUikONYPpYC7Y16sjb EkekhPyn6jTT+wOkdIxiqTtsLusfa0X1iVbJ/p7QHLkG4sgzFtDKIN1ptB2ACef/W7F5 PmhQFfKRE1BctzUnZYENQkLYPih8fXKrDBcNTPw37HFXQs0J61Zt6nnNwEs+kvfv3+wx k/SA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:arc-authentication-results; bh=qtD+hpx790nH8ZAWgcRVNiAwosJCJL+WoO5+bMvnxkI=; b=jPjonKHFBra6CZJIkahPSlTUKGqua0FAUEpago+3FVQYN47ipcFgYpUZxTqOdXSonM SS1Spqvo56MsBTandVgIbGwJpwWmOWfvTbtqG1be39jEGZGti0eWrC3kyfgjfd46/ouN 2dGogLfN/HyWp63wLr8rY4wSSXAoG56PDPmkCn5lW8P9ixKyHxgLmdT0dPfodnYJzukz D5zlM0RCuP5zCbHmwhhapFAgI6dA9JVUqH7HhlNhKCxeUBZmRPDLa6kTSSHbuw2fE0z5 kyzFRhB1d4pT+T9uxk0DU33qMhP0n5QTVYIDCdUPuuGsa9GiZaVrhUJYNXZfNnUdt4P9 zpHQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id ay10-v6si6700768plb.293.2018.08.30.08.09.25; Thu, 30 Aug 2018 08:09:42 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728667AbeH3TJa (ORCPT + 99 others); Thu, 30 Aug 2018 15:09:30 -0400 Received: from hqemgate14.nvidia.com ([216.228.121.143]:13426 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728566AbeH3TJa (ORCPT ); Thu, 30 Aug 2018 15:09:30 -0400 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqemgate14.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Thu, 30 Aug 2018 08:06:52 -0700 Received: from HQMAIL101.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Thu, 30 Aug 2018 08:06:54 -0700 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Thu, 30 Aug 2018 08:06:54 -0700 Received: from HQMAIL101.nvidia.com (172.20.187.10) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 30 Aug 2018 15:06:53 +0000 Received: from hqnvemgw01.nvidia.com (172.20.150.20) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 30 Aug 2018 15:06:53 +0000 Received: from dhcp-10-21-25-168.Nvidia.com (Not Verified[10.21.25.201]) by hqnvemgw01.nvidia.com with Trustwave SEG (v7,5,8,10121) id ; Thu, 30 Aug 2018 08:06:53 -0700 From: Aapo Vienamo To: Rob Herring , Mark Rutland , Thierry Reding , Jonathan Hunter , Ulf Hansson , Adrian Hunter , Mikko Perttunen , Stefan Agner CC: , , , , Aapo Vienamo Subject: [PATCH v3 03/38] dt-bindings: Add Tegra SDHCI pad pdpu offset bindings Date: Thu, 30 Aug 2018 18:06:04 +0300 Message-ID: <20180830150639.21048-4-avienamo@nvidia.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20180830150639.21048-1-avienamo@nvidia.com> References: <20180830150639.21048-1-avienamo@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add bindings documentation for pad pull up and pull down offset values to be programmed before executing automatic pad drive strength calibration. Signed-off-by: Aapo Vienamo Acked-by: Thierry Reding --- .../bindings/mmc/nvidia,tegra20-sdhci.txt | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) diff --git a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt index 90c214dbfb16..9713e052f736 100644 --- a/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt +++ b/Documentation/devicetree/bindings/mmc/nvidia,tegra20-sdhci.txt @@ -45,6 +45,37 @@ Optional properties for Tegra210 and Tegra186: for controllers supporting multiple voltage levels. The order of names should correspond to the pin configuration states in pinctrl-0 and pinctrl-1. +- nvidia,only-1-8-v : The presence of this property indicates that the + controller operates at a 1.8 V fixed I/O voltage. +- nvidia,pad-autocal-pull-up-offset-3v3, + nvidia,pad-autocal-pull-down-offset-3v3 : Specify drive strength + calibration offsets for 3.3 V signaling modes. +- nvidia,pad-autocal-pull-up-offset-1v8, + nvidia,pad-autocal-pull-down-offset-1v8 : Specify drive strength + calibration offsets for 1.8 V signaling modes. +- nvidia,pad-autocal-pull-up-offset-3v3-timeout, + nvidia,pad-autocal-pull-down-offset-3v3-timeout : Specify drive + strength used as a fallback in case the automatic calibration times + out on a 3.3 V signaling mode. +- nvidia,pad-autocal-pull-up-offset-1v8-timeout, + nvidia,pad-autocal-pull-down-offset-1v8-timeout : Specify drive + strength used as a fallback in case the automatic calibration times + out on a 1.8 V signaling mode. +- nvidia,pad-autocal-pull-up-offset-sdr104, + nvidia,pad-autocal-pull-down-offset-sdr104 : Specify drive strength + calibration offsets for SDR104 mode. +- nvidia,pad-autocal-pull-up-offset-hs400, + nvidia,pad-autocal-pull-down-offset-hs400 : Specify drive strength + calibration offsets for HS400 mode. + + Notes on the pad calibration pull up and pulldown offset values: + - The property values are drive codes which are programmed into the + PD_OFFSET and PU_OFFSET sections of the + SDHCI_TEGRA_AUTO_CAL_CONFIG register. + - A higher value corresponds to higher drive strength. Please refer + to the reference manual of the SoC for correct values. + - The SDR104 and HS400 timing specific values are used in + corresponding modes if specified. Example: sdhci@700b0000 { @@ -58,5 +89,9 @@ sdhci@700b0000 { pinctrl-names = "sdmmc-3v3", "sdmmc-1v8"; pinctrl-0 = <&sdmmc1_3v3>; pinctrl-1 = <&sdmmc1_1v8>; + nvidia,pad-autocal-pull-up-offset-3v3 = <0x00>; + nvidia,pad-autocal-pull-down-offset-3v3 = <0x7d>; + nvidia,pad-autocal-pull-up-offset-1v8 = <0x7b>; + nvidia,pad-autocal-pull-down-offset-1v8 = <0x7b>; status = "disabled"; }; -- 2.18.0