From: Pavan Kondeti <pkondeti@codeaurora.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss@lists.ozlabs.org,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: USB support for device tree
Date: Fri, 04 Nov 2011 23:16:05 +0530 [thread overview]
Message-ID: <4EB424DD.4090609@codeaurora.org> (raw)
In-Reply-To: <CACxGe6vMCHdB+J8hX1EPW3m35UaKC-FAZULUA4G11J0FUK6tNQ@mail.gmail.com>
Hi
On 11/4/2011 10:15 PM, Grant Likely wrote:
> On Fri, Nov 4, 2011 at 4:25 AM, Pavan Kondeti <pkondeti@codeaurora.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.
>
In our case OTG, gadget and host controllers are part of a single core
i.e they all share the same register address space.
If I use usb@addr for OTG controller, then host and OTG device node
names becomes same. Is that okay? Can two devices have the same device
node name in device tree source file?
> The label names (hsusb*-host, hsusb*-device) are completely irrelevant
> since Linux never sees them. Use whatever you want for the label
> names.
>
Is it a good practice to give label names? I thought, it improves a bit
readability of device tree source file.
> Also, the form of the node name is: "usb@a6000000" (without '0x' in
> the address).
>
Thanks for the correction.
Thanks,
Pavan
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-11-04 17:46 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
2011-11-04 17:46 ` Pavan Kondeti [this message]
[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=4EB424DD.4090609@codeaurora.org \
--to=pkondeti@codeaurora.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.