[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160113123133.GK6588@sirena.org.uk>
Date: Wed, 13 Jan 2016 12:31:33 +0000
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: Krzysztof Kozlowski <k.kozlowski@...sung.com>, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
linus.walleij@...aro.org, gnurou@...il.com, lee.jones@...aro.org,
a.zummo@...ertech.it, alexandre.belloni@...e-electrons.com,
lgirdwood@...il.com, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
rtc-linux@...glegroups.com, swarren@...dia.com, treding@...dia.com,
Mallikarjun Kasoju <mkasoju@...dia.com>
Subject: Re: [PATCH V2 6/6] regulator: max77620: add regulator driver for
max77620/max20024
On Wed, Jan 13, 2016 at 05:35:33PM +0530, Laxman Dewangan wrote:
> On Wednesday 13 January 2016 05:27 PM, Mark Brown wrote:
> >>Something below. This will do the pre configuration before
> >>regulator_register happena dn machine constraint sets.
> >>I can not use the init_data->regulator_init() as I need to have the init
> >>data passed to the driver.
> >Why do you have this requirement?
> This is require to
> - configure FPS_SRC based on platform data for each rail,
> - If FPS_SRC enabled then enable it always.
> - If FPS_SRC is disabled (NONE) then based on init data constraint,
> set it to desired state.
What is FPS_SRC and why is it set from init_data? A driver should never
be looking at init_data.
> - Power mode and slew rate init based on default configuration from the
> register if platform does not want to set it.
Same here, why is init_data needed here?
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists