From: Greg KH <greg@kroah.com>
To: Simon White <sidplay2@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multiple virtual bus instances
Date: Wed, 7 Feb 2007 21:54:52 -0800 [thread overview]
Message-ID: <20070208055452.GB13270@kroah.com> (raw)
In-Reply-To: <883291.79449.qm@web52902.mail.yahoo.com>
On Wed, Feb 07, 2007 at 02:15:08PM -0800, Simon White wrote:
> Hi,
>
> I've been working through trying to create a virtual
> bus.
How does this differ from a "real" bus?
> I've successfuly made it work for a single instance but wanted to
> confirm how to create multiple instances of the virtual bus.
Why would you need that?
> I believe to do this you have only one instance of your new
> bus_type registered but register multiple instances of struct device
> for it. I just wanted to confirm that was correct.
That would create multiple devices on the same bus. Is that what you
need to do?
> Lastly how do you walk over all devices on a bus
> instance?
You usually do this in your bus-specific code somehow.
> I note bus_for_each_dev but that appears to take a bus_type rather
> than struct device instance, hence I assume it will return all devices
> from all instances.
No, it will walk the bus that you created. If you need multiple busses,
create multiple 'struct bus_type' structures.
> I know I could compare each device to see if it is on a certain bus
> instance but wondered if there was a better way?
I think you will find that it works the way it is described.
Might I ask what you are trying to do with these multiple busses?
Note that you can have multiple trees of devices, all with the same
bus_type, yet not joined together in any other way. Odds are, you
probably want to do that, right?
thanks,
greg k-h
next prev parent reply other threads:[~2007-02-08 5:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 22:15 Multiple virtual bus instances Simon White
2007-02-08 5:54 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-08 9:23 Simon White
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=20070208055452.GB13270@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sidplay2@yahoo.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