From: Patrick Pannuto <ppannuto@quicinc.com>
To: Greg KH <gregkh@suse.de>
Cc: Patrick Pannuto <ppannuto@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"damm@opensource.se" <damm@opensource.se>,
"lethal@linux-sh.org" <lethal@linux-sh.org>,
"rjw@sisk.pl" <rjw@sisk.pl>, "dtor@mail.ru" <dtor@mail.ru>,
"eric.y.miao@gmail.com" <eric.y.miao@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH] platform: Faciliatate the creation of pseduo-platform busses
Date: Tue, 3 Aug 2010 17:17:58 -0700 [thread overview]
Message-ID: <4C58B1B6.9050005@quicinc.com> (raw)
In-Reply-To: <20100804000945.GA19729@suse.de>
>>>>
>>>> struct platform_device sub_bus1 = {
>>>> .name = "sub_bus1",
>>>> .id = -1,
>>>> .dev.bus = &my_bus_type,
>>>> }
>>>> EXPORT_SYMBOL_GPL(sub_bus1);
>>>
>>> You really want a bus hanging off of a bus? Normally you need a device
>>> to do that, which is what I think you have here, but the naming is a bit
>>> odd to me.
>>>
>>> What would you do with this "sub bus"? It's just a device, but you are
>>> wanting it to be around for something.
>>>
>>
>> It's for power management stuff, basically, there are actual physical buses
>> involved that can be completely powered off IFF all of their devices are
>> not in use. Plus it actually matches bus topology this way.
>
> Then create a real bus hanging off of a device, not another device that
> "acts" like a bus here, right? Or am I missing the point?
>
The motivation for doing it this was is that one driver could drive
devices on two different subbusses. In the example, "my-driver" could
drive a device on sub_bus1 AND sub_bus2 (if there were 2+ devices, one
or more on each bus).
>From my understanding, this is not possible if they are actually
different busses.
next prev parent reply other threads:[~2010-08-04 0:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 23:35 [RFC PATCH] platform: Faciliatate the creation of pseduo-platform busses Patrick Pannuto
2010-08-03 23:36 ` Patrick Pannuto
2010-08-03 23:56 ` Greg KH
2010-08-04 0:02 ` Patrick Pannuto
2010-08-04 0:09 ` Greg KH
2010-08-04 0:17 ` Patrick Pannuto [this message]
2010-08-04 0:41 ` Timothy Meade
2010-08-05 22:59 ` Grant Likely
2010-08-06 14:27 ` Greg KH
2010-08-06 15:12 ` Grant Likely
2010-08-06 23:46 ` Greg KH
2010-08-07 6:35 ` Grant Likely
2010-08-07 17:28 ` Grant Likely
2010-08-10 23:53 ` Greg KH
2010-08-05 23:00 ` Grant Likely
2010-08-04 9:37 ` Alan Cox
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=4C58B1B6.9050005@quicinc.com \
--to=ppannuto@quicinc.com \
--cc=damm@opensource.se \
--cc=dtor@mail.ru \
--cc=eric.y.miao@gmail.com \
--cc=gregkh@suse.de \
--cc=lethal@linux-sh.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ppannuto@codeaurora.org \
--cc=rjw@sisk.pl \
/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