On Tue, Mar 03, 2015 at 08:15:41AM -0800, Bjorn Andersson wrote:
> On Tue 03 Mar 04:50 PST 2015, Mark Brown wrote:
> > Why would the driver need to do that? I guess I'll see later on in the
> > series but the changelog should make that clear. Drivers aren't
> > supposed to ever need to look at t
On Tue 03 Mar 04:50 PST 2015, Mark Brown wrote:
> On Mon, Mar 02, 2015 at 08:25:38PM -0800, Bjorn Andersson wrote:
>
> > Expose the newly created init_data to the driver's parse callback so
> > that it can futher enhance it with e.g. constraints of the regulator.
>
> Why would the driver need to
On Mon, Mar 02, 2015 at 08:25:38PM -0800, Bjorn Andersson wrote:
> Expose the newly created init_data to the driver's parse callback so
> that it can futher enhance it with e.g. constraints of the regulator.
Why would the driver need to do that? I guess I'll see later on in the
series but the ch
Expose the newly created init_data to the driver's parse callback so
that it can futher enhance it with e.g. constraints of the regulator.
Signed-off-by: Bjorn Andersson
---
This is needed because calling regulator_register() with a of_node and
of_match will overwrite the passed config->init_dat
4 matches
Mail list logo
