Enable pixel multiplexing in 15/16bpp modes when pixclock is over 115MHz
on Trio3D (86C365) cards to fix artifacts on the left side of screen.
Signed-off-by: NOndrej Zary <linux@rainbow-software.org>
Acked-by: NOndrej Zajicek <santiago@crfreenet.org>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Add support for S3 Trio3D (86C365) cards to s3fb driver. Tested with one 4MB card.
Signed-off-by: NOndrej Zary <linux@rainbow-software.org>
Acked-by: NOndrej Zajicek <santiago@crfreenet.org>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Maximize virtual vertical framebuffer size during init to allow fast scrolling
(accelerated by panning).
Signed-off-by: NOndrej Zary <linux@rainbow-software.org>
Acked-by: NOndrej Zajicek <santiago@crfreenet.org>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

This allows the driver to work in multi-domain PCI
configurations.
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

This allows the driver to work in multi-domain PCI
configurations.
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

This allows the driver to work in multi-domain PCI
configurations.
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Instead of just plain NULL.
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Instead of just plain NULL.
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Instead of just plain NULL.
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

And use vga_{r,w}().
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Add support for ZGI Z9 DDR2 POST. The init sequence is from XGI's
xgifb driver.

Tested with ARM board using a PCI card with XGI Z9s and 32 MB DDR2
memory. After a cold reset the POST succeeds.
Signed-off-by: NAaro Koskinen <aaro.koskinen@iki.fi>
Cc: Thomas Winischhofer <thomas@winischhofer.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Move DDR2 register setting code into separate subroutines. No changes
in functionality.
Signed-off-by: NAaro Koskinen <aaro.koskinen@iki.fi>
Cc: Thomas Winischhofer <thomas@winischhofer.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Detect the XGI Z9 RAM type as "documented" by the XGI's xgifb driver.
Signed-off-by: NAaro Koskinen <aaro.koskinen@iki.fi>
Cc: Thomas Winischhofer <thomas@winischhofer.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Z7 and Z9 have the same PCI ID, so additional checking is needed to
detect Z9. The method was "documented" in XGI's xgifb driver.
Signed-off-by: NAaro Koskinen <aaro.koskinen@iki.fi>
Cc: Thomas Winischhofer <thomas@winischhofer.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Move XGI POST RAM type detection into a separate subroutine to make
further code changes easier. No changes in functionality
Signed-off-by: NAaro Koskinen <aaro.koskinen@iki.fi>
Cc: Thomas Winischhofer <thomas@winischhofer.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Currently there is no indication if R/W test fails during POST. This can
happen e.g. when user plugs in a card with unsupported type of memory.
Since the driver will be unusable, it's better to fail the whole POST
if the memory cannot be configured properly.
Signed-off-by: NAaro Koskinen <aaro.koskinen@iki.fi>
Cc: Thomas Winischhofer <thomas@winischhofer.net>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NKirill A. Shutemov <kirill@shutemov.name>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Signed-off-by: NKirill A. Shutemov <kirill@shutemov.name>
Acked-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

Remove incorrect Matrox G200eV support that was previously added by
commit e3a19388

A serious issue with the incorrect G200eV support that reproduces on the
Matrox G200eV equipped IBM x3650 M2 is the total lack of text (login
banner, login prompt, etc) on the console when X is not running and
total lack of text on all of the virtual consoles after X is started.

Any concerns that the incorrect code (upstream since October 2008) has
been successfully used on non-IBM G200eV equipped system(s) appear to be
unwarranted.  In addition to the serious/non-intermittent nature of
issues that have been spotted on IBM systems, complete removal of the
incorrect code is clearly supported by the following Matrox (Yannick
Heneault) provided input:
 "It impossible that this patch should have work on a system.
 The patch only declare the G200eV as a regular G200 which is
 not case. Many registers are different, including at least the
 PLL programming sequence. If the G200eV is programmed like a
 regular G200, it will not display anything."

v1 - Initial patch that removed the incorrect code for _all_
     G200eV equipped systems.
v2 - Darrick Wong provided patch that blacklisted the incorrect
     code on G200eV equipped IBM systems leaving it enabled on
     all G200eV equipped non-IBM systems.
v3 - Same code changes included with v1 plus additional
     justification for complete removal of the incorrect code.
Signed-off-by: NGary Hade <garyhade@us.ibm.com>
Cc: Darrick J. Wong <djwong@us.ibm.com>
Cc: Krzysztof Helt <krzysztof.h1@wp.pl>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Yannick Heneault <yannick_heneault@matrox.com>
Cc: Christian Toutant <ctoutant@matrox.com>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>

Add dss.dpll4_m4_ck (DSS FCLK) initialization for OMAP4. This is used
to compute the pixel clock for DPI interface and also to reconfigure
the DSS FCLK to the desired rate, corresponding to the rate computed
for pixel clock.

Adding these cpu_is_44xx() checks are meant to be temporary, until a
cleaner implementation to manage these checks are added. Currently this
is needed to get DVI display running on OMAP4 PandaBoard
Signed-off-by: NRaghuveer Murthy <raghuveer.murthy@ti.com>
[tomi.valkeinen@ti.com: minor changes due to conflicts]
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>

OMAP2 does not have dpll4_m4_ck source clock for dss functional clock,
but later OMAPs do. Currently we check for cpu type in multiple places
to find out if dpll4_m4_ck is available.

This patch cleans up dss.c by using the fact that dss.dpll4_m4_ck
pointer is NULL on OMAP2. This allows us to remove many of the cpu
checks.
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>

Replace EXTRA_CFLAGS with ccflags-y.
Signed-off-by: Nmatt mooney <mfm@muteddisk.com>
Acked-by: NWANG Cong <xiyou.wangcong@gmail.com>
Signed-off-by: NMichal Marek <mmarek@suse.cz>

change from original version -- by advice of Paul Mundt
1. remove videomemorysize definitions
2. remove unifb_enable and unifb_setup
3. use dev_warn instead of printk in fb driver
4. remove judgement for FB_ACCEL_PUV3_UNIGFX
5. adjust clk_get and clk_set_rate calls
6. add resources definitions
7. remove unifb_option
8. adjust register for platform_device
9. adjust unifb_ops position and unifb_regs assignment position
Signed-off-by: NGuan Xuetao <gxt@mprc.pku.edu.cn>
Acked-by: NArnd Bergmann <arnd@arndb.de>

Supports YCbCr420sp, YCbCr422sp, and YCbCr44sp, formats
(bpp = 12, 16, and 24) respectively.

When double-buffering both Y planes appear before the C planes (Y-Y-C-C),
as opposed to  Y-C-Y-C.

Set .nonstd in struct sh_mobile_lcdc_chan_cfg to enable YUV mode, and use
.bpp to distiguish between the 3 modes.
The value of .nonstd is copied to bits 16-31 of LDDFR in the LCDC and
should be set accordingly.
.nonstd must be set to 0 for RGB mode.

Due to the encoding of YUV data, the framebuffer will clear to green
instead of black.

In YUV 420 mode, panning is only possible in 2 line increments.
Additionally in YUV 420 mode the vertical resolution of the framebuffer
must be an even number.
Signed-off-by: NDamian Hobson-Garcia <dhobsong@igel.co.jp>
Signed-off-by: NPaul Mundt <lethal@linux-sh.org>

calling the platform registration of HDMI driver from core
during initialization.
Signed-off-by: NMythri P K <mythripk@ti.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>

Adding kconfig and makefile changes to add support for HDMI in OMAP4.
Signed-off-by: NMythri P K <mythripk@ti.com>
Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>