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>

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>

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>

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>

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

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>

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>

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>

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>

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>

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

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

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

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

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>

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

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>

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>

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>

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>

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>

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>

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>

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>

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>

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>

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>

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>

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

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

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

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

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>

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>

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>

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>

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>

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

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

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

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