Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp188649ybi; Thu, 20 Jun 2019 20:51:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqyIL6Co+ZXcBFhSmxuyoKWQOTRu69Cfs82ZfuR+0GsdL0QVJsUCy9zTFZP6hIIHnInhaxdu X-Received: by 2002:a17:90a:2768:: with SMTP id o95mr3569741pje.37.1561089105116; Thu, 20 Jun 2019 20:51:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561089105; cv=none; d=google.com; s=arc-20160816; b=LHme95sUkPcv6NsBmNQxp0HBiQyA75wltUEaRYDKprhy2v0FbjNQgJNK1YNOhjX123 KQaem/WvmGgOU+1jMkrt3pCRUsAzlOHFsKJc20i89J3/qeoB/zahhqKPMRbk9vWnb0Rs tlkAyAweub6h0mIWCVL3qgvl0oPdERMtubF11y68rl6cOZ7+8EY18BTAmvHaJsKRM/RB /G27mS7rX5QwuK3QBW3gbCzXXYDKfbi7/Cfj7yc+kIdkSgipOin+7P1YrnmvmvN24NNg JxxadS/W2NVPT0BwVy8yu7cYoYecsucYqWM/62UxTV1Y0yK6HJmw3etMhb9KeWbMQa0t U5PQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :dkim-signature:dkim-filter; bh=Bg7yz3kGp5oc02/SzDEjzmVnjSSRFRG856VaDIqk91k=; b=ib/BynK9ZTZKSLkmJDtPCi7pZ07F3Mzm64L64B5wU3CpblrKwq1+/Cct9txzQLC1UK +mnDlzynMLU/K+keZ4PPbo8DvhQqohfIXZW+vMewasCqVef/u7y6+FUeJtKyKzUN7uQN liNmBZkTdMnSiEzPbl4Qoc9EzPJruv27yA1KRtHrA1qLqWTibWQK9pcA1PzwXxIu9zdp 1RwBJsQ7CK6gWWynmdbL3bsS8WX9L5wzHn8Ud3RNyN3RzOHzKtSI1ZEtiSWP4PGnRDGo 16cyujE8nWybnsEsr754bl6WXi+De+iYdSGt0AWzLQa6gYTxarqLEbYzQKtjexxu+9SR r89Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b="p0fbb/js"; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i97si1581471plb.50.2019.06.20.20.51.29; Thu, 20 Jun 2019 20:51:45 -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=@nifty.com header.s=dec2015msa header.b="p0fbb/js"; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726073AbfFUDvZ (ORCPT + 99 others); Thu, 20 Jun 2019 23:51:25 -0400 Received: from conuserg-08.nifty.com ([210.131.2.75]:42309 "EHLO conuserg-08.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725911AbfFUDvZ (ORCPT ); Thu, 20 Jun 2019 23:51:25 -0400 Received: from localhost.localdomain (p14092-ipngnfx01kyoto.kyoto.ocn.ne.jp [153.142.97.92]) (authenticated) by conuserg-08.nifty.com with ESMTP id x5L3oRjU014254; Fri, 21 Jun 2019 12:50:27 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conuserg-08.nifty.com x5L3oRjU014254 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1561089028; bh=Bg7yz3kGp5oc02/SzDEjzmVnjSSRFRG856VaDIqk91k=; h=From:To:Cc:Subject:Date:From; b=p0fbb/jsPohS5rptPzipnLIlvOWQM8tXMhDLb7YHN2+8Yor8zp2pNffgMTKrNuzg0 QysWHlt/6pjrwXVhsBAhyOVdhZvMg3OH4nrvyboQN1ZiHKr9gb2pCbqfnUGFzT92eE FFz992l2m4GUK7HCud4x0sErnUpPaaTrP9b/dLpKz090TLQ/+lMlx1qz9fhelpRMIE 5DoOKUT90RO97+qkUUd3LBeen4gekxXCdOLu6GJNwkOwosDqCmhLaSA3LvGI/QnkGr rdl90Lr0E8Dwt7NTzrz64W4QLWR07xIW1zT1dSAAjF/XFfHkldkyZCDClgUUn6Vlz8 Vjuh584X4d2Hw== X-Nifty-SrcIP: [153.142.97.92] From: Masahiro Yamada To: linux-mmc@vger.kernel.org, Ulf Hansson , Rob Herring Cc: Wolfram Sang , linux-renesas-soc@vger.kernel.org, Masahiro Yamada , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Mark Rutland Subject: [PATCH] dt-binding: mmc: rename tmio_mmc.txt to renesas_sdhi.txt Date: Fri, 21 Jun 2019 12:50:10 +0900 Message-Id: <20190621035010.13884-1-yamada.masahiro@socionext.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As commit b6147490e6aa ("mmc: tmio: split core functionality, DMA and MFD glue") said, these MMC controllers use the IP from Panasonic. TMIO (Toshiba Mobile IO) MMC was the first upstreamed user of this IP. The common driver code was split and expanded as 'tmio-mmc-core', then it become historical misnomer since 'tmio' is not the name of this IP in the first place. In the discussion [1], we decide to keep calling these MMC variants 'TMIO MMC' at least in Linux driver level because renaming all of them is a big churn. However, DT should not be oriented to a particular project even though it is developed in Linux communities. Let's stop exporting this unfortunate things to other projects, where there is no good reason to call this "TMIO". Rename the file to renesas_sdhi.txt. In fact, all the information in this file is specific to the Renesas platform. This commit also removes the first paragraph entirely. The DT-binding should describe the hardware. It is really strange to talk about Linux driver internals such as how the drivers are probed, how platform data are handed off, etc. [1] https://www.spinics.net/lists/linux-mmc/msg46952.html Signed-off-by: Masahiro Yamada --- I sent this before, but it was dismissed somehow. I am resending this. .../bindings/mmc/{tmio_mmc.txt => renesas_sdhi.txt} | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) rename Documentation/devicetree/bindings/mmc/{tmio_mmc.txt => renesas_sdhi.txt} (87%) diff --git a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt b/Documentation/devicetree/bindings/mmc/renesas_sdhi.txt similarity index 87% rename from Documentation/devicetree/bindings/mmc/tmio_mmc.txt rename to Documentation/devicetree/bindings/mmc/renesas_sdhi.txt index 2b4f17ca9087..dd08d038a65c 100644 --- a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt +++ b/Documentation/devicetree/bindings/mmc/renesas_sdhi.txt @@ -1,13 +1,4 @@ -* Toshiba Mobile IO SD/MMC controller - -The tmio-mmc driver doesn't probe its devices actively, instead its binding to -devices is managed by either MFD drivers or by the sh_mobile_sdhi platform -driver. Those drivers supply the tmio-mmc driver with platform data, that either -describe hardware capabilities, known to them, or are obtained by them from -their own platform data or from their DT information. In the latter case all -compulsory and any optional properties, common to all SD/MMC drivers, as -described in mmc.txt, can be used. Additionally the following tmio_mmc-specific -optional bindings can be used. +* Renesas SDHI SD/MMC controller Required properties: - compatible: should contain one or more of the following: -- 2.17.1