[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110817063237.GA12344@opensource.wolfsonmicro.com>
Date: Wed, 17 Aug 2011 15:32:42 +0900
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Sagar Dharia <sdharia@...eaurora.org>
Cc: Kenneth Heitke <kheitke@...eaurora.org>,
Arnd Bergmann <arnd@...db.de>,
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 Tue, Aug 16, 2011 at 06:54:45PM -0700, Sagar Dharia wrote:
> > On Tue, Aug 16, 2011 at 05:27:05PM -0600, Kenneth Heitke wrote:
> > There's a callback generated to left the client know when this has
> > happened I'd expect?
> As of now, there is no callback to notify them. They can either query it
> during 1st transaction, or retry with some delay in the probe itself.
> Callback is a good idea and we can definitely use it to inform clients
> that their device has come up.
It's pretty much essential, I'd expect slimbus devices will want to
provide always on functionality like accessory detection which there's
no reason to delay.
--
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