From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755220AbcIJLDk (ORCPT ); Sat, 10 Sep 2016 07:03:40 -0400 Received: from mga11.intel.com ([192.55.52.93]:8687 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752436AbcIJLDi (ORCPT ); Sat, 10 Sep 2016 07:03:38 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,310,1470726000"; d="scan'208";a="877124038" Message-ID: <1473505415.11323.235.camel@linux.intel.com> Subject: Re: Regulator probe From: Andy Shevchenko To: Mark Brown Cc: "linux-kernel@vger.kernel.org" , "Hunter, Adrian" Date: Sat, 10 Sep 2016 14:03:35 +0300 In-Reply-To: <20160909163824.GT27946@sirena.org.uk> References: <20160901153836.GI5967@sirena.org.uk> <1472746516.4887.489.camel@linux.intel.com> <20160901170215.GJ5967@sirena.org.uk> <1473091312.11323.20.camel@linux.intel.com> <20160906102407.GF3950@sirena.org.uk> <1473258241.11323.83.camel@linux.intel.com> <20160909121749.GR27946@sirena.org.uk> <1473425727.11323.144.camel@linux.intel.com> <20160909152952.GS27946@sirena.org.uk> <1473437439.11323.188.camel@linux.intel.com> <20160909163824.GT27946@sirena.org.uk> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2016-09-09 at 17:38 +0100, Mark Brown wrote: > On Fri, Sep 09, 2016 at 07:10:39PM +0300, Andy Shevchenko wrote: > > On Fri, 2016-09-09 at 16:29 +0100, Mark Brown wrote: > ...and then we correctly report that the optional supply that > > > isn't > > > mapped (as far as I remember) isn't there. > But it *will be* soon there. > Hmm... And the proper fix for this case is... (let's assume there > > will > > not be device tree solution in nearest future)? > > To supply this particular mapping before you set full constraints. Please, correct me if I'm wrong in the following: 1) mapping is what kept in the regulator_map_list; 2) the only way to list something for this mapping is to use one of regulator drivers that will call regulator_register() at the end; 3) in case of fixed voltage regulator it prepares configuration and description (based on platform code for example) of the regulator and calls devm_regulator_register(); 4) regulator_register() _will not_ add fixed regulator to the mapping if GPIO is deferred; 5) regulator_dev_lookup() didn't see the regulator before deferred_probe_initcall() happened. If the above is correct, how to add mapping to be seen in 5) ? -- Andy Shevchenko Intel Finland Oy