atomisp: use min_t and max_t instead of direct casting

BZ: 24615

There are few places where max and min macros used as follows
min(a, (<T>)b)
It could be easily changed to
min_t(<T>, a, b)

Change-Id: I7717b16cc9cc79e1da005e10bc8853d78498efc3
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/36100
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

GFX-Display: don't make HDMI display in 1280x720 mode during CLV PR0 system booting.

BZ: 24597

Only reset HDMI preferred mode if NULL EDID detected on PNW C1 or latter. On other
platforms such as CLV PR0, set HDMI with the default preferred mode in the display
driver loading process.

Change-Id: Iee27f2efbd3b71e502af0929f28a6b21e0d96493
Signed-off-by: Austin Hu <austin.hu@intel.com>
Reviewed-on: http://android.intel.com:8080/36067
Reviewed-by: Ai, Ke <ke.ai@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>

v4l2/mt9m114: wait completion after each reg array write

BZ: 24612

MT9M114 sensor shows stability issue after we sync-ed with UMG's R3
code. The reason is that some of the wait/polling code has been
removed perhaps due to the testing have done on phone platforms.
The delay or polling for completion might not be needed for the
phone. However, Aptina (vendor) FAE suggests:

"Polling or delay time is required for current system managerstate
variable (R0xDC01) or state change in host command register (R0x0080)"

This patch enforces polling for host command status after
each register array write that requires polling. This is based
on vendor's INI file. e.g.
for [Change-Config] polling required after writes
REG= 0xDC00, 0x28  // SYSMGR_NEXT_STATE
REG= 0x0080, 0x8002  // COMMAND_REGISTER
POLL_REG = 0x0080, 2, !=0, DELAY=1, TIMEOUT=100

Change-Id: I9f8e8de16c6ebbc90520ef9e2568b7e42d1258e0
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
Acked-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Acked-by: David Cohen <david.a.cohen@intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/36089
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

v4l2/mt9m114: avoid oops in query control

BZ: 24612

Initialize control query function pointers such that NULL pointer
oops can be avoided when v4l2 query control API is called.

Change-Id: Ief0655d7c99aee8cce5bb3a3660ab790e2449dbd
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
Acked-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Acked-by: David Cohen <david.a.cohen@intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/36088
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Alarm: enable suspend log by default

BZ: 23525

This enables a one line log trace only on the suspend
path of the alarm driver. This log shows
when the rtc is programmed to wake up the system:

Example:
rtc alarm set at 1328264643, now 1328264607, rtc delta 1.464516704

To disable the log dynamicaly we can use:
echo 0 > /sys/module/alarm/parameters/debug_mask

to enable again:
echo 16 > /sys/module/alarm/parameters/debug_mask

Change-Id: I27391420eaddf035325a195893fd6695ead8ae3f
Signed-off-by: Axel Haslam <axelx.haslam@intel.com>
Reviewed-on: http://android.intel.com:8080/34262
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Tested-by: Cuesta, FernandX <fernandx.cuesta@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

v4l2/mt9e013: don't use custom typedef for basic type

BZ: 24614

There is no need to redefine the "unsigned int" to the custom type.

No functional change.

Change-Id: I1ea89c066c62c32517a1bb0e11a0b5131af23792
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/36096
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

v4l2/mt9e013: misc clean up

BZ: 24614

Remove unused macros and variables.
Make few structures static.
Use proper address space for variables.

Change-Id: Ia81269969d60bf87566c09fb98cd67557ed8c55a
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/36095
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: Jong-a-lock, Robert <robert.jong-a-lock@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

v4l/mt9e013: detect sensor model and rev id

BZ: 24614

Change-Id: I42aafd397a45be9da553e3adfaae4f3c0af2989d
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
Acked-by: David Cohen <david.a.cohen@intel.com>
Acked-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/36094
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

v4l/mt9e013: clean up reg read/write functions

BZ: 24614

Change-Id: I5a6f95b7600e9f8e0d3f57f49727cc793adbbe9f
Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
Acked-by: David Cohen <david.a.cohen@intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/36093
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Read APIC regiters to track source wakeups

BZ: 23525

Read Interrupt Request Register form apic to track
wakeups that are not from GPIO. This helps us log
wakeups from sources like power button, alarm, and
headset plug.

Change-Id: I4e9ea82541e2e56e39d5de1d761fa9b89656ea7b
Signed-off-by: Axel Haslam <axelx.haslam@intel.com>
Reviewed-on: http://android.intel.com:8080/36068
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: Fiat, Christophe <christophe.fiat@intel.com>
Tested-by: Cuesta, FernandX <fernandx.cuesta@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

mid_pmu: add trace to print wakeup source from s3

BZ: 23525

Add a trace to know the wake source from s3.
If we detect the wakeup reason is GPIO, we set a
flag to print what gpio number caused the wakeup,
on the gpio isr.

Wakeups that are detected are: GPIO, USB, HSI.
Wakeup from other sources, specifically MSIC (pwr_btn, rtc)
are not yet detected this mechanism.

Change-Id: Id06bf387a00bd1abdc37dd229389fcbeb4c4afb7
Signed-off-by: Axel Haslam <axelx.haslam@intel.com>
Reviewed-on: http://android.intel.com:8080/34331
Reviewed-by: Zayet, AymenX <aymenx.zayet@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: Fiat, Christophe <christophe.fiat@intel.com>
Tested-by: Cuesta, FernandX <fernandx.cuesta@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]emmc_ipanic: Kernel panic capture broken after emmc layout change

BZ: 18209

