[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cf66eafcc04bf565edcb330f66a3e12a.squirrel@www.codeaurora.org>
Date: Tue, 16 Aug 2011 18:54:45 -0700 (PDT)
From: "Sagar Dharia" <sdharia@...eaurora.org>
To: "Mark Brown" <broonie@...nsource.wolfsonmicro.com>
Cc: "Kenneth Heitke" <kheitke@...eaurora.org>,
"Arnd Bergmann" <arnd@...db.de>, 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 Tue, Aug 16, 2011 at 05:27:05PM -0600, Kenneth Heitke wrote:
>
>> For the proposed implementation, the client drivers are probed
>> before their devices are discovered because the client driver may
>> need to power-up the device or pull it out of reset. Once the
>> device is powered up, the call to get_logical_address() will let the
>> client know whether or not their device has enumerated.
>
> 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.
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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