From: Arnd Bergmann <arnd@arndb.de>
To: sdharia@codeaurora.org
Cc: Kenneth Heitke <kheitke@codeaurora.org>,
David Brown <davidb@codeaurora.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
bryanh@codeaurora.org, linux-arm-msm@vger.kernel.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 21:49 +0200 [thread overview]
Message-ID: <4380004.YTvKt3Mlxd@wuerfel> (raw)
In-Reply-To: <0446c62c2d4a2c60442c582b4f61f5d3.squirrel@www.codeaurora.org>
On Tuesday 16 August 2011 10:44:35 sdharia@codeaurora.org wrote:
> >
> > SLIMbus is a MIPI standard bus primarily used for digital audio devices.
> > The devices on the bus SLIMbus enumerate themselves by sending an
> > IDENTITY message. I'll let Sagar clarify further.
>
> Thanks everyone for taking your time to review the RFC.
> Regarding device discovery:
> Every device sends a "PRESENT" message when it comes up. Every device has
> 48-bit address like Ethernet and spec lets upto 256 devices (each getting
> 8-bit logical address) on one bus.
> The device can report anytime (when it's plugged in, when a dynamic module
> powers it on etc.)
> Typical use case will be to have it board-specific but as Mark
> mentioned,we may have plug-in cards with slimbus devices so we want
> dynamic support as well.
Thanks for the info. The part that I still don't understand is how the
48-bit address and the 8 bit address are chosen. Do you mean that
the 8-bit address identifies the location on the bus and is used
when talking to the device locally while the 48-bit address is globally
unique and different for each individual board?
In that case, we would still not have any way to identify the type
of device, other than using a look-up table of 8-bit addresses to
device names (or numbers).
Or does the 48-bit number actually tell us something about what
device we're talking to, e.g. 24 bit vendor plus 24 bit device
type and revision or such. If that's the case, the number needs
to be the primary key that gets used to identify the driver,
just like we do it in case of USB or PCI devices.
Arnd
next prev parent reply other threads:[~2011-08-16 19:49 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
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 [this message]
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=4380004.YTvKt3Mlxd@wuerfel \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=bryanh@codeaurora.org \
--cc=davidb@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