From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
Marco Felsch <m.felsch@pengutronix.de>,
Michael Grzeschik <m.grzeschik@pengutronix.de>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Subject: Re: [PATCH v2] media: mt9m111: add regulator support
Date: Fri, 31 May 2019 10:03:44 -0300 [thread overview]
Message-ID: <20190531100240.6f9e5c12@coco.lan> (raw)
In-Reply-To: <20190531112723.ijhkpi354ussgvxq@kekkonen.localdomain>
Hi Sakari,
Em Fri, 31 May 2019 14:27:24 +0300
Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
> Hi Mauro,
>
> On Wed, May 29, 2019 at 03:25:18PM -0400, Mauro Carvalho Chehab wrote:
> > From: Robert Jarzmik <robert.jarzmik@free.fr>
As stated here, this patch is not really mine. It is a rebased version of a
patch that was delegated to a sub-maintainer, being on his queue for more
than 2 years.
> >
> > In the soc_camera removal, the board specific power callback was
> > dropped. This at least will remove the power optimization from ezx and
> > em-x270 pxa based boards.
> >
> > As to recreate the same level of functionality, make the mt9m111 have a
> > regulator providing it its power, so that board designers can plug in a
> > gpio based or ldo regulator, mimicking their former soc_camera power
> > hook.
> >
> > Fixes: 5c10113cc668 ("media: mt9m111: make a standalone v4l2 subdevice")
> >
> > [mchehab+samsung@kernel.org: check return values for regulator_enable and
> > fix a build warning]
> > Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > ---
> >
> > This is a respin of this patch:
> >
> > http://patchwork.linuxtv.org/patch/37950/
> >
> > rebased (and fixed) to apply on the top of upstream.
> >
> > While checking old patches at the ML, I noticed that this patch
> > was never applied:
> >
> > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1238720.html
> >
> > The first patch of this series got applied, though:
> >
> > c771f42fed7f ("[media] media: platform: pxa_camera: add missing sensor power on")
> >
> > So, I'm closing the original patch as obsoleted and I'm sending this
> > one to the ML for tests.
> >
> > Can anyone test this patch and send a tested-by?
> >
> > drivers/media/i2c/mt9m111.c | 17 +++++++++++++++++
> > 1 file changed, 17 insertions(+)
> >
> > diff --git a/drivers/media/i2c/mt9m111.c b/drivers/media/i2c/mt9m111.c
> > index 5168bb5880c4..746d1345b505 100644
> > --- a/drivers/media/i2c/mt9m111.c
> > +++ b/drivers/media/i2c/mt9m111.c
> > @@ -13,6 +13,7 @@
> > #include <linux/log2.h>
> > #include <linux/gpio.h>
> > #include <linux/delay.h>
> > +#include <linux/regulator/consumer.h>
> > #include <linux/v4l2-mediabus.h>
> > #include <linux/module.h>
> > #include <linux/property.h>
> > @@ -243,6 +244,7 @@ struct mt9m111 {
> > int power_count;
> > const struct mt9m111_datafmt *fmt;
> > int lastpage; /* PageMap cache value */
> > + struct regulator *regulator;
> > bool is_streaming;
> > /* user point of view - 0: falling 1: rising edge */
> > unsigned int pclk_sample:1;
> > @@ -982,6 +984,12 @@ static int mt9m111_power_on(struct mt9m111 *mt9m111)
> > if (ret < 0)
> > return ret;
> >
> > + if (mt9m111->regulator) {
> > + ret = regulator_enable(mt9m111->regulator);
> > + if (ret < 0)
> > + return ret;
> > + }
> > +
> > ret = mt9m111_resume(mt9m111);
> > if (ret < 0) {
> > dev_err(&client->dev, "Failed to resume the sensor: %d\n", ret);
> > @@ -994,6 +1002,8 @@ static int mt9m111_power_on(struct mt9m111 *mt9m111)
> > static void mt9m111_power_off(struct mt9m111 *mt9m111)
> > {
> > mt9m111_suspend(mt9m111);
> > + if (mt9m111->regulator)
>
> You could omit this check, same for the above. As Mita-san explained, it
> falls back to using the dummy regulator if there isn't one defined.
>
> > + regulator_disable(mt9m111->regulator);
Makes sense to me.
Feel free to remove it and apply on your tree.
> > v4l2_clk_disable(mt9m111->clk);
> > }
> >
> > @@ -1256,6 +1266,13 @@ static int mt9m111_probe(struct i2c_client *client,
> > if (IS_ERR(mt9m111->clk))
> > return PTR_ERR(mt9m111->clk);
> >
> > + mt9m111->regulator = devm_regulator_get(&client->dev, "vdd");
> > + if (IS_ERR(mt9m111->regulator)) {
> > + dev_err(&client->dev, "regulator not found: %ld\n",
> > + PTR_ERR(mt9m111->regulator));
> > + return PTR_ERR(mt9m111->regulator);
> > + }
> > +
> > /* Default HIGHPOWER context */
> > mt9m111->ctx = &context_b;
> >
>
Thanks,
Mauro
next prev parent reply other threads:[~2019-05-31 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 19:25 [PATCH v2] media: mt9m111: add regulator support Mauro Carvalho Chehab
2019-05-30 14:21 ` Akinobu Mita
2019-05-31 19:43 ` Robert Jarzmik
2019-06-02 15:05 ` Akinobu Mita
2019-05-31 11:27 ` Sakari Ailus
2019-05-31 13:03 ` Mauro Carvalho Chehab [this message]
2019-05-31 19:29 ` Robert Jarzmik
2019-06-18 11:51 ` Sakari Ailus
2019-06-03 19:54 ` Robert Jarzmik
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=20190531100240.6f9e5c12@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=akinobu.mita@gmail.com \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=linux-media@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=m.grzeschik@pengutronix.de \
--cc=mchehab@infradead.org \
--cc=robert.jarzmik@free.fr \
--cc=sakari.ailus@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.