From: Benoit Cousson <b-cousson@ti.com>
To: balbi@ti.com
Cc: Afzal Mohammed <afzal@ti.com>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
Santhapuri Damodar <damodar.santhapuri@ti.com>,
Ravi Babu <ravibabu@ti.com>, Daniel Mack <zonque@gmail.com>,
devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v2] usb: musb: dsps: dt binding - add resources, example
Date: Tue, 6 Nov 2012 17:58:57 +0100 [thread overview]
Message-ID: <509941D1.6020405@ti.com> (raw)
In-Reply-To: <20121106164445.GE3993@arwen.pp.htv.fi>
On 11/06/2012 05:44 PM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Nov 06, 2012 at 07:26:06PM +0530, Afzal Mohammed wrote:
>> OMAP2+ family of devices are now obtaining resources via DT, earlier
>> it was obtained from hwmod. Update binding document accrodingly, while
>> at it add example.
>>
>> Signed-off-by: Afzal Mohammed <afzal@ti.com>
>
> this looks fine to me:
>
> Reviewed-by: Felipe Balbi <balbi@ti.com>
>
> Benoit, do you take Documentation patches too ?
Well, ideally it should go with the driver change. But if this is a
simple change related to generic attribute I can take it.
Regards,
Benoit
>
>> ---
>>
>> v2: node name changed to "usb"
>>
>> .../devicetree/bindings/usb/am33xx-usb.txt | 21 +++++++++++++++++++++
>> 1 file changed, 21 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/usb/am33xx-usb.txt b/Documentation/devicetree/bindings/usb/am33xx-usb.txt
>> index a922505..ea840f7 100644
>> --- a/Documentation/devicetree/bindings/usb/am33xx-usb.txt
>> +++ b/Documentation/devicetree/bindings/usb/am33xx-usb.txt
>> @@ -1,5 +1,7 @@
>> AM33XX MUSB GLUE
>> - compatible : Should be "ti,musb-am33xx"
>> + - reg : offset and length of register sets, first usbss, then for musb instances
>> + - interrupts : usbss, musb instance interrupts in order
>> - ti,hwmods : must be "usb_otg_hs"
>> - multipoint : Should be "1" indicating the musb controller supports
>> multipoint. This is a MUSB configuration-specific setting.
>> @@ -12,3 +14,22 @@ AM33XX MUSB GLUE
>> represents PERIPHERAL.
>> - power : Should be "250". This signifies the controller can supply upto
>> 500mA when operating in host mode.
>> +
>> +Example:
>> +
>> +usb@47400000 {
>> + compatible = "ti,musb-am33xx";
>> + reg = <0x47400000 0x1000 /* usbss */
>> + 0x47401000 0x800 /* musb instance 0 */
>> + 0x47401800 0x800>; /* musb instance 1 */
>> + interrupts = <17 /* usbss */
>> + 18 /* musb instance 0 */
>> + 19>; /* musb instance 1 */
>> + multipoint = <1>;
>> + num-eps = <16>;
>> + ram-bits = <12>;
>> + port0-mode = <3>;
>> + port1-mode = <3>;
>> + power = <250>;
>> + ti,hwmods = "usb_otg_hs";
>> +};
>> --
>> 1.7.12
>>
>
next prev parent reply other threads:[~2012-11-06 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 13:56 [PATCH v2] usb: musb: dsps: dt binding - add resources, example Afzal Mohammed
[not found] ` <1352210166-7253-1-git-send-email-afzal-l0cyMroinI0@public.gmane.org>
2012-11-06 16:44 ` Felipe Balbi
2012-11-06 16:58 ` Benoit Cousson [this message]
2012-11-06 18:22 ` Felipe Balbi
2012-11-07 11:03 ` Benoit Cousson
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=509941D1.6020405@ti.com \
--to=b-cousson@ti.com \
--cc=afzal@ti.com \
--cc=balbi@ti.com \
--cc=damodar.santhapuri@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ravibabu@ti.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=zonque@gmail.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