Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-17 Thread Mark Brown
On Wed, Jun 17, 2020 at 05:39:26PM +0530, Sumit Semwal wrote: > On Wed, 17 Jun 2020 at 17:36, Mark Brown wrote: > > That seems... interesting. Are you sure the regulator has fully ramped > > when STATUS1 starts flagging? > On a consumer device, I am not sure I have any way of checking that, >

Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-17 Thread Sumit Semwal
On Wed, 17 Jun 2020 at 17:36, Mark Brown wrote: > > On Wed, Jun 17, 2020 at 05:27:12PM +0530, Sumit Semwal wrote: > > On Wed, 17 Jun 2020 at 17:17, Mark Brown wrote: > > > On Wed, Jun 17, 2020 at 05:12:35PM +0530, Sumit Semwal wrote: > > > > > I understand from a pure regulators' correctness

Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-17 Thread Mark Brown
On Wed, Jun 17, 2020 at 05:27:12PM +0530, Sumit Semwal wrote: > On Wed, 17 Jun 2020 at 17:17, Mark Brown wrote: > > On Wed, Jun 17, 2020 at 05:12:35PM +0530, Sumit Semwal wrote: > > > I understand from a pure regulators' correctness point of view, > > > ENABLE_CTL should be the one checked

Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-17 Thread Sumit Semwal
On Wed, 17 Jun 2020 at 17:17, Mark Brown wrote: > > On Wed, Jun 17, 2020 at 05:12:35PM +0530, Sumit Semwal wrote: > > > I understand from a pure regulators' correctness point of view, > > ENABLE_CTL should be the one checked there, so I can change the patch > > as you suggested, but there seems

Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-17 Thread Mark Brown
On Wed, Jun 17, 2020 at 05:12:35PM +0530, Sumit Semwal wrote: > I understand from a pure regulators' correctness point of view, > ENABLE_CTL should be the one checked there, so I can change the patch > as you suggested, but there seems to be some performance penalty > there. I thought the goal

Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-17 Thread Sumit Semwal
Hello Mark, On Tue, 2 Jun 2020 at 17:55, Mark Brown wrote: > > On Tue, Jun 02, 2020 at 05:40:45PM +0530, Sumit Semwal wrote: > > On Tue, 2 Jun 2020 at 17:02, Mark Brown wrote: > > > On Tue, Jun 02, 2020 at 03:39:23PM +0530, Sumit Semwal wrote: > > > > This should be a get_status() callback... >

Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-02 Thread Mark Brown
On Tue, Jun 02, 2020 at 05:40:45PM +0530, Sumit Semwal wrote: > On Tue, 2 Jun 2020 at 17:02, Mark Brown wrote: > > On Tue, Jun 02, 2020 at 03:39:23PM +0530, Sumit Semwal wrote: > > This should be a get_status() callback... > From my (limited) understanding of downstream code, it seemed like for

Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-02 Thread Sumit Semwal
Hi Mark, Thank you very much for reviewing. On Tue, 2 Jun 2020 at 17:02, Mark Brown wrote: > > On Tue, Jun 02, 2020 at 03:39:23PM +0530, Sumit Semwal wrote: > > > +static int qcom_labibb_regulator_is_enabled(struct regulator_dev *rdev) > > +{ > > + int ret; > > + unsigned int val; > >

Re: [PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-02 Thread Mark Brown
On Tue, Jun 02, 2020 at 03:39:23PM +0530, Sumit Semwal wrote: > +static int qcom_labibb_regulator_is_enabled(struct regulator_dev *rdev) > +{ > + int ret; > + unsigned int val; > + struct labibb_regulator *reg = rdev_get_drvdata(rdev); > + > + ret = regmap_read(reg->regmap,

[PATCH v4 4/5] regulator: qcom: Add labibb driver

2020-06-02 Thread Sumit Semwal
From: Nisha Kumari Qualcomm platforms have LAB(LCD AMOLED Boost)/IBB(Inverting Buck Boost) regulators, labibb for short, which are used as power supply for LCD Mode displays. This patch adds labibb regulator driver for pmi8998 PMIC, found on SDM845 platforms. Signed-off-by: Nisha Kumari