| Age | Commit message (Collapse) | Author |
|---|
|
is low"
Otherwise playing fullHD videos on HDMI crashes with:
[<800303cc>] (dump_backtrace+0x0/0x10c) from [<803d4104>]
(dump_stack+0x18/0x1c)
r7:8053a048 r6:8053a048 r5:0000000c r4:00000001
[<803d40ec>] (dump_stack+0x0/0x1c) from [<800891d4>]
(__alloc_pages_nodemask+0x524/0x57c)
[<80088cb0>] (__alloc_pages_nodemask+0x0/0x57c) from [<80031a4c>]
(__dma_alloc+0xf4/0x2b8)
[<80031958>] (__dma_alloc+0x0/0x2b8) from [<80031c38>]
(dma_alloc_writecombine+0x28/0x34)
[<80031c10>] (dma_alloc_writecombine+0x0/0x34) from [<801d51e0>]
(mxcfb_set_par+0xd8/0x464)
....
This reverts commit 7c2141d484fbfa03af5f83602162d9576564121b.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
|
|
The SIGKILL signal is received on system poweroff/reboot. If the thread
is not stopped, the schedule() gets interrupted and the thread executes
several consecutive times. It also fails to access the I2C bus printing
error messages on the console.
Making the thread TASK_UNINTERRUPTIBLE before schedule stops the multiple
executions, but still prints I2C access error messages sometimes, when
the thread is scheduled in the middle of the poweroff/reboot.
Stopping the thread on SIGKILL provides a clean shutdown. The thread
won't stop on suspend as a SIGKILL is not received.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Move the battery monitoring kernel thread schedule to the end of the
thread. Before the thread was sleeping just after the freezing check.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
This has the effect of losing the contents of RAM while in self refrsh
mode.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
This patch was provided by Dialog and it doesn't seem to be yet integrated
with Freescale upstream.
It basically does a write flush on a set of registers.
Dialog contact Christophe.Molle@diasemi.com
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
(cherry picked from commit 8d5aa68cad489a1bba040dd32c92b0dd565cc881)
|
|
This commit fixes problems with the LCD displays, where the
pixel format was being incorrectly set after the last
commit.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
(cherry picked from commit a61ef1553c8a65868fd195a05d4ae8f347b97466)
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This commit fixes a problem on the ccxmx5x where the pixel
format was incorrectly set for RGB666, RGB888 on VGA and
HDMI interfaces. For the LCDs it was properly set.
Fixes #41820.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This commit fixes a problem with the dual mode that was
happening in following scenario:
video=displayfb:disabled
video2=displayfb:LCD@LQ121K1LG11
ldb=dual,di=1,ch1_map=JEIDA
Here the image on the LVDS channel 1 was not correctly
represented because in this configuration, the data mapping
is taken from the CH0, instead of the CH1 as should be.
To workarround this problem, when the mode selected is dual
or split, we configure both channels with the data mapping
passed through the command line.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
(cherry picked from commit db349fbadeff2c94856f2a161e386b1a0f09475e)
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
(cherry picked from commit 93a8a2ae939a4e62c6ebb000e156d8efd02cab36)
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This foxes a kernel crash when both cameras are connected and the module removed.
Fixes #41834.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
(cherry picked from commit e9d86e3520636c877e11cda3ef6afbf86e09b133)
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This commit fixes some problems with some macros used
for the dual video.
It also corrects problems with the video memory mappings
that was causing problems when using the vga interface
with a resolution of 1680x1050 at 32 bpp.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
(cherry picked from commit ec0c204972183b5ba1d2ade83bd36a26a1ab410d)
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This reverts commit a3fe22ee824895aafdc1b788e19c081a2e6dd9da.
This commit was causing scheduling problems to gplay. Reverting it fixes
Alternatives to this revert include backporting further scheduling fixes
from 2.6.37, wait for a 2.6.35.15 release which will hopefully fix the
issue, or configuring the kernel with HAVE_AN_UNSTABLE_SCHED_CLOCK,
even though the clock is not really unstable.
|
|
This reverts commit fd72c5feeb61857dbcc4fac1c98157925fbb085e.
This commit depends on a3fe22ee824895aafdc1b788e19c081a2e6dd9da which
will be reverted next.
|
|
Conflicts:
arch/arm/plat-mxc/include/mach/gpio.h
arch/x86/kernel/cpu/mtrr/main.c
drivers/mmc/core/core.c
drivers/net/smsc911x.c
fs/proc/task_mmu.c
include/linux/pm_runtime.h
mm/memory.c
mm/mlock.c
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
And hold back from rewriting that confusing area of code.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
It is believed to improve the stability of the signals so that
they don't require external pull-ups. Specially for the cwme9210js
where the lines are connected to the Redpine chip without pull-ups.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
(cherry picked from commit cffa4f0a5ad8b057d519bac479fdd75c15e4e1ba)
|
|
1. Add DDR self-refresh mode and float pin operation when system idle
For audio playback use case on android r10.3, it can save 10mA@1.54V
about 15mW on DDRIO+ memory power, and 6.6mA@2.5V -16.5mW on VDD_REG
It can reduce more memory power consumption if cpu idle time is longer
2. remove the L1/L2 cache operation during suspend for mx53
The L1/L2 cache are powered by VDDA/VDDAL1 and they should be supplied
according to iMX53 datasheet, there is also no EMPG on MX53,
so it can be removed to improve system performance and power.
3. remap the suspend_iram_base as MT_MEMORY_NONCACHED instead of MT_HIGH_VECTORS
If the IRAM page is marked as Cacheable, the ARM cache controller will
attempt to flush dirty cache lines to DDR, so it can fill those lines with
IRAM instruction code. The problem is that the DDR is in self-refresh mode
and HighZ DDR IO PADs during system idle or suspend, so any DDR access
causes the ARM MPU subsystem to hang.
It needs to cherry-pick two patches(5a4aeb9f6,7c8d972d8) from community.
4. Add DDR self-refresh mode and float pin operation for mx53 ARD board,
and mx53 QS/Ripley board
This patch can resovle ramdom suspend/resume issue, since the early code
didn't consider the TLB missing case during suspend. It needs to save all
the M4IF/IO MUX registers firstly to make sure the page table entried into
TLB, and then enter DDR self-refresh mode.
Signed-off-by: Wayne Zou <b36644@freescale.com>
|
|
The commit f1a2481c0 sets up the default flags for MT_MEMORY and
MT_MEMORY_NONCACHED memory types. L_PTE_USER flag is wrongly
set as default for these entries so remove it. Also adding
the 'L_PTE_WRITE' flag so that these pages become read-write
instead of just being read-only
[this stops them being exposed to userspace, which is the main
concern here --rmk]
Reported-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
|
|
This patch populates the L1 entries for MT_MEMORY and MT_MEMORY_NONCACHED
types so that at boot-up, we can map memories outside system memory
at page level granularity
Previously the mapping was limiting to section level, which creates
unnecessary additional mapping for which physical memory may not
present. On the newer ARM with speculation, this is dangerous and can
result in untraceable aborts.
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
|
|
During the platform boot up, during the platform does DA9053 Read/Write
operation, it writes slave address and wait for ACK . Instead of ACK
PMIC sends NAK. A workaround fix is provided as a part of retries
fix I2C NAK for very first access.
Also fix a bug when the system fails to start after software shutdown.
Signed-off-by: Wayne Zou <b36644@freescale.com>
|
|
Fix the NULL pointer reference when there is no
struct mxc_pm_platform_data defines on MX5 machines.
Signed-off-by: Wayne Zou <b36644@freescale.com>
|
|
restructure the pm suspend/resume routines as mxc_pm_platform_data,
so split the SOC pm routines from machine pm routines.
Signed-off-by: Wayne Zou <b36644@freescale.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
A reported Dialog bug that will make the PMIC not power up again on some
cases is worked around in this way.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
The CTS and RTS pins for UARTS0 and 1 are both set in their respective
select input registers. When both pins are reconfigured, only the last
IOMUX configuration remains.
This change makes the first IOMUX configuration take effect, while the
second IOMUX configuration will affect the pad control but not the select
input control.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This commti workarrounds a problem found with the video
interface where the pad settings (signal strength) needs to
be set differently depending on the display resolution to
avoid that incorrect pixels are shown in the screen.
Similar problem happens with WinCE.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Newer U-Boot will set cold resets by defaults. This commit allows a
kernel override back to the default setting.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
On the ccxmx53, LDO9 is not supplying the touch. LDO8 is, but it also
supplies other elements.
Do not allow the touch driver to modify power supply settings as this
assumes the touch is powered exclusively by a regulator while on the
ccxmx53 it is not the case.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Depending on the module revision, the PMIC has one I2C address or another.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Some regulators have the upper,lower and mask values from old datasheets
belonging to old parts.
This commit corrects them to the latest available datasheet. With this
change the values reported by the kernel now match the PMIC regulator
registers configuration and the measured values in U-Boot.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Strangely, if we don't enable and disable the I2C clock before suspend
the target halts while suspending.
This needs to be investigated although this commit is a workaround that
allows to continue working.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
The PMIC suspend functions do some very peculiar things that are not
needed on the ccxmx53 platforms.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
These comments help see that these functions need not be called for
the ccxmx53 platforms.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Not all regulators require a register trigger. Do not return error for
those cases.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
