From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5AAD9ECDE5F for ; Thu, 19 Jul 2018 15:31:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 202442084E for ; Thu, 19 Jul 2018 15:31:15 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 202442084E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=nvidia.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732559AbeGSQOq (ORCPT ); Thu, 19 Jul 2018 12:14:46 -0400 Received: from hqemgate16.nvidia.com ([216.228.121.65]:5136 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730899AbeGSQOd (ORCPT ); Thu, 19 Jul 2018 12:14:33 -0400 Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1, AES128-SHA) id ; Thu, 19 Jul 2018 08:30:43 -0700 Received: from HQMAIL101.nvidia.com ([172.20.161.6]) by hqpgpgate101.nvidia.com (PGP Universal service); Thu, 19 Jul 2018 08:30:51 -0700 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Thu, 19 Jul 2018 08:30:51 -0700 Received: from [10.21.132.122] (10.124.1.5) by HQMAIL101.nvidia.com (172.20.187.10) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 19 Jul 2018 15:30:50 +0000 Subject: Re: [PATCH v1] memory: tegra: Don't invoke Tegra30+ specific memory timing setup on Tegra20 To: Dmitry Osipenko , Thierry Reding CC: , References: <20180719132453.16860-1-digetx@gmail.com> From: Jon Hunter Message-ID: <39607791-3e71-7784-37db-4e05a316d7a8@nvidia.com> Date: Thu, 19 Jul 2018 16:30:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180719132453.16860-1-digetx@gmail.com> X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL101.nvidia.com (172.20.187.10) To HQMAIL101.nvidia.com (172.20.187.10) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19/07/18 14:24, Dmitry Osipenko wrote: > This fixes irrelevant "tegra-mc 7000f000.memory-controller: no memory > timings for RAM code 0 registered" warning message during of kernels > boot-up on Tegra20. Looking at the tegra20-emc.txt bindings doc [0], the 'nvidia,ram-code' property is also valid for Tegra20. In fact, I see this warning on the Tegra30 Cardhu because this property is not populated. So I think that this warning is valid and harmless. Cheers Jon [0] Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-emc.txt -- nvpublic