From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755194Ab2GaPjp (ORCPT ); Tue, 31 Jul 2012 11:39:45 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:47940 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755135Ab2GaPjn (ORCPT ); Tue, 31 Jul 2012 11:39:43 -0400 Date: Tue, 31 Jul 2012 16:39:41 +0100 From: Mark Brown To: Thierry Reding Cc: Alex Courbot , Stephen Warren , Stephen Warren , Simon Glass , Grant Likely , Rob Herring , Greg Kroah-Hartman , Arnd Bergmann , "linux-tegra@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-fbdev@vger.kernel.org" , "devicetree-discuss@lists.ozlabs.org" Subject: Re: [RFC][PATCH v3 1/3] runtime interpreted power sequences Message-ID: <20120731153941.GF4468@opensource.wolfsonmicro.com> References: <1343390750-3642-1-git-send-email-acourbot@nvidia.com> <1343390750-3642-2-git-send-email-acourbot@nvidia.com> <50170EA0.1010408@wwwdotorg.org> <5017B434.2010706@nvidia.com> <20120731105640.GD16155@avionic-0098.adnet.avionic-design.de> <20120731141328.GS4468@opensource.wolfsonmicro.com> <20120731142216.GA19591@avionic-0098.adnet.avionic-design.de> <20120731142607.GV4468@opensource.wolfsonmicro.com> <20120731143235.GA21126@avionic-0098.adnet.avionic-design.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120731143235.GA21126@avionic-0098.adnet.avionic-design.de> X-Cookie: Give him an evasive answer. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 31, 2012 at 04:32:35PM +0200, Thierry Reding wrote: > On Tue, Jul 31, 2012 at 03:26:07PM +0100, Mark Brown wrote: > > This is framework code - it doesn't have much option. Disabling HOTPLUG > > is totally reasonable on space constrained systems, there's no reason > > for the code to break things for people. > Still if you use this code and disable HOTPLUG, then you shouldn't be > using modules either. I mean there is no way you can write a driver that Of course. > can gracefully handle its platform data being discarded. Sure there is - take a copy of the platform data in probe().