Age | Commit message (Collapse) | Author |
|
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>
|
|
Rootcause:
It's memory overflow and overwrite some other memory space by da9053 drver.
The code does not allocate memory for priv->regulators, which
will cause the following code priv->regulators[i] = regulator_register(..
overwrite other memory place.
Signed-off-by: Wayne Zou <b36644@freescale.com>
|
|
- Fixed PxP input left coordinate value. Was previously being incorrectly
computed such that the value would be incorrect when using 16bpp RGB and an
X coordinate that is offset from 4-pixel alignment by 1 (e.g. x=1, x=5).
The resulting effect was that updates meeting this criteria would be
drawn to the EPD panel shifted to the right by 1 pixel.
Signed-off-by: Danny Nold <dannynold@freescale.com>
|
|
Add print message when ioremap or shared memory alloc fail.
Signed-off-by: Richard Zhao <richard.zhao@freescale.com>
|
|
Fix clock rate setting on mxs-mmc driver.
Previously, if div2 was zero the value for TIMING_CLOCK_RATE
would have been 255 instead of 0.
Also the limits for div1 (TIMING_CLOCK_DIVIDE) and
div2 (TIMING_CLOCK_RATE + 1) where not correctly defined.
Can easily be reproduced on mx23evk: default clock for high speed
sdio cards is 50 MHz.
With a SSP_CLK of 28.8 MHz (default), this resulted in an actual
clock rate of about 56 kHz.
Signed-off-by: Tony Lin <tony.lin@freescale.com>
|
|
1.add AVI and AIF support.
2.add edid 4-block reading support.(not test)
For RGB input fmt support, pls input cmdline like:
video=mxcdixfb:RGB24,1024x768M@60
For YUV input fmt support, pls input cmdline like:
video=mxcdixfb:VYU444,1024x768M@60
Signed-off-by: Jason Chen <b02280@freescale.com>
|
|
1.add VYU444 fmt to support Sii902x hdmi yuv format
2.make pixel clock from internal ipu clock more accurate
Signed-off-by: Jason Chen <b02280@freescale.com>
|
|
add camera embed rotate function: nomarl, flip, mirror, flip&mirror
Signed-off-by: Yuxi Sun <b36102@freescale.com>
|
|
change camera rotate functions always return success.
Signed-off-by: Yuxi Sun <b36102@freescale.com>
|
|
- With FB_POWERDOWN_DISABLE is set as the powerdown delay (disabling the EPDC
driver from powering down), the EPDC driver was having problems going into
suspend. Any request to blank the EPDC driver would result in a timeout
and an error status. And subsequent attempts to send updates to the driver
would fail, as the driver's power state was incorrect. This patch prompts
the EPDC driver to be disabled when the blanking state is changed to
FB_BLANK_POWERDOWN and FB_POWERDOWN_DISABLE is set. Resultingly, the correct
driver power state is maintained and suspend/resume works correctly.
Signed-off-by: Danny Nold <dannynold@freescale.com>
|
|
Framebuffer suspend event comes before framebuffer
blank event when system entering suspend mode.
So, if another driver calls FB_EVENT_BLANK
notifier chain, i.e, Android IPUv3 fb driver,
the suspend and blank event handlers registered
in TVE driver will be called. We used to disable
TVE clock in suspend handler, so it causes system
hang when we try to access TVE register when go
to blank handler. This patch fixes this issue.
Signed-off-by: Liu Ying <Ying.Liu@freescale.com>
|
|
This patch add pm_cap for mx_sdhci driver, so the client mmc driver can use
sdio_set_host_pm_flags() to set the MMC_PM_KEEP_POWER.
Also if the driver found MMC_PM_WAKE_SDIO_IRQ in pm_flags,
it should not unregister irq of this host, since the client
maybe use this irq to support wake up.
Signed-off-by: Zhang Jiejing <jiejing.zhang@freescale.com>
|
|
When using SNAPSHOT update scheme, submitting FULL mode updates can easily
lead to an endlessly looping sequence of collisions if any updates are active
when the new FULL mode update is submitted. Thus, we must first flush any
updates out before submitting a new FULL mode update.
Signed-off-by: Danny Nold <dannynold@freescale.com>
|
|
The vpu code in driver for mx32/mx37 is out of date already, and
we won't support the platforms, so clean the code for removing it.
Signed-off-by: Sammy He <r62914@freescale.com>
|
|
improve mpr121 capacitive key sensitivity by change threshold of
release and touch and add a quick charge bit in init which is not
documented in MPR121's data sheet.
move macro define from header to source file.
Signed-off-by: Zhang Jiejing <jiejing.zhang@freescale.com>
|