From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755704AbbFRPcc (ORCPT ); Thu, 18 Jun 2015 11:32:32 -0400 Received: from h1446028.stratoserver.net ([85.214.92.142]:48281 "EHLO mail.ahsoftware.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753463AbbFRPcY (ORCPT ); Thu, 18 Jun 2015 11:32:24 -0400 Message-ID: <5582E476.6040905@ahsoftware.de> Date: Thu, 18 Jun 2015 17:32:06 +0200 From: Alexander Holler User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Russell King - ARM Linux , Andrzej Hajda CC: Mark Brown , Tomeu Vizoso , linux-arm-kernel@lists.infradead.org, Alexandre Courbot , Arnd Bergmann , Dmitry Torokhov , Grant Likely , Greg Kroah-Hartman , Ian Campbell , Javier Martinez Canillas , Krzysztof Kozlowski , Kumar Gala , Len Brown , Linus Walleij , linux-kernel@vger.kernel.org, Lv Zheng , Mark Rutland , Pawel Moll , "Rafael J. Wysocki" , Robert Moore , Rob Herring , Stephen Warren , =?windows-1252?Q?Terje_Bergstr=F6m?= , Thierry Reding Subject: Re: [PATCH 00/13] Discover and probe dependencies References: <1434548543-22949-1-git-send-email-tomeu.vizoso@collabora.com> <55829269.2090309@samsung.com> <20150618103615.GC14071@sirena.org.uk> <5582C437.4030108@samsung.com> <20150618144934.GM7557@n2100.arm.linux.org.uk> In-Reply-To: <20150618144934.GM7557@n2100.arm.linux.org.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 18.06.2015 um 16:49 schrieb Russell King - ARM Linux: > I think you may need to pick a better example to illustrate your point. :) It's easy to describe: Sort driver probe calls and forget about the whole device-stuff. The real target is to sort the driver probe calls and ideally the whole device stuff could be ignored, leaving it as however it may work. Unfortunately, that's not as easy to implement as it sounds. ;) I've too hit the device-stuff very late in my driver-probe-ordering experiment and just did it somehow, because I already was at the limit of the time I wanted to spend. ;) So to repeat myself, I think the first target has to be to identify drivers either without having to call their initcalls at all, or by making sure their initcalls just register and do nothing else (what I've called "well-done"). Regards, Alexander Holler From mboxrd@z Thu Jan 1 00:00:00 1970 From: holler@ahsoftware.de (Alexander Holler) Date: Thu, 18 Jun 2015 17:32:06 +0200 Subject: [PATCH 00/13] Discover and probe dependencies In-Reply-To: <20150618144934.GM7557@n2100.arm.linux.org.uk> References: <1434548543-22949-1-git-send-email-tomeu.vizoso@collabora.com> <55829269.2090309@samsung.com> <20150618103615.GC14071@sirena.org.uk> <5582C437.4030108@samsung.com> <20150618144934.GM7557@n2100.arm.linux.org.uk> Message-ID: <5582E476.6040905@ahsoftware.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am 18.06.2015 um 16:49 schrieb Russell King - ARM Linux: > I think you may need to pick a better example to illustrate your point. :) It's easy to describe: Sort driver probe calls and forget about the whole device-stuff. The real target is to sort the driver probe calls and ideally the whole device stuff could be ignored, leaving it as however it may work. Unfortunately, that's not as easy to implement as it sounds. ;) I've too hit the device-stuff very late in my driver-probe-ordering experiment and just did it somehow, because I already was at the limit of the time I wanted to spend. ;) So to repeat myself, I think the first target has to be to identify drivers either without having to call their initcalls at all, or by making sure their initcalls just register and do nothing else (what I've called "well-done"). Regards, Alexander Holler