Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp122630ybl; Mon, 12 Aug 2019 12:55:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqwnuPjJSFmq3nBXccXPANj18R5QbDNOdk6+pxsVfhj6K1m4WrrA9KNmpu5JMB7pPlWXIHYQ X-Received: by 2002:a17:902:f81:: with SMTP id 1mr34160171plz.191.1565639739376; Mon, 12 Aug 2019 12:55:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565639739; cv=none; d=google.com; s=arc-20160816; b=nB0/Men5M/4FLbRI+wmidwxuJry1ylifdtHcgrjXcWMqo69tlcwzSBUTmGdq0+WFdU GsSVR0tvzYEB5KShHxAFmUM4Ode5l4j5STg07j8bwClgmAPM6vlUccv4LUVlw3vInsd7 YzEnxRolKiXF6JIVm6XkmL4G6wmWxY2pF79sY9XVbeEMHfaUjWCwWdkKMmI4ISYOJXp4 DPP6iEDF79yfnoF+USe5VSkccc+3+PuLgQAkr3Xgs+xZEiP5jfSXvPGot8h/t+BYZHwu ZQjtwG5ohuJMGzitZSwr7YRhWydj5vLxAG3gg/PRiNZTomItn3Ie4kv3Ec/ori56Pij1 PEzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=ddPsoGt8F/KGLXUlBKjTyS9aZYgiwyfNfL+dV5hM2Aw=; b=BVkioNtraASJnJ8cu1Gv8YkD0u5u6gkFlcysOxvvkhlOAQV6aaHmU9QU0rihZKvxf3 r+8Im34HOWaYnuI0zF0eYFkkIP/8seX7ZdxbO0MW7L/JtptVpKBOycHtByd4tsVKWMzH 3TJSP0cx4QKc4XFmLGO400jl2i4rvW06XVaC3mjCxlMQVG1BFd2WCBq3ous2Jb5cM87y BRKkXc/950kl2pBfRgCAHPOZ/m7ZsfLdeuC4UpaNm9Te9sNORoKeUPHUdN52UtNgxm6/ vxcxxVNSnkQMrSBVJLyHGeoZC/Tv6fH+OE/5f6nayPL6xylvWJi5dnwJo7D6HYuzlQKh 9JUg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=BMU8WnCr; 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 x20si23252222plm.61.2019.08.12.12.55.22; Mon, 12 Aug 2019 12:55:39 -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=BMU8WnCr; 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 S1727107AbfHLTx5 (ORCPT + 99 others); Mon, 12 Aug 2019 15:53:57 -0400 Received: from mail.kernel.org ([198.145.29.99]:57848 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726679AbfHLTx4 (ORCPT ); Mon, 12 Aug 2019 15:53:56 -0400 Received: from mail-qk1-f182.google.com (mail-qk1-f182.google.com [209.85.222.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 76861206C2; Mon, 12 Aug 2019 19:53:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565639635; bh=F/zUy3fK065yrPGhjPTWbq03dhm0wVUyzDzKPDc0vwM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=BMU8WnCrbKPHJn1JUY/xu78450ItVKNYznbbSff2/x8PBE1E1y4OHkwjlPl/GWqQj SIhOE5gP1J06pp89em2uL9icxToECD+QDXDEcBxwf6AarDTmTGydVrNa7VhZOhF4eT FjEfC4QnzrxG0L1q9y1TaxReAxahua7befQXofAc= Received: by mail-qk1-f182.google.com with SMTP id r21so77967190qke.2; Mon, 12 Aug 2019 12:53:55 -0700 (PDT) X-Gm-Message-State: APjAAAXXXzh6fiNvqlMPFl9nCBJVfDU2RYXJTfj8LWIXjBEoM2D3mnnV d9X1TOchurIq8JpEX+PnYnp0ehNPMnmXfl7AHQ== X-Received: by 2002:a37:a48e:: with SMTP id n136mr31785938qke.223.1565639634684; Mon, 12 Aug 2019 12:53:54 -0700 (PDT) MIME-Version: 1.0 References: <20190811210043.20122-1-digetx@gmail.com> <20190811210043.20122-10-digetx@gmail.com> In-Reply-To: <20190811210043.20122-10-digetx@gmail.com> From: Rob Herring Date: Mon, 12 Aug 2019 13:53:43 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v10 09/15] dt-bindings: memory: tegra30: Convert to Tegra124 YAML To: Dmitry Osipenko Cc: Michael Turquette , Joseph Lo , Thierry Reding , Jonathan Hunter , Peter De Schrijver , Prashant Gaikwad , Stephen Boyd , devicetree@vger.kernel.org, linux-clk , linux-tegra@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 11, 2019 at 3:01 PM Dmitry Osipenko wrote: > > 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. > > Reviewed-by: Rob Herring > Signed-off-by: Dmitry Osipenko > --- > .../nvidia,tegra124-mc.yaml | 152 ++++++++++++++++++ > .../memory-controllers/nvidia,tegra30-mc.txt | 123 -------------- > 2 files changed, 152 insertions(+), 123 deletions(-) > create mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra124-mc.yaml > delete mode 100644 Documentation/devicetree/bindings/memory-controllers/nvidia,tegra30-mc.txt Reviewed-by: Rob Herring