From: Janusz Krzysztofik <jmkrzyszt@gmail.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] [media] ov6650: convert to standalone v4l2 subdevice
Date: Fri, 16 Jun 2017 19:56:41 +0200 [thread overview]
Message-ID: <3766309.QcUzr5zhsS@z50> (raw)
In-Reply-To: <20170616091621.GK12407@valkosipuli.retiisi.org.uk>
On Friday 16 June 2017 12:16:21 Sakari Ailus wrote:
> Hi Janusz,
>
> Thanks for the patch. A few comments below.
>
> On Fri, Jun 16, 2017 at 12:52:43AM +0200, Janusz Krzysztofik wrote:
> > Remove the soc_camera dependencies.
> >
> > Lost features, fortunately not used or not critical on test platform:
> > - soc_camera power on/off callback - replaced with clock enable/disable
> > only, no support for platform provided regulators nor power callback,
...
> > - return soc_camera_set_power(&client->dev, ssdd, priv->clk, on);
> > + if (on)
> > + ret = v4l2_clk_enable(priv->clk);
> > + else
> > + v4l2_clk_disable(priv->clk);
>
> It'd be nicer to use the clock framework. Although I'm certainly fine with
> v4l2_clk for now, one thing at a time...
I have that in my queue, but the test platform I'm using does not support CCF
yet so there is no easy way for the host camera interface driver to provide a
compatible clock other than v4l2_clk based.
Thanks,
Janusz
next prev parent reply other threads:[~2017-06-16 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 22:52 [PATCH] [media] ov6650: convert to standalone v4l2 subdevice Janusz Krzysztofik
2017-06-16 7:56 ` Hans Verkuil
2017-06-16 9:16 ` Sakari Ailus
2017-06-16 17:56 ` Janusz Krzysztofik [this message]
2017-06-16 19:39 ` Sakari Ailus
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=3766309.QcUzr5zhsS@z50 \
--to=jmkrzyszt@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hans.verkuil@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@iki.fi \
/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