Change-Id: If5d33b9d41ad4af50e03734cd8fb07309476cc76
Org-Change-Id: Idc3857d428158defc983c445b16d46def8d6a6f2
Signed-off-by: Christophe Guerard <christophe.guerard@intel.com>
Reviewed-on: http://android.intel.com:8080/35850
Reviewed-by: Zhang, Dongxing <dongxing.zhang@intel.com>
Reviewed-by: Qin, Xiaokang <xiaokang.qin@intel.com>
Reviewed-by: Afantenos, Marie CecileX <marie.cecilex.afantenos@intel.com>
Tested-by: Romieu, Benoit <benoit.romieu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] [AUDIO] Increase Audience hardware reset period at boot

BZ: 23660

Increase Audience hardware reset period in order to be compliant with specifications.
Enable extra logging in Audience driver.

Change-Id: I3d280019bff17937fc0196b3938a653d6bd0128c
Old-Change-Id: I853e75d1325d0217cc2b3db4513776cf7fc9a6a5
Signed-off-by: ndifolcx <neilx.di.folco@intel.com>
Reviewed-on: http://android.intel.com:8080/36368
Reviewed-by: Barthes, FabienX <fabienx.barthes@intel.com>
Tested-by: Barthes, FabienX <fabienx.barthes@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

mmc: reset eMMC when switching partition from RPMB to user

BZ: 24218

If RPMB partition is not programmed with authentication key, after
a read operation, switching partition from RPMB back to user will
be failed and got a datatimeout interrupt.

This patch will reset eMMC device if encounter such error

Change-Id: Ie16db67835ce6f7fb81e3631c504ccb490023654
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/35980
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>

mmc: calculate max_discard for secure erase/trim feature

BZ: 24573

Some eMMC card will acquire a much large timeout value for
secure erase/trim feature, which may be larger than the host
supported. For those devices, even their ext_csd support secure
erase/trim feature, driver will still disable it.

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

mfld-pmu: Fix bug that prevents showing warning msg if pm_msic wasn't set

BZ: 24613

In the unlikely situation pm_msic wasn't set when entering
to s0ix, the warning message wasn't shown due to off by one
error.

Change-Id: I01aafff4fb011783c5e7eae6f81b5b76f6be65a5
Signed-off-by: Ilkka Koskinen <ilkka.koskinen@intel.com>
Reviewed-on: http://android.intel.com:8080/36099
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: Hogander, Jouni <jouni.hogander@intel.com>
Tested-by: Cuesta, FernandX <fernandx.cuesta@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

hwmon/l3g4200d: fix gyro sensor init issue

BZ: 24656

Gyro sensor device can not be inited by
i2c_block write function, switch to i2c_write_byte.
Also a delay should be used to wait device to
be stable.

Change-Id: I30c5c6b11846169ccb99dd447ab67cb347467885
Signed-off-by: jli127 <jian.d.li@intel.com>
Reviewed-on: http://android.intel.com:8080/36175
Reviewed-by: Liu, Hong <hong.liu@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>

apds990x: ALS/PS sensor driver for CTP and GI

BZ: 22196

apds990x ALS/PS sensor driver enable on Clovertrail and GI

Change-Id: I4e2d3296eff29d8d3b8d610877686662dee43178
Signed-off-by: Leo Yan <leo.yan@intel.com>
Reviewed-on: http://android.intel.com:8080/33849
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>

usb/ehci: use USBMODE_EX for langwell/penwell usb otg controller

BZ: 23178

Medfield has some non-standard registers. The address of USBMODE
is 0xF8h instead of 0x98h. In Moorestown, these registers has been
added. When trying to suspend the controller, the USBMODE will
be checked and set the controller to halt mode. As the address is
wrong for mfld, the controller is not halted. This will cause the
root hub can't resume. Before the root hub is resumed, controller
RUN/STOP state will be checked.

Change-Id: Ic02f5df7449d3ab1d9b90b20d93633cb85391edb
Signed-off-by: feng wang <feng.a.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/35996
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Zhuang, Jin Can <jin.can.zhuang@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>

atmel_mxt224: change to Multi-touch Protocol B

BZ: 24689

Atmel mxt224 touchscreen chips can do finger id tracking by firmware,
changing to protocol B can reduce kernel-userspace traffic since only
changes are propagated.

Change-Id: Ib7e53f5503e10b31ed21b4033bf288de7e594d1d
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/36167
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

Fix dependency issue in order to enable HDMI audio for CTP

BZ: 24342

The HDMI audio driver uses DRM_MDFLD as a dependency for enabling HDMI.
However, Clovertrail Phone does not use DRM_MDFLD hence HDMI audio can
not be enabled for CTP platform.

This patch fixes this dependency by removing DRM_MDFLD from
/sound/drivers/Kconfig under SND_INTELMID_HDMI_AUDIO section.

Change-Id: I4a2a03e811aa1f1d680a76fa7be50ff9abca07ff
Signed-off-by: Seema Pandit <seema.pandit@intel.com>
Reviewed-on: http://android.intel.com:8080/35815
Reviewed-by: Mai, Leonard <leonard.mai@intel.com>
Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com>
Reviewed-by: Kp, Jeeja <jeeja.kp@intel.com>
Reviewed-by: Agarwal, Vaibhav <vaibhav.agarwal@intel.com>
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]max17042: Added event worker to offload the power supply worker

BZ: 20547

This patch adds a new event worker to offload the power supply worker
and clean up the mutex lock handling in the worker.

Change-Id: I80c62f76035e21ec1b43f4a5b6d952fb5f78297d
Orig-Change-Id: I7576e9dda34b51e6abc67d59158afb02f687b31c
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Signed-off-by: santosh <santoshx.gugwad@intel.com>
Reviewed-on: http://android.intel.com:8080/36225
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]Battery: cleaned up mutex lock dependencies

BZ: 20547

This patch cleans up the mutex lock dependencies between battery
and fuel gauge drivers. Also cleans up some of nested locking code.

Change-Id: I89ba824b32f39d151986cb3b69c32e42137790f0
Orig-Change-Id: I76c28a2c2280f8ad48303a89d5cdf03277c8483f
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Signed-off-by: santosh <santoshx.gugwad@intel.com>
Reviewed-on: http://android.intel.com:8080/35890
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

usb/penwell_otg: keep D0 when A-cable is attached.

BZ: 23598

When user attach A-cable, keep USB stay in D0 in order
to detect the USB connect event. Not allow S3, because
when system is S3, vbus is powered down, so no method
to detect USB devices attached to the A-cable.

Change-Id: If7bcfd359cad30b5cdc3902f22b8f1719785f8c9
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/35593
Reviewed-by: Zhuang, Jin Can <jin.can.zhuang@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Wang, Feng A <feng.a.wang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@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 R1][LOGS] Enable by default kernel configuration to ease debug

BZ: 23268

In the standard build, advance debug capabilities are not enabled
by default in the kernel. It means that it is necessary to provide
a new kernel to analyze defects like memory leak or to add
kernel logs

By enabling CONFIG_DYNAMIC_DEBUG and CONFIG_DEBUG_KMEMLEAK in the
kernel configuration by default, these advanced debug capabilites
can be used on a default build

Change-Id: Iaca1b7726c05f509d31f8bae17271a5431589bf7
Org-Change-Id: I3eebc2af890b1b7dfc4460f43f12ea0ac84ee4ef
Signed-off-by: Christophe Guerard <christophe.guerard@intel.com>
Signed-off-by: Zhang Dongxing <dongxing.zhang@intel.com>
Reviewed-on: http://android.intel.com:8080/35840
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[Revert me]: FW bug: set GPIO 30 for vol-up key

BZ: 24500

GPIO for vol_up key read from SFI table is wrong due to FW bug.
This is a workaround. Revert me later.

Change-Id: I8ba9795eab2c8ab04caef9d03f88d131f3ebcd24
Signed-off-by: Li, Ning <ning.li@intel.com>
Reviewed-on: http://android.intel.com:8080/35982
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>

[PORT FROM R2] remove depmod from build

BZ: 10643

depmod looks like having a strange bug that makes it enter in a
infinite loop writing to a file named modules.ccwmap

We remove the depmod command because it is not needed in android
as we insert our modules via insmod and not modprobe.

Change-Id: I5c25c51d59e2bd141bc124b5da34c89146dd10de
Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Reviewed-on: http://android.intel.com:8080/33238
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>

drivers: staging: sep: Add secure dma operation

BZ: 21789

Change-Id: I8aa0486bee278d8a0a3ddecf4c86297d78a49adb
Signed-off-by: Mark Allyn <mark.a.allyn@intel.com>
Reviewed-on: http://android.intel.com:8080/33427
Reviewed-by: Matthews, Michael L <michael.l.matthews@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>

audio: program OSC clock to 19200khz for Audio Block

BZ: 22329

OSC clock on CloverView is 38.4 Mhz. Audience es3505b requires clock
frequency in the range 12-26 Mhz.
Added SST PLL fucntion to set the clock to 19200khz
Audio codec cs42l73 internal divider change required to reduce the
frequency by 2.

Change-Id: I1e1af4eb8c33c6bc97804b210fcdf2831cb266db
Signed-off-by: KP, Jeeja <jeeja.kp@intel.com>
Reviewed-on: http://android.intel.com:8080/35462
Reviewed-by: R, Dharageswari <dharageswari.r@intel.com>
Reviewed-by: Vinnakota, Lakshmi N <lakshmi.n.vinnakota@intel.com>
Reviewed-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

audience: enable audience for clovertrail platform

BZ: 22328

Change-Id: I3564cbcb846f85917f6cd33ae8af19345cb601ec
Signed-off-by: Ojas Chauhan <ojas.chauhan@intel.com>
Reviewed-on: http://android.intel.com:8080/34359
Reviewed-by: Bellouard, Jean-marieX <jean-mariex.bellouard@intel.com>
Reviewed-by: Centelles, Sylvain <sylvain.centelles@intel.com>
Reviewed-by: Mai, Leonard <leonard.mai@intel.com>
Tested-by: Barthes, FabienX <fabienx.barthes@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

board-blackbay: Added platform specific changes for bq24192 charger

BZ: 22531

This patch adds the platform specific initialization code
for TI BQ24192 charger driver.

Change-Id: I643a904cb1ddb7f4b7be79892fa93425761da731
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/34112
Reviewed-by: Pandey, Raj <raj.pandey@intel.com>
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: Hari, NeelamX <neelamx.hari@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

bq24192_charger: Add support for TI bq24192 charger driver

BZ: 22531

This patch adds the charging driver support for BQ24192 TI chip.
This patch supports USB detection through OTG driver and does
charge enablement and disablement upon charger plug/unplug.

Change-Id: I2a453d86ce19839d47a40662f49498bc6716c5e2
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/34111
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Reviewed-by: Pandey, Raj <raj.pandey@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: Hari, NeelamX <neelamx.hari@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

power_supply: Add generic api support for charger notifications

BZ: 22394

Currently OTG driver sends the charger plug/unplug notification
through private api defined between battery and otg drivers.

This patch adds the generic api support for notifiying the charger
plug/unplug events in  power supply subsystem. Also adds a sysfs
attribute for controlling the charge current from the user space.

Change-Id: I4b7614365eb71b9d205579f84f22527d4b91fbbd
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/34110
Reviewed-by: Pandey, Raj <raj.pandey@intel.com>
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Tested-by: Gugwad, SantoshX <santoshx.gugwad@intel.com>
Reviewed-by: Hari, NeelamX <neelamx.hari@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

board-blackbay: modify the RPMB API according MMC driver

BZ: 24206

MMC driver has added a device node for RPMB partition, and RPMB
API should also be modified according this. This patch will change
this for board-blackbay.c

Change-Id: I3430664a653e4edbedca58b496cedc084f0ada54
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/35719
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>

mmc: add a sysfs entry to show write reliability

BZ: 24365

add a sysfs rel_set in /sys/block/mmcblk0/device/ to show the
write reliability.
If bit0 of rel_set is 1, then write reliability for user data
area is enabled.

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

mmc: change trim timeout time

BZ: 24352

When use TRIM in eMMC, timeout value should be defined in ext_csd
register but not a write block timeout value. Change to use this.
In the mean while, enable erase_group_def to use high capacity erase
group size to improve trim performance

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

[PORT FROM R2] SDIO: Enable the manual suspend/resume by default for SDIO cards.

BZ: 18765 17650

By enabling the manual suspend/resume of the mmc driver for sdio
slot, the sdio card will not be powered OFF on suspend and powered
ON on resume, even if the sdio driver has been removed from the kernel.

This feature is very useful for sdio modules of non-removable cards.
So it is better to keep the power management of the SDIO card, on
suspend / resume, up to the sdio driver.

Orig-Change-Id: Ic003c4b4e933814bc35bbb3f824843442f054b49
Change-Id: I7cd2e370e8bc553771243af248283ef80a399769
Signed-off-by: Aymen Zayet <aymenx.zayet@intel.com>
Reviewed-on: http://android.intel.com:8080/34513
Reviewed-by: Garcia, JeremieX <jeremiex.garcia@intel.com>
Reviewed-by: Regairaz, JulieX <juliex.regairaz@intel.com>
Reviewed-by: Fiat, Christophe <christophe.fiat@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Zurmely, PierreX <pierrex.zurmely@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[drivers] [BT] skbuffer NULL pointer fix

BZ: 21014

This patch prevents the usage of an already freed skbuff and thus prevents memory overwritten error. This is done by adding an error condition check in the btwilink driver.

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

max11871: add touch driver from Maxim 11871

BZ: 21429

Touch driver of Maxim 11871 for Gilligan Island

Change-Id: If4297d55f21ee616c9371e42217127c4e04fc396
Signed-off-by: Andriy Naborskyy <andriy.naborskyy@intel.com>
Signed-off-by: Hong Liu <hong.liu@intel.com>
Signed-off-by: Leo Yan <leo.yan@intel.com>
Signed-off-by: Prabu Renganathan <prabu.renganathan@intel.com>
Reviewed-on: http://android.intel.com:8080/34180
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

hwmon/accel: enable initial event report for 6D interrupt mode

BZ: 23830

When accelerometer is running in 6D interrupt mode, it doesn't report
events if no orientation change. If device first enters sleep mode then
resume, user space app won't receive accelerometer events, and can't
calculate its orientation. This patch forces the accelerometer to report
events when it is enabled so that user space could calculate orientation
correctly.

Change-Id: Ib7738dd87c44d03d45ef7b28fa9ee607d04995a8
Signed-off-by: Zhifeng Wang <zhifeng.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/35684
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

fix led device init issue

BZ: 24312

LED device init is later than IPC driver. It causes LED device being
lost.

Change-Id: Ie5e2d790ed70e77dae644da97f8d95016faadd4a
Signed-off-by: Bin Yang <bin.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/35868
Reviewed-by: Zhang, Shijie <shijie.zhang@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

GFX-Display: updated overlay wait for vblank to use blocked waiting instead of querying it in a busy loop

BZ: 18446

This patch 1/3 for flicking issue on overlay while video playback.
we need wait for vblank to make sure overlay has been switch to
a buffer successfully, or the buffer consumed by overlay might be
dequeued by video driver override the buffer data while overlay
is fetching data. Perviously, wait for vblank was implemented as
a busy loop which is ineffient and power consuming.

This patch reimplemented the overlay wait for vblank as a blocking
waiting, so that OS will put the caller thread to sleep while waiting
for vblank.

Change-Id: I29de9c12155cb0b2b60945e47dd675174bb52717
Signed-off-by: Jackie Li <yaodong.li@intel.com>
Reviewed-on: http://android.intel.com:8080/35165
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

GFX-Display: make HDMI display in 1920x1080p@60Hz as default on CLV for MWC demo.

BZ: 24203

Don't filter out the 1920x1080p@60Hz mode whose dot clock is 148.5 MHz = 2200 x 1125 x 60.

Change-Id: Iaf1a6fc800ae7031b4ede7ddcf6ccb76c45a36a1
Signed-off-by: Austin Hu <austin.hu@intel.com>
Reviewed-on: http://android.intel.com:8080/35712
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

GFX-Display: enabled HDMI HPD interrupt for CloverView SoC.

BZ: 24183

Enabled the HDMI HPD interrupt via GPIO pin 43 and by registering PCI
driver with device ID 0x901, for TI TPD12S015 HDMI companion chip used
for the CLV SoC.

Change-Id: I72879e01dc97b03f25d5d1203c5b1518d76c6458
Signed-off-by: Austin Hu <austin.hu@intel.com>
Reviewed-on: http://android.intel.com:8080/35698
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] max3110: fixing the race between port receive and port
shutdown

BZ: 8746

The main_thread should check port_shutdown status before committing tty
related actions.

Change-Id: I9d3d9a51c5f74222b02b2c2ce5b8e4e03b1fb8ee
Signed-off-by: Alek Du <alek.du@intel.com>
Reviewed-on: http://android.intel.com:8080/35844
Reviewed-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

i386_ctp_defconfig: enable HSU console for Clovertrail

BZ: 23157

Medfield PRx uses UART 3(mirrored from UART 1) as HSU console port.
But for Clovertrail UART 2 is used as HSU console port.
This patch changes the HSU console port to 2 accordingly for Clovertrail.

Please note that only Clovertrail VV and EV boards can use HSU console
but PRx can not. This is by hardware design and is not a software issue.

Removing jumper J3D1 from debug card 3 will switch to HSU console.

Change-Id: I9f1dfdf2493a3229a3e5878532941cd3630ec6e3
Signed-off-by: Bin Gao <bin.gao@intel.com>
Reviewed-on: http://android.intel.com:8080/34809
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

ov8830: limit i2c transfers to 30 bytes due to i2c driver restrictions

BZ: 23715

See also BZ 16310.

The i2c adapter can transfer 32 bytes maximum
at a time, while driver implemets maximum 128
bytes burst transfer length, so i2c driver would
split buffer transfer if buffer length is more than
32 byte. This will cause some problem sometime, since
during two consequtive transfers, if the second transfer
starts at the time when the first transfer completely finishes,
(i2c transfer buffer empty),the i2c controler would start
a new i2c transfer, which include a start/stop signal according to
i2c protocal, but it will break the i2c burst transfer rules
expected by driver.

Change driver's maximum burst length from 128 to 30 bytes
which leaves also a safety margin.

Change-Id: If34a28dc9ea5318bd15769bfeeb501dd36eae7f5
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/35311
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

mmc: use max_discard_to for SD write timeout

BZ: 24030

max_discard_to is the max timeout value allowed by host. Use
this value can stop kernel printing too large timeout warning.

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

mmc: add flag to check suspend status before accessing RPMB partition

BZ: 23276

RPMB partition is accessed by an API which is called by SEP driver. Before
process RPMB partition access request, driver needs to make sure host is not
in suspended status.

Add a flag to check MMC block device status before handle a RPMB request

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

media: video: append $(srctree) to -I parameters

BZ: 23514

Without this we have got the warnings like following if build with "make W=1
O=/var/tmp":
   CHECK   drivers/media/video/videobuf-vmalloc.c
   CC [M]  drivers/media/video/videobuf-vmalloc.o
 +cc1: warning: drivers/media/dvb/dvb-core: No such file or directory [enabled by default]
 +cc1: warning: drivers/media/dvb/frontends: No such file or directory [enabled by default]
 +cc1: warning: drivers/media/dvb/dvb-core: No such file or directory [enabled by default]
 +cc1: warning: drivers/media/dvb/frontends: No such file or directory [enabled by default]
   LD      drivers/media/built-in.o

Some details could be found in [1] as well.

[1] http://comments.gmane.org/gmane.linux.kbuild.devel/7733

Change-Id: I5418bce1e72fec10be1b5d297bc512b87798fa1d
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/35256
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] intel_idle: re-order power_trace

BZ: 23293

Part of this patch was merged in earlier code changes.

When ftrace is run with power events enabled it prevents
the device from going to higher c states and power_start and
power_stop traces are printed continuously.

This patch moves the trace_power_start and trace_power_end calls to the
main cpuidle routine.

There is no impact on the system as these are non intrusive traces.The device
now gows to higher c-states.

Upstream is already going that way, but the actual patch is depending on
lot of other stuff that we dont want to all take.

Orig-Change-Id: Idf7d983466afd9b2800d834032bf1fb05c6d4b32
Signed-off-by: John Mathew johnx.mathew@elektrobit.com
Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Change-Id: I85833541014c82eb44358ede7ba5371005c3cd67
Signed-off-by: John Mathew <john.mathew@intel.com>
Reviewed-on: http://android.intel.com:8080/35132
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] trace/runtime_pm: add runtime_pm trace event

BZ: 23293

based on the recent hook from Arjan for powertop statistics
we add a tracepoint in order for pytimechart to display
the runtime_pm activity over time, and versus other events.

We also add a usage counter change tracer that will trace
accountability of a runtime_resume

Change-Id: Iab7cb7a09fc002c3e74e0186855edc2d0367a8b3
Orig-Change-Id: I59f8162e7129b98454752ca60c920c40ce4e8bd1
Signed-off-by: Pierre Tardy <pierre.tardy@intel.com>
Reviewed-on: http://android.intel.com:8080/35159
Reviewed-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] mid_pmu: check completion flag after wait_for_completion timeout

BZ: 21156 23293

In S3 flow pci_pmu_set_power_state waits on d0ix command
completion interrupt, the interrupt is received but the
completion signal is not delivered since the threads are
frozen.

Hence pci_pmu_set_power_state timesout after 5secs and
calls BUG()

Fixed this by checking the completion flag that gets cleared
when d0ix completion interrupt is received.

<0>[ 7959.846890] ------------[ cut here ]------------
<2>[ 7959.846903] Kernel BUG at c1852942 [verbose debug info unavailable]
<0>[ 7959.846917] invalid opcode: 0000 [#1] PREEMPT SMP
<0>[ 7959.846933] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
<4>[ 7959.846944] Modules linked in: ipv6 atomisp lm3554 mt9m114 mt9e013 videobuf_vmalloc videobuf_dma_contig videobuf_core wl12xx_sdio wl12xx mac80211 cfg80211 compat btwilink st_drv
<4>[ 7959.846995]
<4>[ 7959.847010] Pid: 19, comm: suspend Not tainted 2.6.35.3-84696-gf486d97 #1 /
<4>[ 7959.847024] EIP: 0060:[<c1852942>] EFLAGS: 00010246 CPU: 1
<4>[ 7959.847046] EIP is at pmu_pci_set_power_state+0x322/0x6e0
<4>[ 7959.847059] EAX: 00000000 EBX: 0000001a ECX: c186dd96 EDX: 00000000
<4>[ 7959.847071] ESI: 00000000 EDI: 00000001 EBP: f78e3d74 ESP: f78e3cd0
<4>[ 7959.847083] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
<0>[ 7959.847097] Process suspend (pid: 19, ti=f78e2000 task=f7899b20 task.ti=f78e2000)
<0>[ 7959.847106] Stack:
<4>[ 7959.847114] c1bcee0b f78e3cf8 c14b502a 00000002 f78e3d4e c1b77d00 f78e3dcc c1bcf200
<4>[ 7959.847142] <0> 00000002 c1bcee0b f78e3d9c f78e3d48 00000008 00000000 00000000 0000011e
<4>[ 7959.847172] <0> 00018601 f78e3d38 c14b502a 00000008 f78e3d02 f78e3d44 c2603920 ffffffff
<0>[ 7959.847204] Call Trace:
<4>[ 7959.847227] [<c14b502a>] ? put_dec+0x2a/0xa0
<4>[ 7959.847249] [<c14b502a>] ? put_dec+0x2a/0xa0
<4>[ 7959.847276] [<c12384a5>] ? sub_preempt_count+0x85/0xc0
<4>[ 7959.847295] [<c14cee6e>] ? pci_platform_power_transition+0x3e/0xa0
<4>[ 7959.847314] [<c18715f3>] ? _raw_spin_unlock_irqrestore+0x23/0x50
<4>[ 7959.847333] [<c14cf5df>] ? pci_set_power_state+0x3f/0x2c0
<4>[ 7959.847353] [<c14ced7c>] ? pci_update_current_state+0x3c/0x50
<4>[ 7959.847372] [<c14d180e>] ? pci_pm_runtime_resume+0x5e/0xa0
<4>[ 7959.847390] [<c12384a5>] ? sub_preempt_count+0x85/0xc0
<4>[ 7959.847406] [<c14d17b0>] ? pci_pm_runtime_resume+0x0/0xa0
<4>[ 7959.847425] [<c1554d7b>] ? rpm_callback+0x3b/0x70
<4>[ 7959.847442] [<c155577c>] ? rpm_resume+0x37c/0x5c0
<4>[ 7959.847460] [<c124923b>] ? release_console_sem+0x37b/0x3c0
<4>[ 7959.847482] [<c1238593>] ? add_preempt_count+0xb3/0xf0
<4>[ 7959.847500] [<c1556609>] ? __pm_runtime_resume+0x49/0xc0
<4>[ 7959.847519] [<c14d1b71>] ? pci_pm_prepare+0x21/0x60
<4>[ 7959.847536] [<c1553947>] ? dpm_suspend_start+0x137/0x7d0
<4>[ 7959.847554] [<c12384a5>] ? sub_preempt_count+0x85/0xc0
<4>[ 7959.847572] [<c18715f3>] ? _raw_spin_unlock_irqrestore+0x23/0x50
<4>[ 7959.847590] [<c126f548>] ? up+0x28/0x40
<4>[ 7959.847610] [<c1288f13>] ? suspend_devices_and_enter+0x73/0x1d0
<4>[ 7959.847628] [<c1289196>] ? enter_state+0x126/0x1e0
<4>[ 7959.847646] [<c1289277>] ? pm_suspend+0x27/0x70
<4>[ 7959.847662] [<c128acba>] ? suspend+0x8a/0x160
<4>[ 7959.847678] [<c186e445>] ? schedule+0x545/0x9e0
<4>[ 7959.847701] [<c12384a5>] ? sub_preempt_count+0x85/0xc0
<4>[ 7959.847720] [<c1265833>] ? worker_thread+0x123/0x2c0
<4>[ 7959.847736] [<c186e445>] ? schedule+0x545/0x9e0
<4>[ 7959.847755] [<c128ac30>] ? suspend+0x0/0x160
<4>[ 7959.847772] [<c12690d0>] ? autoremove_wake_function+0x0/0x50
<4>[ 7959.847790] [<c1265710>] ? worker_thread+0x0/0x2c0
<4>[ 7959.847807] [<c1268c34>] ? kthread+0x74/0x80
<4>[ 7959.847825] [<c1268bc0>] ? kthread+0x0/0x80
<4>[ 7959.847843] [<c120357a>] ? kernel_thread_helper+0x6/0x10
<0>[ 7959.847852] Code: ff 33 00 00 e8 40 b3 9d ff 85 c0 89 c6 0f 85 aa 02 00 00 a1 c0 de b8 c1 ba f4 01 00 00 05 1c 19 00 00 e8 82 b5 01 00 85 c0 75 04 <0f> 0b eb fe a1 c0 de b8 c1 c7 80 14 0a 00 00 00 00 00 00 83 7c
<0>[ 7959.848033] EIP: [<c1852942>] pmu_pci_set_power_state+0x322/0x6e0 SS:ESP 0068:f78e3cd0
<4>[ 7959.848064] ---[ end trace f7884632b6bd02b8 ]---

Change-Id: I230427819b80875cc7da106f3339546c2a1ff2cb
Orig-Change-Id: I6774d29f74a66d413c2e8cb0514bcc6468ccdd20
Signed-off-by: Illyas Mansoor <illyas.mansoor@intel.com>
Reviewed-on: http://android.intel.com:8080/35158
Reviewed-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2] nohz: delay going tickless under CPU load to favor deeper C states

BZ: 23293

While there is CPU load, continue the periodic tick in order to give
CPUidle another opportunity to pick a deeper C-state instead of
spending potentially long idle times in a shallow C-state.

Long winded version:

When going idle with a high load average, CPUidle menu governor will
decide to pick a shallow C-state since one of the guiding principles
of the menu governor is "The busier the system, the less impact of C
states is acceptable" (taken from cpuidle/governors/menu.c.)  That
makes perfect sense.

However, there are missed power-saving opportunities for bursty
workloads with long idle times (e.g. MP3 playback.)  Given such a
workload, because of the load average, CPUidle tends to pick a shallow
C-state.  Because we also go tickless, this shallow C-state is used
for the duration of the idle period.  If the idle period is long, a
deeper C state would've resulted in better power savings.

This patch delays going tickless when there is a load such that on the
next tick, the CPUidle governor will have another opportunity to to
pick a deeper C-state.  Since the system will have been idle for
potentially a full tick, the load average will drop and a deeper C
state will most likely be chosen.

Delaying NOHZ decisions until the load is zero improved the load
estimation on our ARM/OMAP4 platform where HZ=128 and increased the
time spent in deep C-states (~50% of idle time in C-states deeper than
C1).  A power saving of ~20mA at battery level is observed during MP3
playback on OMAP4/Blaze board.

Change-Id: I574a4a70ec90c19aef94fd7ebd4904b2cef94d30
Orig-Change-Id: I941465f66fa69e9e9a59d2de7211a8d6f519a715
Signed-off-by: Nicole Chalhoub <n-chalhoub@ti.com>
Signed-off-by: Vincent Bour <v-bour@ti.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
Signed-off-by: Sundar Iyer <sundar.iyer@intel.com>
Reviewed-on: http://android.intel.com:8080/35157
Reviewed-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

audio: To Enable Audio for CTP.

BZ: 15274 15273

Add codec driver for Cirrus Logic cs42l73
Added CLV Machine driver to integrate codec driver for Clovertrail Platform
Added support to enable Audio on Clovertrail platform

Change-Id: Iaa1e9232bd9b2095c38982b190fbc1b934ab642e
Signed-off-by: Jeeja Kp <jeeja.kp@intel.com>
Signed-off-by: Ojas Chauhan <ojas.chauhan@intel.com>
Reviewed-on: http://android.intel.com:8080/33071
Reviewed-by: Agarwal, Vaibhav <vaibhav.agarwal@intel.com>
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

HDMI-Audio: Ported to R3

BZ: 18092

Some HAD patches were not ported from R2 to R3.

This patch includes Patch#26712, 30304, 30338, 31988,
3216 and 31452(only HAD related changes) alongwith some
code cleaning changes.

Change-Id: Ifedf346ca85f5e6a7c0c760341e5dec0ea762a00
Signed-off-by: Vaibhav Agarwal <vaibhav.agarwal@intel.com>
Reviewed-on: http://android.intel.com:8080/33720
Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com>
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: M, Arulselvan <arulselvan.m@intel.com>
Tested-by: M, Arulselvan <arulselvan.m@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

hwmon/lis3dh: fix critical array out of bounds issue

BZ: 23918

Fix a possible array out of bound issue reported by Klocwork scan.

Change-Id: I273b0aa2f20162727d28820726f23d566d61231c
Signed-off-by: Zhifeng Wang <zhifeng.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/35673
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

medfield: mfld_cstates table referenced when not defined

BZ: 22306

Fixes error:
drivers/idle/intel_idle.c: In function 'intel_idle_probe':
drivers/idle/intel_idle.c:717: error: 'mfld_cstates' undeclared (first use in this function)

Change-Id: I74cae19ffbff38f8581d442c1f9a01b557159e96
Signed-off-by: Mark F. Brown <mark.f.brown@intel.com>
Reviewed-on: http://android.intel.com:8080/33984
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

usb: corrected references to otg_notify when CONFIG_USB_OTG undefined

BZ: 22291

Fixes errors:
drivers/usb/core/generic.c: In function 'generic_probe':
drivers/usb/core/generic.c:195: error: 'struct usb_hcd' has no member named 'otg_notify'
drivers/usb/core/generic.c:196: error: 'struct usb_hcd' has no member named 'otg_notify'
drivers/usb/core/generic.c:198: error: 'struct usb_hcd' has no member named 'otg_notify'

Change-Id: I5255fe1843f6a1f394252ddb1ea4267f8cee1063
Signed-off-by: Mark F. Brown <mark.f.brown@intel.com>
Reviewed-on: http://android.intel.com:8080/33983
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

mrst.c: reimplement the force cold boot properly

BZ: 22672

Do a cold reset in normal case. Do a cold boot depending of module param force_cold_boot.

Change-Id: I422ac66c070f24c287fc625e1d282e2be71cbe84
Reviewed-on: http://android.intel.com:8080/34345
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atmel_mxt_ts: enable mxt1386 for mfld_dv10 tablet

BZ: 20808

Patches are from OTC build:
1943-Input-atmel_mxt_ts-update-object-list.patch
1944-Input-atmel_mxt_ts-handle-objects-with-multiple-inst.patch
1945-Input-atmel_mxt_ts-report-pressure-information-from-.patch
2182-Input-atmel_mxt_ts-update-the-i2c-communication-rout.patch
2183-Input-atmel_mxt_ts-add-firmware-interface-for-config.patch
2184-Input-atmel_mxt_ts-add-some-saving-to-mxt_start-stop.patch
2185-Input-atmel_mxt_ts-add-Android-specifig-PM-functions.patch
2186-mrst-add-support-for-atmel_mxt_ts-touchscreen.patch
2187-Input-atmel_mxt_ts-Add-device-id-for-mxt1386-and-tun.patch
2188-Input-atmel_mxt_ts-free-the-memory-used-by-config-fi.patch
2189-Input-atmel_mxt_ts-Release-touch-points-before-suspe.patch
2190-Input-atmel_mxt_ts-increase-retry-number-for-I2C-R-W.patch

Change-Id: I7bc95f8333e2411796e655d9891ef74d36ed12b9
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34435
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atmel_mxt_ts: revert changes to the upstream atmel_mxt_ts driver

BZ: 20808

Revert the changes to prepare for applying the OTC patches to
this driver.

Change-Id: Ia3b8db53861069e12d7e3237ae62d11fd12341d0
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/34434
Reviewed-by: Continente, Christophe <christophe.continente@intel.com>
Reviewed-by: Chotard, Celine <celine.chotard@intel.com>
Tested-by: Chotard, Celine <celine.chotard@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

