Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp335431ybi; Fri, 21 Jun 2019 00:10:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqy9wz5cMdeImF8qIkUMVf4pFLM1ioIsxYdJQD7wXildJiH3UH5kNEb3mOcpGIkqYj7pXVQR X-Received: by 2002:a17:902:290b:: with SMTP id g11mr127237151plb.26.1561101031297; Fri, 21 Jun 2019 00:10:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561101031; cv=none; d=google.com; s=arc-20160816; b=DLcYwXansruKSIXzSkrIxkI3Lknxb1EG7faqyVt73F2hn9t77nkMdSkqEFrUEvEUfG H2RGMB5iij+f+COdVYzEvdrlJkr6oGZC+wkNdJUruR2GEkcwtJXsstbR2T1n35RbsXmg NXAiKu6/zXvJhKzj0Mz+vg0AetKhLOVNKdu6SAD23/w6BaXwjPktl8aueqnRknNulXb5 kWZzLV62KTrvvBCjn0SDMWTFMKR40Jx+J7GJK3yzSSm3zt3af2gv+A9qjVfMwvbzgZPQ ZuKjiqvn4zTgnL0Pb7HcAfjWu5xNJV1AR5h2yWHm2sEgPxGkNimWieScu2CMytb2jdi4 j/1w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organisation:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ZhlQg2rK7VKBX7Wcu/Vh7OZjwJb1vQaEFh9tgNVnaXY=; b=d44aEPWVe6UB5JCZjxHKW7H4Tyqze7LQU2mtbB4s5mURpOqUDrZEjjr1EuppsI+Yqi WTGYvNRrkk0RnYDtnAu8YJNxh7hFQFUo7eYXAgH4HYmbr3LGj1yVxiUfWQTevuDaJ695 JRpx65k07d785l+UYVHZLfeKwojZLOoPbe1c2SMvJ6Z2merwzPQGD7lm+EW9dVi4B9qL YvwpIjFThlfZQRkCKQS3k19MDB/3kOWfVVwk9C4DbGIKyTbkBq7R6+PpzIG0Bc6flCqB h0W/kfpDqq6kpBZJJ4K6Sv+VDVdkLVBgnJDJWbc5KcELilddVMk9oLWFHRuYszaHonv4 xkug== ARC-Authentication-Results: i=1; mx.google.com; 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 d62si1774515pga.447.2019.06.21.00.10.16; Fri, 21 Jun 2019 00:10:31 -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; 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 S1726200AbfFUHIz (ORCPT + 99 others); Fri, 21 Jun 2019 03:08:55 -0400 Received: from kirsty.vergenet.net ([202.4.237.240]:55706 "EHLO kirsty.vergenet.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726008AbfFUHIy (ORCPT ); Fri, 21 Jun 2019 03:08:54 -0400 Received: from reginn.horms.nl (watermunt.horms.nl [80.127.179.77]) by kirsty.vergenet.net (Postfix) with ESMTPA id 0FC9025AE8A; Fri, 21 Jun 2019 17:08:52 +1000 (AEST) Received: by reginn.horms.nl (Postfix, from userid 7100) id 121309408C4; Fri, 21 Jun 2019 09:08:50 +0200 (CEST) Date: Fri, 21 Jun 2019 09:08:50 +0200 From: Simon Horman To: Masahiro Yamada Cc: linux-mmc@vger.kernel.org, Ulf Hansson , Rob Herring , Wolfram Sang , linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Mark Rutland Subject: Re: [PATCH] dt-binding: mmc: rename tmio_mmc.txt to renesas_sdhi.txt Message-ID: <20190621070849.7efe5qihb3zxgjse@verge.net.au> References: <20190621035010.13884-1-yamada.masahiro@socionext.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190621035010.13884-1-yamada.masahiro@socionext.com> Organisation: Horms Solutions BV User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 21, 2019 at 12:50:10PM +0900, Masahiro Yamada wrote: > 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. Hi Yamada-san, I for one am fine with this change. My minor nit is that I think that renesas,sdhi.txt would be a slightly better filename in terms of consistency with other renesas bindings documentation filenames. > > > .../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 >