devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: kishon@ti.com, balbi@ti.com, b-cousson@ti.com, tony@atomide.com,
	linux@arm.linux.org.uk, s-guiriec@ti.com, gg@slimlogic.co.uk,
	linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 1/6] ARM: dts: omap5: Add omap control usb data
Date: Fri, 25 Jan 2013 16:41:47 +0530	[thread overview]
Message-ID: <1359112312-6918-2-git-send-email-kishon@ti.com> (raw)
In-Reply-To: <1359112312-6918-1-git-send-email-kishon@ti.com>

Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt

Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
---
 arch/arm/boot/dts/omap5.dtsi |    8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 7a78d1b..edc7464 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/omap5.dtsi
@@ -504,5 +504,13 @@
 			hw-caps-ll-interface;
 			hw-caps-temp-alert;
 		};
+
+		omap_control_usb: omap-control-usb@4a002300 {
+			compatible = "ti,omap-control-usb";
+			reg = <0x4a002300 0x4>,
+			      <0x4a002370 0x4>;
+			reg-names = "control_dev_conf", "phy_power_usb";
+			ti,type = <2>;
+		};
 	};
 };
-- 
1.7.9.5


  reply	other threads:[~2013-01-25 11:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 11:11 [PATCH v2 0/6] ARM: dts: omap: add dt data for dwc3 Kishon Vijay Abraham I
2013-01-25 11:11 ` Kishon Vijay Abraham I [this message]
     [not found] ` <1359112312-6918-1-git-send-email-kishon-l0cyMroinI0@public.gmane.org>
2013-01-25 11:11   ` [PATCH v2 2/6] ARM: dts: omap5: Add ocp2scp data Kishon Vijay Abraham I
2013-01-25 11:11   ` [PATCH v2 3/6] ARM: dts: omap5: Add omap-usb3 and omap-usb2 dt data Kishon Vijay Abraham I
2013-01-25 12:18   ` [PATCH v2 0/6] ARM: dts: omap: add dt data for dwc3 Felipe Balbi
2013-01-25 11:11 ` [PATCH v2 4/6] ARM: dts: omap5: add dwc3 omap dt data Kishon Vijay Abraham I
2013-01-26 19:47   ` Sergei Shtylyov
2013-02-05  8:29     ` kishon
     [not found]       ` <5110C2E6.30504-l0cyMroinI0@public.gmane.org>
2013-02-05  8:38         ` Felipe Balbi
     [not found]           ` <20130205083828.GE32118-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2013-02-05  8:46             ` kishon
     [not found]               ` <5110C6EC.6050606-l0cyMroinI0@public.gmane.org>
2013-02-05  9:07                 ` Santosh Shilimkar
     [not found]                   ` <5110CBB9.5080307-l0cyMroinI0@public.gmane.org>
2013-02-05  9:46                     ` Felipe Balbi
2013-01-25 11:11 ` [PATCH v2 5/6] ARM: dts: omap5: add dwc3 core " Kishon Vijay Abraham I
2013-01-26 19:49   ` Sergei Shtylyov
2013-01-25 11:11 ` [PATCH v2 6/6] ARM: dts: palmas: update dt data for palmas-usb Kishon Vijay Abraham I

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1359112312-6918-2-git-send-email-kishon@ti.com \
    --to=kishon@ti.com \
    --cc=b-cousson@ti.com \
    --cc=balbi@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gg@slimlogic.co.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=s-guiriec@ti.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).