devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: bcousson@baylibre.com, tony@atomide.com
Cc: balbi@ti.com, lee.jones@linaro.org, arnd@arndb.de,
	sre@debian.org, mark.rutland@arm.com,
	m.paolino@virtualopensystems.com, linux-omap@vger.kernel.org,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Roger Quadros <rogerq@ti.com>
Subject: [PATCH v6 06/10] ARM: dts: omap4: Update omap-usb-host node
Date: Mon, 20 Jan 2014 16:11:27 +0200	[thread overview]
Message-ID: <1390227091-4523-7-git-send-email-rogerq@ti.com> (raw)
In-Reply-To: <1390227091-4523-1-git-send-email-rogerq@ti.com>

The omap-usb-host driver expects a certain name for internal
and external reference clocks. Provide these clocks.

Signed-off-by: Roger Quadros <rogerq@ti.com>
---
 arch/arm/boot/dts/omap4.dtsi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index d3f8a6e..39a05ce 100644
--- a/arch/arm/boot/dts/omap4.dtsi
+++ b/arch/arm/boot/dts/omap4.dtsi
@@ -697,6 +697,12 @@
 			#address-cells = <1>;
 			#size-cells = <1>;
 			ranges;
+			clocks = <&init_60m_fclk>,
+				 <&xclk60mhsp1_ck>,
+				 <&xclk60mhsp2_ck>;
+			clock-names = "refclk_60m_int",
+				      "refclk_60m_ext_p1",
+				      "refclk_60m_ext_p2";
 
 			usbhsohci: ohci@4a064800 {
 				compatible = "ti,ohci-omap3", "usb-ohci";
-- 
1.8.3.2

  parent reply	other threads:[~2014-01-20 14:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 14:11 [PATCH v6 00/10] USB Host support for OMAP5 uEVM (for 3.14) Roger Quadros
2014-01-20 14:11 ` [PATCH v6 02/10] mfd: omap-usb-host: Get clocks based on hardware revision Roger Quadros
2014-01-20 14:11 ` [PATCH v6 03/10] mfd: omap-usb-host: Use clock names as per function for reference clocks Roger Quadros
2014-01-20 14:11 ` [PATCH v6 04/10] mfd: omap-usb-host: Update DT clock binding information Roger Quadros
     [not found] ` <1390227091-4523-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2014-01-20 14:11   ` [PATCH v6 01/10] mfd: omap-usb-host: Use resource managed clk_get() Roger Quadros
2014-01-20 14:11   ` [PATCH v6 05/10] mfd: omap-usb-tll: Update DT clock binding information Roger Quadros
2014-01-20 14:11 ` Roger Quadros [this message]
2014-01-20 14:11 ` [PATCH v6 07/10] ARM: dts: omap5: Update omap-usb-host node Roger Quadros
2014-01-20 14:11 ` [PATCH v6 08/10] ARM: dts: omap4-panda: Provide USB PHY clock Roger Quadros
2014-01-20 14:11 ` [PATCH v6 09/10] ARM: dts: omap5-uevm: " Roger Quadros
2014-01-20 14:11 ` [PATCH v6 10/10] ARM: OMAP2+: Remove legacy_init_ehci_clk() Roger Quadros
2014-01-21 17:19 ` [PATCH v6 00/10] USB Host support for OMAP5 uEVM (for 3.14) Lee Jones

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=1390227091-4523-7-git-send-email-rogerq@ti.com \
    --to=rogerq@ti.com \
    --cc=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.paolino@virtualopensystems.com \
    --cc=mark.rutland@arm.com \
    --cc=sre@debian.org \
    --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).