From: David Brown <davidb@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Kenneth Heitke <kheitke@codeaurora.org>,
davidb@codeaurora.org, bryanh@codeaurora.org,
linux-arm-msm@vger.kernel.org,
Sagar Dharia <sdharia@codeaurora.org>,
rdunlap@xenotime.net, rmk+kernel@arm.linux.org.uk,
john.stultz@linaro.org, akpm@linux-foundation.org,
ohad@wizery.com, gregkh@suse.de, stefanr@s5r6.in-berlin.de,
lethal@linux-sh.org, linville@tuxdriver.com, zajec5@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] slimbus: Linux driver framework for SLIMbus.
Date: Tue, 16 Aug 2011 06:50:51 -0700 [thread overview]
Message-ID: <20110816135051.GA22227@huya.qualcomm.com> (raw)
In-Reply-To: <201108161537.28612.arnd@arndb.de>
On Tue, Aug 16, 2011 at 03:37:28PM +0200, Arnd Bergmann wrote:
> On Friday 12 August 2011, Mark Brown wrote:
> > On Thu, Aug 11, 2011 at 02:55:55PM +0200, Arnd Bergmann wrote:
> > > On Thursday 11 August 2011, Kenneth Heitke wrote:
> >
> > > > +EXPORT_SYMBOL_GPL(slim_add_device);
> >
> > > I don't think this should be exported: AFAICT, the set of slim_devices
> > > is a property of the platform, so I don't see how any other device driver
> > > would add another device.
> >
> > The platform may be comprised of multiple hardwaare modules with
> > functionality on daughtercards which can be probed at runtime. You may
> > also find someone constructing a PCI card or something with a slimbus
> > controller on it at some point.
>
> This is theoretically true, but IIRC David mentioned that the bus is
> only present on few SoCs and has since been abandoned in favor of standard
> busses for new devices.
Actually, this is a different one than the one I was mentioning at the
Linaro Connect. I believe SLIMbus is more active
http://en.wikipedia.org/wiki/SLIMbus
The other bus I was mentioning is called SSBI, which as far as I know
is only used to communicate between MSMs and certain Qualcomm
peripheral chips.
Kenneth would better be able to clarify how dynamic the SLIMbus is.
David
--
Sent by an employee 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-08-16 13:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 23:31 [RFC PATCH] slimbus: Linux driver framework for SLIMbus Kenneth Heitke
2011-08-11 12:55 ` Arnd Bergmann
2011-08-11 20:51 ` Kenneth Heitke
2011-08-12 16:46 ` Mark Brown
2011-08-16 13:37 ` Arnd Bergmann
2011-08-16 13:50 ` David Brown [this message]
2011-08-16 14:32 ` Arnd Bergmann
2011-08-16 15:40 ` Mark Brown
2011-08-16 17:13 ` Kenneth Heitke
2011-08-16 17:16 ` Kenneth Heitke
2011-08-16 17:44 ` sdharia
2011-08-16 19:49 ` Arnd Bergmann
2011-08-16 23:27 ` Kenneth Heitke
2011-08-17 0:59 ` Mark Brown
2011-08-17 1:54 ` Sagar Dharia
2011-08-17 6:32 ` Mark Brown
2011-08-17 7:09 ` Arnd Bergmann
2011-08-17 8:03 ` Mark Brown
2011-08-17 10:42 ` Arnd Bergmann
2011-08-17 13:04 ` Mark Brown
2011-08-17 13:17 ` Linus Walleij
2011-08-18 3:00 ` Mark Brown
2011-08-24 9:15 ` Linus Walleij
2011-08-24 9:21 ` Mark Brown
2011-08-25 7:10 ` Linus Walleij
2011-08-25 9:44 ` Mark Brown
2011-08-17 14:00 ` Arnd Bergmann
2011-08-19 3:24 ` Mark Brown
2011-08-21 22:10 ` Sagar Dharia
2011-08-22 13:47 ` Arnd Bergmann
2011-08-16 15:23 ` Mark Brown
2011-08-14 14:34 ` Mark Brown
2011-08-15 17:55 ` Kenneth Heitke
2011-08-15 19:37 ` Russell King
2011-08-15 20:12 ` Kenneth Heitke
2011-08-16 19:33 ` Jean Delvare
2011-08-17 13:12 ` Mark Brown
2011-08-23 23:24 ` Randy Dunlap
2011-08-23 23:32 ` Kenneth Heitke
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=20110816135051.GA22227@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=bryanh@codeaurora.org \
--cc=gregkh@suse.de \
--cc=john.stultz@linaro.org \
--cc=kheitke@codeaurora.org \
--cc=lethal@linux-sh.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ohad@wizery.com \
--cc=rdunlap@xenotime.net \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=sdharia@codeaurora.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=zajec5@gmail.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