From: Ian Molton <ian.molton@codethink.co.uk>
To: linux-media@vger.kernel.org
Cc: William Towle <william.towle@codethink.co.uk>,
mchehab@redhat.com, hans.verkuil@cisco.com,
sylvester.nawrocki@gmail.com, g.liakhovetski@gmx.de,
vladimir.barinov@cogentembedded.com
Subject: RFC: soc_camera, rcar_vin, and adv7604
Date: Wed, 9 Jul 2014 17:42:25 +0100 [thread overview]
Message-ID: <20140709174225.63a742ce09418cff539bb70a@codethink.co.uk> (raw)
Hi folks,
My colleague and I are trying to work out what to do to support the following combination:
soc_camera + rcar_vin for capture, and the mainline adv7604 driver (which we have modified to successfully drive the adv7612).
The problem we face is that the 7604 driver uses the new "pads" API, but soc_camera based drivers like rcar_vin do not.
Obviously, there are a few approaches we could take, but we could use some guidance on this.
One approach would be to bodge some non-pads older API support into the 7604 driver. This would probably be the easiest solution.
A better approach might be to add pad API support to soc_camera, but it seems to me that the soc_camera API does not abstract away all of the areas that might need to be touched, which would lead to much pad-related churn in all the other soc_camera drivers.
The codebase is rather large, and we're struggling to see a clear path through this. Whatever we do, we would like to be acceptable upstream, so we'd like to open a discussion.
Perhaps a soc_camera2 with pads support?
--
Ian Molton <ian.molton@codethink.co.uk>
next reply other threads:[~2014-07-09 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 16:42 Ian Molton [this message]
2014-07-09 20:34 ` RFC: soc_camera, rcar_vin, and adv7604 Guennadi Liakhovetski
2014-07-10 10:12 ` Ian Molton
2014-10-15 17:03 ` William Towle
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=20140709174225.63a742ce09418cff539bb70a@codethink.co.uk \
--to=ian.molton@codethink.co.uk \
--cc=g.liakhovetski@gmx.de \
--cc=hans.verkuil@cisco.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sylvester.nawrocki@gmail.com \
--cc=vladimir.barinov@cogentembedded.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 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.