ved: Enable video decode on CLV

BZ: 23230

Video decode doesn't work on CLV

CLV ved use punit to upload firmware as MFLD D0, modify a macro IS_D0. Disable D0i3 for CLV.

Change-Id: Id817e9dd9d2ab5e27a285630b33a75b91b462bd7
Signed-off-by: Li Zeng <li.zeng@intel.com>
Reviewed-on: http://android.intel.com:8080/35014
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

[PORT FROM R2]ved: Remove DSIABLE_FW_WDT flag

BZ: 17954

When ved goes to invalid state, driver waits 3s for sync buffer. 3s is relativelg long that media framework drops a lot frames

Remove DSIABLE_FW_WDT flag to enable WDT so that hw responds quickly in invalid state

Change-Id: I33a1992c0c01d996d96a91c910a409e801ac806e
Signed-off-by: Li Zeng <li.zeng@intel.com>
Reviewed-on: http://android.intel.com:8080/34403
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atomisp: fix runtime PM issues

BZ: 23514

Fix 'Unbalanced pm_runtime_enable' issue by removing such call from driver
as PCI core already calls it for each device. In addition, enable runtime
PM for camera by default so that it does not block PM.

Change-Id: I7f60d8a9b9330b6a324a4435d7b57ff8a78a48ab
Signed-off-by: Yong Wang <yong.y.wang@intel.com>
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34938
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atomisp: don't leave mutex locked

BZ: 23514

In case of timeout the lock left untouched.

This patch fixes following bug.

[   73.121283] BUG: workqueue leaked lock or atomic: kworker/u:0/0x00000000/5
[   73.121311]     last function: atomisp_work+0x0/0x6ef [atomisp]
[   73.121466] 1 lock held by kworker/u:0/5:
[   73.121486]  #0:  (&isp->isp_lock){+.+.+.}, at: [<f978e8e5>] atomisp_work+0x369/0x6ef [atomisp]
[   73.121664] Pid: 5, comm: kworker/u:0 Tainted: G        W   3.0.13-mid4-02284-g2796f20-dirty #149
[   73.121690] Call Trace:
[   73.121735]  [<c1034497>] ? console_unlock+0x178/0x18a
[   73.121844]  [<c1048240>] process_one_work+0x2b0/0x32c
[   73.121984]  [<f978e57c>] ? atomisp_buffer_dequeue+0x9b/0x9b [atomisp]
[   73.122588]  [<c1048ffb>] worker_thread+0xbb/0x136
[   73.122632]  [<c1048f40>] ? manage_workers.isra.24+0x150/0x150
[   73.122672]  [<c104bf09>] kthread+0x73/0x78
[   73.122718]  [<c104be96>] ? __init_kthread_worker+0x47/0x47
[   73.122763]  [<c14df342>] kernel_thread_helper+0x6/0x10

Change-Id: I2059b6db63bfa0d9ae4baed0353a0304907dd33f
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: David Cohen <david.a.cohen@intel.com>
Reviewed-on: http://android.intel.com:8080/34937
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Tuominen, TeemuX <teemux.tuominen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atomisp: fix typo in lock initialization

BZ: 23514

Fix typo when the same lock was initialized twice.

During the fix of another issue the lock was initialized twice. This patch
fixes the typo.

Change-Id: If5b42286ae9cd7de30bf9bb8844cf7dd7e01b7e7
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34936
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atomisp: cosmetic indentation fix

BZ: 23514

No functional change here.

Just fix the indentation.

Change-Id: I9a461b42b532d9a35c4b2c3b08a7fa58adef6c5b
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34935
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atomisp/css: fix return type of sh_css.c:check_infos_match

BZ: 23514

The return type should be enum. Currently the boolean is used that is
incorrect.

Change-Id: Ia88db94019998d3d5dd1677f97580ff2941350fc
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34933
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atomisp/css: optimize sh_css_hrt_irq_get_id()

BZ: 23514

There is no need to loop to find the first set bit. We can easily use the ffs()
function to do the job. And this way is faster.

This patch implements faster and simplier codepiece.

Change-Id: Id9d26a0cbf3c9a965e0c82fbd47d47734730df29
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34932
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

atomisp/css: Remove PC_MONITORING thread before release

BZ: 23514

In case when the atomisp driver is built as module with the PC_MONITORING
turned on, the release of the module will wait for the pc_monitoring thread
which never stops.

This patch stops the thread correctly during release procedure.

Change-Id: I8926a524b94e552d412c764c6746df786f0394ce
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-on: http://android.intel.com:8080/34931
Reviewed-by: Shevchenko, Andriy <andriy.shevchenko@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

gpio: add wakeup source trace in GPIO driver

BZ: 23641

Add logs to trace the wakeup source at each time the langwell-gpio
device resumes.

Change-Id: I8774526d1a529205c8c4681a20ba6a4beac6065f
Signed-off-by: Li, Ning <ning.li@intel.com>
Reviewed-on: http://android.intel.com:8080/35387
Reviewed-by: Yang, Bin <bin.yang@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

hwmon: lps331ap: Add lps331ap baro sensor for cvt

BZ: 22002

Add lps331ap baro sensor for Clover Trail platform.

Change-Id: I3e811fc403ddff5aeb7a7589b4ea639ec762a3a7
Signed-off-by: jli127 <jian.d.li@intel.com>
Reviewed-on: http://android.intel.com:8080/33633
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

hwmon: l3g4200d: Initial version of gyroscope driver

BZ: 22173

This commit adds the ST L3G4200D gyroscope driver. The driver is polling
based and suitable for android system.

Change-Id: I50952855fc38d0ee92125a11e45a4e9ce8a1b7b5
Signed-off-by: Zhifeng Wang <zhifeng.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/21906
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>

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>