linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Hunter, Adrian" <adrian.hunter@intel.com>
Subject: Re: Regulator probe
Date: Sat, 10 Sep 2016 14:03:35 +0300	[thread overview]
Message-ID: <1473505415.11323.235.camel@linux.intel.com> (raw)
In-Reply-To: <20160909163824.GT27946@sirena.org.uk>

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 <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  parent reply	other threads:[~2016-09-10 11:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01 14:53 Regulator probe Andy Shevchenko
2016-09-01 15:38 ` Mark Brown
2016-09-01 16:15   ` Andy Shevchenko
2016-09-01 17:02     ` Mark Brown
2016-09-05 16:01       ` Andy Shevchenko
2016-09-06 10:24         ` Mark Brown
2016-09-07 14:24           ` Andy Shevchenko
2016-09-09 12:17             ` Mark Brown
2016-09-09 12:55               ` Andy Shevchenko
2016-09-09 15:29                 ` Mark Brown
2016-09-09 16:10                   ` Andy Shevchenko
2016-09-09 16:38                     ` Mark Brown
2016-09-09 17:04                       ` Andy Shevchenko
2016-09-09 17:18                         ` Mark Brown
2016-09-10 11:03                       ` Andy Shevchenko [this message]
2016-09-12 15:27                         ` Mark Brown
2016-09-12 16:01                           ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1473505415.11323.235.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).