From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
linux-media@vger.kernel.org, linux-sh@vger.kernel.org,
magnus.damm@gmail.com, hans.verkuil@cisco.com,
ian.molton@codethink.co.uk, lars@metafoo.de,
william.towle@codethink.co.uk
Subject: Re: [PATCH 0/3] adv7604: .g_crop and .cropcap support
Date: Sun, 13 Dec 2015 20:10:19 +0200 [thread overview]
Message-ID: <11156352.tBa7SdgW3Q@avalon> (raw)
In-Reply-To: <566AF904.9050102@xs4all.nl>
Hi Hans,
On Friday 11 December 2015 17:25:40 Hans Verkuil wrote:
> On 12/11/2015 05:04 PM, Ulrich Hecht wrote:
> > Hi!
> >
> > The rcar_vin driver relies on these methods. The third patch makes sure
> > that they return up-to-date data if the input signal has changed since
> > initialization.
> >
> > CU
> > Uli
> >
> > Ulrich Hecht (3):
> > media: adv7604: implement g_crop
> > media: adv7604: implement cropcap
>
> I'm not keen on these changes. The reason is that these ops are deprecated
> and soc-camera is - almost - the last user. The g/s_selection ops should be
> used instead.
>
> Now, I have a patch that changes soc-camera to g/s_selection. The reason it
> was never applied is that I had a hard time finding hardware to test it
> with.
>
> Since you clearly have that hardware I think I'll rebase my (by now rather
> old) patch and post it again. If you can switch the adv7604 patch to
> g/s_selection and everything works with my patch, then I think I should
> just make a pull request for it.
>
> I hope to be able to do this on Monday.
>
> If switching soc-camera over to g/s_selection isn't possible, then at the
> very least your adv7604 changes should provide the g/s_selection
> implementation. I don't want to have to convert this driver later to
> g/s_selection.
I understand your concern and i agree with you. Our plan is to move the rcar-
vin driver away from soc-camera. Unfortunately that will take some time, and
being able to use the adv7604 driver with rcar-vin would be very handy for
testing on some of our boards.
Let's see how g/s_selection support in soc-camera works out and then decide on
what to do.
> > media: adv7604: update timings on change of input signal
> >
> > drivers/media/i2c/adv7604.c | 38 ++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 38 insertions(+)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-12-14 1:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 16:04 [PATCH 0/3] adv7604: .g_crop and .cropcap support Ulrich Hecht
2015-12-11 16:04 ` [PATCH 1/3] media: adv7604: implement g_crop Ulrich Hecht
2015-12-13 18:18 ` Laurent Pinchart
2015-12-11 16:04 ` [PATCH 2/3] media: adv7604: implement cropcap Ulrich Hecht
2015-12-13 18:22 ` Laurent Pinchart
2015-12-11 16:04 ` [PATCH 3/3] media: adv7604: update timings on change of input signal Ulrich Hecht
2015-12-11 18:15 ` Sergei Shtylyov
2015-12-13 18:30 ` Laurent Pinchart
2015-12-11 16:25 ` [PATCH 0/3] adv7604: .g_crop and .cropcap support Hans Verkuil
2015-12-13 18:10 ` Laurent Pinchart [this message]
2015-12-14 10:34 ` Hans Verkuil
2015-12-14 10:33 ` Hans Verkuil
2015-12-14 12:55 ` Ulrich Hecht
2015-12-14 13:02 ` Hans Verkuil
2015-12-14 15:41 ` Ulrich Hecht
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=11156352.tBa7SdgW3Q@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=ian.molton@codethink.co.uk \
--cc=lars@metafoo.de \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ulrich.hecht+renesas@gmail.com \
--cc=william.towle@codethink.co.uk \
/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