From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 15/28] drm/i2c: tda998x: use the tda998x video format when cea mode
Date: Mon, 13 Jan 2014 16:13:34 +0000 [thread overview]
Message-ID: <20140113161333.GA15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140113170707.10b908dc@armhf>
On Mon, Jan 13, 2014 at 05:07:07PM +0100, Jean-Francois Moine wrote:
> On Sat, 11 Jan 2014 18:18:32 +0000
> Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
>
> > On Thu, Jan 09, 2014 at 12:04:48PM +0100, Jean-Francois Moine wrote:
> > > This patch uses the tda998x video format tied to the CEA mode.
> > > This reduces the number of i2c exchanges.
> >
> > It is my understanding that one of the major design goals of this driver
> > is to avoid the use of such a table, and therefore this change is
> > undesirable by the original driver authors. This is more a comment for
> > Rob to pick up on.
>
> I retrieved a message from Rabeeh who got this description from NXP
> (http://www.solid-run.com/phpbb/viewtopic.php?f=9&t=1205&start=10
> Thu Mar 28, 2013 10:59 am):
>
> 1. write register FF of CEC device to &h87.
> (68ff = 87h) -> activate all clock tree inc HDMI ones so you can then use HDMI device
> 2. select page 00 of HDMI device : write 00 in FF
> (e0ff =00h)
> 3. write register A0 of HDMI device to select predefined format :
> (e0a0 = 06h) -> select a predefined 1080p60 format
> 4. write registers A5 and A6 with total number of pixels per line (or greater value)
> (e0a5 = 08h)
> (e0a6 = 97h) for example
> 5. write register TBG_CTRL1 of HDMI device to select resync method
> (e0cb = 7ch) -> select
> 6. write registers VIP_CTRL to configure RGB input ports :
> (e020 = 45h) -> select VP port configuration
> (e021 = 01h)
> (e022 = 23h)
> 7. write register VIP_CTRL3 to 20h vto select external SP sync method
> (e023 = 20h)
Sorry, I don't see what bearing your response to my reply has.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-13 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 11:04 [PATCH v2 15/28] drm/i2c: tda998x: use the tda998x video format when cea mode Jean-Francois Moine
2014-01-11 18:18 ` Russell King - ARM Linux
2014-01-13 16:07 ` Jean-Francois Moine
2014-01-13 16:13 ` Russell King - ARM Linux [this message]
2014-01-13 16:22 ` Jean-Francois Moine
2014-01-13 16:35 ` Russell King - ARM Linux
2014-01-13 17:24 ` Jean-Francois Moine
2014-01-13 17:46 ` Russell King - ARM Linux
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=20140113161333.GA15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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