[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1313636407.19990.102.camel@finisterre.wolfsonmicro.main>
Date: Thu, 18 Aug 2011 12:00:07 +0900
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Arnd Bergmann <arnd@...db.de>,
Kenneth Heitke <kheitke@...eaurora.org>,
sdharia@...eaurora.org, David Brown <davidb@...eaurora.org>,
bryanh@...eaurora.org, linux-arm-msm@...r.kernel.org,
rdunlap@...otime.net, rmk+kernel@....linux.org.uk,
john.stultz@...aro.org, akpm@...ux-foundation.org, ohad@...ery.com,
gregkh@...e.de, stefanr@...6.in-berlin.de, lethal@...ux-sh.org,
linville@...driver.com, zajec5@...il.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] slimbus: Linux driver framework for SLIMbus.
On Wed, 2011-08-17 at 15:17 +0200, Linus Walleij wrote:
> On Wed, Aug 17, 2011 at 3:04 PM, Mark Brown
> <broonie@...nsource.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists