From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org, linux-omap@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, tony@atomide.com
Subject: [PATCH v3 0/3] OMAP 3 CSI-2 configuration
Date: Sun, 7 Oct 2012 23:07:30 +0300 [thread overview]
Message-ID: <20121007200730.GD14107@valkosipuli.retiisi.org.uk> (raw)
Hi all,
This is an update to an old patchset for CSI-2 configuration for OMAP 3430
and 3630r. The patches have been tested on the 3630 only so far, and I don't
plan to test them on 3430 in the near future.
I changed quite a few things after a discussion with Tony a few days ago.
The ISP driver now maps the relevant register from the control block and
uses it directly. Which register is required is determined by the ISP
revision: this is theoretically wrong, but since we only support OMAP 3430
and 3630 which have different ISPs it should be all right. If we need to
support more OMAPs in the future we could revisit how that's being
determined.
Comments, questions and other kind of feedback is very welcome.
Kind regards,
--
Sakari Ailus
e-mail: sakari.ailus@iki.fi XMPP: sailus@retiisi.org.uk
next reply other threads:[~2012-10-07 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 20:07 Sakari Ailus [this message]
2012-10-07 20:07 ` [PATCH v3 1/3] omap3isp: Add CSI configuration registers from control block to ISP resources Sakari Ailus
2012-10-08 22:06 ` Tony Lindgren
2012-10-08 22:22 ` Sakari Ailus
2012-10-07 20:07 ` [PATCH v3 2/3] omap3isp: Add PHY routing configuration Sakari Ailus
2012-10-09 0:17 ` Laurent Pinchart
2012-10-09 6:08 ` Sakari Ailus
2012-10-07 20:07 ` [PATCH v3 3/3] omap3isp: Configure CSI-2 phy based on platform data Sakari Ailus
2012-10-09 0:33 ` Laurent Pinchart
2012-10-09 6:03 ` Sakari Ailus
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=20121007200730.GD14107@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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