When CONFIG_PM_DEBUG is set, kmsg is able to reflect
1)status of active wakelock held,
2)callbacks registered with early_suspend and late_resume, and
3)when entering kernel PM transition.
Change-Id: I41a7bb3e1ee47a02f80b1433fdeeb5e691acd0e2
Signed-off-by: paris_yeh <paris_yeh@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/62176
Reviewed-by: Chuang Simon <Simon_Chuang@asus.com>
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/62899
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68031
Reviewed-by: Jive Hwang <jive_hwang@asus.com>
Tested-by: Jive Hwang <jive_hwang@asus.com>
1. slimport basic function
2. set gpio 50 as 27M clock (function_2, refer to document 80-N7752-2 p.435)
3. request USB_ID pin (gpio 77) to let detect pin work
4. the version history:
V0.1
The gerenal slimport ANX7808 driver for customer evalutaion and application.
2013-01-08
V0.2
1. Add pull down ID_OUT pin once the slimport accessary is plugged, and left it to default status
once the accessay is unplugged.
2. If the incoming video is YUV, convert it to RGB colorspace, since our RGB dangle only support RGB.
2013-01-29
V0.3
1. Correct the error in eye diagram test.
2. Correct the phy auto test.
Change-Id: I0d35945b5682ca736ec00b3d5166001f2ab5dfc3
Change-Id: Ibdf3ba27e119f0ae361b28b1f33f7522d5fdf758
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/67937
Reviewed-by: Yetta Wu <Yetta_Wu@asus.com>
Tested-by: Yetta Wu <Yetta_Wu@asus.com>
Reviewed-by: Warlock Tai <warlock_tai@asus.com>
From Qualcomm errta, 8064 V2 SOC has the stability issue if MIDR ID is 0x511F06F0.
Change-Id: Iac4f6081109bd4780156c988de0d115a1cf04425
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/67933
Reviewed-by: Singhome Lee <singhome_lee@asus.com>
Tested-by: Singhome Lee <singhome_lee@asus.com>
1. port LG and panasonic panel
2. remove the choice "LCD Panel" in Kconfig because we need to config multiple mipi panels in one code base
3. pwm and LCD_BL_EN power source change to L17
Change-Id: I793114db222ed7712662495cd7106f1d0d41ddd3
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/67830
Reviewed-by: Warlock Tai <warlock_tai@asus.com>
Tested-by: Warlock Tai <warlock_tai@asus.com>
support the initial flo hardware. enabled basic power, storage,
and debug-uart.
Change-Id: Ie62deb0cb0d3d1ce42878d9d0a68e511e3249a68
Signed-off-by: paris_yeh <paris_yeh@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/67777
Reviewed-by: Edward Lu <Edward_Lu@asus.com>
Reviewed-by: Victor Chen <Victor_Chen@asus.com>
Tested-by: Victor Chen <Victor_Chen@asus.com>
Adds support for the MFC core to add the bitstream_restrict flag in the
sps/pps for H264 codecs. This allows for the decoder to determine how
many frames to buffer when decoding.
Change-Id: I30dc17a29b9fcc1ee76265f0318a0a581316dd49
Signed-off-by: Deva Ramasubramanian <dramasub@codeaurora.org>
Signed-off-by: Iliyan Malchev <malchev@google.com>
Conflicts:
drivers/video/msm/vidc/1080p/ddl/vcd_ddl.h
drivers/video/msm/vidc/1080p/ddl/vcd_ddl_properties.c
drivers/video/msm/vidc/1080p/ddl/vcd_ddl_shared_mem.c
drivers/video/msm/vidc/1080p/ddl/vcd_ddl_shared_mem.h
drivers/video/msm/vidc/1080p/ddl/vcd_ddl_vidc.c
include/media/msm/vcd_property.h
The current code can divide by zero in the scale_soc_while_chg
function if calculated_soc drops while charging.
This patch fix it.
Change-Id: I83c7e9c7056990499f474c9e1882f0377df05f0c
Add code to calculate the run queue depth of a cpu and iowait
depth of the cpu.
The scheduler calls in to sched_update_nr_prod whenever there
is a runqueue change. This function maintains the runqueue average
and the iowait of that cpu in that time interval.
Whoever wants to know the runqueue average is expected to call
sched_get_nr_running_avg periodically to get the accumulated
runqueue and iowait averages for all the cpus.
Signed-off-by: Jeff Ohlstein <johlstei@codeaurora.org>
(cherry picked from commit 0299fcaaad80e2c0ac9aa583c95107f6edc27750)
Signed-off-by: Ram Kumar Chakravarthy Chebathini <rcheba@codeaurora.org>
(cherry picked from commit 5325d8a44f8296170cd8f42e245dd79f7b7347bf)
Change-Id: I92875789886c3f7c2457a063de4b3b6d8c893718
Signed-off-by: Sudhir Sharma <sudsha@codeaurora.org>
We need to tune the board specific adcmap parameters
So need functions to set specific parameters.
void pm8xxx_set_adcmap_btm_threshold(void *pts, int size)
void pm8xxx_set_adcmap_pa_therm(void *pts, int size)
void pm8xxx_set_adcmap_ntcg_104ef_104fb(void *pts, int size)
Change-Id: Ie78c11f5fb998ecc456defa3c8e3e7a3e0b9b45f
Rather than checking for the value 1 check that
bit zero is set.
Change-Id: Ie2842b28648084d8970329d7c76fcf0d0666a847
Signed-off-by: David Keitel <dkeitel@codeaurora.org>
Signed-off-by: Iliyan Malchev <malchev@google.com>
Some workarounds that are required for PMIC die version 3.0
differ slightly for die version 3.0.1.
Fix this by checking the PMIC subversion register to distinguish
between 3.0 and 3.0.1.
CRs-Fixed: 403150
Signed-off-by: David Keitel <dkeitel@codeaurora.org>
(cherry picked from commit 913c55e2706c36132fd42f90c05530b8e55a26ed)
Conflicts:
drivers/power/pm8921-charger.c
Change-Id: I11155d6180de09e1b9e0137f7943603d44102d07
Signed-off-by: Sridhar Gujje <sgujje@codeaurora.org>
Signed-off-by: Iliyan Malchev <malchev@google.com>
During charging adjustment, the measurement of voltage is not accurate.
Since the measured voltage during charging adjustment is not OCV
(open circuit voltage), it cannot show real battery voltage at CC to CV
point. But current implementation use inaccurate voltage as a voltage of
CC to CV point. This inaccurate voltage of CC to CV point can cause
wrong SoC adjusting. For instance, the SoC could stick at fixed value
until end of charging.
This patch increase accuracy of voltage measurement by using battery
current and battery resister.
Change-Id: I3a4cc4e58e409be5422ec6bf64678a9a92b9fe25
We observed that SoC suddenly increase from 98% or 99% to 100%
right after charger removal. This issue caused by charging adjusting
algorithm which adjust SoC to sync 100% with end of charging.
During charging adjustment, the adjusted SoC could be smaller than
original SoC. So when we remove charger, charging adjusting algorithm
stop adjusting SoC and then bms report original SoC which is larger
than before.
Previously, bms driver considered most of this case by using previous
SoC when SoC increase during discharging. But if SoC is 100%, previous
patch doesn't work.
So this patch add SoC 100% case by checking if charger is enabled.
Change-Id: I70945d391c9d821eaf875f1bcd1e8787077b98da
