From patchwork Thu Jul 26 03:28:56 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Masahiro Yamada X-Patchwork-Id: 10545159 X-Patchwork-Delegate: geert@linux-m68k.org Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id F0F6714E0 for ; Thu, 26 Jul 2018 03:42:13 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id D91922A82E for ; Thu, 26 Jul 2018 03:42:13 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id CC0442ACA1; Thu, 26 Jul 2018 03:42:13 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.9 required=2.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=unavailable version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 777762A82E for ; Thu, 26 Jul 2018 03:42:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726292AbeGZE46 (ORCPT ); Thu, 26 Jul 2018 00:56:58 -0400 Received: from condef-08.nifty.com ([202.248.20.73]:53845 "EHLO condef-08.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725973AbeGZE45 (ORCPT ); Thu, 26 Jul 2018 00:56:57 -0400 X-Greylist: delayed 394 seconds by postgrey-1.27 at vger.kernel.org; Thu, 26 Jul 2018 00:56:55 EDT Received: from conuserg-08.nifty.com ([10.126.8.71])by condef-08.nifty.com with ESMTP id w6Q3Vn8n032169 for ; Thu, 26 Jul 2018 12:31:49 +0900 Received: from pug.e01.socionext.com (p14092-ipngnfx01kyoto.kyoto.ocn.ne.jp [153.142.97.92]) (authenticated) by conuserg-08.nifty.com with ESMTP id w6Q3Ukma012011; Thu, 26 Jul 2018 12:30:48 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conuserg-08.nifty.com w6Q3Ukma012011 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1532575848; bh=EEqpSaOIiLKXtDgT7Y6aO0wGsVqAQ/kQYtQDKX5JCJE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=dTub7q4piXnDxzVAC5TN+ptpnjKkoqYRKMYhdrTcKJj35RqeX8FA93JGZtgMzxhi1 SdNcbMOsclTeH7Su/Z3GOsZyCTiN1sd/FC/6eWAblMYrLnxstXwSkKlJvFVh3Qn725 pGDCnMPdrZ2l9X+rgflDtuTMdWmnZWcMzEoyn1jblqqZiBtfYMB13KZsiTQoCmgHs0 oVsH3+tVZqTnM80wXbikFZCHqlvbwuusYzw4wDy6DVcQUfsLfGnuSAKzsuXgguK+nv bVsOQ0GyisPHuaT1YYpLm+8BuTgPeBw7vih1HwcBJ5TTwTpV2bhdoK5xtzGwhTwJQU 4Lz4TABXT5D8w== X-Nifty-SrcIP: [153.142.97.92] From: Masahiro Yamada To: Wolfram Sang , linux-mmc@vger.kernel.org, Ulf Hansson , Rob Herring Cc: devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Masahiro Yamada Subject: [PATCH 2/2] dt-binding: mmc: rename tmio_mmc.txt to renesas_sdhi.txt Date: Thu, 26 Jul 2018 12:28:56 +0900 Message-Id: <1532575736-20138-3-git-send-email-yamada.masahiro@socionext.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1532575736-20138-1-git-send-email-yamada.masahiro@socionext.com> References: <1532575736-20138-1-git-send-email-yamada.masahiro@socionext.com> Sender: linux-renesas-soc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-renesas-soc@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP 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 discussion [1], we decide to continue calling these variants 'TMIO MMC' at least in Linux driver level, but let's stop exposing this unfortunate things to other projects. DT should not be oriented to a particular project even though it is developed in Linux communities. Also, remove the first paragraph, "The tmio-mmc driver doesn't probe..." entirely. The DT-binding should describe the hardware. It is wrong 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 --- .../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} (86%) diff --git a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt b/Documentation/devicetree/bindings/mmc/renesas_sdhi.txt similarity index 86% rename from Documentation/devicetree/bindings/mmc/tmio_mmc.txt rename to Documentation/devicetree/bindings/mmc/renesas_sdhi.txt index 839f469..a27e091 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: