Chuanxiao Dong [Mon, 20 Feb 2012 06:27:39 +0000 (14:27 +0800)]
mmc: add a sysfs entry to show write reliability
BZ: 24365
add a sysfs rel_set in /sys/block/mmcblk0/device/ to show the
write reliability.
If bit0 of rel_set is 1, then write reliability for user data
area is enabled.
Change-Id: I02700b7597499d5660b4ee46a781f6c2bb002b88
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/35851
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Thu, 16 Feb 2012 07:42:19 +0000 (15:42 +0800)]
mmc: change trim timeout time
BZ: 24352
When use TRIM in eMMC, timeout value should be defined in ext_csd
register but not a write block timeout value. Change to use this.
In the mean while, enable erase_group_def to use high capacity erase
group size to improve trim performance
Change-Id: I29c736a0609ebf6936562009e9030b6db08b329c
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/35837
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jeremie GARCIA [Fri, 27 Jan 2012 13:09:52 +0000 (14:09 +0100)]
[PORT FROM R2] SDIO: Enable the manual suspend/resume by default for SDIO cards.
BZ: 18765 17650
By enabling the manual suspend/resume of the mmc driver for sdio
slot, the sdio card will not be powered OFF on suspend and powered
ON on resume, even if the sdio driver has been removed from the kernel.
This feature is very useful for sdio modules of non-removable cards.
So it is better to keep the power management of the SDIO card, on
suspend / resume, up to the sdio driver.
Orig-Change-Id: Ic003c4b4e933814bc35bbb3f824843442f054b49
Change-Id: I7cd2e370e8bc553771243af248283ef80a399769
Signed-off-by: Aymen Zayet <aymenx.zayet@intel.com>
Reviewed-on: http://android.intel.com:8080/34513
Reviewed-by: Garcia, JeremieX <jeremiex.garcia@intel.com>
Reviewed-by: Regairaz, JulieX <juliex.regairaz@intel.com>
Reviewed-by: Fiat, Christophe <christophe.fiat@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Zurmely, PierreX <pierrex.zurmely@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ovidiu Beldie [Fri, 27 Jan 2012 14:49:01 +0000 (15:49 +0100)]
[drivers] [BT] skbuffer NULL pointer fix
BZ: 21014
This patch prevents the usage of an already freed skbuff and thus prevents memory overwritten error. This is done by adding an error condition check in the btwilink driver.
Change-Id: I459f29b14a2b9ddc5c568a42ae497a6534d64527
Signed-off-by: Ovidiu Beldie <ovidiux.beldie@intel.com>
Reviewed-on: http://android.intel.com:8080/33544
Reviewed-by: Peix, FabienX <fabienx.peix@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Zurmely, PierreX <pierrex.zurmely@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Yan Leo [Fri, 17 Feb 2012 22:56:22 +0000 (14:56 -0800)]
max11871: add touch driver from Maxim 11871
BZ: 21429
Touch driver of Maxim 11871 for Gilligan Island
Change-Id: If4297d55f21ee616c9371e42217127c4e04fc396
Signed-off-by: Andriy Naborskyy <andriy.naborskyy@intel.com>
Signed-off-by: Hong Liu <hong.liu@intel.com>
Signed-off-by: Leo Yan <leo.yan@intel.com>
Signed-off-by: Prabu Renganathan <prabu.renganathan@intel.com>
Reviewed-on: http://android.intel.com:8080/34180
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Zhifeng Wang [Fri, 17 Feb 2012 05:05:03 +0000 (13:05 +0800)]
hwmon/accel: enable initial event report for 6D interrupt mode
BZ: 23830
When accelerometer is running in 6D interrupt mode, it doesn't report
events if no orientation change. If device first enters sleep mode then
resume, user space app won't receive accelerometer events, and can't
calculate its orientation. This patch forces the accelerometer to report
events when it is enabled so that user space could calculate orientation
correctly.
Change-Id: Ib7738dd87c44d03d45ef7b28fa9ee607d04995a8
Signed-off-by: Zhifeng Wang <zhifeng.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/35684
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Bin Yang [Mon, 20 Feb 2012 07:39:45 +0000 (15:39 +0800)]
fix led device init issue
BZ: 24312
LED device init is later than IPC driver. It causes LED device being
lost.
Change-Id: Ie5e2d790ed70e77dae644da97f8d95016faadd4a
Signed-off-by: Bin Yang <bin.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/35868
Reviewed-by: Zhang, Shijie <shijie.zhang@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jackie Li [Mon, 13 Feb 2012 14:40:19 +0000 (22:40 +0800)]
GFX-Display: updated overlay wait for vblank to use blocked waiting instead of querying it in a busy loop
BZ: 18446
This patch 1/3 for flicking issue on overlay while video playback.
we need wait for vblank to make sure overlay has been switch to
a buffer successfully, or the buffer consumed by overlay might be
dequeued by video driver override the buffer data while overlay
is fetching data. Perviously, wait for vblank was implemented as
a busy loop which is ineffient and power consuming.
This patch reimplemented the overlay wait for vblank as a blocking
waiting, so that OS will put the caller thread to sleep while waiting
for vblank.
Change-Id: I29de9c12155cb0b2b60945e47dd675174bb52717
Signed-off-by: Jackie Li <yaodong.li@intel.com>
Reviewed-on: http://android.intel.com:8080/35165
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Austin Hu [Fri, 17 Feb 2012 09:01:02 +0000 (17:01 +0800)]
GFX-Display: make HDMI display in 1920x1080p@60Hz as default on CLV for MWC demo.
BZ: 24203
Don't filter out the 1920x1080p@60Hz mode whose dot clock is 148.5 MHz = 2200 x 1125 x 60.
Change-Id: Iaf1a6fc800ae7031b4ede7ddcf6ccb76c45a36a1
Signed-off-by: Austin Hu <austin.hu@intel.com>
Reviewed-on: http://android.intel.com:8080/35712
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Austin Hu [Fri, 17 Feb 2012 07:20:41 +0000 (15:20 +0800)]
GFX-Display: enabled HDMI HPD interrupt for CloverView SoC.
BZ: 24183
Enabled the HDMI HPD interrupt via GPIO pin 43 and by registering PCI
driver with device ID 0x901, for TI TPD12S015 HDMI companion chip used
for the CLV SoC.
Change-Id: I72879e01dc97b03f25d5d1203c5b1518d76c6458
Signed-off-by: Austin Hu <austin.hu@intel.com>
Reviewed-on: http://android.intel.com:8080/35698
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Alek Du [Mon, 20 Feb 2012 05:36:24 +0000 (05:36 +0000)]
[PORT FROM R2] max3110: fixing the race between port receive and port
shutdown
BZ: 8746
The main_thread should check port_shutdown status before committing tty
related actions.
Change-Id: I9d3d9a51c5f74222b02b2c2ce5b8e4e03b1fb8ee
Signed-off-by: Alek Du <alek.du@intel.com>
Reviewed-on: http://android.intel.com:8080/35844
Reviewed-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Bin Gao [Fri, 17 Feb 2012 08:21:17 +0000 (00:21 -0800)]
i386_ctp_defconfig: enable HSU console for Clovertrail
BZ: 23157
Medfield PRx uses UART 3(mirrored from UART 1) as HSU console port.
But for Clovertrail UART 2 is used as HSU console port.
This patch changes the HSU console port to 2 accordingly for Clovertrail.
Please note that only Clovertrail VV and EV boards can use HSU console
but PRx can not. This is by hardware design and is not a software issue.
Removing jumper J3D1 from debug card 3 will switch to HSU console.
Change-Id: I9f1dfdf2493a3229a3e5878532941cd3630ec6e3
Signed-off-by: Bin Gao <bin.gao@intel.com>
Reviewed-on: http://android.intel.com:8080/34809
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Fri, 3 Feb 2012 13:13:38 +0000 (15:13 +0200)]
ov8830: limit i2c transfers to 30 bytes due to i2c driver restrictions
BZ: 23715
See also BZ 16310.
The i2c adapter can transfer 32 bytes maximum
at a time, while driver implemets maximum 128
bytes burst transfer length, so i2c driver would
split buffer transfer if buffer length is more than
32 byte. This will cause some problem sometime, since
during two consequtive transfers, if the second transfer
starts at the time when the first transfer completely finishes,
(i2c transfer buffer empty),the i2c controler would start
a new i2c transfer, which include a start/stop signal according to
i2c protocal, but it will break the i2c burst transfer rules
expected by driver.
Change driver's maximum burst length from 128 to 30 bytes
which leaves also a safety margin.
Change-Id: If34a28dc9ea5318bd15769bfeeb501dd36eae7f5
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/35311
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Fri, 17 Feb 2012 06:40:25 +0000 (14:40 +0800)]
mmc: use max_discard_to for SD write timeout
BZ: 24030
max_discard_to is the max timeout value allowed by host. Use
this value can stop kernel printing too large timeout warning.
Change-Id: Iaa0828475849f466f45ef55d3d4c8ae7f220b073
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/35692
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Fri, 10 Feb 2012 09:36:28 +0000 (17:36 +0800)]
mmc: add flag to check suspend status before accessing RPMB partition
BZ: 23276
RPMB partition is accessed by an API which is called by SEP driver. Before
process RPMB partition access request, driver needs to make sure host is not
in suspended status.
Add a flag to check MMC block device status before handle a RPMB request
Change-Id: I0804a2e3a271dadc62a344bcb8384fbc7392f09b
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/35537
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Gao, Yunpeng <yunpeng.gao@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Andy Shevchenko [Wed, 15 Feb 2012 15:02:59 +0000 (17:02 +0200)]
media: video: append $(srctree) to -I parameters
BZ: 23514
Without this we have got the warnings like following if build with "make W=1
O=/var/tmp":
CHECK drivers/media/video/videobuf-vmalloc.c
CC [M] drivers/media/video/videobuf-vmalloc.o
+cc1: warning: drivers/media/dvb/dvb-core: No such file or directory [enabled by default]
+cc1: warning: drivers/media/dvb/frontends: No such file or directory [enabled by default]
+cc1: warning: drivers/media/dvb/dvb-core: No such file or directory [enabled by default]
+cc1: warning: drivers/media/dvb/frontends: No such file or directory [enabled by default]
LD drivers/media/built-in.o
Some details could be found in [1] as well.
[1] http://comments.gmane.org/gmane.linux.kbuild.devel/7733
Change-Id: I5418bce1e72fec10be1b5d297bc512b87798fa1d
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/35256
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jmath3 [Mon, 13 Feb 2012 13:07:05 +0000 (15:07 +0200)]
[PORT FROM R2] intel_idle: re-order power_trace
BZ: 23293
Part of this patch was merged in earlier code changes.
When ftrace is run with power events enabled it prevents
the device from going to higher c states and power_start and
power_stop traces are printed continuously.
This patch moves the trace_power_start and trace_power_end calls to the
main cpuidle routine.
There is no impact on the system as these are non intrusive traces.The device
now gows to higher c-states.
Upstream is already going that way, but the actual patch is depending on
lot of other stuff that we dont want to all take.
Orig-Change-Id: Idf7d983466afd9b2800d834032bf1fb05c6d4b32
Signed-off-by: John Mathew johnx.mathew@elektrobit.com
Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Change-Id: I85833541014c82eb44358ede7ba5371005c3cd67
Signed-off-by: John Mathew <john.mathew@intel.com>
Reviewed-on: http://android.intel.com:8080/35132
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Pierre Tardy [Fri, 22 Oct 2010 08:07:07 +0000 (03:07 -0500)]
[PORT FROM R2] trace/runtime_pm: add runtime_pm trace event
BZ: 23293
based on the recent hook from Arjan for powertop statistics
we add a tracepoint in order for pytimechart to display
the runtime_pm activity over time, and versus other events.
We also add a usage counter change tracer that will trace
accountability of a runtime_resume
Change-Id: Iab7cb7a09fc002c3e74e0186855edc2d0367a8b3
Orig-Change-Id: I59f8162e7129b98454752ca60c920c40ce4e8bd1
Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Reviewed-on: http://android.intel.com:8080/35159
Reviewed-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Illyas Mansoor [Wed, 25 Jan 2012 14:11:03 +0000 (19:41 +0530)]
[PORT FROM R2] mid_pmu: check completion flag after wait_for_completion timeout
BZ: 21156 23293
In S3 flow pci_pmu_set_power_state waits on d0ix command
completion interrupt, the interrupt is received but the
completion signal is not delivered since the threads are
frozen.
Hence pci_pmu_set_power_state timesout after 5secs and
calls BUG()
Fixed this by checking the completion flag that gets cleared
when d0ix completion interrupt is received.
<0>[ 7959.846890] ------------[ cut here ]------------
<2>[ 7959.846903] Kernel BUG at
c1852942 [verbose debug info unavailable]
<0>[ 7959.846917] invalid opcode: 0000 [#1] PREEMPT SMP
<0>[ 7959.846933] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
<4>[ 7959.846944] Modules linked in: ipv6 atomisp lm3554 mt9m114 mt9e013 videobuf_vmalloc videobuf_dma_contig videobuf_core wl12xx_sdio wl12xx mac80211 cfg80211 compat btwilink st_drv
<4>[ 7959.846995]
<4>[ 7959.847010] Pid: 19, comm: suspend Not tainted 2.6.35.3-84696-gf486d97 #1 /
<4>[ 7959.847024] EIP: 0060:[<
c1852942>] EFLAGS:
00010246 CPU: 1
<4>[ 7959.847046] EIP is at pmu_pci_set_power_state+0x322/0x6e0
<4>[ 7959.847059] EAX:
00000000 EBX:
0000001a ECX:
c186dd96 EDX:
00000000
<4>[ 7959.847071] ESI:
00000000 EDI:
00000001 EBP:
f78e3d74 ESP:
f78e3cd0
<4>[ 7959.847083] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
<0>[ 7959.847097] Process suspend (pid: 19, ti=
f78e2000 task=
f7899b20 task.ti=
f78e2000)
<0>[ 7959.847106] Stack:
<4>[ 7959.847114]
c1bcee0b f78e3cf8 c14b502a 00000002 f78e3d4e c1b77d00 f78e3dcc c1bcf200
<4>[ 7959.847142] <0>
00000002 c1bcee0b f78e3d9c f78e3d48 00000008 00000000 00000000 0000011e
<4>[ 7959.847172] <0>
00018601 f78e3d38 c14b502a 00000008 f78e3d02 f78e3d44 c2603920 ffffffff
<0>[ 7959.847204] Call Trace:
<4>[ 7959.847227] [<
c14b502a>] ? put_dec+0x2a/0xa0
<4>[ 7959.847249] [<
c14b502a>] ? put_dec+0x2a/0xa0
<4>[ 7959.847276] [<
c12384a5>] ? sub_preempt_count+0x85/0xc0
<4>[ 7959.847295] [<
c14cee6e>] ? pci_platform_power_transition+0x3e/0xa0
<4>[ 7959.847314] [<
c18715f3>] ? _raw_spin_unlock_irqrestore+0x23/0x50
<4>[ 7959.847333] [<
c14cf5df>] ? pci_set_power_state+0x3f/0x2c0
<4>[ 7959.847353] [<
c14ced7c>] ? pci_update_current_state+0x3c/0x50
<4>[ 7959.847372] [<
c14d180e>] ? pci_pm_runtime_resume+0x5e/0xa0
<4>[ 7959.847390] [<
c12384a5>] ? sub_preempt_count+0x85/0xc0
<4>[ 7959.847406] [<
c14d17b0>] ? pci_pm_runtime_resume+0x0/0xa0
<4>[ 7959.847425] [<
c1554d7b>] ? rpm_callback+0x3b/0x70
<4>[ 7959.847442] [<
c155577c>] ? rpm_resume+0x37c/0x5c0
<4>[ 7959.847460] [<
c124923b>] ? release_console_sem+0x37b/0x3c0
<4>[ 7959.847482] [<
c1238593>] ? add_preempt_count+0xb3/0xf0
<4>[ 7959.847500] [<
c1556609>] ? __pm_runtime_resume+0x49/0xc0
<4>[ 7959.847519] [<
c14d1b71>] ? pci_pm_prepare+0x21/0x60
<4>[ 7959.847536] [<
c1553947>] ? dpm_suspend_start+0x137/0x7d0
<4>[ 7959.847554] [<
c12384a5>] ? sub_preempt_count+0x85/0xc0
<4>[ 7959.847572] [<
c18715f3>] ? _raw_spin_unlock_irqrestore+0x23/0x50
<4>[ 7959.847590] [<
c126f548>] ? up+0x28/0x40
<4>[ 7959.847610] [<
c1288f13>] ? suspend_devices_and_enter+0x73/0x1d0
<4>[ 7959.847628] [<
c1289196>] ? enter_state+0x126/0x1e0
<4>[ 7959.847646] [<
c1289277>] ? pm_suspend+0x27/0x70
<4>[ 7959.847662] [<
c128acba>] ? suspend+0x8a/0x160
<4>[ 7959.847678] [<
c186e445>] ? schedule+0x545/0x9e0
<4>[ 7959.847701] [<
c12384a5>] ? sub_preempt_count+0x85/0xc0
<4>[ 7959.847720] [<
c1265833>] ? worker_thread+0x123/0x2c0
<4>[ 7959.847736] [<
c186e445>] ? schedule+0x545/0x9e0
<4>[ 7959.847755] [<
c128ac30>] ? suspend+0x0/0x160
<4>[ 7959.847772] [<
c12690d0>] ? autoremove_wake_function+0x0/0x50
<4>[ 7959.847790] [<
c1265710>] ? worker_thread+0x0/0x2c0
<4>[ 7959.847807] [<
c1268c34>] ? kthread+0x74/0x80
<4>[ 7959.847825] [<
c1268bc0>] ? kthread+0x0/0x80
<4>[ 7959.847843] [<
c120357a>] ? kernel_thread_helper+0x6/0x10
<0>[ 7959.847852] Code: ff 33 00 00 e8 40 b3 9d ff 85 c0 89 c6 0f 85 aa 02 00 00 a1 c0 de b8 c1 ba f4 01 00 00 05 1c 19 00 00 e8 82 b5 01 00 85 c0 75 04 <0f> 0b eb fe a1 c0 de b8 c1 c7 80 14 0a 00 00 00 00 00 00 83 7c
<0>[ 7959.848033] EIP: [<
c1852942>] pmu_pci_set_power_state+0x322/0x6e0 SS:ESP 0068:
f78e3cd0
<4>[ 7959.848064] ---[ end trace
f7884632b6bd02b8 ]---
Change-Id: I230427819b80875cc7da106f3339546c2a1ff2cb
Orig-Change-Id: I6774d29f74a66d413c2e8cb0514bcc6468ccdd20
Signed-off-by: Illyas Mansoor <illyas.mansoor@intel.com>
Reviewed-on: http://android.intel.com:8080/35158
Reviewed-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Nicole Chalhoub [Tue, 12 Apr 2011 12:49:16 +0000 (18:19 +0530)]
[PORT FROM R2] nohz: delay going tickless under CPU load to favor deeper C states
BZ: 23293
While there is CPU load, continue the periodic tick in order to give
CPUidle another opportunity to pick a deeper C-state instead of
spending potentially long idle times in a shallow C-state.
Long winded version:
When going idle with a high load average, CPUidle menu governor will
decide to pick a shallow C-state since one of the guiding principles
of the menu governor is "The busier the system, the less impact of C
states is acceptable" (taken from cpuidle/governors/menu.c.) That
makes perfect sense.
However, there are missed power-saving opportunities for bursty
workloads with long idle times (e.g. MP3 playback.) Given such a
workload, because of the load average, CPUidle tends to pick a shallow
C-state. Because we also go tickless, this shallow C-state is used
for the duration of the idle period. If the idle period is long, a
deeper C state would've resulted in better power savings.
This patch delays going tickless when there is a load such that on the
next tick, the CPUidle governor will have another opportunity to to
pick a deeper C-state. Since the system will have been idle for
potentially a full tick, the load average will drop and a deeper C
state will most likely be chosen.
Delaying NOHZ decisions until the load is zero improved the load
estimation on our ARM/OMAP4 platform where HZ=128 and increased the
time spent in deep C-states (~50% of idle time in C-states deeper than
C1). A power saving of ~20mA at battery level is observed during MP3
playback on OMAP4/Blaze board.
Change-Id: I574a4a70ec90c19aef94fd7ebd4904b2cef94d30
Orig-Change-Id: I941465f66fa69e9e9a59d2de7211a8d6f519a715
Signed-off-by: Nicole Chalhoub <n-chalhoub@ti.com>
Signed-off-by: Vincent Bour <v-bour@ti.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
Signed-off-by: Sundar Iyer <sundar.iyer@intel.com>
Reviewed-on: http://android.intel.com:8080/35157
Reviewed-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jeeja Kp [Tue, 14 Feb 2012 16:15:13 +0000 (08:15 -0800)]
audio: To Enable Audio for CTP.
BZ: 15274 15273
Add codec driver for Cirrus Logic cs42l73
Added CLV Machine driver to integrate codec driver for Clovertrail Platform
Added support to enable Audio on Clovertrail platform
Change-Id: Iaa1e9232bd9b2095c38982b190fbc1b934ab642e
Signed-off-by: Jeeja Kp <jeeja.kp@intel.com>
Signed-off-by: Ojas Chauhan <ojas.chauhan@intel.com>
Reviewed-on: http://android.intel.com:8080/33071
Reviewed-by: Agarwal, Vaibhav <vaibhav.agarwal@intel.com>
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Vaibhav Agarwal [Wed, 25 Jan 2012 20:44:42 +0000 (02:14 +0530)]
HDMI-Audio: Ported to R3
BZ: 18092
Some HAD patches were not ported from R2 to R3.
This patch includes Patch#26712, 30304, 30338, 31988,
3216 and 31452(only HAD related changes) alongwith some
code cleaning changes.
Change-Id: Ifedf346ca85f5e6a7c0c760341e5dec0ea762a00
Signed-off-by: Vaibhav Agarwal <vaibhav.agarwal@intel.com>
Reviewed-on: http://android.intel.com:8080/33720
Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com>
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Zhifeng Wang [Fri, 17 Feb 2012 02:11:26 +0000 (10:11 +0800)]
hwmon/lis3dh: fix critical array out of bounds issue
BZ: 23918
Fix a possible array out of bound issue reported by Klocwork scan.
Change-Id: I273b0aa2f20162727d28820726f23d566d61231c
Signed-off-by: Zhifeng Wang <zhifeng.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/35673
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Mark F. Brown [Fri, 3 Feb 2012 18:40:37 +0000 (10:40 -0800)]
medfield: mfld_cstates table referenced when not defined
BZ: 22306
Fixes error:
drivers/idle/intel_idle.c: In function 'intel_idle_probe':
drivers/idle/intel_idle.c:717: error: 'mfld_cstates' undeclared (first use in this function)
Change-Id: I74cae19ffbff38f8581d442c1f9a01b557159e96
Signed-off-by: Mark F. Brown <mark.f.brown@intel.com>
Reviewed-on: http://android.intel.com:8080/33984
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Mark F. Brown [Fri, 3 Feb 2012 15:38:05 +0000 (07:38 -0800)]
usb: corrected references to otg_notify when CONFIG_USB_OTG undefined
BZ: 22291
Fixes errors:
drivers/usb/core/generic.c: In function 'generic_probe':
drivers/usb/core/generic.c:195: error: 'struct usb_hcd' has no member named 'otg_notify'
drivers/usb/core/generic.c:196: error: 'struct usb_hcd' has no member named 'otg_notify'
drivers/usb/core/generic.c:198: error: 'struct usb_hcd' has no member named 'otg_notify'
Change-Id: I5255fe1843f6a1f394252ddb1ea4267f8cee1063
Signed-off-by: Mark F. Brown <mark.f.brown@intel.com>
Reviewed-on: http://android.intel.com:8080/33983
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Benoit Romieu [Tue, 7 Feb 2012 16:44:49 +0000 (17:44 +0100)]
mrst.c: reimplement the force cold boot properly
BZ: 22672
Do a cold reset in normal case. Do a cold boot depending of module param force_cold_boot.
Change-Id: I422ac66c070f24c287fc625e1d282e2be71cbe84
Reviewed-on: http://android.intel.com:8080/34345
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Hong Liu [Tue, 7 Feb 2012 10:25:56 +0000 (18:25 +0800)]
atmel_mxt_ts: enable mxt1386 for mfld_dv10 tablet
BZ: 20808
Patches are from OTC build:
1943-Input-atmel_mxt_ts-update-object-list.patch
1944-Input-atmel_mxt_ts-handle-objects-with-multiple-inst.patch
1945-Input-atmel_mxt_ts-report-pressure-information-from-.patch
2182-Input-atmel_mxt_ts-update-the-i2c-communication-rout.patch
2183-Input-atmel_mxt_ts-add-firmware-interface-for-config.patch
2184-Input-atmel_mxt_ts-add-some-saving-to-mxt_start-stop.patch
2185-Input-atmel_mxt_ts-add-Android-specifig-PM-functions.patch
2186-mrst-add-support-for-atmel_mxt_ts-touchscreen.patch
2187-Input-atmel_mxt_ts-Add-device-id-for-mxt1386-and-tun.patch
2188-Input-atmel_mxt_ts-free-the-memory-used-by-config-fi.patch
2189-Input-atmel_mxt_ts-Release-touch-points-before-suspe.patch
2190-Input-atmel_mxt_ts-increase-retry-number-for-I2C-R-W.patch
Change-Id: I7bc95f8333e2411796e655d9891ef74d36ed12b9
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34435
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Hong Liu [Tue, 7 Feb 2012 10:02:34 +0000 (18:02 +0800)]
atmel_mxt_ts: revert changes to the upstream atmel_mxt_ts driver
BZ: 20808
Revert the changes to prepare for applying the OTC patches to
this driver.
Change-Id: Ia3b8db53861069e12d7e3237ae62d11fd12341d0
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34434
Reviewed-by: Continente, Christophe <christophe.continente@intel.com>
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Li Zeng [Mon, 13 Feb 2012 01:49:00 +0000 (09:49 +0800)]
ved: Enable video decode on CLV
BZ: 23230
Video decode doesn't work on CLV
CLV ved use punit to upload firmware as MFLD D0, modify a macro IS_D0. Disable D0i3 for CLV.
Change-Id: Id817e9dd9d2ab5e27a285630b33a75b91b462bd7
Signed-off-by: Li Zeng <li.zeng@intel.com>
Reviewed-on: http://android.intel.com:8080/35014
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Li Zeng [Wed, 8 Feb 2012 02:03:14 +0000 (10:03 +0800)]
[PORT FROM R2]ved: Remove DSIABLE_FW_WDT flag
BZ: 17954
When ved goes to invalid state, driver waits 3s for sync buffer. 3s is relativelg long that media framework drops a lot frames
Remove DSIABLE_FW_WDT flag to enable WDT so that hw responds quickly in invalid state
Change-Id: I33a1992c0c01d996d96a91c910a409e801ac806e
Signed-off-by: Li Zeng <li.zeng@intel.com>
Reviewed-on: http://android.intel.com:8080/34403
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Yong Wang [Wed, 11 Jan 2012 06:44:24 +0000 (22:44 -0800)]
atomisp: fix runtime PM issues
BZ: 23514
Fix 'Unbalanced pm_runtime_enable' issue by removing such call from driver
as PCI core already calls it for each device. In addition, enable runtime
PM for camera by default so that it does not block PM.
Change-Id: I7f60d8a9b9330b6a324a4435d7b57ff8a78a48ab
Signed-off-by: Yong Wang <yong.y.wang@intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34938
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Andy Shevchenko [Wed, 21 Dec 2011 13:43:04 +0000 (15:43 +0200)]
atomisp: don't leave mutex locked
BZ: 23514
In case of timeout the lock left untouched.
This patch fixes following bug.
[ 73.121283] BUG: workqueue leaked lock or atomic: kworker/u:0/0x00000000/5
[ 73.121311] last function: atomisp_work+0x0/0x6ef [atomisp]
[ 73.121466] 1 lock held by kworker/u:0/5:
[ 73.121486] #0: (&isp->isp_lock){+.+.+.}, at: [<
f978e8e5>] atomisp_work+0x369/0x6ef [atomisp]
[ 73.121664] Pid: 5, comm: kworker/u:0 Tainted: G W 3.0.13-mid4-02284-g2796f20-dirty #149
[ 73.121690] Call Trace:
[ 73.121735] [<
c1034497>] ? console_unlock+0x178/0x18a
[ 73.121844] [<
c1048240>] process_one_work+0x2b0/0x32c
[ 73.121984] [<
f978e57c>] ? atomisp_buffer_dequeue+0x9b/0x9b [atomisp]
[ 73.122588] [<
c1048ffb>] worker_thread+0xbb/0x136
[ 73.122632] [<
c1048f40>] ? manage_workers.isra.24+0x150/0x150
[ 73.122672] [<
c104bf09>] kthread+0x73/0x78
[ 73.122718] [<
c104be96>] ? __init_kthread_worker+0x47/0x47
[ 73.122763] [<
c14df342>] kernel_thread_helper+0x6/0x10
Change-Id: I2059b6db63bfa0d9ae4baed0353a0304907dd33f
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: David Cohen <david.a.cohen@intel.com>
Reviewed-on: http://android.intel.com:8080/34937
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Tuominen, TeemuX <teemux.tuominen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Andy Shevchenko [Tue, 17 Jan 2012 17:32:24 +0000 (09:32 -0800)]
atomisp: fix typo in lock initialization
BZ: 23514
Fix typo when the same lock was initialized twice.
During the fix of another issue the lock was initialized twice. This patch
fixes the typo.
Change-Id: If5b42286ae9cd7de30bf9bb8844cf7dd7e01b7e7
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34936
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Andy Shevchenko [Thu, 26 Jan 2012 14:59:26 +0000 (16:59 +0200)]
atomisp: cosmetic indentation fix
BZ: 23514
No functional change here.
Just fix the indentation.
Change-Id: I9a461b42b532d9a35c4b2c3b08a7fa58adef6c5b
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34935
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Andy Shevchenko [Thu, 24 Nov 2011 09:34:29 +0000 (11:34 +0200)]
atomisp/css: fix return type of sh_css.c:check_infos_match
BZ: 23514
The return type should be enum. Currently the boolean is used that is
incorrect.
Change-Id: Ia88db94019998d3d5dd1677f97580ff2941350fc
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34933
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Andy Shevchenko [Fri, 21 Oct 2011 14:31:38 +0000 (17:31 +0300)]
atomisp/css: optimize sh_css_hrt_irq_get_id()
BZ: 23514
There is no need to loop to find the first set bit. We can easily use the ffs()
function to do the job. And this way is faster.
This patch implements faster and simplier codepiece.
Change-Id: Id9d26a0cbf3c9a965e0c82fbd47d47734730df29
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34932
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Andy Shevchenko [Wed, 23 Nov 2011 15:37:15 +0000 (17:37 +0200)]
atomisp/css: Remove PC_MONITORING thread before release
BZ: 23514
In case when the atomisp driver is built as module with the PC_MONITORING
turned on, the release of the module will wait for the pc_monitoring thread
which never stops.
This patch stops the thread correctly during release procedure.
Change-Id: I8926a524b94e552d412c764c6746df786f0394ce
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34931
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Li, Ning [Wed, 15 Feb 2012 07:13:47 +0000 (15:13 +0800)]
gpio: add wakeup source trace in GPIO driver
BZ: 23641
Add logs to trace the wakeup source at each time the langwell-gpio
device resumes.
Change-Id: I8774526d1a529205c8c4681a20ba6a4beac6065f
Signed-off-by: Li, Ning <ning.li@intel.com>
Reviewed-on: http://android.intel.com:8080/35387
Reviewed-by: Yang, Bin <bin.yang@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jli127 [Thu, 2 Feb 2012 00:53:24 +0000 (08:53 +0800)]
hwmon: lps331ap: Add lps331ap baro sensor for cvt
BZ: 22002
Add lps331ap baro sensor for Clover Trail platform.
Change-Id: I3e811fc403ddff5aeb7a7589b4ea639ec762a3a7
Signed-off-by: jli127 <jian.d.li@intel.com>
Reviewed-on: http://android.intel.com:8080/33633
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Zhifeng Wang [Wed, 15 Feb 2012 03:44:45 +0000 (11:44 +0800)]
hwmon: l3g4200d: Initial version of gyroscope driver
BZ: 22173
This commit adds the ST L3G4200D gyroscope driver. The driver is polling
based and suitable for android system.
Change-Id: I50952855fc38d0ee92125a11e45a4e9ce8a1b7b5
Signed-off-by: Zhifeng Wang <zhifeng.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/21906
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jli127 [Wed, 1 Feb 2012 01:49:21 +0000 (09:49 +0800)]
hwmon: lsm303dlhc: Add lsm303dlhc compass sensor for cvt
BZ: 21806
Add lsm303dlhc compass sensor for Clover Trail platform.
Change-Id: Iba53311ffa451fd3a35f3bad004c1d515e52aa69
Signed-off-by: jli127 <jian.d.li@intel.com>
Reviewed-on: http://android.intel.com:8080/33444
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Zhifeng Wang [Wed, 15 Feb 2012 03:03:17 +0000 (11:03 +0800)]
hwmon: lis3dh: Add support of the ST LSM303DLHC accelerometer
BZ: 22035
Modify the ST LIS3DH accelerometer driver code to support the new type
accelerometer ST LSM303DLHC.
Basically, the ST LSM303DLHC is a combination of the LIS3DH accelerometer
and a magnetometer. So very few code changes are necessary.
Change-Id: I858870fbf48336db0ad7b14ed0f43478ec76b777
Signed-off-by: Zhifeng Wang <zhifeng.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/22091
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Fri, 3 Feb 2012 18:04:59 +0000 (10:04 -0800)]
GPIO[2/2]: langwell-gpio causing panic when NR_CPUS=2
BZ: 11245
After enabling SPARSE_IRQ to make allocation of irqdesc a dynamic
one, kernel fail to boot because the langwell-gpio driver doesn't
request_irq for the gpio pins, thus irqdesc is not allocated for
them. Add irq_alloc_descs call in the probe function to allocate
irqsec.
Change-Id: I26ab2882c2be7114976fd55068de34e6b6cadf32
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/34159
Reviewed-by: Monroy, German <german.monroy@intel.com>
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Fri, 3 Feb 2012 18:02:19 +0000 (10:02 -0800)]
GPIO[1/2]: langwell-gpio causing panic when NR_CPUS=2
BZ: 11245
For X86_32, NR_CPUS can be any value from 2 to 8. However when
set NR_CPUS=2 kernel doesn't boot on Intel Medfield platform due to
a panic caused by langwell gpio driver. The problem is that kernel
statically allocates an arry of NR_IRQS elements for irqdesc, when
NR_CPUS=2, NR_IRQS is set to 320. This number is much less than the
GPIO irq number on Medfield platform, thus some of the gpio irqdesc
do not get created properly and causing kernel panic when trying to
access the irqdesc for these GPIO irqs.
Problem can be solved by increasing the value of NR_IRQS, but
statically allocating irqdesc is not a good way to handle multiple
hardware platforms in the first place, so making this a dynamic one
by enabling SPARSE_IRQ should be the right way to go.
Change-Id: Ia0d548e247a4cb71f8073e3b447a31c9cd07831d
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/34158
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jiebing Li [Wed, 27 Apr 2011 11:23:56 +0000 (19:23 +0800)]
[PORT FROM R2]usb: gadget-zero: fix OUT transaction stall issue
BZ: 23299
When error returns from req complete callback API, received data
should be discarded instead of be checked as they're not the data
we wish to receive.
Change-Id: Ifc24c44472e18e1354e0b396ff349b6b8b435480
Signed-off-by: Jiebing Li <jiebing.li@intel.com>
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/35092
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Zhuang, Jin Can <jin.can.zhuang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Lei Zhang [Wed, 15 Feb 2012 03:29:26 +0000 (11:29 +0800)]
Gfx-Display: [CTP] change hdmi status to be disconnected for WMC demo.
BZ: 23755
This patch changes the hdmi status on CTP to be disconnected as default for video playing
on MIPI. HDMI connect status now is blocked by HDP enabling on CTP and used default seting
in driver. Former setting as connected is for hdmi function enabling test on CTP by Seema.
Change-Id: I9065532ca333b397e46386c72aed9c8f941319a3
Signed-off-by: Lei Zhang <lei.zhang@intel.com>
Reviewed-on: http://android.intel.com:8080/35368
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Austin Hu [Fri, 10 Feb 2012 02:23:02 +0000 (10:23 +0800)]
GFX-Display: fixed the issue that pipe B vblank interrupt couldn't be re-enabled.
BZ: 23164
Whend display driver enables pipe B vblank interrupt after it's enabled in DPMS on,
it would be disabled as it's masked out by the incorrectly defined pipe event mask.
Fixed the issue by adding the bits enabling interrupts (at least bit 17) to the pipe
event mask for PIPExSTAT register.
Change-Id: I782ba606d9ed029a95ae37b8a8d86a8443c7bc1c
Signed-off-by: Austin Hu <austin.hu@intel.com>
Reviewed-on: http://android.intel.com:8080/34810
Reviewed-by: Tong, BoX <box.tong@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Zhifeng Wang [Wed, 15 Feb 2012 06:02:53 +0000 (14:02 +0800)]
touch screen: change max finger touch to be 10
BZ: 21729
Change max finger touch from 2 to 10.
Change-Id: I802ac20508794eb4a556bed24a4bda12ccdc9873
Signed-off-by: Zhifeng Wang <zhifeng.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/35079
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Asutosh Pathak [Wed, 8 Feb 2012 02:36:17 +0000 (18:36 -0800)]
rmi_sensor: Resolved RMI driver early suspend panic issue.
BZ: 22970
Fixing kernel panic due to "custom_ops" NULL pointer dereferencing in
rmi_sensor_suspend()
Signed-off-by: Asutosh Pathak <asutosh.pathak@intel.com>
Change-Id: Ia07ae63c26a20467c17987d0dd94b14a37f4ec92
Reviewed-on: http://android.intel.com:8080/34613
Reviewed-by: Pathak, Asutosh <asutosh.pathak@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Wed, 8 Feb 2012 08:55:39 +0000 (16:55 +0800)]
mmc: add a rpmb device node and RPMB ioctl
BZ: 22886
Add a device node rpmb partition. So that every RPMB partition access
can be directly sent by using a separated device node mmcblk0rpmb instead
of using mmcblk0, which makes more sense.
With this ioctl, RPMB reading/writing can be tested easily
Change-Id: Ifdb510f1d08d567a2eac55b4e05fba3bed1b0bc6
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/34476
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
santosh [Tue, 14 Feb 2012 09:23:57 +0000 (14:53 +0530)]
[PORT FROM R2]Battery: Add voltage margin of 50mV to detect battery full
BZ: 21617
This patch adds the voltage margin of 50mV to detect the
battery full condition during charging.
Change-Id: I8c096fc2aa26b73dc27c7b31db21ed606a205838
Orig-Change-Id: I4d83829e6bdd99cf696778408078cd711db0700a
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Signed-off-by: santosh <santoshx.gugwad@intel.com>
Reviewed-on: http://android.intel.com:8080/35227
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Mon, 6 Feb 2012 07:52:37 +0000 (15:52 +0800)]
[PORT FROM R2]mmc: core: increase eMMC card write timeout response time
BZ: 23202
original commit:
BZ: 22383
Medfiled boards has observed MMC card -110 errors, but card status
is still in 0xc00. So seems some MMC card cannot meet its CSD
guaranteed write response timeout value. Increase this timeout value
from host driver side. If the increasing cannot workaround the timeout
error totally, the increasing can be tuned.
This increase won't impact performance. Host controller only use
this value to decide how long to wait before generate a data timeout
interrupt.
Change-Id: Ib1ddbb98c52649778d0a071acdeef91d2b3f63d9
Change-Id: Iddae9353fd7708cfbac0cb599433757036adc71f
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/35375
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Thu, 2 Feb 2012 06:37:12 +0000 (14:37 +0800)]
[PORT FROM R2]mmc: core: increase SD card data write timeout value
BZ: 23202
original commit:
BZ: 16069
Some SD cards don't have a good storage management, which make
themselves cannot finish data receiving in 300ms during a write
request. SD card spec defines 300ms is enough, but for some SD,
it is not.
This patch will increase 300ms to be 3s, which can let host controller
to wait longer for SD card to finish data receiving.
This increase won't impact SD performance. Host controller only use
this value to decide how long to wait before generate a data timeout
interrupt.
Orig-Change-Id: I704c31b5811977342003091fd6eba35670c5c93c
Change-Id: I2ccd0abe50e07ea37e37eb220be05f5d060205f8
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/35374
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Xiaokang Qin [Thu, 5 Jan 2012 17:12:37 +0000 (01:12 +0800)]
[PORT FROM R2] osip: Support reboot recovery/bootloader/android
BZ: 22489
Change-Id: I5b5d281d073ca4dc54e230705dd95fc2a2d6e684
Signed-off-by: Xiaokang Qin <xiaokang.qin@intel.com>
Reviewed-on: http://android.intel.com:8080/34217
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Tue, 14 Feb 2012 20:05:40 +0000 (12:05 -0800)]
COMPASS: missing compass device when re-struct mrst.c
BZ: 23712
Add compass back into the platform device table for blackbay.
Change-Id: Ie91ed1d19b8047c7e5b115b2e75eae9575021e6f
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/35336
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Alek Du [Thu, 9 Feb 2012 14:06:03 +0000 (14:06 +0000)]
[PORT FROM R2] gpio_alt_func: make this function atomic
BZ: 21608
This function will first read out ALT reg, and then change
bits and write back.
It is not safe when without atomic context protection, the
concurrent calling of this function will override each other.
Change-Id: Id47027f055d65772a62b7d4c0742d87366deb898
Signed-off-by: Alek Du <alek.du@intel.com>
Reviewed-on: http://android.intel.com:8080/35128
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
he bo [Tue, 31 Jan 2012 22:10:44 +0000 (06:10 +0800)]
config: enable CONFIG_NOHIGHMEM to enlarge the memory to 1G
BZ: 21826
When CONFIG_NOHIGHMEM=y, kernel just uses 856M memory as it
couldn’t map all physical memory to the 1GB virtual space
between 0xc0000000~0xffffffff. Some virtual space is reserved
for VMALLOC.
Change-Id: Id5cf139757f2ff42751a184e62929380324b077e
Signed-off-by: Yanmin Zhang <yanmin.zhang@intel.com>
Signed-off-by: he bo <bo.he@intel.com>
Reviewed-on: http://android.intel.com:8080/33461
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Fri, 27 Jan 2012 17:40:53 +0000 (09:40 -0800)]
RTC: time drifting caused by system suspend/resume
BZ: 20145
RTC interface provides time in second granularity, this causes half
second error accumulation each time system goes in and out of
suspension.
Change ported from commit
641a260ee5342ff42bdd500f93af5083c096f6f4
in UMG 2.6.35 tree.
Another problem fixed in this patch is that "rtc_mrst" platform device
gets registered twice in arch/x86/platform/mrst/vrtc.c and
drivers/rtc/rtc-mrst.c respectively, this would cause a failure for
the second platform device registration. Remove the one in vrtc.c
Change-Id: I9ea350f1f299033bb88e5a19b20caf71b79fec18
Signed-off-by: Fei Yang <fei.yang@intel.com>
Signed-off-by: ShuoX Liu <shuox.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/33112
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Fri, 27 Jan 2012 17:25:34 +0000 (09:25 -0800)]
RTC: Enable RTC_HCTOSYS
BZ: 20145
This is used to sync system time with RTC device. It was enabled in
UMG 2.6.35 kernel, but missing in K3.0.8 tree.
Change-Id: I6af2275d9f0492609f7ca02776df25966532dcfc
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/33111
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Liu, DongxingX [Thu, 9 Feb 2012 02:48:34 +0000 (10:48 +0800)]
usb: gadget: android: Modify next_string_id reset value
BZ: 22206
Modify next_string_id to reset_string_id because
"android_usb" driver is working and its string
descriptor numbers have been allocated.
Change-Id: Ic36cfc307608105568aa61bdba43082d2be5c374
Signed-off-by: Liu, DongxingX <dongxingx.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34610
Reviewed-by: Wu, Hao <hao.wu@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Zhuang, Jin Can <jin.can.zhuang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Wu, Hao [Thu, 2 Feb 2012 11:50:13 +0000 (19:50 +0800)]
usb/penwell_otg: WA: reset controller to recover from PHY issue in device mode.
BZ: 22901
This patch is a workaround solution, when PHY stop working due to
Hardware issue, add ulpi_polling to detect the error and reset to
recover from bad state.
As this PHY issue has low reproduce rate, so add one debug interface
(inputs/ulpi_err)to trigger it manually, only for debug and test.
This workaround should be removed once we got a final hardware fix.
This change is for MFLD only.
Change-Id: I873122b8eac2cbf8c176ee624d436e04c4384323
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/34496
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Wu, Hao [Tue, 31 Jan 2012 05:02:43 +0000 (13:02 +0800)]
usb/penwell_otg: disable PHY interrupt VBUSVALID/ID when connect to Host
BZ: 22901
This is a workaround patch in penwell_otg driver, disable PHY interrupt
VBUSVALID and ID when connected to a USB Host to avoid unexpected RxCMD
from PHY, this is for MFLD only.
Change-Id: I6d80a2b5d3d5b91a7a49685b0d1fb0afb7b1df41
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/34495
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Mon, 6 Feb 2012 09:45:08 +0000 (17:45 +0800)]
mmc: move ready/frame field into mmc_core_rpmb_req
BZ: 22879
mmc_rpmb_req is used for external use. Keeping ready/frame field
in this structure is not safe.
Create a new struct named mmc_core_rpmb_req which is for mmc core
only. No external user can touch it. So move ready/frame field into
this structure
Change-Id: I767e47c31a0ce6396f099c46056c100aa40e6f6f
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/34475
Reviewed-by: Jiang, Brendan <brendan.jiang@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Sathyanarayanan Kuppuswamy [Mon, 13 Feb 2012 19:49:10 +0000 (11:49 -0800)]
Redridge touchscreen support
BZ: 22780
DV10 SFI device table is not supplying mxt1386 info. So initializing it
separately.We have to remove this hack once SFI tables are updated
properly.
Change-Id: I47e732d8b65f6dd3a0d0fa62ab6398450b6e3d0d
Signed-off-by: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-on: http://android.intel.com:8080/35172
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Wood, Brian J <brian.j.wood@intel.com>
Tested-by: Wood, Brian J <brian.j.wood@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
sathyanarayanan kuppuswamy [Tue, 7 Feb 2012 20:13:35 +0000 (12:13 -0800)]
Flattened the platform directory structure
BZ: 22780
Moved the contents of both mrst and mfld directories to a single folder (intel-mid/).
Change-Id: I78d8915b4513f0032e5221eaa2bc79edfbf4512b
Signed-off-by: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-on: http://android.intel.com:8080/34378
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Wood, Brian J <brian.j.wood@intel.com>
Tested-by: Wood, Brian J <brian.j.wood@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
sathyanarayanan kuppuswamy [Wed, 25 Jan 2012 01:39:02 +0000 (17:39 -0800)]
Renamed mrst.h to intel-mid.h
BZ: 22780
Change-Id: Iaef116f80a64cc2c0d7c6b7d8a97634fdbb163eb
Signed-off-by: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-on: http://android.intel.com:8080/34377
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Wood, Brian J <brian.j.wood@intel.com>
Tested-by: Wood, Brian J <brian.j.wood@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
sathyanarayanan kuppuswamy [Tue, 7 Feb 2012 01:19:44 +0000 (17:19 -0800)]
Restructured mrst.c
BZ: 22780
Mrst.c file contents are divided into soc & board components. Details are,
Platform/intel-mid.c - Common SOC functionalities are part of this file.
Like SFI parsing, platform device initialization
routines,etc.
Platform/mrst/mrst.c - Moorestown specific code should go into this file.
Platform/mfld/mfld.c - Medfield specific code should go into this file.
Platform/mfld/board-blackbay.c - Board specific initilizations should be part
of this file.
Added a new member(device_handler) to devs_id structure. Platform devices
can use this member to define their own device handlers. If the value is
left NULL then default handler will get called.
intel_mid_weak_decls.h contains weak declaration of the functions defined in
intel-mid.c.It will help us to override these functions in SOC specific files.
Change-Id: I7340a5a197af6340b899e8dff0f1a9ca0929fe2b
Signed-off-by: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-on: http://android.intel.com:8080/34375
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Wood, Brian J <brian.j.wood@intel.com>
Tested-by: Wood, Brian J <brian.j.wood@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
sathyanarayanan kuppuswamy [Mon, 6 Feb 2012 22:03:04 +0000 (14:03 -0800)]
Renamed the common code with *mrst* to *intel_mid*
BZ: 22780
Renamed the common code with *mrst* to *intel_mid*
Change-Id: Idda11c11916472f415d5502b47c982f4ff1d0896
Signed-off-by: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-on: http://android.intel.com:8080/34374
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Wood, Brian J <brian.j.wood@intel.com>
Tested-by: Wood, Brian J <brian.j.wood@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Lokesh Gupta [Mon, 6 Feb 2012 21:23:03 +0000 (22:23 +0100)]
[PORT FROM R2] atomisp: CSS/FW release from Synergy BL
03Feb2012
BZ: 23295
To crop off affected by filtering completely, crop size is changed 8 from 12.
Blue/Green woolen yarn will disappear.
This should be applied with new firmware together.
Change-Id: If6e48e991dd26cea0767d7aa6cb1e2fdb26a8690
Orig-Change-Id: Ic403b07e663b04c7c9ca2c83fce6d5ad005b3d51
Signed-off-by: Lokesh Gupta <lokesh.gupta@intel.com>
Reviewed-on: http://android.intel.com:8080/34899
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
ziyux.jiang [Mon, 6 Feb 2012 16:17:19 +0000 (00:17 +0800)]
[PORT FROM R2] mt9e013: sometimes OTP memory initialized with error while sensor register.
BZ: 23295
MT9E013_BYTE_MAX(that is, the block bytes for one times read) should be decreased
to 30 to not be bigger than rx fifo depth(=32), if MT9E013_BYTE_MAX >= 32, the OTP
data read from sensor via i2c may be corrupted.
Change-Id: Idbe3bf13ffcf194d8eec95268993afb5155fd488
Orig-Change-Id: Ic857285b0915ef9696345e94244531fe57fab7a2
Signed-off-by: ziyux.jiang <ziyux.jiang@intel.com>
Reviewed-on: http://android.intel.com:8080/34898
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Robert Jong-A-Lock [Fri, 20 Jan 2012 14:05:25 +0000 (15:05 +0100)]
[PORT FROM R2] atomisp: mt9e013: add D1 PAL and D1 NTSC to video res. table, timing update.
BZ: 23295
Request from video team to add D1 PAL and D1 NTSC resolution to video table.
Resolution uses binning and sensor scaling.
Support for 20% DVS.
Includes minor update to settings comments to improve readability.
Unified timing information (ppl,lpf) for 720p and WVGA with other resolutions.
Change-Id: Ibf64c35113fb4fe29791bc5c6106b81ca9599436
Orig-Change-Id: I2d7b9538ee583c4bf3ccbf836e11fe73c83ad7fe
Reviewed-on: http://android.intel.com:8080/34897
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Robert Jong-A-Lock [Wed, 18 Jan 2012 14:57:00 +0000 (15:57 +0100)]
[PORT FROM R2] atomisp: mt9e013: sensor settings updated for max VBI, change order
BZ: 23295
Sensor settings need to be updated for maximized VBI.
The order of the regsiters was changed, to speedup loading of registers.
Removed, debug code that was left behind.
Change-Id: Iedbfffb66fec9e209a63245a61efc4638d37b7aa
Orig-Change-Id: I16c72ff96a5b8da9e8e4f509d4b30f928e42254d
Reviewed-on: http://android.intel.com:8080/34896
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Austin Hu [Wed, 8 Feb 2012 08:36:17 +0000 (16:36 +0800)]
GFX-Display: Add code to support GI Sony command mdoe and video mode MIPI panels.
BZ: 18256
Change-Id: I32da855ec82fe3ccefe6e40408b4bc0774451a8d
Signed-off-by: Jim Liu <jim.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34457
Reviewed-by: Mahe, Erwan <erwan.mahe@intel.com>
Tested-by: Mahe, Erwan <erwan.mahe@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Austin Hu [Sun, 15 Jan 2012 06:47:26 +0000 (14:47 +0800)]
GFX-Display: enabled Enzo MIPI panel with command mode.
BZ: 20137
The patch depends on patch #31959.
Fixed the Enzo panel turning on unstability issue in command mode, by refining
the panel resetting process, updating DSI controller registers in the init
process, sending strict DCS command sequence according to the ITP scripts when
power on/off the panel, setting MIPI device unready and power gating DSI PLL
when disabling DSI PLL.
Now Enzo panel could be turned on in command mode with IFWI which displays
"Intel" logo splash in command mode, Android UI could launch, and suspending
(D0i3) / resuming could work as well.
Change-Id: I2672bddcc1d6043ea3a11c3d5eb3bcb0f260f1b1
Signed-off-by: Ivan Chou <ivan.y.chou@intel.com>
Signed-off-by: Austin Hu <austin.hu@intel.com>
Reviewed-on: http://android.intel.com:8080/31960
Reviewed-by: Mahe, Erwan <erwan.mahe@intel.com>
Tested-by: Mahe, Erwan <erwan.mahe@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
gwang23 [Thu, 2 Feb 2012 07:28:08 +0000 (15:28 +0800)]
Graphics: Integrate IMG DDK from drop
ED789263 to drop
ED793010
BZ: 22168
Change-Id: I0f27d5008c1af4382d6084e472bc25a1a86a32d7
Signed-off-by: gwang23 <gang.a.wang@intel.com>
Signed-off-by: Tong, Bo <box.tong@intel.com>
Reviewed-on: http://android.intel.com:8080/33694
Reviewed-by: Ye, John <john.ye@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Austin Hu [Sun, 15 Jan 2012 06:41:06 +0000 (14:41 +0800)]
GFX-Display: enabled Enzo MIPI panel with video mode.
BZ: 20132
1. Also included Enzo panel's command mode codes.
2. Fixed the "Android" splash hang issue in command mode, because when
updating DBI panel, it shouldn't clean the IN_DSR flag if FB is
damaged, as the flag will be cleaned when entering DSR.
3. Fixed the Enzo panel power on unstability issue in command mode,
by not setting DSI PLL in mdfld_auo_dsi_dbi_power_on(), as it has
been set in mdfld_dsi_controller_dbi_init().
Change-Id: I1f71711fafb300ee9ab73015f8144958c7412f57
Signed-off-by: Ivan Chou <ivan.y.chou@intel.com>
Signed-off-by: Austin Hu <austin.hu@intel.com>
Signed-off-by: Tong, Bo <box.tong@intel.com>
Reviewed-on: http://android.intel.com:8080/31959
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
yifei.xue [Tue, 7 Feb 2012 02:38:08 +0000 (10:38 +0800)]
Graphics: add support for disable HDMI config
BZ: 20871
While disable the CONFIG_MDFD_HDMI, add two MACRO to disable the hdmi_do_hotplug_wq and hdmi_do_audio_wq to make compiling successful.
Change-Id: I09f4fc1bfcc3f6a0a8d6aaa7a2b3e90f7ff51ca9
Signed-off-by: yifei.xue <yifeix.xue@intel.com>
Signed-off-by: Tong, Bo <box.tong@intel.com>
Reviewed-on: http://android.intel.com:8080/34261
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Omair Mohammed Abdullah [Tue, 27 Dec 2011 06:25:23 +0000 (11:55 +0530)]
[PORT FROM R2]audio: sn95031: added GPIO support for jack detection
BZ: 14181 20155
PR3.2 devices have a GPIO pin which can be used to detect high impedance
headsets.
Added GPIO support in the codec driver so that whenever an insert interrupt is
received and the micbias value is out of range, it checks the GPIO pin and
reports the jack as a HEADSET if the GPIO pin says that there is a headset.
PR2 devices don't have this GPIO pin and cannot support high impedance headsets.
PR3.1 and PR3.0 devices need to add a pull up/down resistor (enabled in IFWI) so
that the GPIO_AON_77 value doesn't fluctuate.
Change-Id: Iea972f515584354903e045ca3c2e631713439c3f
Old-Change-Id: Id524cc3bda8f7fb9688f7f2df4ff9bfabe99acb0
Signed-off-by: Omair Mohammed Abdullah <omair.m.abdullah@intel.com>
Reviewed-on: http://android.intel.com:8080/34870
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
namarta [Fri, 3 Feb 2012 10:41:54 +0000 (16:11 +0530)]
[PORT FROM R2]audio: mfld_machine: Increased the wake lock duration from 1 second to 2 seconds
BZ: 22014
If frequent jack insertion/removal is done when phone is in S3 state, jack
events are reported by ALSA but they are not propagated to Andriod due to
hardcoded delay of 1 second in the HeadsetObserver before sending the intent.
But phone goes back to S3 state in 1 second, so intent is sent only when phone
wakes up.
Increased the wake lock duration to 2 seconds because duration of 1 second was
not sufficient.
Change-Id: I21cf5b9bb516051fbc0e0d9c2126335d03bde3fa
old-Change-Id: I64dd3d0a28107082177c88ab92c65d3b216b5f6d
Signed-off-by: namarta <namartax.kohli@intel.com>
Reviewed-on: http://android.intel.com:8080/34871
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Li Zeng [Thu, 5 Jan 2012 06:56:35 +0000 (14:56 +0800)]
[PORT FROM R2]ved/vec: reduce ttm fence timeout length
BZ: 19044
When ved got invalid/wrong bitstream and no WDT enabled by ved, driver has to wait ttm fence timeout. Current length of timeout is 3s, reduce it ot 1s to improve respond time.
Change-Id: I1b6b0face2699215fc7ede32cafde4c665ee7999
Signed-off-by: Li Zeng <li.zeng@intel.com>
Reviewed-on: http://android.intel.com:8080/32572
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Li Zeng [Wed, 4 Jan 2012 09:41:43 +0000 (17:41 +0800)]
[PORT FROM R2]ved: remove delay when submit multiple slices
BZ: 18451
Root cause is driver delay 250us for each slices when submit multiple slices at one time. The issue clip has much number of slices per frame
Remove the delay to fix the issue. The delay is add to workaround an old ved firmware issue which was already fixed in latest ved firmware
Change-Id: Iaabaf9ef3cb53c3f2eb4d8202e679c170cea8177
Signed-off-by: Li Zeng <li.zeng@intel.com>
Reviewed-on: http://android.intel.com:8080/32571
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Rocher, JeremyX [Tue, 7 Feb 2012 09:29:23 +0000 (10:29 +0100)]
uuid: restore the old version of hash for device id generation
BZ: 22684
To match the usb serial number, the uuid should use the same
algorithm.
Change-Id: Ia31bad349b683519e895e729e153b3efc0ab4b80
Signed-off-by: Rocher, JeremyX <jeremyx.rocher@intel.com>
Reviewed-on: http://android.intel.com:8080/34242
Reviewed-by: Tardy, Pierre <pierre.tardy@intel.com>
Tested-by: Zhang, Dongxing <dongxing.zhang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
shenghua.lu [Thu, 5 Jan 2012 09:35:27 +0000 (17:35 +0800)]
MFLD_DV10: display and touchscreen support components
BZ:20808
This commit contains the display and touchscreen driver
component changes necessary to support the MFLD DV10
tablet device..
Signed-off-by: Lu Shenghua <shenghua.lu@intel.com>
Change-Id: Ibb09c5de4144e8673c1a580f22ab376f08bbe90d
Reviewed-on: http://android.intel.com:8080/32093
Reviewed-by: Wood, Brian J <brian.j.wood@intel.com>
Reviewed-by: Seibel, Eric <eric.seibel@intel.com>
Tested-by: Seibel, Eric <eric.seibel@intel.com>
Tested-by: Wood, Brian J <brian.j.wood@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Axel Haslam [Tue, 7 Feb 2012 11:18:59 +0000 (12:18 +0100)]
gpio: langwell: fix possible null pointer dereference.
BZ: 22932
The function checks for null and then makes a dereference
of the same pointer. This is a no-no.
Change-Id: I30e10396e13f5f69cfe5a01d30526c840286da08
Signed-off-by: Axel Haslam <axelx.haslam@intel.com>
Reviewed-on: http://android.intel.com:8080/34277
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Yang, Bin <bin.yang@intel.com>
Reviewed-by: Li, Ning <ning.li@intel.com>
Reviewed-by: Fiat, Christophe <christophe.fiat@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
feng wang [Fri, 3 Feb 2012 06:07:57 +0000 (14:07 +0800)]
usb:langwell_ude: Check ep desc to guarantee it is not disabled
BZ: 20895
A panic is raised in langwell_irq as ep->desc is set to NULL.
In langwell_ep_disable, ep is disabled and spin_lock get unlocked
in langwell_irq to handle the trans complete. In function done,
ep->desc is accessed and we meet NULL pointer. Function done will
be skipped as it is called in nuke to release resources. So no leakage.
Change-Id: I0c72ad83e12b6e61e04128dbafb492417eb1de01
Signed-off-by: feng wang <feng.a.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/33821
Reviewed-by: Zhuang, Jin Can <jin.can.zhuang@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
ShuoX Liu [Mon, 14 Nov 2011 04:52:08 +0000 (12:52 +0800)]
[PORT FROM R2] VRTC: Sync time to MSIC RTC when NTP enabled
BZ: 22580
NTP uses update_persistent_clock->...->vrtc_set_mmss to set vRTC.
We should sync the modified time to MSIC RTC.
Change-Id: I2376909e401f96c972c58de6bf2bfdfef1398d63
Signed-off-by: ShuoX Liu <shuox.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/29665
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Zhang, Yanmin <yanmin.zhang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Mon, 6 Feb 2012 22:04:10 +0000 (14:04 -0800)]
CPUFREQ: PORT FROM R2: expose DOWN_DIFFERENTIAL via sysfs
BZ: 22582
Expose down_differential through sysfs for experiment with CPU freq
using different workload.
Change-Id: Ic0f4cf55a6a641b42aeed77101d51bb7298c8b73
Signed-off-by: Winson Yung <winson.w.yung@intel.com>
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/34161
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
sathyanarayanan kuppuswamy [Wed, 11 Jan 2012 21:09:53 +0000 (13:09 -0800)]
Recommended kernel config options for more secure system
BZ 19489
enable : CONFIG_DEBUG_SET_MODULE_RONX
disable : CONFIG_DEVMEM
set : CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
CONFIG_DEBUG_SET_MODULE_RONX=y
Enabling this will cause the kernel modules to also get NX/RO protection, not just the core kernel;
no perf impact (few hundred cycles on loading a module, but no runtime impact)
CONFIG_DEVMEM=n
Nothing SHOULD be using it in a non-legacy-linux environment.
CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
64Kb is a better/safer default without negative impact to userspace in practice.
Change-Id: Ic5cc04f678688eb9c08c2fa68898eaf0385d5499
Reviewed-on: http://android.intel.com:8080/31582
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Tardy, Pierre <pierre.tardy@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Hong Liu [Tue, 31 Jan 2012 02:50:32 +0000 (10:50 +0800)]
[PORT FROM R2] atmel_mxt224: change idle acquisition interval back to 32ms
BZ: 20572
Idle acquisition interval can impact power consumption for idle-display-on
case on our platform. The 25mW interval consumes ~14mW, while 32ms
consumes ~7mW and can still maintain the user experience, no touch delay
from idle to active.
Change-Id: I5277eb4d9a00f10ba15960a080831d9753f39dc8
Orig-Change-Id: Ic0b60816bd710b8c80e2dc6f1cf5e538fcda7f49
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34461
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Bin Gao [Thu, 2 Feb 2012 02:35:59 +0000 (18:35 -0800)]
atomisp: use type 1 instead of message bus for PCI config space access.
BZ: 2243
We need use type 1 standard PCI config space access for real
PCI devices in Penwell Soc. These devices are 0:0:0(host bridge),
0:2:0(graphics) and 0:3:0(ISP).
The original codes in arch/x86/pci/mrst.c missed the ISP device
(00:03.0) from type 1 device white list. This patch fixes it.
Change-Id: Ib8348764148e94a657783dce8a53d44ffad6531b
Signed-off-by: Bin Gao <bin.gao@intel.com>
Reviewed-on: http://android.intel.com:8080/33628
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Tao, Jing <jing.tao@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Tue, 7 Feb 2012 09:49:24 +0000 (17:49 +0800)]
sdhci-pci: remove sd detect pin enabling workaround
BZ: 22694
SD detect GPIO aon_69 needs to works as a normal GPIO function. Driver
has to hack and change this. But finally IFWI help to change aon_69 to
work as normal GPIO function. So remove the software workaround
Change-Id: Ic9354588a5bbf52e32816815daa184dab55c1f75
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/34250
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
samix.lebsir [Fri, 25 Nov 2011 12:45:57 +0000 (13:45 +0100)]
[PORT FROM R2] [hsi] change TTY_HANGUP_DELAY to 100000
BZ: 9832
change TTY_HANGUP_DELAY to 100000 in hsi_ffl_tty.c
a workaround to the issue: phone lost signal while sending MMS
Change-Id: Ia0969ede226b1ef8e8692df15b205497b8fec08a
Orig-Change-Id: Ibdb2e17c9ef1fb9c86a68f59325d04411fa9c026
Signed-off-by: samix.lebsir <samix.lebsir@intel.com>
Reviewed-on: http://android.intel.com:8080/34082
Reviewed-by: Myara, David <david.myara@intel.com>
Reviewed-by: Predon, Frederic <frederic.predon@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Yu Wang [Mon, 16 Jan 2012 06:09:12 +0000 (14:09 +0800)]
ehci/penwell: Do EHCI hardware workaround.
BZ: 18046
Sometimes, the mouse and keyboard will auto disconnect during using. And
after disconnect 60 seconds, host auto re-enum the device.
Rootcause:
On Intel Medfield platform, EHCI hardware update FRINDEX register before
update completed QH's ACTIVE flag. This behavior caused EHCI driver
can't find the completed QH in some cases. So EHCI would not send the
QH which is already completed. It need to SW to re-submit QH. But EHCI
driver lost it, then class driver would not resubmit URB forever.
Change-Id: Ic492e162b001d3cdaf1d098f9366c625e0ad10de
Signed-off-by: Yu Wang <yu.y.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/32125
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Wu, Hao <hao.wu@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Seema Pandit [Mon, 6 Feb 2012 17:45:30 +0000 (09:45 -0800)]
panel type read from gct table for CTP.
BZ: 20804
This patch adds the support to read the panel type and timing info
from gct table for clovertrail platform. Depends on corresponding FW
changes in IFWI.
Change-Id: Ib47427bf0f43576c5a90b40eb0f5709816917ced
Signed-off-by: Seema Pandit <seema.pandit@intel.com>
Reviewed-on: http://android.intel.com:8080/34166
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: Ai, Ke <ke.ai@intel.com>
Reviewed-by: Liu, Jim <jim.liu@intel.com>
Reviewed-by: Tong, BoX <box.tong@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Wu, Hao [Fri, 3 Feb 2012 12:22:25 +0000 (20:22 +0800)]
usb/penwell_otg: add charger detection flow for Clovertrail
BZ: 14625
This patch adds charger detection flow for Clovertrail, which
is different than what we used for MFLD.
Change-Id: I7d0442967babf08aa31f42209f1c79b11ce8c6d7
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/33883
Reviewed-by: Wang, Feng A <feng.a.wang@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Hong Liu [Tue, 31 Jan 2012 02:21:43 +0000 (10:21 +0800)]
[PORT FROM R2] atmel_mxt224: restore power config during resume
BZ: 19465
If we put palm/face on screen during touch resume, touch may send
multi-point touch data to driver before it performs a reset. Then after
reset, all touch state will be cleared in touch firmware, and it will
not report finger lift for the 2nd finger. This causes driver always report
multi-touch data (2 points in our driver config) for singer finger operation.
For apps don't support multi-touch operation (like phone app), it looks like
touch is dead at that time.
Fixed by do a power config restoration and then do manual calibration instead
of doing a soft reset during late resume.
Change-Id: Iba3f67debd2486d6830298dd87a8c2368e8fa520
Orig-Change-Id: I710e75bfab5170ee7a91029db28c8da3d1fa6115
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34008
Reviewed-by: Cai, Stanley W <stanley.w.cai@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Hong Liu [Mon, 26 Dec 2011 07:44:43 +0000 (15:44 +0800)]
[PORT FROM R2] atmel_mxt224: manually check calibration stop condition
BZ: 19465
If auto-calibration is stopped immaturely with wrong condition, certain
area of touchscreen is not working after calibrated with finger touching
on it.
Manually check the calibration stop condition to avoid auto-calibration
being stopped immaturely.
Change-Id: Ic6baa38c54d703862e4d57aa84ea5c8de7aaf8c8
Orig-Change-Id: I6280fb6a2171f5e5bf5f5ec0318fccaa9db0a5cb
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34007
Reviewed-by: Cai, Stanley W <stanley.w.cai@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Alek Du [Sun, 29 Jan 2012 01:50:23 +0000 (09:50 +0800)]
[PORT FROM R2] hsu: port recent fix from R2
BZ: 21502
The fix hsu: turn off RX dma before runtime suspend was merged in R2
need port it to R3.(BZ 18936)
Also include a fix for holding tty ref during rx dma handling.(BZ 21234)
Change-Id: I88647c9fb50d7f8c3056b70d37b5a8fe972ec645
Signed-off-by: Alek Du <alek.du@intel.com>
Reviewed-on: http://android.intel.com:8080/33119
Reviewed-by: Cai, Stanley W <stanley.w.cai@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Gilles Rimauro [Fri, 6 Jan 2012 16:13:25 +0000 (17:13 +0100)]
arch/x86: Clean up mxt224 platform data
BZ: 20624
Remove useless platform data functions for mxt224 touchcreen
driver. Let the driver take defaults one instead.
Remove valid_interrupt function since it is the exact same than
driver's default one.
Remove init_platform_hw and exit_platform_hw functions since
they are empty.
Change-Id: Iff0344ece9971903c0f72f960a5be8d25fcabf51
Signed-off-by: Gilles Rimauro <gilles.rimauro@intel.com>
Reviewed-on: http://android.intel.com:8080/32376
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Norvin Shuster [Mon, 23 Jan 2012 17:05:07 +0000 (09:05 -0800)]
Disk Encryption: Enable user file system encryption
BZ: 20830
Include the device-mapper in the kernel configuration o
Include crypto SHA256 and CBC in the kernel configuraiton.
Change-Id: Ic75bbe96ebf8ddbb4799119eb69aa3a1bea590bd
Signed-off-by: Norvin Shuster <Norvin.Shuster@intel.com>
Reviewed-on: http://android.intel.com:8080/32762
Reviewed-by: Allyn, Mark A <mark.a.allyn@intel.com>
Reviewed-by: Shuster, Norvin <norvin.shuster@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Mangalampalli, Jayant <jayant.mangalampalli@intel.com>
Tested-by: Mangalampalli, Jayant <jayant.mangalampalli@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>