| Age | Commit message (Collapse) | Author |
|---|
|
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 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 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>
|
|
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>
|
|
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: 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)
|
|
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>
|
|
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>
|
|
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>
|
|
Not all regulators require a register trigger. Do not return error for
those cases.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
If a regulator is disabled, return zero voltage.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
In old PMIC versions the PERI regulator had a variable step voltage values
range.
Recent PMICs, including in all Digi modules, have a fix 25mv step size, so
remove the code that handled the variable step.
We don't have revision information from Dialog to ascertain when the
change happens, so we assume all supported PMICs are the new version.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
This commit changes the i2c address of the pmic (0x68 on the
third spin of the hardware).
It also adds a new file devices_ccxmx5x.[c,h] to place common
ccxmx51 and ccxmx53 initialization code.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
(cherry picked from commit e244c9d4e62bfd8be91c9b640cadb8590d0f328b)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
|
|
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
|
|
This commit reverts a single line hunk that got mixed with a different
patch and pushed by mistake.
It causes the da9052 drivers to crash when the I2C IMX module is loaded
instead of being built in.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
The driver enables by default a window filter that stops tracking movement
if it detects a pixel difference of 50 pixels between positions. Disabling
this "feature" fixes this Vantive.
This commit allows for the driver to be configured to use the window or
not, with the default being to disable it.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
If not connected the status reported in sysfs should be unknown.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
(cherry picked from commit 06c35f3d5c78ca6d22e812b2145dcf1493cd3e40)
|
|
User space monitoring tools will use the generated uevents to update
the battery status.
Tested on Android.
(cherry picked from commit f738425e8dd325f3f07427180be7bb677342da87)
|
|
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This commit fixes a problem with the overlay and the dual-head
support. The problem was related with the first initializtion
of the overlay framebuffer and was caused by a previous work-
arround that was done to support the dual-head video mode.
Fixes #40054.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
This code skips the execution of some code in the
mxc_ipuv3_fb driver when dual head is used. This code
was causing that the dual head was not working.
This patch was implemented time ago for the wimx51 but
had been lost while merging recent patches from FSL.
It is not clear why we need this. Needs to be investigated.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This commit adds support to control the LED4 and LED5 PWM
outputs of the DA9053 through the backlight driver.
This is used in the CCWi-i.MX53 JSK board to control the
backlight brightness of the LCD displays.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This battery driver is based on the da9052-battery.c driver by Dialog, and on the DVT battery scripts specific to the CCXMX53 JSK.
The following limitations apply:
- No battery temperature measurements are possible on the CCXMX53 JSK.
- No events notifications are implemented.
- No junction temperature or battery temperature monitoring.
- VBUS charging not supported by JSK.
- The only battery technology supported is Lithium-Ion.
- Only standard working temperatures are supported.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
This commit fixes the way the driver parses the command line
parameters.
It also adds the code to call the pin configuration functions
based on the bridge setup.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
Not that the implementation differs from the one from FSL.
This one is similar to what we have implemented in WinCE.
The procedure comes directly from Dialog.
We dont know why the method used by FSL in their QSB it
doesnt work in our module.
She the comments in the code for additional details.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
This commit implements a workarround to avoid that the video output
is shifted 1 pixel to the right.
This happens when the original code from FSL (after applying a patch)
and has been also observed in their Evaluation Board.
Their fix tries to correct a fuzzy VGA output.
In order to get the best video output we only apply the new code when
the configured output is the VGA interface.
This is the best fix I can implement at this point. This is the video
controller microcode and I dont know what they are exactly doing in
each configuration. We have to check with FSL for a better fix.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
blanking period""
This reverts commit ad3a2ef14bf1e74ec78ee4daf70a692c3200d554.
|
|
FG pos need be reset to 0 when channel disable, but it will lost old setting.
Signed-off-by: Jason Chen <b02280@freescale.com>
|
|
For split mode, if using vf/enc task, the display is not correct.
Signed-off-by: Jason Chen <b02280@freescale.com>
|
|
wait_event_interruptible_timeout function could be signal
return, so we need add ERESTARTSYS return value to let libc
retry sys call.
Signed-off-by: Jason Chen <b02280@freescale.com>
|
|
1) Current blank information should be unblank if
we return back from mxcfb_set_par() function
successfully.
2) Remove bypassing the suspend handling for
overlay framebuffer for Android.
3) Synchronize fb unblanking operation bewteen
Android early suspend and mxcfb_set_par() to
avoid fb being unblanked after early suspend
is done, as Android early suspend doesn't
guarantee fb cannot be operated after early
suspend.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
|
|
1) Fix race condition issue for enable/disable ipu clk.
2) Remove uninitializing MEM_FG_SYNC channel when
suspend for Android.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
|
|
set vga output gain to improve quality.
Signed-off-by: Jason Chen <b02280@freescale.com>
|
|
This commit adds preliminary support for the VGA interface
on the ccxmx53 modules, through the TVE decoder.
There are some pending patches that have to be applied on
the ipu drivers, in order to have a more clear image on
this interface.
Signed-off-by: Pedro Perez de Heredia <pedro.perez@digi.com>
|
|
A character device interface is needed for backwards compatibility with
the adc_test application.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
|
|
|
|
1) Current blank information should be unblank if
we return back from mxcfb_set_par() function
successfully.
2) Remove bypassing the suspend handling for
overlay framebuffer for Android.
3) Synchronize fb unblanking operation bewteen
Android early suspend and mxcfb_set_par() to
avoid fb being unblanked after early suspend
is done, as Android early suspend doesn't
guarantee fb cannot be operated after early
suspend.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
|
|
1) Fix race condition issue for enable/disable ipu clk.
2) Remove uninitializing MEM_FG_SYNC channel when
suspend for Android.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
|
|
Fix the issue of missing to increase open_count when vpu_open.
This is due to the patch of removing mx32 and mx37 code.
Signed-off-by: Sammy He <r62914@freescale.com>
|
|
change QCIF resolution size from 177X144 to 176X144
Signed-off-by: Yuxi Sun <b36102@freescale.com>
|
|
add QCIF 177x144 resolution for ov5642
Signed-off-by: Yuxi Sun <b36102@freescale.com>
|
