All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: phil.edworthy@renesas.com
Cc: vladimir.barinov@cogentembedded.com, g.liakhovetski@gmx.de,
	linux-media@vger.kernel.org, linux-sh@vger.kernel.org,
	magnus.damm@gmail.com, matsu@igel.co.jp, mchehab@redhat.com
Subject: Re: [PATCH v5] V4L2: soc_camera: Renesas R-Car VIN driver
Date: Tue, 21 May 2013 14:47:04 +0000	[thread overview]
Message-ID: <519B88E8.3040101@cogentembedded.com> (raw)
In-Reply-To: <OF7D5F7F7E.CF4ED120-ON80257B72.0042ED42-80257B72.004332EB@eu.necel.com>

Hello.

On 21-05-2013 16:13, phil.edworthy@renesas.com wrote:

>>>>> Subject: [PATCH v5] V4L2: soc_camera: Renesas R-Car VIN driver

>>>>> 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>.

>>>> I've seen old patches that add VIN to the Marzen board, do you have an
>>>> updated version?

>>>      The last version of that patchset is 4, here it is archived:

>>> http://marc.info/?l=linux-sh&m\x136865481429756
>>> http://marc.info/?l=linux-sh&m\x136865499029807
>>> http://marc.info/?l=linux-sh&m\x136865509129843
>>> http://marc.info/?l=linux-sh&m\x136865520029900

>> First of all, thank you for your work on this driver.

>> I have tried your patches on the Marzen board using an Expansion
>> Board with an OmniVision 10635 camera (progressive BT656), using an
>> out-of-tree driver. There appears to be an issue with the interrupt
>> handling compared to my original driver.

>> I realise that you don't have the Marzen Expansion Board & don't
>> have an ov10635 camera. However, unfortunately, I don't have much
>> time that I can spend on this. Do any of the boards you have use a
>> progressive camera?

    No. Is there any way you can send us that expansion board? It seems
the only way we can get some progress on this issue.

> Oops, the comments about the captured image contents are my fault.
> However, the unhandled irq after stopping capture is still an issue.

    Thanks for letting us know.

> Regards
> Phil

WBR, Sergei


WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: phil.edworthy@renesas.com
Cc: vladimir.barinov@cogentembedded.com, g.liakhovetski@gmx.de,
	linux-media@vger.kernel.org, linux-sh@vger.kernel.org,
	magnus.damm@gmail.com, matsu@igel.co.jp, mchehab@redhat.com
Subject: Re: [PATCH v5] V4L2: soc_camera: Renesas R-Car VIN driver
Date: Tue, 21 May 2013 18:47:04 +0400	[thread overview]
Message-ID: <519B88E8.3040101@cogentembedded.com> (raw)
In-Reply-To: <OF7D5F7F7E.CF4ED120-ON80257B72.0042ED42-80257B72.004332EB@eu.necel.com>

Hello.

On 21-05-2013 16:13, phil.edworthy@renesas.com wrote:

>>>>> Subject: [PATCH v5] V4L2: soc_camera: Renesas R-Car VIN driver

>>>>> 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>.

>>>> I've seen old patches that add VIN to the Marzen board, do you have an
>>>> updated version?

>>>      The last version of that patchset is 4, here it is archived:

>>> http://marc.info/?l=linux-sh&m=136865481429756
>>> http://marc.info/?l=linux-sh&m=136865499029807
>>> http://marc.info/?l=linux-sh&m=136865509129843
>>> http://marc.info/?l=linux-sh&m=136865520029900

>> First of all, thank you for your work on this driver.

>> I have tried your patches on the Marzen board using an Expansion
>> Board with an OmniVision 10635 camera (progressive BT656), using an
>> out-of-tree driver. There appears to be an issue with the interrupt
>> handling compared to my original driver.

>> I realise that you don't have the Marzen Expansion Board & don't
>> have an ov10635 camera. However, unfortunately, I don't have much
>> time that I can spend on this. Do any of the boards you have use a
>> progressive camera?

    No. Is there any way you can send us that expansion board? It seems
the only way we can get some progress on this issue.

> Oops, the comments about the captured image contents are my fault.
> However, the unhandled irq after stopping capture is still an issue.

    Thanks for letting us know.

> Regards
> Phil

WBR, Sergei


  reply	other threads:[~2013-05-21 14:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 21:01 [PATCH v5] V4L2: soc_camera: Renesas R-Car VIN driver Sergei Shtylyov
2013-05-17 21:01 ` Sergei Shtylyov
2013-05-20  7:31 ` phil.edworthy
2013-05-20  7:31   ` phil.edworthy
2013-05-20 13:07   ` Sergei Shtylyov
2013-05-20 13:07     ` Sergei Shtylyov
2013-05-21  9:51     ` phil.edworthy
2013-05-21  9:51       ` phil.edworthy
     [not found]     ` <OF0ABE628B.1C271A20-ON80257B72.002ED824-80257B72.003627CD@LocalDomain>
2013-05-21 12:13       ` phil.edworthy
2013-05-21 12:13         ` phil.edworthy
2013-05-21 14:47         ` Sergei Shtylyov [this message]
2013-05-21 14:47           ` Sergei Shtylyov
2013-05-28 14:08           ` phil.edworthy
2013-05-28 14:08             ` phil.edworthy

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=519B88E8.3040101@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.