review.tizen.org Git - platform/kernel/kernel-mfld-blackbay.git/log

[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>

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>

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>

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>

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>

[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>

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>

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>

[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>

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>

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>

[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>

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>

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>

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>

[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>

[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>

[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>

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>

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>

n_gsm.c : More cleanup to fullfill Linux 3.0 API

BZ: 21896

- Struct file *filp in tiocmget and tiocmset are not nedded anymore.
- Need to cast dummy file * with correct type.

Change-Id: I63c1b36c065c92509fe957e107cee2666386d646
Signed-off-by: Vincent Pillet <vincentx.pillet@intel.com>
Reviewed-on: http://android.intel.com:8080/33515
Reviewed-by: Guerard, Christophe <christophe.guerard@intel.com>
Reviewed-by: Predon, Frederic <frederic.predon@intel.com>
Reviewed-by: Robert, Denis <denis.robert@intel.com>
Reviewed-by: Lebsir, SamiX <samix.lebsir@intel.com>
Tested-by: Lebsir, SamiX <samix.lebsir@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

usb:host:usb devices can be detected but can't work when boot up
system with Hub&keyboard&mouse connected

BZ: 19184

When registering a new composite driver in system start up, pull up D+ will
be called.USBCMD registers will be changed and host controller will be halt.
This will lead to host controller halt in a_host mode.

Change-Id: I82076437c9eb9e115f98102653fb3a0861943de8
Reviewed-on: http://android.intel.com:8080/32475
Reviewed-by: Wang, Feng A <feng.a.wang@intel.com>
Reviewed-by: Zhuang, Jin Can <jin.can.zhuang@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: Wu, Hao <hao.wu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] atomisp: fix part of the preview is black after capturing

BZ: 22233

ORIG-BZ: 15781

we need to set the static pointer "sc_table" to NULL when invalidated.

Change-Id: Iec92c32632c20bdceb262ee921d29d52c76c8601
Orig-Change-Id: I9ebb9afea74f74e122d48221b1e346dff67d6428
Signed-off-by: Yoshio Wada <yoshio.wada@intel.com>
Reviewed-on: http://android.intel.com:8080/33281
Reviewed-by: Hu, Gang A <gang.a.hu@intel.com>
Reviewed-by: Samurov, Vitali <vitali.samurov@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Kantola, Lasse <lasse.kantola@intel.com>
Reviewed-by: Tuppurainen, Miikka <miikka.tuppurainen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Reviewed-on: http://android.intel.com:8080/33905
Reviewed-by: Lampila, KalleX <kallex.lampila@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>

[Graphics/Display]: Port a bunch of patches from R2

BZ: 17008

This patch includes below bug fixing

0002-GFX-pvr-PVR-Vulnerability-kernel-part.patch:                BZ:16572
0003-Gfx-Display-Remove-unecessary-checks-during-HDMI-aud.patch: BZ:15315
0004-Graphics-Perf-Don-t-touch-GL3-island-if-GL3-is-disab.patch: BZ:19285
0005-GFX-DISPLAY-flush-flip-queue-when-turnning-screen-of.patch: BZ:20078
0006-GFX-Display-fix-screen-black-screen-problem.patch:          BZ:20280
0007-GFX-display-Correct-missing-HDMI-audio-interrupt-cas.patch: BZ:18865
0008-Gfx-Display-Solve-HDMI-mess-issue-when-setting-mode-.patch: BZ:19601

0007-GFX-Display-fix-HDMI-can-not-resume-issue-when-bench.patch  BZ:13403
0008-GFX-Display-Fix-Maximum-Display-Timing-Determination.patch  BZ:16583
0009-Gfx-Display-fix-issue-of-uninitialized-variable-in-p.patch  BZ:15899
0010-Gfx-Display-Add-protection-for-DSPBCNTR-reg-access.patch    BZ:16589
0011-Gfx-Display-Add-mutex-protection-for-Display-PIPE-B-.patch  BZ:18201
0012-GFX-Display-display-plane-state-should-be-set-after-.patch  BZ:18486
0013-Gfx-Display-invalidate-the-hdmi-mode-if-it-exceeds-D.patch  BZ:18659
0014-GFX-Display-if-not-get-EDID-fix-hard-code-to-720.patch      BZ:18659
0015-Gfx-Display-Fix-app-ANR-issue-when-suspend-resume-du.patch  BZ:18681
0016-GFX-Display-fix-resume-abnormal-after-HDMI-unplug.patch     BZ:16837
0017-GFX-Display-fix-DPMS-on-off-FIFO-not-empty-issue.patch      BZ:18447
0018-Display-HDMI-Add-new-logic-to-parse-video-data-block.patch  BZ:19218
0019-Gfx-Display-Add-print-in-EDID-reading-and-four-block.patch  BZ:19218

Change-Id: I11e2b2c6b1ba9e7139b2460ede9328d27d63a3cf
Signed-off-by: Tong, Bo <box.tong@intel.com>
Reviewed-on: http://android.intel.com:8080/32132
Reviewed-by: Lu, Liuhui <liuhui.lu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

intel_scu_ipc: remove the un-neccessary capability check inside
IPC ioctl calls. This prevents user space app (i.e. Android app)
from getting our fw information such as IFWI fw version.

BZ: 20905

Change-Id: I4b13346026c450f365111856ee89be2cc665f22c
Signed-off-by: Winson Yung <winson.w.yung@intel.com>
Reviewed-on: http://android.intel.com:8080/32689
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: Yang, Bin <bin.yang@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

sdhci-pci: use X86_MDFLD to replace X86_MRST

BZ: 22235

In R3, kernel is using X86_MDFLD but not X86_MRST for MFLD
project. sdhci-pci.c need to be updated accordingly otherwise
some functions depends on X86_MDFLD cannot be used.

Change-Id: Ica51ad2095d497cf7bee00e44f510cb3cc5678c0
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/33851
Reviewed-by: Tang, Richard <richard.tang@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>

FIX COMPILATION WARNING

BZ: 15901

blackbay_pr2.c:170: warning: function declaration isn't a prototype
blackbay_pr2.c:96: warning: 'audience_free_resources' defined but not used

Change-Id: Ie9363e06fa9a9e166d481344bb0fadf33b147943
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/33260
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

FIX COMPILATION WARNING

BZ: 15908

switch_mid.c: In function 'headset_print_state':
switch_mid.c:99: warning: control reaches end of non-void function
switch_mid.c: In function 'headset_print_name':
switch_mid.c:73: warning: control reaches end of non-void function

Change-Id: I35b34c6b4d9f4c05ed6190df5912b046bc5d5e6f
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/33261
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Deng, BingX <bingx.deng@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>

[PORT FROM R2] driver: intel_scu_watchdog: remove all gating from interrupt handler

BZ: 21273

There was some lagacy gating code in the driver from the days
when the driver would do the initial setting of the clock.

Change-Id: Id5520a832cc7d0e90fe39876ede62bcbe5d6486c
Reviewed-on: http://android.intel.com:8080/33944
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: Lebouc, Christophe <christophe.lebouc@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] Audio: enable CONFIG_SND_ALOOP to get Alsa loopback virtual soundcard

BZ: 6685

To enable the Alsa loopback virtual device, the CONFIG_SND_ALOOP must be
set to yes to get snd-aloop built and linked to the kernel.
This virtual sound card consists of 2 devices:

hw:Loopback,0
hw:Loopback,1
If an application outputs its audio to one of the subdevices e.g. say
hw:Loopback,0,0 the audio will be available as input in the corresponding
subdevice hw:Loopback,1,0 because the whole point for this card is to
send the signal back to itself.

The loopback soundcard is needed to enable WiDi capability, as detailled
in use case description of P_UC_20322.

Note: Cherry pick of Change-Id: I61acb233c5568b80b0d6e9f1f12ad6c673953eb3 to ICS branch
did not work in enabling the loopback virtual soundcard. CONFIG_SND_ALOOP needs to be
enabled after the CONFIG_SND_DRIVERS.

Change-Id: Ia350cd40ce3dd558a6eb24c3ac5ed971649677bd
Orig-Change-id: I61acb233c5568b80b0d6e9f1f12ad6c673953eb3
Signed-off-by: Rajneesh Chowdhury <rajneeshx.chowdhury@intel.com>
Reviewed-on: http://android.intel.com:8080/31589
Reviewed-by: Soulard, MathieuX <mathieux.soulard@intel.com>
Reviewed-by: Veeramani, Karthik <karthik.veeramani@intel.com>
Reviewed-by: Poornachandran, Rajesh <rajesh.poornachandran@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Marotte, Fabien <fabien.marotte@intel.com>
Reviewed-by: Bachot, Jean-michelX <jean-michelx.bachot@intel.com>
Tested-by: Zurmely, PierreX <pierrex.zurmely@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

ctp_config: enable fuse for CTP

BZ: 21218

ICS need to use FUSE file system to mount sdcard. Enable FUSE
in kernel

Change-Id: I18e8549eee7609a34fca36247ad326258ee3e644
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/33502
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Seibel, Eric <eric.seibel@intel.com>
Tested-by: Seibel, Eric <eric.seibel@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>

GPIO-KEYS: combine two gpio-keys devices into one

BZ: 20893

There are currently two "gpio-keys" platform devices defined in the
kernel with the same string name, one is in blackbay_pr2.c and the
other in mrst.c. This is causing problem when registering the second
one. Solution is to combine them into one platform device.

Change-Id: I83385db305f68e59c7878aed46b5defd66ec9d8e
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/32692
Reviewed-by: Gross, Mark <mark.gross@intel.com>
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>

GFX-display: Audio can't play on hdmi after suspend phone

BZ: 18580

In this scenario, runtime_idle returns busy, so runtime_suspend should
not be called by runtime pm core. This is the way in GB. But in ics,
runtime_suspend is called, it will disable hdmi plane, while audio sends
data to it.

This patch add some code in runtime_suspend to detect whether audio is busy.

Change-Id: I5b1b20943e2344d15a5800091e7f3e1137e6667b
Signed-off-by: Geng Xiujun <xiujun.geng@intel.com>
Reviewed-on: http://android.intel.com:8080/32311
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>

Enable config option for I2C_GPIO for clovertrail.

BZ: 14963

Enable config option I2C_GPIO for clovertrail. This is required for
HDMI monitor edid read functionality.

Signed-off-by: Seema Pandit <seema.pandit@intel.com>
Change-Id: I2843aa7d0d7fde8f328be1010b7074fa5d2495c1
Reviewed-on: http://android.intel.com:8080/31245
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Enable edid read, ported to ICS.

BZ: 14963

This patch includes changes to enable EDID read on clovertrail platform, hot-plug functionality for clovertrail is not enabled yet.

Change-Id: I9b00c4955ec944ebf84aa6c0254fba92d4620ad5
Signed-off-by: Seema Pandit <seema.pandit@intel.com>
Reviewed-on: http://android.intel.com:8080/31244
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Clocking changes for CTP, for HDMI and DSI

BZ: 18114

Clocking changes for CTP. Requird for HDMI and DSI.

Change-Id: Ifed5001f1c110e4a9b052cbcdb898a88fbef976e
Signed-off-by: Seema Pandit <seema.pandit@intel.com>
Reviewed-on: http://android.intel.com:8080/29644
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

GFX-DISPLAY: Add support for CMI 720p video mode MIPI display.

    BZ: 13458

    video mode support for CMI panel 720p used on CTP
    Added new files. h8c7_vid.c h8c7_vid.h

Change-Id: I6f1eb1b1f2f3c963fb6c564de842551826af8da2
Signed-off-by: Prabu Renganathan <prabu.renganathan@intel.com>
Reviewed-on: http://android.intel.com:8080/29772
Reviewed-by: Mai, Leonard <leonard.mai@intel.com>
Reviewed-by: Pandit, Seema <seema.pandit@intel.com>
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] Update logging mechanism to match SCU implementation 21613

BZ: 21886

Update logging mechanism to match SCU implementation 21613

Change-Id: Ic6809e829e63e53daa5cab14f8dba00b2d8aec17
Reviewed-on: http://android.intel.com:8080/33709
Reviewed-by: Lebouc, Christophe <christophe.lebouc@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>

[PORT FROM R2] atomisp: mt9e013: add fuseid data to sensor's private data

BZ: 21906

ORIG-BZ: 15475

FUSEID information is necessary to userspace. This patch adds FUSEID
to sensor's private data.

Change-Id: I12eb18309de497db8d9983dc4c632e5339cd2096
Orig-Change-Id: Ic9995c477d9930e87ef958a73d3ac9b64d39b29c
Signed-off-by: David Cohen <david.a.cohen@intel.com>
Reviewed-on: http://android.intel.com:8080/27052
Reviewed-by: Jong-a-lock, Robert <robert.jong-a-lock@intel.com>
Reviewed-by: Tuppurainen, Miikka <miikka.tuppurainen@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Reviewed-on: http://android.intel.com:8080/33538
Reviewed-by: Lampila, KalleX <kallex.lampila@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>

[PORT FROM R2] mt9m114: mt9e013: add return value checking to prevent further processing when i2c err happens

BZ: 21906

ORIG-BZ: 19774

When condition mt9m114_MAX_WRITE_BUF_SIZE matched, the __mt9m114_buf_reg_array
called in mt9m114_write_reg_array doesn't use the return value to prevent
further processing in case of i2c transfer err happens. The same scenario exists
with mt9e013.

This patch adds the return value checking to resolve this issue.

Change-Id: I17c7460b6314f8f87698f89db56a30f936377c85
Orig-Change-Id: I9f30c699dcb598ceaaf938f8aca6b0258a2085b3
Signed-off-by: Huang Shenbo <shenbo.huang@intel.com>
Signed-off-by: David Cohen <david.a.cohen@intel.com>
Reviewed-on: http://android.intel.com:8080/32483
Reviewed-by: Hu, Gang A <gang.a.hu@intel.com>
Reviewed-by: Jong-a-lock, Robert <robert.jong-a-lock@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Reviewed-on: http://android.intel.com:8080/33537
Reviewed-by: Lampila, KalleX <kallex.lampila@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>

gpadc: enable GPADC on Clovertrail

BZ: 21885

Platform device creation is handled by the MSIC MFD driver, add
Clovertrail support to mrst.c. The adc driver is changed since
GSM pulse mode is no longer supported on Clovertrail.

Change-Id: I933810065a42305d0c4aa5029db8a94fb6aed4eb
Signed-off-by: Li, Ning <ning.li@intel.com>
Reviewed-on: http://android.intel.com:8080/33511
Reviewed-by: Zhang, Shijie <shijie.zhang@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>

[PORT_FROM_R2]mmc: panic: using the api provided by PMU driver in panic mode

BZ: 21728

To power up host controller in panic mode, pci_set_power_state() is not
suitable since it will cause schedule in panic mode.

PMU driver has provided an API named pmu_set_lss01_to_d0i0_atomic which
is for lss01 device only to put it in D0i0 mode, and it can only be used
in atomic context.

Change-Id: I47b4c6e2c61d570999a57bcdf80554cab91401d2
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/33349
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[Port from R2]Fuel Gauging : Port MSIC Fuel Gauging driver to R3

BZ: 21080

This patch is to port the coloumb counter based Medfield
MSIC Fuel Gauging Driver from R2.

Change-Id: I54cd82add2abcc08b044984af28d32adc63d6995
Signed-off-by: Saranya Gopal <saranya.gopal@intel.com>
Reviewed-on: http://android.intel.com:8080/32846
Reviewed-by: Pallala, Ramakrishna <ramakrishna.pallala@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]max17042: Vempty param to lower value to adjust empty compensation

BZ: 15725

This patch set the Vempty parameter to Lower value(0x7d5a) to
improve the empty compensation behaviour on max17042 FG chip.

Change-Id: Id628582c7905c538b61baddf689ab8bbb89e66c1
Orig-Change-Id: I07cfb1ee69b01749c2902bd587b4dfd2074616c2
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/33509
Reviewed-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]max17042: enable fuel gauge interrupts for Vmin and 0%

BZ: 20429

This patch enables FG interrupts, cleans up the existing
set_soc_intr_thresholds function and sets the voltage, SoC and
temperature thresholds to default values. Also adds the wake
capability for Low Battery condition.

Change-Id: I024b9852210419e2d1a0105680ac5365afe624b5
Orig-Change-Id: I6b60375fdf3ebb4f045d23b03c1f7c6f8ec4bd23
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/33508
Reviewed-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

ov8830: change full resolution mode to use 4 lanes

BZ: 21601

Change-Id: I1d1b5980947938195330de68abf050963864a84b
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/33230
Reviewed-by: Jong-a-lock, Robert <robert.jong-a-lock@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@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>

ov8830: adjust PLL settings for new full resolution mode

BZ: 21601

The reference mode design from Omnivision uses 24 MHz
external clock, Clovertrail clock is 19.2 MHz. Adjust
the sensor PLL registers for this difference.

Change-Id: I2f7e81889f579cf6fc5dc0445706bbb7cd0209f7
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/33229
Reviewed-by: Jong-a-lock, Robert <robert.jong-a-lock@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@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>

ov8830: add full resolution mode 8 Mpix, 3264x2448 pixels

BZ: 21601

Change-Id: I41262f65bba11f758f1f5146a12baefc13f3c98d
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/33228
Reviewed-by: Kruger, Jozef <jozef.kruger@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>

[PORT FROM R2] [CRASHLOG] Fix capture of new SCU halts cases kernel

BZ: 21339

Change-Id: I9117fa60da04bb7ba455a59ee25c5a838d227cea
Reviewed-on: http://android.intel.com:8080/33350
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: Lebouc, Christophe <christophe.lebouc@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] [CRASH] Capture other SCU halt sources kernel

BZ: 19772

Change-Id: Ica09153a8dbbf66072dca1720313a1fb0461b450
Reviewed-on: http://android.intel.com:8080/33347
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: Lebouc, Christophe <christophe.lebouc@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

pvr: extended PVRSRVMapDeviceMemoryBW interface to support non-SGX mapped memory

BZ: 19617

This is 1/4 patch to solve 1080p video playback low memory issue which was caused
by unnecessary SGX memory mapping.

This patch extended PVRSRVMapDeviceMemoryBW interface to support no SGX mapped
memory mapping, so that PVR service layer only maps a given buffer to CPU address
space.

Change-Id: Ic156ae54b9f960face644ae8a0833a97a7c952a3
Signed-off-by: Jackie Li <yaodong.li@intel.com>
Reviewed-on: http://android.intel.com:8080/32070
Reviewed-by: Hu, Jason <jason.hu@intel.com>
Reviewed-by: Hu, Austin <austin.hu@intel.com>
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>

[PORT FROM R2] FB: reduce the prepare time for display logo

BZ: 16563

Borqs-Id: 9400eaacfe2e96ed81af199ed51b2fd475a273ea
Borqs-Contact: b094 <leo.he@borqs.com>
Commit-Date: Mon Sep 19 01:30:04 PDT 2011

borqsbtx: 5085

Reduce the prepare time for display logo:
1) enable VT_BUF_VRAM_ONLY for MFLD platform
2) remove the buffer reset in psb_fb.c

These two changes will help to remove the LOGO flicker between IAFW and Linux.

Orig-Change-Id: I43dc5ec33bd76b0c41f943510c339f70183be905
Signed-off-by: Leo He <leo.he@borqs.com>
Conflicts:

drivers/char/vt.c

Change-Id: Ieacde3f704dc07a3a27aa850a754948a91e0a64f
Reviewed-on: http://android.intel.com:8080/33087
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>

[PORT FROM R2] Boot Anim : patch from Lei & Tim for R2

BZ: 16563

Reworked patch when porting to R3

Change-Id: I6b5c4b4ca5d66601ed7e1c7d6b7574467227be6c
Borqs-Id: b710666d19df4f91ba97fd1f8a49054e9cc97f00
Borqs-Contact: Celine Chotard <celine.chotard@intel.com>
Gerrit-Id: I4ddb4ede55fe7f26a96ed9fdc23528abe7267d5a
Orig-Change-Id: Idf0556df3e029dc62026cfe497d0787cd0c75583
Reviewed-on: http://android.intel.com:8080/33073
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>

[PORT FROM R2] FB: Workaround for demo

BZ: 16563

Borqs-Id: 62317bd238851b553de03f8630b233081a312f39
Borqs-Contact: b094 <leo.he@borqs.com>
Commit-Date: Sun Sep 18 15:40:12 PDT 2011

borqsbtx: 5085

At IAFW side, the framebuffer resolution is 608x1024, but the scrren
size is 600x1024, IAFW draw logo framebuffer centered, not scrren
centered, so we need this 4-pixels shift workaround to make sure
linux draw logo at the same posotion with IAFW.
This workaround just for demo, should be removed when IAFW fix the issue

Change-Id: Ie28e5905386fefa52259402af23c9e92c06f5f3c
Orig-Change-Id: I9ff6864021dfb567262d58826e0b793487195a51
Signed-off-by: Leo He <leo.he@borqs.com>
Reviewed-on: http://android.intel.com:8080/33070
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] FB logo: remove the hard code during draw boot logo

BZ: 16563

Borqs-Id: ee0a5544ba5d57edbd50efb9584def0041ad0137
Borqs-Contact: b094 <leo.he@borqs.com>
Commit-Date: Wed Sep 14 02:56:03 PDT 2011

borqsbtx: 3347
The PR2/PR3 framebuffer geometry issue already fixed,
so remove the hard code.

Change-Id: I99213fd0e1aacc276bdea9e689b21b265b4e2652
Orig-Change-Id: I73bab4a65ba8d93b543ce66d921c7151a7342a11
Signed-off-by: Leo He <leo.he@borqs.com>
Reviewed-on: http://android.intel.com:8080/33062
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] boot: change boot logo

BZ: 16563

Borqs-Id: a5a33ca74bddcba830d25cc2bd1b174a56cdbbf6
Borqs-Contact: b094 <leo.he@borqs.com>
Commit-Date: Tue Sep 13 02:10:54 PDT 2011

Change-Id: I15a2bdfa6a6677fbcd537f05e4e0d2a8c3a61a59
Orig-Change-Id: I580eddf4401566b8c95043b08961ebd53536f4bd
borqsbtx: 4603
Reviewed-on: http://android.intel.com:8080/33057
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>

[PORT FROM R2]Dump RESETIRQ1 and RESETIRQ2 at boot time

BZ: 16168

This is the equivalent of the SHTDWN traces but for the boot time.
The traces will show the RESETIRQ1 and 2 MSIC registers that are
involved in IAFW's boot flow.

Change-Id: Ie8d46bc93b71fc95dce646b2fb419ca14873ab06
Orig-Change-Id: Ib8ddc84b5ad41d1d0afd1aede9bad7e30804756b
Orig-Signed-off-by: Yann Puech <yannx.puech@intel.com>
Reviewed-on: http://android.intel.com:8080/33075
Reviewed-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Tested-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]Factor code for writing the reboot reason in OSNIB

BZ: 14252

The previous code in intel_mid_osip.c was writing the reboot reason
using the mask 0x0f instead of 0x01. The right code was done in
intel_scu_ipcutil.c. Now the code is factored in intel_scu_ipcutil.c
Signed-off-by: Yann Puech <yannx.puech@intel.com>
Orig-Change-Id: I2945054b6bf2dc73e9275b8391e72d6f202e89a5

Conflicts:

drivers/platform/x86/intel_scu_ipcutil.c

Change-Id: I3209f3747fd5b381689f121ca3c1a5ad1fc69f06
Signed-off-by: Eduardo Mendi <eduardox.mendi@intel.com>
Reviewed-on: http://android.intel.com:8080/33060
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

n_gsm.c : Use of asynchronous hangup

BZ: 19302

In Linux 3.0 a new "big tty mutex" have been implemented.
This prevent tty_vhangup to be nested checking task ID (in tty_lock).
We need to launch the hangup in another workqueue which has a different task ID.
This is done by an asynchronous hangup.

flush_work is not necessary as this is done by tty layer before releasing the tty.

Change-Id: Ifdb1a4a942861e84ab948e5c978d9e493d70297a
Signed-off-by: Vincent Pillet <vincentx.pillet@intel.com>
Reviewed-on: http://android.intel.com:8080/32192
Reviewed-by: Stoltz-douchet, OlivierX <olivierx.stoltz-douchet@intel.com>
Reviewed-by: Guerard, Christophe <christophe.guerard@intel.com>
Tested-by: Guerard, Christophe <christophe.guerard@intel.com>
Reviewed-by: Predon, Frederic <frederic.predon@intel.com>
Reviewed-by: Lebsir, SamiX <samix.lebsir@intel.com>
Tested-by: Lebsir, SamiX <samix.lebsir@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Increase I2C fifo threshold for heavy workload

BZ: 20703

Current TX fifo threshold is 1 byte. it might be not enough when
system is in very heavy workload.
This patch increases it to half of fifo size. If only 1 byte left
in ISR, it should be not safe already. I2C transfering might be
stopped during fifo filling.

Change-Id: I7ddea8d9a90333563480b031ae2ae10e5e63724e
Signed-off-by: Bin Yang <bin.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/32412
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>

jhash: restore the old version of hash for serial number generation

BZ: 21473

having a different serial number for R2 and R3 is too annoying for people,
so we use the old version of the algorithm

This new file will only be included by android.c thus do not
impact any other user of jhash

Change-Id: I5ea9493de9380584a27cb128d042f5e32e0ab52f
Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Reviewed-on: http://android.intel.com:8080/33094
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] PM: add statistics debugfs file for suspend to ram.

BZ: 6275

Record S3 failure time about each reason and the latest two failed
devices' name in S3 progress.
We can check it through 'suspend_stats' entry in debugfs.

Change-Id: I080c7ffe3a5539d6e0882b927438db7456d4973d
Orig-Change-Id: Ieed7fd74e27d3b482675a20cb0bb26b9054a1624
Signed-off-by: ShuoX Liu <shuox.liu@intel.com>
Signed-off-by: Loic Martin <loicx.martin@intel.com>
Reviewed-on: http://android.intel.com:8080/32873
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[LOG] fix ordering of overall logs including kernel

BZ: 11070

To be able to flush the kernel logs into logcat buffer
and having the correct timestamp of any logs, a new
console logk0 is created to redirect the kernel logs into
a new logcat buffer named kernel. This implementation
also provides also the ability to have multiple instance
of logcat -b kernel

The new kernel log buffer fixes the drawback of logcat -k.
which are:

1/ The timestamp of kernel logs are added when these
logs are flushed into the file system (for example) and
not when the kernel log is created leading to have logs
in an incorrect order compared to the other OS logs

2/ If there are multiple instances of logcat -k, some
instances do not have the complete kernel logs since each
reading operation of /proc/kmsg changes the dmesg pointer

For legacy usage of logcat, logcat -k still reads /proc/kmsg
To benefit of the new buffer, use logcat -b kernel

This patch provides also some changes to optimize logs sent
to PTI (Parallel Trace Interface) without buffering.
Any log (whatever the buffer) is directly sent from the driver.

Change-Id: I80a79c0c1a4519ca5c78b9a960f24ce81f1f919b
Signed-off-by: Christophe Guerard <christophe.guerard@intel.com>
Reviewed-on: http://android.intel.com:8080/29147
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] drivers: intel_scu_watchdog: use scu access for timer; don't use regs

BZ: 19331

- Remove all regiser access; use scu commands discussed at 1/6/12 meeting
- Create ioctl to set all the thresholds, stop/start the WD
- Add support for MSI #6
- Cleaning

Change-Id: I5d88e9b92e567b4e6393bdac9d0b79d87d65b9b7
Reviewed-on: http://android.intel.com:8080/32817
Reviewed-by: Allyn, Mark A <mark.a.allyn@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>

intel_scu_ipc: calculate divisor for osc clk

BZ: 16972 20596

Accept requested frequency as parameter to intel_scu_ipc_osc_clk()
when a clock is enabled. The base frequency varies between
different platforms so take it into account in the calculations.

Also fix any calls to intel_scu_ipc_osc_clk() to provide the
requested frequency.

Change-Id: Id1ca4f1067e766de744543018fe5427db2de0b75
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32620
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>

mrst: temporary: ignore SFI table definitions for legacy cameras

BZ: 16972 20596

The SFI tables contains bogus definitions which allocate i2c
addresses and prevent actual drivers from loading. Skip the definitions.
The SFI table needs to be fixed after which this patch can be removed.

Change-Id: I0e81131245f8e6236911796970bcaa990bc58ecf
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32619
Reviewed-by: Yang, Fei <fei.yang@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>

mt9m114: temporary: add device registration

BZ: 20596

Device firmware SFI table does not yet define mt9m114 device.
Add the driver by explicitly registering it in the kernel platform code.

This patch is temporary. It should be reverted when SFI contains
the device.

Change-Id: I20b324db79eed56936651d5cf1d479ea36ed4ae4
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32618
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>

ov8830: temporary: add device registration

BZ: 16972

Device firmware SFI table does not yet define ov8830 device.
Add the driver by explicitly registering it in the kernel platform code.

This patch is temporary. It should be reverted when SFI contains
the device.

Change-Id: I57f472d1cc8f14e66858382de493c5400915d509
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32617
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>

ov8830: use all four CSI lanes

BZ: 16972

Change-Id: I2b014c7686e31402a44ba7b50202e44b0e069176
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32616
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>

ov8830: adjust sensor mode for 19.2 MHz ext clock (from 24 MHz)

BZ: 16972

Reference design from Omnivision uses 24 MHz clock, but the
Red Hook Bay allows using only 38.4/n MHz where n is an integer.
Modify the PLL settings so that the internal frequencies
correspond to the original mode but with 19.2 MHz external clock.

Change-Id: I559247a685681f8a773378c862ba139517b4a7bd
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32615
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>

ov8830: update driver interfaces for new kernel version

BZ: 16972

Change-Id: Id6fe28d52ca7516fa1f0a8fbe5bbe542fcba997f
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32614
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>

ov8830: add first sensor mode for 800x600 resolution

BZ: 16972

Add initial mode for the ov8830 sensor, 800x600 pixels,
2 lanes, 30 fps. Remove also settings and code which were
inherited from the mt9e013 driver.

Change-Id: Ia01e303a1b916595b79576a7b22d9cf4fcf89e4b
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32613
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>

ov8830: add driver skeleton and platform data

BZ: 16972

A driver is created by copying it from mt9e013 driver. In this
patch it is not yet functional, only the labels have been renamed.

Change-Id: I8de8f32fd795eefd19dcb15a2beb21ab1ee64e7f
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32612
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>

mrst: get video subdevices using a function

BZ: 16972

Different platforms supported by the mrst will have different
subdevices. Therefore the list of subdevices can not be obtained
from a fixed table.

Change-Id: I8a6f7fecf35a18f6840b93e4bb1b9591dd3a3ff9
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/32611
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>

[PORT FROM R2] Bluetooth: phone hang while transferring files via BT

BZ: 8203 17106

Borqs-Id: bd3021797b4bc7d192a4cbae42375befbc79d84f
Borqs-Contact: b132 <stone.zhang@borqs.com>
Commit-Date: Wed Aug 24 10:40:33 PDT 2011

borqsbtx: 0004232
While receiving files via opp, turn on UMS mode and then turn UMS off. Phone hang appeared when
trying to receive a file again.
From log, there is a NULL pointer in l2cap_sock_sendmsg(). So handle the exception.

And add a log in headsetservice to track the connection performance.

Change-Id: I2ef19bd476dc601c9a314a00839817cc2b4cdb40
Orig-Change-Id: Idaed4e3b216192642f900b76f7a9ff66aa9636d8
Signed-off-by: Ovidiu Beldie <ovidiux.beldie@intel.com>
Reviewed-on: http://android.intel.com:8080/32735
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Peix, FabienX <fabienx.peix@intel.com>
Tested-by: Zurmely, PierreX <pierrex.zurmely@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] Battery: remove battery validity check code

BZ: 19918

This patch removes the battery validity check code from the driver
as it is done by IAFW. IAFW populates SFI table for battery if it
valid else OEM0 Battery table will not be populated.

Change-Id: I4bff022edc84281d2bbf9aee3b86b54f187d8013
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Conflicts:

drivers/power/intel_mdf_battery.c

Change-Id: I718f65ff35d190c56b6861daf9df5ef8ad86e8c0
Signed-off-by: Eduardo Mendi <eduardox.mendi@intel.com>
Reviewed-on: http://android.intel.com:8080/32758
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Alarm: Port driver changes to R3-ICS

BZ: 19303

This patch has the defect-fixes/enhancements from R2-stable to R3-ICS,
for alarm driver.
The major changes are w.r.t the alarm type POWER_OFF_WAKEUP, which
supports wakeup from poweroff state.

Change-Id: I4ddabe02bf78aa9561b49bd97df85f5afac8564d
Signed-off-by: Pavan Kumar S <pavan.kumar.s@intel.com>
Reviewed-on: http://android.intel.com:8080/32363
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Reviewed-by: Hari, NeelamX <neelamx.hari@intel.com>
Reviewed-by: Centelles, Sylvain <sylvain.centelles@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

ipcutil: Port rtc-alarm ioctl interface changes to R3-ICS

BZ: 19303

A new ioctl interface was created to set rtc-alarm flag in osnib.
(Original R2-patch#: 19755).
One of the changes of this patch was not ported properly in R3.
This patch corrects this.

Change-Id: I0b1caaa6010f3a122819d2979ed478bdb144d4df
Signed-off-by: Pavan Kumar S <pavan.kumar.s@intel.com>
Reviewed-on: http://android.intel.com:8080/32362
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Reviewed-by: Hari, NeelamX <neelamx.hari@intel.com>
Reviewed-by: Centelles, Sylvain <sylvain.centelles@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

vRTC: Port driver changes to R3-ICS

BZ: 19303

This patch has the defect-fixes/enhancements from R2-stable to R3-ICS,
for vRTC driver.
This enables wake capabilities from S3, support for alarm more than
24-hours and wakeup-alarm from S5.

Change-Id: If0a7a06dfe2ebd89a4a55002bf9e5d31a4c916b4
Signed-off-by: Pavan Kumar S <pavan.kumar.s@intel.com>
Reviewed-on: http://android.intel.com:8080/32360
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Reviewed-by: Veera, Bharath K <bharath.k.veera@intel.com>
Reviewed-by: Hari, NeelamX <neelamx.hari@intel.com>
Reviewed-by: Centelles, Sylvain <sylvain.centelles@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]max17042: cleaned up battery detection logic

BZ: 14245

This patch cleans up the valid battery detection logic from the
driver as battery detection will be done as part of platfrom
specific initialization code.

R2-Change-Id: Iddb476ec85809754af14724dcccd43322c82271d
Orig-Change-Id: I62655277c4097bd7945c4b8e8af1c87f0a52598f
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Conflicts:

drivers/power/max17042_battery.c

Change-Id: I239cac9d49cc26b120f2a3852a31adc30f271f43
Signed-off-by: Eduardo Mendi <eduardox.mendi@intel.com>
Reviewed-on: http://android.intel.com:8080/32751
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] mrst: Added logic for battery detection in mx17042 platform specific code

BZ: 14245

This patch adds the logic to detect the valid or invalid battery
based on sfi oem0 table population.

R2-Change-Id: I60cc596296a9412e595a6978e0e0f70cab667a5a
Orig-Change-Id: I53b5b82deb9b99641f8db41efccab933f51b28f8
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Conflicts:

arch/x86/kernel/mrst.c

Change-Id: I542548fa37847ece21f079e1a8e26dbc6be74f05
Signed-off-by: Eduardo Mendi <eduardox.mendi@intel.com>
Reviewed-on: http://android.intel.com:8080/32749
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]max17042: block maxim registers reads during reboot

BZ: 15870

This patch blocks the maxim register reads during reboot, as
the chip cannot be recovered if the i2c transaction is broken.

Change-Id: I2dceba9ba9d863e3b6cf36b46f821ec4d26cf5a7
R2-Change-Id: I889135b8e76717d1fcbb742eca2e9ecccc9ac086
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/32753
Reviewed-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Tested-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]Battery: limit input current in case of vbus regulation interrupt

BZ: 18115

This patch limits the input current to 500mA in case vbus input
voltgae regulation interrupt.

Change-Id: I2020bb16a9f437c3050da67242ca11ff5f425a52
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/32755
Reviewed-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Tested-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]Battery: improve fault handling for weak chargers

BZ: 17841

This patch lowers the VBUSDET threshold and improves the fault handling
by checking the USBDET bit and the charging mode parameters.

R2-Change-Id: Iabd0b004fc7d85d56c60337b1896e09035c6f044
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Conflicts:

drivers/power/intel_mdf_battery.c

Change-Id: I63ed7a73df212e4ed6b6fa13d49a2fa6d0552a2b
Signed-off-by: Eduardo Mendi <eduardox.mendi@intel.com>
Reviewed-on: http://android.intel.com:8080/32756
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] pci.c: dont call msleep(0) in suspend flow

BZ: 2700

Gerrit patch #9116 was introduced to decrease the delay after changing
the device state. Unfortunately, msleep(0) will actually delay until the
next tick which is about 10ms on Medfield.

Solution: do not call msleep() if the requested delay is 0.
Added the same check before udelay(PCI_PM_D2_DELAY).

Change-Id: Ic07477be6c5f293f5007a1420a34d749571d04cd
Orig-Change-Id: Ifea81bdc31836dbbc26c4a7a6e6c5419dfb38f4e
Signed-off-by: Jean-Pierre Stierlin <jean-pierrex.stierlin@intel.com>
Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Signed-off-by: Loic Martin <loicx.martin@intel.com>
Reviewed-on: http://android.intel.com:8080/32685
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] alarm: Migrate legacy suspend/resume to dev_pm_ops

BZ: 2881

alarm driver uses legacy suspend/resume callbacks. Migrate them to
dev_pm_ops

Orig-Change-Id: I698c5d2112658dac6836963758c0b7fcd8e4d57e
Signed-off-by: MingmingX Zhang <mingmingx.zhang@intel.com>
Conflicts:

drivers/rtc/alarm.c

Change-Id: I2c5f453d1b36493390e24bef1ce87f4d3d7fe11a
Signed-off-by: Loic Martin <loicx.martin@intel.com>
Reviewed-on: http://android.intel.com:8080/32684
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] rtc-mrst: Migrate legacy suspend/resume callbacks of rtc driver to dev_pm_ops.

