- Reversed ordering in which clocks are disabled. Child clocks should
be disabled before parent (root) clocks.
Signed-off-by: Danny Nold <dannynold@freescale.com>
This fixes some braindead bug in gst_mfw_v4lsink or libipu or some other
userspace code (or maybe a hidden kernel thing) where it cannot work out
what it's doing unless the overlay is /dev/fb2.
Ahmed Ammar originally wrote this for our .35 port but we're backporting it
now in lieu of .35 actually being production ready. Thanks Ahmed!
When the system enters low bus frequency mode by executing the
following operations, the system enters dead loop to check
arm_podf_busy bit:
1. Store the rootfs on SD card.
2. type "echo 8 > /proc/sys/kernel/printk"
3. type "echo 1 > /sys/devices/platform/mxc_dvfs_core.0/enable"
4. type "ifconfig eth0 down"
5. type "echo 1 > /sys/class/graphics/fb0/blank"
6. The system enters low bus frequency mode. And it keeps
to print "ARM_PODF still in busy!!!!"
sys_accept4() was added in kernel 2.6.28, but ARM was not updated
to include it. The number and types of parameters is such that
no ARM-specific processing is needed, so wiring up sys_accept4()
just requires defining __NR_accept4 and adding a direct call in
the syscall entry table.
to modularize these in the grand scheme of things even if this is what Ubuntu
tends to do (it is not as if we have PCI slots and potential for multiple
different options).
MX51 will hang if gpu is running when emi_fast was disabled,
add depends on clock tree to fix it.
Signed-off-by: Zhang Jiejing <jiejing.zhang@freescale.com>
* 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
with very high resolution displays, power management causes serious performance
regressions which we cannot really accept when it comes to video playback
and other features. However, Smartbook display resolution is low enough and
power usage is important enough that we should leave it on for those systems
* Make lid switch, power key and wireless switch into a real input device as it was in the deep dark past..
* weird regression: something changed in GNOME, so you can't suspend by dropping the lid (the option has been
removed from gnome-power-preferences). And because if you suspend with the lid up, the lid switch is not set
to wake, lifting the lid won't unsuspend. The only way to get the system back is with the power key. Damn
you GNOME developers.
* weird behavior: smarttop will immediately come back after suspend
