Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp3538982ybk; Tue, 19 May 2020 07:08:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx4RqsycijV1BjArnNmlCpaAeDo+H4w2p2Rw/PJ4Y1xqMQ2k66ISjMLYhAMIl2f/xrc4uxP X-Received: by 2002:a17:906:7083:: with SMTP id b3mr18904097ejk.57.1589897332967; Tue, 19 May 2020 07:08:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589897332; cv=none; d=google.com; s=arc-20160816; b=xfztsMxCUc14QQEgn/mEBafiFGJ2tvVosv6fauseIVT8dk6O90x0USSRZrHYqU2Do1 OEU75KBviBn+F26YxD699So1kQbrnDgWSH7FUyzjU8HA2sRSDMZKIV8WtSr6SKpq2TX+ 8dOVRg3v77Px8wC0ZFMlltZG382mr62pC8cqYM5SiczkinjkIN1KRHefl1/Vm95MPyFX w3bO6R94ZF1di/xzJpyemRUr/vB4VTwttQGvUfcqggylqVGioc05h921b8fHyAAVMeyH rriVGMlWl86WZcGvzqWpsFvNX1lTZej8H1KC6bkGrMKXersDg25Qy+ZCzd6znYze0wM4 AyuQ== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=3ngWGohqyk1bY0kV0++kwnpeD3y2ZE5Nt8l5LSZ6FRQ=; b=N1YAVJ26WCuM6biLYifwNbOHM9uvW/mdJhML/RvVX6jHq7dqnmRDDV5lTYJOHpDPlX AURphoxkNYZ1xpswVhbaVCkOzynUuTR6XtePXua9rRLinQGUc5NsE8dUorLkkHyi2Cmn yypAImcodlxCfjuVLbMSI7PvQF6lo6SS6THP7/Jb1VCFH1b4oF848TlfZLNHBPVRYxKW QxnrOgnvbSiVVcCwvGw0Lhy5OdtQ9a5twKuanGfjLe/vWzU9t1ejICPb6t8J+G6U4lE9 mG1kOD7uMqWurWS+2EaeMnOcQn0nIgTemDTZLxw9/A/Ga1rGU9PJropoMsnTXLZq1Ozp qVhQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=JNM5HwwQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id c21si8347048edv.154.2020.05.19.07.08.29; Tue, 19 May 2020 07:08:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=JNM5HwwQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1729136AbgESOFd (ORCPT + 99 others); Tue, 19 May 2020 10:05:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52960 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727910AbgESOFc (ORCPT ); Tue, 19 May 2020 10:05:32 -0400 Received: from mail-lf1-x141.google.com (mail-lf1-x141.google.com [IPv6:2a00:1450:4864:20::141]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EE78BC08C5C0; Tue, 19 May 2020 07:05:31 -0700 (PDT) Received: by mail-lf1-x141.google.com with SMTP id w15so3988578lfe.11; Tue, 19 May 2020 07:05:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=3ngWGohqyk1bY0kV0++kwnpeD3y2ZE5Nt8l5LSZ6FRQ=; b=JNM5HwwQ0gQ6nuCM6Kwij9v2fd9iRgUdc+MT4Op08k7J6Ulu1qQVyXeFLvk7ehAi8K +EnpUcbc4KK4ErikoxL4837JsZFfJMcoh84iWKWNRzVzXjZ3XIG6NVQUa2XVeWrq25d2 V+UdACbBZga9RlPT36llf67I9pQrLn+zXRj6i2YjZOWNjdlLzI2cV4vuVtzqUlp3NvXH Xrnj8h6hFoKRUMc+ejo1L08QIDjmdyERbsLAqcmyc67t1TPEFbBmc1JE3Al9M9lw9Izt 3QnnpQRuriGz91mMQ8rFOxR8bHQDEtW4+Xes5BCx5wARSFHjdNioYpTlgqJiJcPj5rl8 VRzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=3ngWGohqyk1bY0kV0++kwnpeD3y2ZE5Nt8l5LSZ6FRQ=; b=lUGHUGAWx44nLseswMnQXMVm+h1ToXFRKJ7YL3gp2bTOkXFFpGrQ3cNx6ReSUJ5IGu Ut7/21Rnfbv7kAoS26kfpsmQQqzEphvJda4BOqY4Z8Ax8gzfC9xM6pfLxMPO6bEnn25O jOnLir1rXwPLWWNVuAZvd1Qvvuf4Cb9cEmB+mgwtDS8QO2PFJefqqQ9PAKWyZ+ZTRY1w FGTfS5eNhl8Bhic18ijsABOg6lFaG9Q4BMKGu5xp2oC233cs9PUVjXgi/DQ1SzT8PbUJ 0s2Q0bZylQZp6HDvDLROVXLCd80S33pQJWUxoyvUOq93PmaebAd58UnztztVBAytnYLL Ou3Q== X-Gm-Message-State: AOAM530uvaFHxBxrAGSQsCX4/DrK7951SFU6uSGeL8x9vkBatDq2wRN0 wLh4XtwUD1uTfmNzixHjeBd2A8kZ X-Received: by 2002:ac2:5f69:: with SMTP id c9mr8778817lfc.2.1589897130069; Tue, 19 May 2020 07:05:30 -0700 (PDT) Received: from [192.168.2.145] (ppp91-78-208-152.pppoe.mtu-net.ru. [91.78.208.152]) by smtp.googlemail.com with ESMTPSA id v28sm3041273lfd.35.2020.05.19.07.05.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 May 2020 07:05:28 -0700 (PDT) Subject: Re: [PATCH v1] sdhci: tegra: Remove warnings about missing device-tree properties To: Ulf Hansson Cc: Thierry Reding , Jonathan Hunter , Adrian Hunter , "linux-mmc@vger.kernel.org" , linux-tegra , Linux Kernel Mailing List References: <20200516154314.14769-1-digetx@gmail.com> From: Dmitry Osipenko Message-ID: Date: Tue, 19 May 2020 17:05:27 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 19.05.2020 10:28, Ulf Hansson пишет: > On Sat, 16 May 2020 at 17:44, Dmitry Osipenko wrote: >> >> Several people asked me about the MMC warnings in the KMSG log and >> I had to tell to ignore them because these warning are irrelevant to >> pre-Tegra210 SoCs. > > Why are the warnings irrelevant? That's what the DT binding doc says [1]. [1] https://www.kernel.org/doc/Documentation/devicetree/bindings/mmc/nvidia%2Ctegra20-sdhci.txt Although, looking at the driver's code and TRM docs, it seems that all those properties are really irrelevant only to the older Terga20 SoC. So the binding doc is a bit misleading. Nevertheless, the binding explicitly says that the properties are optional, which is correct. >> It should be up to a board's device-tree writer to >> properly describe all the necessary properties. Secondly, eventually all >> device-tree bindings will be converted to YAML, which allows to validate >> board DT files, giving a warning about missing properties. Hence let's >> remove the noisy warnings to stop the confusion. > > Yep, makes sense. However, perhaps we should do this conversion then, > rather than first drop the warnings? I don't mind to postpone this patch. But again, IIUC, all these properties are optional, and thus, there is no critical need to verify them in DT right now, it could be done later on.