From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gy0-f170.google.com (mail-gy0-f170.google.com [209.85.160.170]) by ozlabs.org (Postfix) with ESMTP id 1CBCFB7CF5 for ; Sun, 11 Apr 2010 11:32:42 +1000 (EST) Received: by gyf2 with SMTP id 2so2142066gyf.15 for ; Sat, 10 Apr 2010 18:32:41 -0700 (PDT) Message-ID: <4BC12701.7000208@billgatliff.com> Date: Sat, 10 Apr 2010 20:33:53 -0500 From: Bill Gatliff MIME-Version: 1.0 To: Grant Likely Subject: Re: A better way to sequence driver initialization? References: <4BBF7E9C.80604@billgatliff.com> <1270889597.6865.107.camel@pasglop> <4BC07EAD.9020307@billgatliff.com> <20100410233909.GA16099@linux-sh.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Cc: Paul Mundt , linux-embedded , Linux/PPC Development List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Grant Likely wrote: > On Sat, Apr 10, 2010 at 5:39 PM, Paul Mundt wrote: > >> In cases where you can specifically note that dependencies, doing so will >> save you a world of pain. Despite that, it's simply not possible to do >> this as a free-for-all. Devices or busses that can tolerate multi-threaded >> probing need to be converted over one at a time, but even then you still >> need the dependency tracking for those that depend on link order today. >> Who's to say a function like gpio_request_wait_for_it(GPIO_NUMBER, "dependent-driver") isn't the way to do the dependency tracking? I can't even implement that without a context that can sleep... b.g. -- Bill Gatliff bgat@billgatliff.com