From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
mchehab@kernel.org, akinobu.mita@gmail.com,
jacopo+renesas@jmondi.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] media: mt9m111: fix device power usage
Date: Mon, 19 Sep 2022 13:13:38 +0000 [thread overview]
Message-ID: <YyhrAg1GJ+arWdMt@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20220919131009.m2vdtsmftqntc2e6@pengutronix.de>
On Mon, Sep 19, 2022 at 03:10:09PM +0200, Marco Felsch wrote:
> On 22-09-19, Laurent Pinchart wrote:
> > On Mon, Sep 19, 2022 at 12:45:42PM +0000, Sakari Ailus wrote:
> > > Hi Marco,
> > >
> > > On Fri, Sep 16, 2022 at 03:57:12PM +0200, Marco Felsch wrote:
> > > > @@ -758,10 +751,14 @@ static int mt9m111_g_register(struct v4l2_subdev *sd,
> > > > if (reg->reg > 0x2ff)
> > > > return -EINVAL;
> > > >
> > > > + mt9m111_s_power(sd, 1);
> > >
> > > It would be nice to have this driver converted to runtime PM. Up to you.
> >
> > I second that :-)
>
> I would rather keep it this way and add 2nd patch to change. So it would
> be easier to backport the patch.
Works for me.
--
Sakari Ailus
next prev parent reply other threads:[~2022-09-19 13:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 13:57 [PATCH v2 1/3] media: mt9m111: add V4L2_CID_LINK_FREQ support Marco Felsch
2022-09-16 13:57 ` [PATCH v2 2/3] media: mt9m111: fix device power usage Marco Felsch
2022-09-19 12:45 ` Sakari Ailus
2022-09-19 12:55 ` Laurent Pinchart
2022-09-19 13:10 ` Marco Felsch
2022-09-19 13:13 ` Sakari Ailus [this message]
2022-09-20 10:27 ` Jacopo Mondi
2022-09-20 10:34 ` Jacopo Mondi
2022-09-20 10:36 ` Laurent Pinchart
2022-09-16 13:57 ` [PATCH v2 3/3] media: mt9m111: don't turn on the output while powering it Marco Felsch
2022-09-19 13:00 ` Laurent Pinchart
2022-09-19 13:17 ` Marco Felsch
2022-09-20 10:39 ` Jacopo Mondi
2022-09-19 12:42 ` [PATCH v2 1/3] media: mt9m111: add V4L2_CID_LINK_FREQ support Sakari Ailus
2022-09-19 12:55 ` Laurent Pinchart
2022-09-19 13:08 ` Marco Felsch
2022-09-19 13:18 ` Sakari Ailus
2022-09-20 8:56 ` Marco Felsch
2022-09-20 9:19 ` Jacopo Mondi
2022-09-20 10:36 ` Sakari Ailus
2022-09-20 9:43 ` Jacopo Mondi
2022-09-20 9:48 ` Laurent Pinchart
2022-09-20 14:37 ` Marco Felsch
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=YyhrAg1GJ+arWdMt@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=akinobu.mita@gmail.com \
--cc=jacopo+renesas@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=mchehab@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®