All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Towle <william.towle@codethink.co.uk>
To: g.liakhovetski@gmx.de
Cc: ian.molton@codethink.co.uk,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-media@vger.kernel.org, mchehab@redhat.com,
	hans.verkuil@cisco.com, sylvester.nawrocki@gmail.com,
	vladimir.barinov@cogentembedded.com
Subject: Re: RFC: soc_camera, rcar_vin, and adv7604
Date: Wed, 15 Oct 2014 18:03:53 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1410151757420.5023@xk120> (raw)
In-Reply-To: <20140710111218.60572c1fc814de541b886147@codethink.co.uk>


   Earlier this year, a colleague and I sought advice on the
combination of "soc_camera + rcar_vin for capture, and the mainline
adv7604 driver (which we have modified to successfully drive the
adv7612).", with reasonable results, noting that we might move
towards "a soc_camera2 with pads support?".

   For the next stage of work, we have created a test branch that
contains an alternative version of rcar_vin.c, based on
v4l2-pci-skeleton.c [from the Documentation tree] and with device
tree initialisation code transplanted back into it.

   This presently creates device nodes happily, and if code from
soc_camera.c is transplanted, we observe appropriate low-level
interaction with hardware prompted by code in adv7604.c.

   I have not yet progressed to seeing calls to rcar_vin_irq()
succeed, however, and wondered if you could shed light onto the places
I might have overlooked?

Cheers,
   Wills.
   (William Towle; william.towle@codethink.co.uk)

      reply	other threads:[~2014-10-15 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 16:42 RFC: soc_camera, rcar_vin, and adv7604 Ian Molton
2014-07-09 20:34 ` Guennadi Liakhovetski
2014-07-10 10:12   ` Ian Molton
2014-10-15 17:03     ` William Towle [this message]

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=alpine.DEB.2.02.1410151757420.5023@xk120 \
    --to=william.towle@codethink.co.uk \
    --cc=g.liakhovetski@gmx.de \
    --cc=hans.verkuil@cisco.com \
    --cc=ian.molton@codethink.co.uk \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=sylvester.nawrocki@gmail.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.