public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	Greg KH <greg@kroah.com>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Handling devices that don't have a bus
Date: Sat, 1 Apr 2006 09:32:54 -0800	[thread overview]
Message-ID: <200604010932.55104.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0604011128020.17557-100000@netrider.rowland.org>

On Saturday 01 April 2006 8:46 am, Alan Stern wrote:

> I think you have misunderstood my point.  Yes, devices are part of the
> platform bus only if they explicitly want to be.  My point was that even
> though they _do_ want to be on the platform bus, 

I'm not clear on why it would want to be on the platform bus;
what would its inner platform-ness consist of?

There really isn't a "bus" that makes much sense for such a
singleton device to sit on.  


> in this situation they 
> _can't_ because they are forced to register a struct device, not a struct
> platform_device.  The choice is not up to the driver; it is determined by
> the USB Gadget framework. 


  parent reply	other threads:[~2006-04-01 17:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 20:45 Handling devices that don't have a bus Alan Stern
2006-03-30 21:28 ` David Brownell
2006-03-30 22:26 ` Greg KH
2006-04-01  9:38   ` Russell King
2006-04-01  9:47 ` Russell King
2006-04-01 16:46   ` Alan Stern
2006-04-01 17:12     ` Russell King
2006-04-01 17:32     ` David Brownell [this message]
2006-04-01 20:14       ` Alan Stern

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=200604010932.55104.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=stern@rowland.harvard.edu \
    /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