BZ: 2607

rtc driver uses legacy suspend/resume callbacks.
Migrate them to dev_pm_ops.do not use legacy for D3 suspend/resume callbacks

Change-Id: I8003640c25b35f3d8a721597762967ac77920283
Orig-Change-Id: If0397defee1966b6a153e4849f212ecd8f5c6d05
Signed-off-by: he bo <bo.he@intel.com>
Signed-off-by: Loic Martin <loicx.martin@intel.com>
Reviewed-on: http://android.intel.com:8080/32683
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] pci_rtpm: remove the pm delay for intel_mid platforms

BZ: 2700

pci framework force a wait of 10ms for every pci devices
upon resume. This is not needed on mid_pmu platform and strongly impacts
performance

remove those default timers if we are on intel_mid platforms

Change-Id: I73ed8ea6560791fb5c44eb9bdaf9ddb6c315ffd5
Orig-Change-Id: If5824c5b7a1c8cd7698c979ab7d609aea60d2ea0
Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Signed-off-by: Loic Martin <loicx.martin@intel.com>
Reviewed-on: http://android.intel.com:8080/32682
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] cpufreq: assign function to get freq correctly

BZ: 20997

The function to get the current cpu frquency was being assigned
wrongly.

Change-Id: I31468fe1ac4184abe2083429dc040262281a7f60
Signed-off-by: john mathew <john.mathew@intel.com>
Reviewed-on: http://android.intel.com:8080/32730
Reviewed-by: Hogander, Jouni <jouni.hogander@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]dma: wrong debug message and wrong masking of error interrupts

BZ: 20940

oldBZ-20433
This patch fixes 2 issues :
- In DMA tasklet, debug messages when handling error interrupts are the same as when handling
TX complete interrupts.
- In DMA ISR, if errors are detected at the same time on multiple channels, the ISR masks error
interrupts for wrong channel.
Signed-off-by: Catalin Popescu <catalinx.popescu@intel.com>
Change-Id: Idbad4352d3d6a38fe68bec7dbd03363f59983c6e
Old-Change-Id: Id4755d5e85b9bb916569196d5c51a5c3830781d2
Reviewed-on: http://android.intel.com:8080/32590
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: Popescu, CatalinX <catalinx.popescu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[REBASED on r2-stable branch] audio:enable msic pll only if it is disabled

BZ: 20940

old-BZ: 12022
MSIC PLL state needs to be checked before re-enabling it.
Disabling and re-enabling while stream is active would
cause undesirable effects/glitches.

This patch fixes the regression caused the patch:
6e50b8ed59528963db50e63e9dcf65f8a3d9adb3

old-Change-Id: Iaee8d3ea69e7bec0823123d7b919f0c7209f1812

Change-Id: I0256be9e1d3fdba946c458ab97c5581a8bf57310
Signed-off-by: Ramesh Babu K V <ramesh.babu@intel.com>
Reviewed-on: http://android.intel.com:8080/32715
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>

Audio: sst: Prevents concurrent access to firmware download code

BZ: 20940

OldBZ:9443

The code to download firmware can be accessed by more than one thread at a time
leading to panic. Proper locking along with a new sst state (firmware starting
to download) prevents this. (Ported to gb-stable)

Change-Id: Ic56e3bfd68cf89c2b8937a572a70f01b80e3b27e
Old-Change-Id: I16ef33e6ed26407ffe2e7c7693976ce1ec8e09cb
Signed-off-by: Omair Mohammed Abdullah <omair.m.abdullah@intel.com>
Reviewed-on: http://android.intel.com:8080/32721
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>

Graphics: add GL3 Cache support for OSPM

BZ: 16808

This reverts commit 8dadfb803535c6d77eba52216c595f984706e19d.
and add GL3 enbling in mdfld kernel config

Change-Id: I5c784a831043c6bff4c2058f371a1a3a96516106
Signed-off-by: Randy Xu <randy.xu@intel.com>
Reviewed-on: http://android.intel.com:8080/32576
Reviewed-by: Pandit, Seema <seema.pandit@intel.com>
Reviewed-by: Stimson, DaleX B <dalex.b.stimson@intel.com>
Reviewed-by: Hu, Austin <austin.hu@intel.com>
Reviewed-by: Seibel, Eric <eric.seibel@intel.com>
Tested-by: Seibel, Eric <eric.seibel@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] hsi_ffl_tty.c: adding some /sys/module interface to manage modem reset

BZ: 19623

This patch is adding two sysFS interfaces aimed at managing modem reset and TTY
interface hang-up:
- /sys/module/hsi_ffl_tty/parameters/reset_modem for resetting the modem and
  querying its reset status;
- /sys/module/hsi_ffl_tty/parameters/hangup_reasons for accessing and clearing
  hang-up reasons.

The /sys/module/hsi_ffl_tty/parameters/reset_modem interface is exporting some
decimal data consisting of a bitfield of 1 bit per TTY interface (bit 0 for
ttyIFX0, bit 1 for ttyIFX1...) where:
- when written to 1 is resetting the corresponding modem (the one attached to
  the TTY interface);
- when read to 1 is signalling that the corresponding modem is still resetting,
  as it did not successfully managed any TX or RX transaction.

The /sys/module/hsi_ffl_tty/parameters/hangup_reasons interface is exporting
some decimal data consisting of a bitfield of 1 nibble (4-bits) per TTY
interface (bit0 to 3 for ttyIFX0, bit 4 to 7 for ttyIFX1...) where:
- when read is getting the last hangup reasons of the considered TTY interface
  (bit 0 for TX timeout, bit 1 for modem reset and bit 2 for modem core dump);
- when written is clearing the given hangup reasons of the considered TTY
  interface (bit 0 to clear TX timeout, bit 1 for modem reset and bit 2 for
  modem core dump).

This last interface is different from the related IOCTL, which is working in a
read-to-clear mode. This is no longer the case with this sysFS interface where
the read data shall be written back to clear the hangup reasons. A correct
management would be:
1. read /sys/module/hsi_ffl_tty/parameters/hangup_reasons,
2. write back the read value to acknowledge those hangup reasons and then,
3. perform whatever is necessary to manage the hangup reasons.

See the functions header descriptions for more information regarding those new
interfaces.

