This reverts commit 994ff121f0c2e3ff00fa38ae2f8dfde4bda1b332.
PM8921 MPP7 no longer must be kept high at all times for targets
using PCDDR3 memory because newer hardware ensures that memory is
always powered when necessary.
picked from fb3d2f519b3dabf307596389365fe04384d0c3eb
Change-Id: If5691877ea5b0e9c268d32fe4b9458652bf77c7f
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/69275
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
Tested-by: Sam hblee <Sam_hblee@asus.com>
This is a workaround, for instability seen with leaving gfx footswitch
go on/off.
Separate board-flo-gpu.c is based on board-8064-gpu.c for flo hardware
so that workaround is also added. This refers to the following change
Change-Ids
bbe03d50952ebac9b6fdef315cf12ae57e7963da
Change-Id: Ia49ccae7d2cfc64cf2f22bf053683dc728cc4f20
Signed-off-by: paris_yeh <paris_yeh@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/69279
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
The current 8064 frequency plan supports max mdp clk up to 266.667MHz.
CRs-Fixed: 405103
Author is Huaibin Yang <huaibiny@codeaurora.org>
Reference change-id is I326f5becc642399a4a0e9d97752d893752388066
Change-Id: I873d0058602cba7e2239daecce89ee8f7613faa4
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/69303
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
Tested-by: Sam hblee <Sam_hblee@asus.com>
In order to support extra data during secure playback,
video core meta data buffers need to be allocated from
MFC heap. This is required as both HLOS and video core
have read-write access to this heap. As each meta buffer
size is 8KB and there can be 32 meta & output buffers,
increase the MFC ION heap size by 256KB.
Author is Deepak Verma <dverma@codeaurora.org>
Reference change-id is I033d24c9d02a879e38c5f6d86b2b6c0a767ec25c
Change-Id: I60f595c7e2a2a569dcfa320c7c1e3ff5bdd6f064
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/69302
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
Tested-by: Sam hblee <Sam_hblee@asus.com>
This branch is currently very outdated. Cherry pick the following
changes in order to bring recent fixes to this branch.
Separate board-flo-*.c is based on board-8064-*.c for flo hardware,
it needs following change to fix build break:
Change-Ids
999ee576589682c27492184c22053d19819c0285
Change-Id: Ic51f927c0efc350372ccc98e2805cbde0bb26cb1
Change-Id: I6187110b272c6032d90b1a42e97bbbc25bd9edce
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/69295
Reviewed-by: Nick Cheng <nick_cheng@asus.com>
Tested-by: Nick Cheng <nick_cheng@asus.com>
8960AB and 8064AB have a new revision of the Krait SPM hardware.
The SPM v1.15x on these targets uses a different bit to control the
apc_pdn signal.
Update the SPM sequences for standalone and power collapse to use the
new sequences.
L2 SPM or Krait WFI/Retention sequences are not affected.
CRs-fixed: 419258
Author is Anji Jonnala <anjir@codeaurora.org>
Reference change-id is I3bcf335ac50cd1181047fe1ee1d56ecd507ae35c.
Change-Id: If532e26601e52a3b304cdc0c1856cf0b234dcee0
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/69287
Reviewed-by: Singhome Lee <singhome_lee@asus.com>
Tested-by: Singhome Lee <singhome_lee@asus.com>
Re-caculate the index of sysfs project_id because hardware revision
shorten from 3 bits to 2 bits.
Change-Id: I84910ae4d743fc45660f547e2f149c7e75334372
Signed-off-by: paris_yeh <paris_yeh@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/69155
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
1. set fps back to 60 for LG panel
for panasonic panel, set to fps 60 still have underrun
2. hard code ab, ib (memory clock) to max for mipi video mode panel
because the priority of display is not high enough, the bandwidth may be robbed by others
for JDI mipi command mode panel, there may not be underrun issue because the panel has framebuffer itself
Change-Id: Id95c56ecf570a7cae8db37eede0b3555b3186bd5
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/69094
Reviewed-by: Yetta Wu <Yetta_Wu@asus.com>
Tested-by: Yetta Wu <Yetta_Wu@asus.com>
Reviewed-by: Warlock Tai <warlock_tai@asus.com>
3-4mA power hit is expected. Keep GFX3D footswitch always on to
resovle instability during suspend and resume testing. In RTB log,
system locks up in and between footswitch_enable() operations when
issue is reproduced.
FIXME: Qualcomm will continue to debug this issue and submit a
formal fix to partner gerrit once this problem is identified.
Change-Id: If5753f9f6e7ebac47a6dbca849b16ee7ba68fceb
Signed-off-by: paris_yeh <paris_yeh@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68850
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68854
3V3 is always high in spec, so we need to delay more time after 3V3 on
Change-Id: Iab0ecaecefb98cc6bae441381d233759b235e2ba
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68839
Reviewed-by: Yetta Wu <Yetta_Wu@asus.com>
Tested-by: Yetta Wu <Yetta_Wu@asus.com>
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
to make charging IC function correctly
Change-Id: I619ee5eccb85e586b8a5adbacc40115547e1d168
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68687
Reviewed-by: Yetta Wu <Yetta_Wu@asus.com>
Tested-by: Yetta Wu <Yetta_Wu@asus.com>
Reviewed-by: Warlock Tai <warlock_tai@asus.com>
- Revise gpio settings to active gsbi2 bus in board-flo-gpiomux.c.
- Register both mpu6500 and akm8963 to gsbi2 bus.
- Add drivers for mpu6500 and akm8963 with MotionApps v5.1.4.
Change-Id: I2ddfc1bc28153c6396d5fa0534927ede31383e94
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68257
Reviewed-by: Jive Hwang <jive_hwang@asus.com>
Tested-by: Jive Hwang <jive_hwang@asus.com>
This is to avoid the leakage from the ap2mdm_status pin when the modem is not on yet.
Change-Id: Ic36ca808dd0ace918ea33b0dc6c877b018934aab
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68259
Reviewed-by: Leslie Yu <Leslie_Yu@asus.com>
Tested-by: Leslie Yu <Leslie_Yu@asus.com>
Disable the mdm2ap_pbl_ready pin after mdm is now ready
and enable the mdm2ap_pbl_ready pin when the soft reset modem.
Change-Id: I6d1b6d549c7baab41fcc20cee573f97bd463c113
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68256
Reviewed-by: Yi-Hsin Hung <Yi-Hsin_Hung@asus.com>
Tested-by: Yi-Hsin Hung <Yi-Hsin_Hung@asus.com>
Reviewed-by: Leslie Yu <Leslie_Yu@asus.com>
Patch from Ken that can solve fsstress failing issue
commit b9fa7bb8ff207eeb27d2e0ed45b8c3acf1a7af8c
Author: Tao Ma <boyu.mt@taobao.com>
Date: Mon May 28 18:20:59 2012 -0400
ext4: protect group inode free counting with group lock
Now when we set the group inode free count, we don't have a proper
group lock so that multiple threads may decrease the inode free
count at the same time. And e2fsck will complain something like:
Free inodes count wrong for group #1 (1, counted=0).
Fix? no
Free inodes count wrong for group #2 (3, counted=0).
Fix? no
Directories count wrong for group #2 (780, counted=779).
Fix? no
Free inodes count wrong for group #3 (2272, counted=2273).
Fix? no
So this patch try to protect it with the ext4_lock_group.
btw, it is found by xfstests test case 269 and the volume is
mkfsed with the parameter
"-O ^resize_inode,^uninit_bg,extent,meta_bg,flex_bg,ext_attr"
and I have run it 100 times and the error in e2fsck doesn't
show up again.
Change-Id: Iba773843728759e1d64d4ff57765288eb5977665
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/67871
Reviewed-by: Lin Johnny1 <Johnny1_Lin@asus.com>
Tested-by: Lin Johnny1 <Johnny1_Lin@asus.com>
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
In kernel space, include <mach/board_asustek.h> to have the following
exported APIs for inquiry
--asustek_get_tp_type(void);
*Touch panel vendor
--asustek_get_lcd_type(void);
*LCD vendor
--asustek_get_hw_rev(void);
*Hardware revision
Below sysfs are created under /sys/devices/platform/asustek_pcbid
--asustek_pcbid
*show up pcbid value
--asustek_chipid
*show up system UUID as same as ro.serialno
--asustek_projectid
*show up project id
Change-Id: Id10c8baf28220fd52754bec069fa1f4e6f456f25
Signed-off-by: paris_yeh <paris_yeh@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/63004
Reviewed-by: Sam hblee <Sam_hblee@asus.com>
Reviewed-on: http://mcrd1-5.corpnet.asus/code-review/master/68055
Reviewed-by: Jive Hwang <jive_hwang@asus.com>
Tested-by: Jive Hwang <jive_hwang@asus.com>
