From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Vladimir Barinov <vladimir.barinov@cogentembedded.com>,
mchehab@redhat.com, linux-media@vger.kernel.org,
magnus.damm@gmail.com, linux-sh@vger.kernel.org,
phil.edworthy@renesas.com, matsu@igel.co.jp
Subject: Re: [PATCH v7] V4L2: soc_camera: Renesas R-Car VIN driver
Date: Fri, 28 Jun 2013 21:11:26 +0400 [thread overview]
Message-ID: <51CDC3BE.1040603@cogentembedded.com> (raw)
In-Reply-To: <51CCD1B7.3040009@cogentembedded.com>
Hello.
On 06/28/2013 03:58 AM, Vladimir Barinov wrote:
>>> From: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
>>> Add Renesas R-Car VIN (Video In) V4L2 driver.
>>> Based on the patch by Phil Edworthy <phil.edworthy@renesas.com>.
>>> Signed-off-by: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
>>> [Sergei: removed deprecated IRQF_DISABLED flag, reordered/renamed
>>> 'enum chip_id'
>>> values, reordered rcar_vin_id_table[] entries, removed senseless
>>> parens from
>>> to_buf_list() macro, used ALIGN() macro in rcar_vin_setup(), added {}
>>> to the
>>> *if* statement and used 'bool' values instead of 0/1 where
>>> necessary, removed
>>> unused macros, done some reformatting and clarified some comments.]
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Reviewing this iteration of the patch is still on my todo, in the
>> meantime you might verify whether it works on top of the for-3.11-3
>> branch of my
>> http://git.linuxtv.org/gliakhovetski/v4l-dvb.git
>> git-tree, or "next" after it's been pulled by Mauro and pushed
>> upstream. With that branch you shouldn't need any additional patches
>> andy more.
> Actually we need to apply/merge more patches here that enables VIN
> support on separate platform (like pinctrl/clock/setup/) :)
> Despite of above the rcar_vin driver works fine on Marzen board in
> v4l-dvb.git after adding soc_camera_host_ops clock_start/clock_stop.
Guennadi, does that mean that we should rebase the driver to the
branch that you've named now?
> Regards,
> Vladimir
WBR, Sergei
next prev parent reply other threads:[~2013-06-28 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 20:52 [PATCH v7] V4L2: soc_camera: Renesas R-Car VIN driver Sergei Shtylyov
2013-06-26 7:28 ` Guennadi Liakhovetski
2013-06-27 23:58 ` Vladimir Barinov
2013-06-28 17:11 ` Sergei Shtylyov [this message]
2013-06-29 10:57 ` Guennadi Liakhovetski
2013-06-29 11:28 ` Vladimir Barinov
2013-06-29 15:04 ` Sergei Shtylyov
2013-06-28 22:01 ` Vladimir Barinov
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=51CDC3BE.1040603@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=matsu@igel.co.jp \
--cc=mchehab@redhat.com \
--cc=phil.edworthy@renesas.com \
--cc=vladimir.barinov@cogentembedded.com \
/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).