Re: [PATCH v2 15/28] drm/i2c: tda998x: use the tda998x videoformat when cea mode

From: Russell King - ARM Linux
Date: Mon Jan 13 2014 - 11:13:53 EST


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@xxxxxxxxxxxxxxxx> 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".
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/