Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp1373424ybi; Sun, 30 Jun 2019 14:05:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqxVUQmxeeEYOE32cqJw9c49P8M++4X7acJ6JQRgeFuKtAbFj2dWFpSfdDK0IH+bs3pfYTYe X-Received: by 2002:a17:902:290b:: with SMTP id g11mr24425427plb.26.1561928727944; Sun, 30 Jun 2019 14:05:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561928727; cv=none; d=google.com; s=arc-20160816; b=CYYdZNRwRu1IUIFdAM5F3beAS+b9jvk61qkSbhcm2stL4+LVFJl3Vk1YCfw/QKTaBb T7a4x6fRbjvlWvGY53KWSo3a/vJ3q79T8JEAfZxDyRWBsGbqgX7UlLB42lT4XUzvrYym bB1uu49FKe18WjDkmqRgoIShEq7UjRkJxIbRmxFT8ct+PmrnnWdFagpkQCiRIkVwfJCb 1Y4aMzZchiVNGH0FUjUCqMwH8wDSJcH3HQNAONRTvCELIeIyeeIoqtbkM/rqS7KZqIkW rPCBGT77CPfRffpKY9yZq15Dg3yuuJKOHVEBRumQd8lVorqtsfi2dU+mwfGB88ybHGHH INfg== 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 :dkim-signature; bh=w5DeDNLd/nQYRKa3PrC/JK8YgoKIo6tthgU3l9nbyhM=; b=D+mTYx4ux5K7QKxmRAT+BIsBswSPTch8kXptvujljj/PZ/ZUr49WnYvG0YTGQPTPLt Zi1aNhYImRhYSXb9EWsqMpyWuOAuGVgEowAga4aQCkxowS6mhcIfRBx5yPMsOTgEirLZ uzmnLNgiVa0U9I2/tcO4vMxoKXKNWj+r/bXoWpWh12lpCktEh4t/m7Xai15FVLoZQSpS 6CdB7KIHuxlM8xnIqUVQHLYbO2aDax0fPw4iRe9CkGSWirvIDKuOOixwRgpJ5psH/D87 8ep9WW0WKIMSoQL83uNfBKS0/OMfeCbnshZWAhDaoSsGz9kXcH6eIwmMoHT536J2PQYs UkHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=L8lXtyLt; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s33si6096501pgk.112.2019.06.30.14.05.12; Sun, 30 Jun 2019 14:05:27 -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=@gmail.com header.s=20161025 header.b=L8lXtyLt; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727130AbfF3VEr (ORCPT + 99 others); Sun, 30 Jun 2019 17:04:47 -0400 Received: from mail-lj1-f193.google.com ([209.85.208.193]:46242 "EHLO mail-lj1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727084AbfF3VEq (ORCPT ); Sun, 30 Jun 2019 17:04:46 -0400 Received: by mail-lj1-f193.google.com with SMTP id v24so10913512ljg.13; Sun, 30 Jun 2019 14:04:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=w5DeDNLd/nQYRKa3PrC/JK8YgoKIo6tthgU3l9nbyhM=; b=L8lXtyLtevN0fPA9VQbbOOjoI8pIdxDsdA3iC5X+mNx9KALw1hHwmqUo6svcNQpQGS q7ihkyhqbugkSfpDXjk7GcgyAPrgs6euJh2kD6j9zxCDDoDgRe9y/h09u4IH6o65P3F/ UsieJZaizfR313jX5pCW78cbLYUkmn1ntk4OTWZTrUPTalvbd8jDBcCWtKYOUpDJmkHD bv/b2LamCUhoprhzgdvEcp85te6rCgWSaLry/PLXduG+W+np7Q2HX7cUhSTCN5+UR1BH yNMHzcWIyAjczHR6b8hqfzeFt+iPw4yrPvh4Rh2+aTHXtC/5EC5NNLnl4Y05c4hOXDtq qU4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=w5DeDNLd/nQYRKa3PrC/JK8YgoKIo6tthgU3l9nbyhM=; b=g6Ob2J9Oz9+GoulwpjsWAAl7yJLuuox531O9zxNg/mJl2Uar9PmB5f/b8Ttp+5303I l1gyaQOPSdShtKFX56qr3LvuwLQ1Ke4ScvBMVPDQFDNgfCSH/gfxhh33qs3v1tKmPThj q1VoD1c32t6Z+B6KN8WKPlJBI0abjgDF1eg7c+yzgkMtQ3ZyKJv0Sw9sLY1f9H22AAmB E4+tk35zHpE7bzaPBwa4k8WMtYmqaaxbvaE6FK4qrujBCrx6cCdDNIJfaQAjF85eXpXk FTQp4eKKSFMLpt9CqHweETswS0eCG4aPOGMzat9409h93DICJxSndKLvdChPMbh1Tkbe yaFA== X-Gm-Message-State: APjAAAWd4Krw/kv1Ad0Bt1iSzxE7JO1LrlNFHk+0l/5UWcgytREGdHX4 a7UDeeFhSGt4lGC01KlO+XM= X-Received: by 2002:a2e:3e01:: with SMTP id l1mr12034305lja.208.1561928683855; Sun, 30 Jun 2019 14:04:43 -0700 (PDT) Received: from localhost.localdomain (ppp79-139-233-208.pppoe.spdop.ru. [79.139.233.208]) by smtp.gmail.com with ESMTPSA id u9sm2221408lfb.38.2019.06.30.14.04.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Jun 2019 14:04:43 -0700 (PDT) From: Dmitry Osipenko To: Rob Herring , Michael Turquette , Joseph Lo , Thierry Reding , Jonathan Hunter , Peter De Schrijver , Prashant Gaikwad , Stephen Boyd Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v6 07/15] dt-bindings: memory: tegra30: Convert to Tegra124 YAML Date: Mon, 1 Jul 2019 00:00:11 +0300 Message-Id: <20190630210019.26914-8-digetx@gmail.com> X-Mailer: git-send-email 2.22.0 In-Reply-To: <20190630210019.26914-1-digetx@gmail.com> References: <20190630210019.26914-1-digetx@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The Tegra30 binding will actually differ from the Tegra124 a tad, in particular the EMEM configuration description. Hence rename the binding to Tegra124 during of the conversion to YAML. Signed-off-by: Dmitry Osipenko --- .../nvidia,tegra124-mc.yaml | 149 ++++++++++++++++++ 1 file changed, 149 insertions(+) create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-mc.yaml diff --git a/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-mc.yaml b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-mc.yaml new file mode 100644 index 000000000000..d18242510295 --- /dev/null +++ b/Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-mc.yaml @@ -0,0 +1,149 @@ +# SPDX-License-Identifier: (GPL-2.0) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra124-mc.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: + NVIDIA Tegra124 SoC Memory Controller + +maintainers: + - Jon Hunter + - Thierry Reding + +description: | + Tegra124 SoC features a hybrid 2x32-bit / 1x64-bit memory controller. + These are interleaved to provide high performance with the load shared across + two memory channels. The Tegra124 Memory Controller handles memory requests + from internal clients and arbitrates among them to allocate memory bandwidth + for DDR3L and LPDDR3 SDRAMs. + +properties: + compatible: + const: nvidia,tegra124-mc + + reg: + maxItems: 1 + description: + Physical base address. + + clocks: + maxItems: 1 + description: + Memory Controller clock. + + clock-names: + items: + - const: mc + + interrupts: + maxItems: 1 + description: + Memory Controller interrupt. + + "#reset-cells": + const: 1 + + "#iommu-cells": + const: 1 + +patternProperties: + ".*": + properties: + nvidia,ram-code: + $ref: /schemas/types.yaml#/definitions/uint32 + description: + Value of RAM_CODE this timing set is used for. + + patternProperties: + ".*": + properties: + clock-frequency: + description: + Memory clock rate in Hz. + + nvidia,emem-configuration: + $ref: /schemas/types.yaml#/definitions/uint32-array + description: | + Values to be written to the EMEM register block. See section + "15.6.1 MC Registers" in the TRM. + items: + - description: MC_EMEM_ARB_CFG + - description: MC_EMEM_ARB_OUTSTANDING_REQ + - description: MC_EMEM_ARB_TIMING_RCD + - description: MC_EMEM_ARB_TIMING_RP + - description: MC_EMEM_ARB_TIMING_RC + - description: MC_EMEM_ARB_TIMING_RAS + - description: MC_EMEM_ARB_TIMING_FAW + - description: MC_EMEM_ARB_TIMING_RRD + - description: MC_EMEM_ARB_TIMING_RAP2PRE + - description: MC_EMEM_ARB_TIMING_WAP2PRE + - description: MC_EMEM_ARB_TIMING_R2R + - description: MC_EMEM_ARB_TIMING_W2W + - description: MC_EMEM_ARB_TIMING_R2W + - description: MC_EMEM_ARB_TIMING_W2R + - description: MC_EMEM_ARB_DA_TURNS + - description: MC_EMEM_ARB_DA_COVERS + - description: MC_EMEM_ARB_MISC0 + - description: MC_EMEM_ARB_MISC1 + - description: MC_EMEM_ARB_RING1_THROTTLE + + required: + - clock-frequency + - nvidia,emem-configuration + + required: + - nvidia,ram-code + +required: + - compatible + - reg + - interrupts + - clocks + - clock-names + - "#reset-cells" + - "#iommu-cells" + +examples: + - | + memory-controller@70019000 { + compatible = "nvidia,tegra124-mc"; + reg = <0x0 0x70019000 0x0 0x1000>; + clocks = <&tegra_car 32>; + clock-names = "mc"; + + interrupts = <0 77 4>; + + #iommu-cells = <1>; + #reset-cells = <1>; + + emc-timings-3 { + nvidia,ram-code = <3>; + + timing-12750000 { + clock-frequency = <12750000>; + + nvidia,emem-configuration = < + 0x40040001 /* MC_EMEM_ARB_CFG */ + 0x8000000a /* MC_EMEM_ARB_OUTSTANDING_REQ */ + 0x00000001 /* MC_EMEM_ARB_TIMING_RCD */ + 0x00000001 /* MC_EMEM_ARB_TIMING_RP */ + 0x00000002 /* MC_EMEM_ARB_TIMING_RC */ + 0x00000000 /* MC_EMEM_ARB_TIMING_RAS */ + 0x00000002 /* MC_EMEM_ARB_TIMING_FAW */ + 0x00000001 /* MC_EMEM_ARB_TIMING_RRD */ + 0x00000002 /* MC_EMEM_ARB_TIMING_RAP2PRE */ + 0x00000008 /* MC_EMEM_ARB_TIMING_WAP2PRE */ + 0x00000003 /* MC_EMEM_ARB_TIMING_R2R */ + 0x00000002 /* MC_EMEM_ARB_TIMING_W2W */ + 0x00000003 /* MC_EMEM_ARB_TIMING_R2W */ + 0x00000006 /* MC_EMEM_ARB_TIMING_W2R */ + 0x06030203 /* MC_EMEM_ARB_DA_TURNS */ + 0x000a0402 /* MC_EMEM_ARB_DA_COVERS */ + 0x77e30303 /* MC_EMEM_ARB_MISC0 */ + 0x70000f03 /* MC_EMEM_ARB_MISC1 */ + 0x001f0000 /* MC_EMEM_ARB_RING1_THROTTLE */ + >; + }; + }; + }; -- 2.22.0