devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavan Kondeti <pkondeti@codeaurora.org>
To: Greg KH <greg@kroah.com>
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:21:00 +0530	[thread overview]
Message-ID: <4EB42604.3030701@codeaurora.org> (raw)
In-Reply-To: <20111104154356.GA30439@kroah.com>

Hi Greg,

On 11/4/2011 9:13 PM, Greg KH wrote:
> On Fri, Nov 04, 2011 at 01:55:09PM +0530, Pavan Kondeti 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.
> 
> Why do you need to name the speed of the device and the host?  That
> doesn't really matter if you plug a low-speed device into that super
> speed host controller, right?
> 

Right :-)

> I'm not familiar with device tree naming conventions, but is this
> something you do for network devices?  If not, I'd not recommend it for
> USB controllers either.
> 

I am also not sure about the label names. The reason I would like to
have them in device tree source file is just for readability. One can
easily correlates the device node properties with the label. Say if I
want to change the IRQ number or some property value of 1st instance
HSUSB device controller (while porting a different board), I look for
hsusb0-device.

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.

  parent reply	other threads:[~2011-11-04 17:51 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 [this message]
2011-11-04 16:45   ` Grant Likely
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=4EB42604.3030701@codeaurora.org \
    --to=pkondeti@codeaurora.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=greg@kroah.com \
    --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 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).