Change-Id: I82647742ce6292950cb5216593611146c151c533
Signed-off-by: Olivier Stoltz Douchet <olivierx.stoltz-douchet@intel.com>
Reviewed-on: http://android.intel.com:8080/31415
Reviewed-by: Predon, Frederic <frederic.predon@intel.com>
Reviewed-by: Lebsir, SamiX <samix.lebsir@intel.com>
Tested-by: Lebsir, SamiX <samix.lebsir@intel.com>
Reviewed-by: Lucas, GuillaumeX <guillaumex.lucas@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] hsi_ffl_tty.c: streamlining the TX timeout and stop TX timer management

BZ: 15222

This patch is cleaning and factorising the TX timeout and stop TX timer
management to limit the number of code sections where those timers are updated
In more details, this patch is:
- also directly killing the stop TX timer in the _ffl_from_wait_to_ctrl()
   function upon successful insertion of HSI message in the controller at the
   very same location where the TX timeout timer is updated;
- adding a _ffl_update_state_tx() function aimed at factorising those timers
   management, mainly killing the hangup timer when there is no left HSI
   message in the controller and starting the stop TX timer when the full write
   pipeline is empty. This helper function is the sibling of the
   _ffl_update_state_rx() function;
- this _ffl_update_state_tx() is now called wherever the wait FIFO and the
   controller FIFO are updated: in the _ffl_pop_wait_push_ctrl() function,
   which is transferring as much TX messages as possible from the wait FIFO and
   the controller as well as in the ffl_destruct_frame() callback;
- the _ffl_tx_ctx_is_empty() helper function has been removed as it was only
   used once in this new code version, and its internal code has been directly
   carbon copied in the ffl_tx_full_pipe_is_clean() function;
- the TX timeout and stop TX timer management has been removed from the
   ffl_complete_tx() function for it is now included in the
   _ffl_pop_wait_push_ctrl() call;
- the ffl_throw_tty_hangup() function has been dropped as it was mistakenly
   used with a spinlock_irq_save in the ISR (which is bad) and was only used
   once elsewhere. The content of this initial function has been copied to the
   ISR without the _irqsave modifier, and was updated in the
   ffl_tty_tx_timeout() timer handler callback to only throw a TTY hangup if
   the HSI controller FIFO is not empty - which is safer than the current
   implementation.

This latter modification is further ensuring that no unexpected TX timeout
hangup can happen when the HSI controller FIFO is empty - maybe due to a race
condition between the del_timer() and mod_timer() functions.

This new hangup management is simpler than the previous one as it does not
update the TX timeout timer upon reception on a frame, but only when adding a
new frame in the controller.

Finally, this new version is also adding better traces for RESET_OUT and
CORE_DUMP, adding the cause information.

In a nutshell, the purpose of this patch is to bind the TX timeout and stop TX
timer management to ensure a full coherency in this respect, to simplify the
TX timeout management and to filter out potential spurious TX timeout hangups.

Change-Id: I0cc4e5ca720a1fee4060681780c59aeada476193
Orig-change-Id: Id53abc766cd9687321f3f21195fe7f898e24948f
Orig-Change-Id: I6e1ce86acbde63f96b744d972a31fcb53afb1205
Signed-off-by: Olivier Stoltz Douchet <olivierx.stoltz-douchet@intel.com>
Reviewed-on: http://android.intel.com:8080/31445
Reviewed-by: Predon, Frederic <frederic.predon@intel.com>
Reviewed-by: Lebsir, SamiX <samix.lebsir@intel.com>
Tested-by: Lebsir, SamiX <samix.lebsir@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] hsi_ffl_tty.c: kill 30-second tty_wait_until_sent timeout and refactorise code

BZ: 15526

When closing the IFX 0 TTY interface, the TTY layer is relying on the
tty_chars_in_buffer() callback function to wait for the TTY port emptiness. It
is only later that it is calling the wait_until_sent() callback function.
The current implementation is potentially stalling on the first wait loop as
no event is waking the TTY interface up should this happen. The current patch
is addressing this issue by calling a tty_wakeup whenever the last TX message
is returned back from the controller.

Still on this TX path emptiness, a new _ffl_tx_ctx_is_empty() helper function
has been introduced not to consider the TX path as empty as long as there is
write pending - e.g. writes which are no longer in the wait FIFO, but not yet
in the controller.

Finally this patch is also refactoring the _ffl_pop_wait_push_ctrl() to kill a
tail recursion call - which is forbidden in the kernel - and to merge two very
similar function.

Change-Id: Ie3dbe03e285fff60ef172924e2e631f069ffb9c8
Orig-change-Id: I40da402cdbbcc953912adfcaae4265ec48e8af54
Signed-off-by: Olivier Stoltz Douchet <olivierx.stoltz-douchet@intel.com>
Reviewed-on: http://android.intel.com:8080/31431
Reviewed-by: Predon, Frederic <frederic.predon@intel.com>
Reviewed-by: Lebsir, SamiX <samix.lebsir@intel.com>
Tested-by: Lebsir, SamiX <samix.lebsir@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Revert "[Rebase from r2]]audio: sn95031: added GPIO support for jack detection"

BZ: 20873

Bug id which merged the patch 19775

This reverts commit 932aa03c1092173047d0eec75b3496582e82ba02.

Change-Id: If2ae534c63131e83e0de9667cefe899b0bab46a9
Reviewed-on: http://android.intel.com:8080/32635
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Enable VEC D0i3.

BZ: 19416

Video encoding HW island should be powered down when it is idle.
This patch enables VEC D0i3 by default.
Signed-off-by: Elaine Wang <elaine.wang@intel.com>
Change-Id: I40fa00ea2519c8acdb1a1bc19f94b89ae91c89f2
Reviewed-on: http://android.intel.com:8080/31174
Reviewed-by: Yuan, Shengquan <shengquan.yuan@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] lm3554: update step size for flash and torch

BZ: 20773

ORIG_BZ: 19823

to protect the LED and LM3554 the current through the LED should
not surpass 800mA. This means 100% should be mapped to 800mA
instead of the 1000mA it is now. To accomodate this the flash step
should be increased from 625 to 909 and for torch from 1250 to
1818.

Change-Id: I15ed7e1bda2b345132fbbd614a0710268484f65e
Orig-Change-Id: Iff17edc6575284b6b8a0f74dc179a4678b831bcc
Reviewed-on: http://android.intel.com:8080/31668
Reviewed-by: Jong-a-lock, Robert <robert.jong-a-lock@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Suzuki, Kunimitsu <kunimitsu.suzuki@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Tested-by: Haapakorpi, Juha <juha.haapakorpi@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Reviewed-on: http://android.intel.com:8080/32603
Reviewed-by: Lampila, KalleX <kallex.lampila@intel.com>
Tested-by: Lampila, KalleX <kallex.lampila@intel.com>