From: Jingoo Han <jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: 'Doug Anderson'
<dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
'Kukjin Kim' <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
'Jingoo Han' <jg1.han-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
'Rob Herring'
<rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
'Vivek Gautam'
<gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] usb: Document clocks in samsung,exynos4210-ehci/ohci bindings
Date: Fri, 15 Mar 2013 10:30:40 +0900 [thread overview]
Message-ID: <005c01ce211c$b45da540$1d18efc0$%han@samsung.com> (raw)
In-Reply-To: <1363302046-31684-1-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
On Friday, March 15, 2013 8:01 AM, Doug Anderson wrote:
>
> The exynox4210-ehci and exynos4210-ohci nodes need a clock specified
> using the common clock framework. Document it.
>
> Signed-off-by: Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> ---
> Documentation/devicetree/bindings/usb/exynos-usb.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/exynos-usb.txt
> b/Documentation/devicetree/bindings/usb/exynos-usb.txt
> index f66fcdd..d557cf7 100644
> --- a/Documentation/devicetree/bindings/usb/exynos-usb.txt
> +++ b/Documentation/devicetree/bindings/usb/exynos-usb.txt
> @@ -10,6 +10,8 @@ Required properties:
> - reg: physical base address of the controller and length of memory mapped
> region.
> - interrupts: interrupt number to the cpu.
> + - clocks: from common clock binding: handle to adc clock.
^^^
Is it right? I think that 'adc' can be changed to 'usb host'.
Best regards,
Jingoo Han
> + - clock-names: from common clock binding: Shall be "usbhost".
>
> Optional properties:
> - samsung,vbus-gpio: if present, specifies the GPIO that
> @@ -22,6 +24,9 @@ Example:
> reg = <0x12110000 0x100>;
> interrupts = <0 71 0>;
> samsung,vbus-gpio = <&gpx2 6 1 3 3>;
> +
> + clocks = <&clock 285>;
> + clock-names = "usbhost";
> };
next prev parent reply other threads:[~2013-03-15 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 23:00 [PATCH] usb: Document clocks in samsung,exynos4210-ehci/ohci bindings Doug Anderson
[not found] ` <1363302046-31684-1-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2013-03-15 1:30 ` Jingoo Han [this message]
2013-03-15 2:58 ` [PATCH v2] usb: Document clocks in samsung, exynos4210-ehci/ohci bindings Doug Anderson
2013-03-15 3:06 ` [PATCH v2] usb: Document clocks in samsung,exynos4210-ehci/ohci bindings Jingoo Han
2013-04-04 6:12 ` Kukjin Kim
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='005c01ce211c$b45da540$1d18efc0$%han@samsung.com' \
--to=jg1.han-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
/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).