From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-media@vger.kernel.org
Subject: Re: [RFC PATCH] [media] mt9v032: Add support for mt9v022 and mt9v024
Date: Wed, 28 May 2014 13:04:21 +0200 [thread overview]
Message-ID: <2161017.E5TWD97cmR@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1405281155440.27831@axis700.grange>
Hello,
On Wednesday 28 May 2014 12:07:57 Guennadi Liakhovetski wrote:
> On Wed, 28 May 2014, Philipp Zabel wrote:
> > Am Dienstag, den 27.05.2014, 21:48 +0200 schrieb Guennadi Liakhovetski:
> > > On Mon, 26 May 2014, Philipp Zabel wrote:
> > > > From the looks of it, mt9v022 and mt9v032 are very similar,
> > > > as are mt9v024 and mt9v034. With minimal changes it is possible
> > > > to support mt9v02[24] with the same driver.
> > >
> > > Are you aware of drivers/media/i2c/soc_camera/mt9v022.c?
> >
> > Yes. Unfortunately this driver can't be used in a system without
> > soc_camera. It uses soc_camera helpers and doesn't implement pad ops
> > among others.
>
> As I mentioned many times, this compatibility is a matter of someone just
> needing and finally doing this. If you need this, please, extend the
> mt9v022 driver to also work with non soc-camera hosts, if you need any
> help - please feel free to ask, I can send you my conversion code, that
> I've done for ov772x, but never managed to finalise testing,
> unfortunately.
>
> > > With this patch you'd duplicate support for both mt9v022 and mt9v024,
> > > which doesn't look like a good idea to me.
> >
> > While this is true, given that the mt9v02x/3x sensors are so similar,
> > the support is already duplicated in all but name.
> > Would you suggest we should try to merge the mt9v032 and mt9v022
> > drivers?
>
> Out of 3 options:
>
> 1. extend mt9v022 to work with non soc-camera hosts
> 2. extend mt9v032 to also support mt9v022 and mt9v024
> 3. merge both mt9v022 and mt9v032 drivers
>
> option 2 seems the worst to me. I'm ok with either 1 or 3, whereas 3 is
> more difficult than 1.
This topic has been discussed over and over. It indeed "just" requires someone
to do it, although it might be more complex than that sounds.
We need to fix the infrastructure to make sensor drivers completely unaware of
soc-camera. This isn't about extending the mt9v022 driver to work with non
soc-camera hosts, it's about fixing soc-camera not to require any change to
sensor drivers. Philipp, if you have time to work on that, we can discuss what
needs to be done.
On the sensor side, we should have a single driver for the mt9v022, 024 and
032 sensors. I would vote for merging the two drivers into
drivers/media/i2c/mt9v032.c, as that one is closer to the goal of not being
soc-camera specific.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-05-28 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 14:03 [RFC PATCH] [media] mt9v032: Add support for mt9v022 and mt9v024 Philipp Zabel
2014-05-27 19:48 ` Guennadi Liakhovetski
2014-05-28 9:50 ` Philipp Zabel
2014-05-28 10:07 ` Guennadi Liakhovetski
2014-05-28 11:04 ` Laurent Pinchart [this message]
2014-05-28 14:36 ` Philipp Zabel
2014-05-28 14:44 ` Laurent Pinchart
2014-06-03 9:30 ` Philipp Zabel
2014-06-05 0:32 ` Laurent Pinchart
2014-06-19 9:28 ` Guennadi Liakhovetski
2014-05-28 11:43 ` Laurent Pinchart
2014-05-28 14:37 ` Philipp Zabel
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=2161017.E5TWD97cmR@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=p.zabel@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).