From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Pavan Kondeti <pkondeti-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: USB support for device tree
Date: Fri, 4 Nov 2011 12:45:04 -0400 [thread overview]
Message-ID: <CACxGe6vMCHdB+J8hX1EPW3m35UaKC-FAZULUA4G11J0FUK6tNQ@mail.gmail.com> (raw)
In-Reply-To: <4EB3A165.8060300-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
On Fri, Nov 4, 2011 at 4:25 AM, Pavan Kondeti <pkondeti-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> wrote:
> Hi
>
> I am working on adding USB device tree support for MSM platform. One of
> our chip set has 2 hsusb cores. The first core is configured as otg and
> the other core is configured in host only mode (EHCI compliant). Are the
> below device node names Okay? Please suggest.
>
> hsusb0-otg: usb@0xa6000000 {
> compatible = "qcom,hsusb-otg";
> ---
> };
>
> hsusb0-device: usb@0xa6000000 {
> compatible = "qcom,hsusb-device";
> ---
> };
>
> hsusb0-host: usb@0xa6000000 {
> compatible = "qcom,hsusb-host", "usb-ehci";
> ---
> };
>
> hsusb1-host: usb@0xa6000000 {
> compatible = "qcom,hsusb-host", "usb-ehci";
> ---
> };
>
> /* super speed support
>
> ssusb0-device: usb@0xa6000000 {
> compatible = "qcom,ssusb-device";
> };
The host controller node names as "usb@<adddr>" as you have here is
exactly right. The driver doesn't care and will only look at the
compatible list. OTG controllers can also use "usb@" as the prefix.
Controllers that are only in device mode should probably be called
something like "usb-gadget@<addr>" or similar, because "usb@" is used
for host controllers.
The label names (hsusb*-host, hsusb*-device) are completely irrelevant
since Linux never sees them. Use whatever you want for the label
names.
Also, the form of the node name is: "usb@a6000000" (without '0x' in
the address).
g.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-04 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 8:25 USB support for device tree Pavan Kondeti
[not found] ` <4EB3A165.8060300-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-11-04 15:43 ` Greg KH
2011-11-04 16:08 ` Grant Likely
2011-11-04 16:17 ` Grant Likely
2011-11-04 17:51 ` Pavan Kondeti
2011-11-04 16:45 ` Grant Likely [this message]
2011-11-04 17:46 ` Pavan Kondeti
[not found] ` <4EB424DD.4090609-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-11-04 18:12 ` Grant Likely
[not found] ` <CACxGe6sYkCSnFvybGcjrkh4cNvtjS=t6fr456be4KFDc3Gre2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-05 3:08 ` Pavan Kondeti
[not found] ` <4EB4A897.8020305-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2011-11-05 3:52 ` Grant Likely
2011-11-05 8:12 ` Pavan Kondeti
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=CACxGe6vMCHdB+J8hX1EPW3m35UaKC-FAZULUA4G11J0FUK6tNQ@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pkondeti-sgV2jX0FEOL9JmXXK+q4OQ@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).