From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Kenneth Heitke <kheitke@codeaurora.org>,
sdharia@codeaurora.org, David Brown <davidb@codeaurora.org>,
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: Thu, 18 Aug 2011 12:00:07 +0900 [thread overview]
Message-ID: <1313636407.19990.102.camel@finisterre.wolfsonmicro.main> (raw)
In-Reply-To: <CACRpkdbSVF1FxpuocoXkDFH3vDQc4OoTwjU+9iqj0=vVs3R3dQ@mail.gmail.com>
On Wed, 2011-08-17 at 15:17 +0200, Linus Walleij wrote:
> On Wed, Aug 17, 2011 at 3:04 PM, Mark Brown
> <broonie@opensource.wolfsonmicro.com> wrote:
> > The device driver will know what power supplies and other signals the
> > device has, and it will know how and when to use them. (...)
> And I guess there is nothing in the spec claiming that all devices
> be powered-on when you boot?
I don't believe so, and if there were I'd not expect anyone to pay a
blind bit of notice to it.
> In that case the devices living on that bus will not respond to
> discovery messages until they are powered on, will they?
> Or is there some ingenious self-powered shift register
> logic doing these responses?
If my memory serves (I don't have access to the relevant documents right
now) the device announces itself when it detects that the bus is alive.
Slimbus is a relatively heavyweight interface so the extra cost of doing
this won't be too bad.
next prev parent reply other threads:[~2011-08-18 3:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 23:31 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
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 [this message]
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=1313636407.19990.102.camel@finisterre.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--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=linus.walleij@linaro.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
all inboxes | Powered by JetHome®