From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756347Ab1GFVBw (ORCPT ); Wed, 6 Jul 2011 17:01:52 -0400 Received: from utopia.booyaka.com ([72.9.107.138]:58346 "EHLO utopia.booyaka.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756326Ab1GFVBv (ORCPT ); Wed, 6 Jul 2011 17:01:51 -0400 Date: Wed, 6 Jul 2011 15:01:49 -0600 (MDT) From: Paul Walmsley To: Tony Lindgren cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Aaro Koskinen , Rajendra Nayak , =?ISO-8859-15?Q?Beno=EEt_Cousson?= , Michael Buesch Subject: Re: [PATCH] OMAP: hwmod: add kernel cmdline flag to avoid resetting IP blocks during init In-Reply-To: <20110706064326.GI5783@atomide.com> Message-ID: References: <20110703010204.19046.85186.stgit@dusk> <20110703010206.19046.85293.stgit@dusk> <20110704085503.GQ23145@atomide.com> <20110706064326.GI5783@atomide.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 5 Jul 2011, Tony Lindgren wrote: > * Paul Walmsley [110705 18:55]: > > On Tue, 5 Jul 2011, Paul Walmsley wrote: > > > > > For this case, we probably need some board file function to tell the > > > hwmod code to disregard a device completely, to tell the kernel to > > > pretend that the device does not exist. > > > > ... and the other problem here is that we currently probe devices via an > > arch_initcall(), and the board file init_machine is also an arch_initcall. > > Either we'll need to be very careful about Makefile ordering, or we should > > just call omap2_init_devices() from the board file init_machine directly. > > The latter makes the most sense to me. > > And that can then be passed the list of devices with the special flags > for noreset, disabled and reserved. Then the late_initcall can optionally > reset the rest of the devices. 'disabled' can probably be the default for a device that doesn't have a driver associated with it, once the runtime PM conversion is complete. That's what the late_initcall would do. Then if a driver is dynamically loaded for one of those devices, the hwmod code would just re-enable it. - Paul