From patchwork Wed Jan 16 16:54:41 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Guennadi Liakhovetski X-Patchwork-Id: 1991791 Return-Path: X-Original-To: patchwork-linux-mmc@patchwork.kernel.org Delivered-To: patchwork-process-083081@patchwork2.kernel.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by patchwork2.kernel.org (Postfix) with ESMTP id 61809DF2A2 for ; Wed, 16 Jan 2013 16:55:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754310Ab3APQy7 (ORCPT ); Wed, 16 Jan 2013 11:54:59 -0500 Received: from moutng.kundenserver.de ([212.227.17.8]:60838 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757890Ab3APQyt (ORCPT ); Wed, 16 Jan 2013 11:54:49 -0500 Received: from axis700.grange (dslb-178-006-255-053.pools.arcor-ip.net [178.6.255.53]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0MdWxQ-1TaWvj3Ojk-00PZxP; Wed, 16 Jan 2013 17:54:48 +0100 Received: from 6a.grange (6a.grange [192.168.1.11]) by axis700.grange (Postfix) with ESMTPS id 4341840BB7; Wed, 16 Jan 2013 17:54:47 +0100 (CET) Received: from lyakh by 6a.grange with local (Exim 4.72) (envelope-from ) id 1TvWGE-0006mj-Uk; Wed, 16 Jan 2013 17:54:46 +0100 From: Guennadi Liakhovetski To: linux-mmc@vger.kernel.org Cc: linux-sh@vger.kernel.org, Magnus Damm Subject: [PATCH/RFC 06/11] mmc: tmio-mmc: define device-tree bindings Date: Wed, 16 Jan 2013 17:54:41 +0100 Message-Id: <1358355286-26029-7-git-send-email-g.liakhovetski@gmx.de> X-Mailer: git-send-email 1.7.2.5 In-Reply-To: <1358355286-26029-1-git-send-email-g.liakhovetski@gmx.de> References: <1358355286-26029-1-git-send-email-g.liakhovetski@gmx.de> X-Provags-ID: V02:K0:2lp/MvmMeRaSDsYMaM1zx4zPEoysNux384vgGq4glAu qkz+tzBgWEK8eaaTQ1BBVO+L08F2B7lWp2vVZqu1p2I3zvtYcB Kg9GV8seohprNZu2agLn6TbTypO1ZesEio7T5wheo5IQVtizR8 AmqU1DHhYUVzbDqRSFhQkhzUuMu7j155KsFpJ3TdV5fFAxqpiA fTO+d/wayoxJNbWdJS3Flw4WxhQC2CFHcQsTJVC2uKfTDJVMfk CdVn1WpK8T0OxQ6NaZfgaLm3DtCy61HXkV06zpf6jk/cX6CgaR rjxrYJLus9ClNFco5WVvr2QojCrpWNLb3/pjDgTYYir5owvfZD T4xSEWAJTzS7XKsoRFbHKZsbx78IqjyjO6p4eWtbwFImsn6bWz wzZHZBFhSzcjw== Sender: linux-mmc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-mmc@vger.kernel.org Define device-tree bindings for the tmio-mmc driver to be able to specify parameters, currently provided in platform data. Signed-off-by: Guennadi Liakhovetski --- Please, comment on this one, since it is defining an ABI to be kept forever;-) Documentation/devicetree/bindings/mmc/tmio_mmc.txt | 19 +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-) create mode 100644 Documentation/devicetree/bindings/mmc/tmio_mmc.txt diff --git a/Documentation/devicetree/bindings/mmc/tmio_mmc.txt b/Documentation/devicetree/bindings/mmc/tmio_mmc.txt new file mode 100644 index 0000000..dd8decd --- /dev/null +++ b/Documentation/devicetree/bindings/mmc/tmio_mmc.txt @@ -0,0 +1,19 @@ +* 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, should or can be used. Additionally the following optional +bindings can be used. They set either respective TMIO_MMC_* flags or MMC_CAP_* +capabilities. + +Optional properties: +- toshiba,mmc-wrprotect-disable : set TMIO_MMC_WRPROTECT_DISABLE flag +- toshiba,mmc-blksz-2bytes : set TMIO_MMC_BLKSZ_2BYTES +- toshiba,mmc-cap-sdio-irq : SDIO IRQ signalling should be used, if + supported by the hardware, i.e. set MMC_CAP_SDIO_IRQ if + TMIO_MMC_SDIO_IRQ is also set +- toshiba,mmc-has-idle-wait : set TMIO_MMC_HAS_IDLE_WAIT