When register platform driver in 2.6.31 kernal, suspend
and resume are not set for device driver.
The patch fix this issue by using platform driver's
suspend/resume rountine directly in otg driver.
Signed-off-by: Li Jun <r65092@freescale.com>
In virtual gpio irq init func, fix miscalculation for all GPIO pins.
In gpio chained irq handler, need mask, ack, umask
Signed-off-by: Robby Cai <R63905@freescale.com>
Policy min and max is set to current frequency.
emi.S use wrong register address
Some line miss at clock.c when port from 28 kernel.
Signed-off-by: Frank.Li <Frank.Li@freescale.com>
wm8580 is using regulators that can't change state. The
regulator driver doesn't handle this case well so it crashes
during regulator_bulk_enable. Eventually this will be fixed in the
regulator driver. For now, remove regulators from list in
wm8580 driver.
Fix spi_rw err. hw_write needs to return transferred data length.
Signed-off-by: Alan Tull <r80115@freescale.com>
Signed-off-by: Wallace Wang <r59996@freescale.com>
Move regulator control into codec drivers.
Move codec platform data to machine layer.
Remove unused fields from mxc_audio_platform_data.
soc multiple audio cards support:
dai_list is a list for all registered codec/cpu dais.
One codec/cpu dais can't be registered twice, so move the
cpu dai registering into imx-ssi.c/imx-esai.c
Fix ak4647_read_reg error.
Put ssi/esai mode in the cpu_dai private_data.
sgtl5000: Fix the power for MX35
1. MX35 vddio and vddd are directly connected to
external 3V3. It has no regulator control.
2. sgtl5000 needs some time to be ready after vdda
is switched on so msleep(1) is added before regiter
read/write.
3. On MX35 platform, vdda is from VCAM.
Signed-off-by: Alan Tull <r80115@freescale.com>
Signed-off-by: Wallace Wang <r59996@freescale.com>
Bootload may do ipu init to display something, add SRC reset here to
make sure ipu working well in BSP.
Signed-off-by: Jason Chen <b02280@freescale.com>
Simplified the partitioning mechanism and, as a side effect, made the
GPMI NAND Flash driver usable (it was always crashing the kernel).
Signed-off-by: Patrick Turley <patrick.turley@freescale.com>
The patch to add support for looking up consumers by device name
had the side effect of causing us to require a device which is
at best premature since at least cpufreq still operates outside
the device model. Remove that requirement.
Reported-by: Haojian Zhuang <haojian.zhuang@gmail.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
Follow the approach suggested by Russell King and implemented by him in
the clkdev API and allow consumer device supply mapings to be set up
using the dev_name() for the consumer instead of the struct device.
In order to avoid making existing machines instabuggy and creating merge
issues the use of struct device is still supported for the time being.
This resolves problems working with buses such as I2C which make the
struct device available late providing that the final device name is
known, which is the case for most embedded systems with fixed setups.
Consumers must still use the struct device when calling regulator_get().
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
Add basic support for integration with the regulator API to WM8580.
Since the core cannot yet disable biases when the CODEC is idle we
simply request and enable the regulators for the entire time the
driver is active.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
For best performance the DAC sloping stopband filter should be enabled
below 24kHz and not enabled above that so remove the user visible
control for this and do it autonomously in the driver.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
1) When using CSI->MEM to capture frames, the output frame resolution of
channel CSI->MEM should be the same with that of cropping input frame.
2) Enable to capture frames bigger than the cropped input frames.
Signed-off-by: Liu Ying <b17645@freescale.com>
(cherry picked from commit eee5a08306df7d9b1f23f463c9e9439e04293b57)
1)Update MXC V4L2 capture driver for 2.6.31 kernel.
2)Update ov3640 camera and ov2640 camera driver for 2.6.31 kernel.
Signed-off-by: Liu Ying <b17645@freescale.com>
irq handler should be re-register to the correct FB's ipu channel.
Signed-off-by: Jason Chen <b02280@freescale.com>
(cherry picked from commit 37140ac9a62a382a6d206aa0754eedac90a151c0)
This issue is caused by the improper PAD configuration.
Modify the PAD configurations and this issue disappeared.
Signed-off-by: Richard Zhu <r65037@freescale.com>
The battery charger driver contains 37xx specific battery charger
driver code that is incompatible with 378x/iMX23 and needs removal
Signed-off-by: Robert Lee <robert.lee@freescale.com>
ASRC can not work correctly when SPDIF_TX provides clock for asrc input
or output. The root cause is, the clock divider should be set as 6 if
SPDIF_TX provides the bit clock for ASRC, and be set as 7 if SPDIF_RX
provides the bit clock.
Signed-off-by: William Lai <b04597@freescale.com>
IPU channel disable should wait all channels finish busy state, should
wait for input dma interrupt first then output dma interrupt as the
correct sequence for all channels. This patch fix the DQ_BUF fail issue
in VPU unit test.
Signed-off-by: Jason Chen <b02280@freescale.com>
IPU channel disable should wait all channels finish busy state, should
wait for input dma interrupt as the correct finish signal for all
channels. This patch fix the DQ_BUF fail issue in VPU unit test.
Signed-off-by: Jason Chen <b02280@freescale.com>
Previous values being used were for STMP378x which has lower temperature
requirements. The updated values work with 105C temperatures but require
higher digital core voltages and lower maximum EMI clock speeds.:$lower
maximum EMI clock speeds.:
Signed-off-by: Robert Lee <robert.lee@freescale.com>
Change the code such that suspend and resume always set the CPU frequency
and voltage to the highest level.
Signed-off-by: Ranjani Vaidyanathan-RA5478 <Ranjani.Vaidyanathan@freescale.com>
Changing the LCD pin drive strengths to 8mA reduces
the amount of overshoot in half (15% and 50%) and
does not significantly change the rise and fall time
characteristics of the digital LCD signals
Signed-off-by: Frank Li <Frank.Li@freescale.com>