From: Mark Rutland <mark.rutland@arm.com>
To: Roger Quadros <rogerq@ti.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"tony@atomide.com" <tony@atomide.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"balbi@ti.com" <balbi@ti.com>,
"bcousson@baylibre.com" <bcousson@baylibre.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 1/5] mfd: omap-usb-host: Update DT clock binding information
Date: Wed, 8 Jan 2014 09:56:52 +0000 [thread overview]
Message-ID: <20140108095652.GD6701@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1389161742-10533-2-git-send-email-rogerq@ti.com>
On Wed, Jan 08, 2014 at 06:15:38AM +0000, Roger Quadros wrote:
> The omap-usb-host driver expects the 60MHz functional clock
> of the USB host module to be named as "init_60m_fclk".
> Add this information in the DT binding document.
>
> CC: Lee Jones <lee.jones@linaro.org>
> CC: Samuel Ortiz <sameo@linux.intel.com>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> ---
> Documentation/devicetree/bindings/mfd/omap-usb-host.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/omap-usb-host.txt b/Documentation/devicetree/bindings/mfd/omap-usb-host.txt
> index b381fa6..5635202 100644
> --- a/Documentation/devicetree/bindings/mfd/omap-usb-host.txt
> +++ b/Documentation/devicetree/bindings/mfd/omap-usb-host.txt
> @@ -32,6 +32,10 @@ Optional properties:
> - single-ulpi-bypass: Must be present if the controller contains a single
> ULPI bypass control bit. e.g. OMAP3 silicon <= ES2.1
>
> +- clocks: phandle to 60MHz functional clock to the USB Host module.
> +
> +- clock-names: must be "init_60m_fclk"
> +
Nit: clocks aren't just phandles, there's a clock-specifier too.
Also, it would be nicer if clocks was defined in terms of clock-names,
as it makes the relationship between clocks and clock-names clear, and
makes it easier to extend the list in future. Something like:
- clocks: a list of phandles + clock-specifiers, one for each entry in
clock-names
- clock-names: should include:
* "init_60m_fclk" - the 60MHz functional clock to the USB host module.
Thanks,
Mark.
next prev parent reply other threads:[~2014-01-08 9:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 6:15 [PATCH v4 0/5] USB Host support for OMAP5 uEVM (for 3.14) Roger Quadros
2014-01-08 6:15 ` [PATCH v4 1/5] mfd: omap-usb-host: Update DT clock binding information Roger Quadros
2014-01-08 9:08 ` Sebastian Reichel
[not found] ` <20140108090808.GB16313-SfvFxonMDyemK9LvCR3Hrw@public.gmane.org>
2014-01-08 10:09 ` Roger Quadros
2014-01-08 10:19 ` Arnd Bergmann
2014-01-08 10:27 ` Roger Quadros
2014-01-08 10:40 ` Arnd Bergmann
2014-01-08 11:04 ` Roger Quadros
2014-01-08 10:52 ` Sebastian Reichel
2014-01-08 10:55 ` Arnd Bergmann
2014-01-08 11:11 ` Roger Quadros
2014-01-08 11:35 ` Arnd Bergmann
[not found] ` <201401081235.40927.arnd-r2nGTMty4D4@public.gmane.org>
2014-01-08 11:48 ` Roger Quadros
2014-01-08 9:56 ` Mark Rutland [this message]
2014-01-08 10:12 ` Roger Quadros
[not found] ` <1389161742-10533-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2014-01-08 6:15 ` [PATCH v4 2/5] ARM: dts: OMAP5: Add 60MHz clock reference to USB Host module Roger Quadros
2014-01-08 6:15 ` [PATCH v4 4/5] ARM: dts: omap5-uevm: Provide USB PHY clock Roger Quadros
2014-01-08 6:15 ` [PATCH v4 3/5] ARM: dts: omap4-panda: " Roger Quadros
2014-01-08 6:15 ` [PATCH v4 5/5] ARM: OMAP2+: Remove legacy_init_ehci_clk() Roger Quadros
[not found] ` <52CE824D.2090905@virtualopensystems.com>
[not found] ` <52CE824D.2090905-lrHrjnjw1UfHK3s98zE1ajGjJy/sRE9J@public.gmane.org>
2014-01-09 11:08 ` [PATCH v4 0/5] USB Host support for OMAP5 uEVM (for 3.14) Roger Quadros
2014-01-09 11:22 ` Michele Paolino
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=20140108095652.GD6701@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.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=rogerq@ti.com \
--cc=sameo@linux.intel.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).