[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1473696075.11323.258.camel@linux.intel.com>
Date: Mon, 12 Sep 2016 19:01:15 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Mark Brown <broonie@...nel.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Hunter, Adrian" <adrian.hunter@...el.com>
Subject: Re: Regulator probe
On Mon, 2016-09-12 at 16:27 +0100, Mark Brown wrote:
> On Sat, Sep 10, 2016 at 02:03:35PM +0300, Andy Shevchenko wrote:
>
> >
> > 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) ?
>
> You may need to extend the interfaces offered by the core - one of the
> great advantages of an open source kernel like Linux is that you can
> modify the whole system if needed.
Yeah, the core seems not able to handle my case. So, that's what I was
trying to tell.
I will look at the code later and see what I can amend there.
Thanks!
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists