From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>, Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Daniel Drake <dsd@laptop.org>
Subject: Re: [PATCH] viafb camera controller driver
Date: Sat, 16 Oct 2010 10:44:56 -0300 [thread overview]
Message-ID: <4CB9AC58.5020301@infradead.org> (raw)
In-Reply-To: <20101010162313.5caa137f@bike.lwn.net>
Em 10-10-2010 19:23, Jonathan Corbet escreveu:
> Howdy, all,
>
> Well, that took a whole lot longer than I had hoped...but, attached, is a
> new version of the viafb camera driver patch, done against 2.6.36-rc7.
> I've tried to address most of Laurent's comments from back in June; in
> particular, I have:
>
> - Gotten rid of the static device structure
> - Fixed some locking glitches
> - Fixed a bit of device initialization silliness.
>
> One thing I have *not* done is to push locking down into the ov7670
> driver. That would be a good thing to do at some point, but playing with
> that driver was beyond the scope of what I was trying to do here.
>
> This driver will still need some OLPC bits to work properly, but Daniel is
> working on that. This version of the driver does work on XO-1.5 systems,
> modulo some 2.6.36 API changes.
>
> Mauro, any chance of putting this in the queue for 2.6.37? Yes, I know
> it's really late, my apologies for that.
>
> Thanks,
>
> jon
> +static const struct v4l2_file_operations viacam_fops = {
> + .owner = THIS_MODULE,
> + .open = viacam_open,
> + .release = viacam_release,
> + .read = viacam_read,
> + .poll = viacam_poll,
> + .mmap = viacam_mmap,
> + .ioctl = video_ioctl2,
Hmm... do you need BKL? Otherwise, you should be using, instead, .unlocked_ioctl.
Btw, the driver build is broken:
drivers/media/video/via-camera.c: In function ‘viacam_configure_sensor’:
drivers/media/video/via-camera.c:228: error: ‘const struct v4l2_subdev_video_ops’ has no member named ‘s_fmt’
drivers/media/video/via-camera.c:228: error: ‘const struct v4l2_subdev_video_ops’ has no member named ‘s_fmt’
drivers/media/video/via-camera.c: In function ‘viacam_open’:
drivers/media/video/via-camera.c:651: error: too few arguments to function ‘videobuf_queue_sg_init’
drivers/media/video/via-camera.c: In function ‘viacam_enum_fmt_vid_cap’:
drivers/media/video/via-camera.c:878: error: ‘const struct v4l2_subdev_video_ops’ has no member named ‘enum_fmt’
drivers/media/video/via-camera.c:878: error: ‘const struct v4l2_subdev_video_ops’ has no member named ‘enum_fmt’
drivers/media/video/via-camera.c: In function ‘viacam_try_fmt_vid_cap’:
drivers/media/video/via-camera.c:921: error: ‘const struct v4l2_subdev_video_ops’ has no member named ‘try_fmt’
drivers/media/video/via-camera.c:921: error: ‘const struct v4l2_subdev_video_ops’ has no member named ‘try_fmt’
drivers/media/video/via-camera.c: In function ‘viacam_s_fmt_vid_cap’:
drivers/media/video/via-camera.c:959: error: ‘const struct v4l2_subdev_video_ops’ has no member named ‘try_fmt’
drivers/media/video/via-camera.c:959: error: ‘const struct v4l2_subdev_video_ops’ has no member named ‘try_fmt’
The main responsible for this breakage is this commit: 383e6ad73194814cfc980c302e0173fac11f0ee0
You may take a look on those commits also:
2e2ae382d956aa221c7b4fd897346c1b39f1699d
8c26cfe8d5f05ec9f945ea825c7eb28f46d04348
all commits are at staging/v2.6.37 branch on my tree:
http://git.linuxtv.org/media_tree.git
They removed s_fmt/enum_fmt/try_fmt in favor of a different approach, as sometimes, the format between the
sensor and the bridge is not exactly the same as seen on userspace.
The fix for this one is trivial:
drivers/media/video/via-camera.c:651: error: too few arguments to function ‘videobuf_queue_sg_init’
Just add an extra NULL parameter to the function.
-
Hans,
You're not playing nice with the others by changing their drivers without their ack, and without even
c/c them. I'm sure that, if Jon was aware on the changes you did on cafe-ccic and ov7670, he would be
submitting this driver with the build issues addressed.
So, please help him to address this issue.
Mauro.
next prev parent reply other threads:[~2010-10-16 13:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 22:23 [PATCH] viafb camera controller driver Jonathan Corbet
2010-10-11 12:09 ` Mauro Carvalho Chehab
2010-10-11 12:18 ` Laurent Pinchart
2010-10-11 15:30 ` Jonathan Corbet
2010-10-11 23:20 ` Laurent Pinchart
2010-10-16 13:44 ` Mauro Carvalho Chehab [this message]
2010-10-18 13:25 ` Jonathan Corbet
2010-10-19 3:20 ` Jonathan Corbet
2010-10-19 6:54 ` Hans Verkuil
2010-10-19 7:52 ` Laurent Pinchart
2010-10-19 10:46 ` Mauro Carvalho Chehab
2010-10-19 13:05 ` Laurent Pinchart
2010-10-19 14:04 ` Hans Verkuil
2010-10-19 14:21 ` Hans Verkuil
2010-10-19 14:49 ` Mauro Carvalho Chehab
2010-10-19 14:52 ` Laurent Pinchart
2010-10-19 15:42 ` Mauro Carvalho Chehab
2010-10-20 19:23 ` ext_lock (was viafb camera controller driver) Jonathan Corbet
2010-10-21 2:57 ` Mauro Carvalho Chehab
2010-10-21 6:51 ` Hans Verkuil
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=4CB9AC58.5020301@infradead.org \
--to=mchehab@infradead.org \
--cc=FlorianSchandinat@gmx.de \
--cc=corbet@lwn.net \
--cc=dsd@laptop.org \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.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