siihdmi: don't reconfigure the SII9022 just because there was a mode change if the mode is identical
ipuv3fb: default to a real 640x480 mode and not a "dummy" xres/yres
modedb: move cea modes to an extern so it only gets included once in the kernel
also: whitespace police
- Remove tty_buffer_request_room() in mxcuart_readdma_callback()
tty_insert_flip_string will call tty_buffer_request_room() in
his loop, but if we call it here, it will return 0, and we
will lost some read data.
- Remove tasklet when dma_writeback, it's will cause hci lost data
when write(tx).
since when this dma callback maybe re-order the next buffer data,
it will mess up data, make it to a direct call to perpare next
dma buffer.
Signed-off-by: Zhang Jiejing <jiejing.zhang@freescale.com>
The user mode libsahara library relied on header file
drivers/mxc/security/sahara2/include/sahara.h. However, to make
the lib build after headers_install step and to remove dependency on
kernel source, moved this header to include/linux/mxc_sahara.h.
These are the necessary changes in the SAHARA driver to use the new
header file in the new location.
Signed-off-by: Anish Trivedi <anish@freescale.com>
To allow SCC2 and SAHARA drivers to work as loadable modules, needed
to add GPL license to SAHARA driver, export a couple of functions
from SCC2 driver, and the following data buffer mapping change in
SAHARA driver:
When compiled as a loadable module, a data buffer to be DMA'ed in the
SAHARA driver may not be in the kernel direct-mapped region but in
the "Kernel module space" between TASK_SIZE and high_memory-1
(see http://www.arm.linux.org.uk/developer/memory.txt). In this
scenario, the driver canno simply use the __pa macro to obtain
the physical address. It must walk the page tables to find the
page and use the page_to_phys function to find the physical
address that corresponds to the data buffer.
Signed-off-by: Anish Trivedi <anish@freescale.com>
This patch aligns IDMAC burst size and DMFC FIFO burst
size to get better performance and workarounds black
flash issue when playing video on DP-FG with full
screen mode at 1024x768M@60.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
(cherry picked from commit 0e81c738566c2c97541dd92a5978c756b5c22e76)
(cherry picked from commit bbf3e59476f8e2b2453bd5a90664514ed3568207)
Conflicts:
drivers/mxc/ipu3/ipu_prv.h
This patch increases IDMAC burst size from 16 pixels to
32 pixels for RGBP pixel format and increases DMFC burst
size to 128 pixels to workaround 1080P60 display video
black flash issue.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
(cherry picked from commit c9fbed971c5a1adf7c727a6b1eba67e179bd1502)
The new microcode fix some easy hang issues.
Signed-off-by: Richard Zhao <richard.zhao@freescale.com>
(cherry picked from commit a48455dbea90720cba4be3e827e8b90e6abffd7d)
(cherry picked from commit cf09e2bac1cac560c6019332c37676b919700dda)
If you disable display, the display port's pin may keep high voltage which
may cause power leakage. Fix this issue by make all pin go into low level
after display disable.
Signed-off-by: Jason Chen <b02280@freescale.com>
(cherry picked from commit 165df9e8d525082e70a165516e2bcd1d0529b148)
This patch increases IDMAC burst size from 16 pixels to
32 pixels for RGBP pixel format and increases DMFC burst
size to 128 pixels to workaround 1080P60 display video
black flash issue.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
(cherry picked from commit c9fbed971c5a1adf7c727a6b1eba67e179bd1502)
With MMU enabled, there is no need to reserve memory for GPU
at boot time
Signed-off-by: Zhou, Jie <b30303@freescale.com>
(cherry picked from commit 326da1d885108399f4e22d10a8fe341a7a110ffc)
pending indicate the timer has been fired but clock not yet disabled.
This patch fixs the bug that sometimes in irq handle it tries to enable
clock and cause BUG.
Signed-off-by: Richard Zhao <richard.zhao@freescale.com>
(cherry picked from commit 4b73c7a14fdebbd1240dbb1f5e4efa5b7a65f63c)
seperate interrupt handling and clk_enable for Z160 and Z430
Signed-off-by: Zhou, Jie <b30303@freescale.com>
(cherry picked from commit 7da21af984a50ffb166ab1a088cd2c5d4313537b)
FlashPlayer 11.05 BSP has been fixed to support 32-bit modes so it will function
correctly on Smarttop now. GPU performance hit is still noticable but the extra
colour definition more than makes up for it. Smartbook is not affected.
This reverts commit 1ce3ee7a5a.
* 720p and 1080p are now attempted on DVI monitors on the revelation that some DVI monitors can display real CEA-style modes
* use the fb_find_best_nearest_mode function to better select resolutions and refresh rates
* cleanups
The intent is that if you have a native panel resolution of 1920x1080@60 but this cannot
be displayed, you can find the nearest resolution with the HIGHEST refresh rate (fb_find_nearest_mode
only selects the CLOSEST refresh rate). It also, by virtue of some rather unintended
side effect, picks better matches (1680x1050->1440x900) than find_nearest (1680x1050->1280x1024)
when it comes to widescreen modes.
small optimizations come with this:
* no longer redundantly recalculate refresh rate just to print it when setting resolution
* can use siihdmi_dump_single_modeline to print the modeline for Setting Resolution (more descriptive)
* less variables in use where we don't need var but have mode
* less data copying where we don't need var but have mode (since fb_videomode_to_var sets ~15 fields from mode)
* more const variables passed to functions
*
* use CEA mode 4 (720p60) instead of 19 (720p50) to improve compatibility for fallback mode
* Remove IPU bandwidth warning as this has been worked around to some degree in other parts of the kernel
* Refactor CEA duplicate culling such that on DVI monitors, the CEA mode is removed instead of the IT mode
* Switch siihdmi.useitmodes=1 to force DVI culling behavior on
* Do not enforce lower_margin limit for HDMI on DVI monitors
Due to performance issues, disable 1080p output by default, we will choose a
720p mode first, and if we can't find that, we then try to choose a native
output, and barring that, we default to 1280x720. You should still be able to
add siihdmi.teneighty=1 to your bootargs if you wish to output in 1080p
The root cause is endless GSL_INTR_BLOCK_YDX_CP interrupt.
Apply interrupt status read work around only when yamato started.
Signed-off-by: Richard Zhao <richard.zhao@freescale.com>
The GPU hang when run two cubes together with one video playback.
According to the suggestion from AMD, we'd better not read register
when GPU active, especially for CP block.
Signed-off-by: Zhou, Jie <b30303@freescale.com>
Refresh rate nearness is not calculated or reset when nearest resolution
changes.
This patch resets the refresh rate differential measurement whenever a
new nearest resolution is discovered. This fixes two error cases;
first, wherein the first mode's refresh rate differential is never
calculated and second, when the closest refresh rate from a previous
nearest resolution is erroneously preserved.
Signed-off-by: Andrew Kephart <andrew.kephart@alereon.com>
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
The previous fix of 800x600 fixes the frame buffer issue, but I had the x and
y resolutions switched, and since 640x480 uses less memory, switch to that.
The initial framebuffer is set to 320x240. This seems to cause issues with
plymouth and displaying text, so increase it to default to 800x600. This fixes
the headless boot issue.
* prep for 2.6.35 and a coexisting "sii9022" driver from Freescale by calling ours "siihdmi" as per the filename
* never put the chip into D3 power off state if we cannot hotplug the chip out of it
* semi-catch setting a mode with a null fb_videomode argument, since this is impossible to perform (there may be other places this needs handling, and there should be a healthy fallback)
* don't perform fb_videomode_to_var for screen blanking, and simplify blanking functions to not require fb_videomode_to_var since they do not actually use them
