From patchwork Tue Feb 28 18:07:47 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Simon Glass X-Patchwork-Id: 143525 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 88609B6FA2 for ; Wed, 29 Feb 2012 05:09:47 +1100 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756958Ab2B1SJa (ORCPT ); Tue, 28 Feb 2012 13:09:30 -0500 Received: from mail-wi0-f202.google.com ([209.85.212.202]:54236 "EHLO mail-wi0-f202.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965802Ab2B1SJX (ORCPT ); Tue, 28 Feb 2012 13:09:23 -0500 X-Greylist: delayed 76560 seconds by postgrey-1.27 at vger.kernel.org; Tue, 28 Feb 2012 13:09:23 EST Received: by wibhm11 with SMTP id hm11so110998wib.1 for ; Tue, 28 Feb 2012 10:09:22 -0800 (PST) Received-SPF: pass (google.com: domain of sjg@google.com designates 10.14.127.10 as permitted sender) client-ip=10.14.127.10; Authentication-Results: mr.google.com; spf=pass (google.com: domain of sjg@google.com designates 10.14.127.10 as permitted sender) smtp.mail=sjg@google.com Received: from mr.google.com ([10.14.127.10]) by 10.14.127.10 with SMTP id c10mr3534423eei.2.1330452562604 (num_hops = 1); Tue, 28 Feb 2012 10:09:22 -0800 (PST) Received: by 10.14.127.10 with SMTP id c10mr3082826eei.2.1330452562565; Tue, 28 Feb 2012 10:09:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.127.10 with SMTP id c10mr3082799eei.2.1330452562430; Tue, 28 Feb 2012 10:09:22 -0800 (PST) Received: from hpza10.eem.corp.google.com ([74.125.121.33]) by gmr-mx.google.com with ESMTPS id s3si14123716eem.3.2012.02.28.10.09.22 (version=TLSv1/SSLv3 cipher=AES128-SHA); Tue, 28 Feb 2012 10:09:22 -0800 (PST) Received: from sglass.mtv.corp.google.com (sglass.mtv.corp.google.com [172.22.72.144]) by hpza10.eem.corp.google.com (Postfix) with ESMTP id 3DEC820004E; Tue, 28 Feb 2012 10:09:22 -0800 (PST) Received: by sglass.mtv.corp.google.com (Postfix, from userid 121222) id 80B9D14094B; Tue, 28 Feb 2012 10:09:21 -0800 (PST) From: Simon Glass To: U-Boot Mailing List Cc: Tom Warren , Stephen Warren , Simon Glass , linux-tegra@vger.kernel.org, Jerry Van Baren , Devicetree Discuss Subject: [PATCH v7 09/20] tegra: fdt: Add additional USB binding Date: Tue, 28 Feb 2012 10:07:47 -0800 Message-Id: <1330452478-5039-10-git-send-email-sjg@chromium.org> X-Mailer: git-send-email 1.7.7.3 X-Gm-Message-State: ALoCoQl9sGlX3mCv3Pj0rk0CVddTurLT33ja0izSYBHcZm38xKeo12uNgLXnpMDDydCiiS6Gn3BIEKQLe+iAu95+kgQiM8ZSDrmuLxJesBSur03nxgUofxSdRrRE/jQtSyLLeFQVbsn0uaqn7Rv0QuC7TwIhJ6TtLHGXKx+5vuhGojnLsmaBzwI= Sender: linux-tegra-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-tegra@vger.kernel.org This adds a property to indicate a port which can switch between host and device mode. Signed-off-by: Simon Glass Acked-by: Stephen Warren --- Changes in v5: - Add dr_mode property to control host/device/otg mode - Add nvidia,has-legacy-mode property per review comments Changes in v7: - Fix space indent nit doc/device-tree-bindings/usb/tegra-usb.txt | 12 ++++++++++++ 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/doc/device-tree-bindings/usb/tegra-usb.txt b/doc/device-tree-bindings/usb/tegra-usb.txt index 035d63d..5282d44 100644 --- a/doc/device-tree-bindings/usb/tegra-usb.txt +++ b/doc/device-tree-bindings/usb/tegra-usb.txt @@ -11,3 +11,15 @@ Required properties : - phy_type : Should be one of "ulpi" or "utmi". - nvidia,vbus-gpio : If present, specifies a gpio that needs to be activated for the bus to be powered. + +Optional properties: + - dr_mode : dual role mode. Indicates the working mode for + nvidia,tegra20-ehci compatible controllers. Can be "host", "peripheral", + or "otg". Default to "host" if not defined for backward compatibility. + host means this is a host controller + peripheral means it is device controller + otg means it can operate as either ("on the go") + - nvidia,has-legacy-mode : boolean indicates whether this controller can + operate in legacy mode (as APX 2500 / 2600). In legacy mode some + registers are accessed through the APB_MISC base address instead of + the USB controller.