unit power off failed when removed charger in factory mode.
Because google android R define CONFIG_STATIC_USERMODEHELPER
and CONFIG_STATIC_USERMODEHELPER_PATH = "", so sub_info->path
is always empty.
Change-Id: If06b3a52e657e083ce89f2f75f717c753a57d685
Signed-off-by: mahj8 <mahj8@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1899604
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
This change is not need. Because we have changed the code
to reach the goal at https://gerrit.mot.com/#/c/1899604/
Mot-CRs-fixed:(CR)
This reverts commit d80c7cd6d49b21e72e2b91e9e5c556dbeb5b5e85.
Change-Id: I3a58e7d0153f0751f2e8714669683a980b1bf736
Reviewed-on: https://gerrit.mot.com/1900615
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Tbase load was failing intermittently during fc_init() operation
in __smc() with error:
Trustonic TEE: ERROR -14 __smc: fc_init failed (4dee8000)
The root cause has two components
1- qcom_scm_call() needs to be done atomically. Task reschedule was
causing a failure. Thus changed to the atomic call qcom_scm_call_atomic().
2- Qcom scm_call requires cache maintenance. API attests that any buffers
that are expected to be accessed by the secure world must be flushed before
invoking qcom_scm_call and invalidated in the cache immediately after
qcom_scm_call returns. Cache invalidation was missing, hence add it.
Change-Id: I83139fc5110eb3af536a30800c994c8e451df1fa
Signed-off-by: quebs2 <quebs2@motorola.com>
Reviewed-on: https://gerrit.mot.com/1899491
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Zhenxin Xi <xizx@motorola.com>
Submit-Approved: Jira Key
if a prject need extra config, please add to the extra config
for example:
moto-holi-ibiza-cmcc-extra.config
match TARGET_PRODUCT_TYPE:
cmcc
factory
retail
...
Change-Id: I6157eee802bfe4cd11c5d6b76b518b04353c9c27
Signed-off-by: louhs1 <louhs1@motorola.com>
Reviewed-on: https://gerrit.mot.com/1898417
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Yiwen Liu <liuyw2@motorola.com>
Reviewed-by: Yonghui Jia <jiayh2@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
In kernel 5.4, the old qcom interface scm_call2() has been abandoned, so
add new function trustonic_smc_fastcall() for Trustonic TEE driver module,
and it will send syscall to the secure world through new qcom scm interface.
Change-Id: Ib76c00e9910be6796fc71bdcfaf4352fd8f2806c
Signed-off-by: linyx10 <linyx10@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1836283
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Zhenxin Xi <xizx@motorola.com>
Submit-Approved: Jira Key
These ABI are used in mcDrvModule.ko and they have been added to GKI whitelist,
so add them to qcom whitelist:
d_path
get_task_exe_file
get_task_mm
ktime_get_raw_ts64
mmput
release_pages
Change-Id: If1d64546756b658e4e726ee8abef452d79a9aa5c
Signed-off-by: linyx10 <linyx10@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1892816
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Binsheng Que <quebs2@motorola.com>
Reviewed-by: Zhenxin Xi <xizx@motorola.com>
Submit-Approved: Jira Key
This l(CR) breaks tracing tools l(CR) trace-cmd. It logs in the same
format but now addresses are all 0x0.
Bug: 34277115
MOT-CRs-fixed: (CR)
Change-Id: Ifb0d4d2a184bf0d95726de05b1acee0287a375d9
Reviewed-on: https://gerrit.mot.com/1887836
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Wang Wang <wangwang1@lenovo.com>
Reviewed-by: Xiangpo Zhao <zhaoxp3@motorola.com>
Submit-Approved: Jira Key
Reviewed-on: https://gerrit.mot.com/1892775
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
On kernel 4.14, no matter sd card type, all use max discard value.
However, kernel 5.4 remove this logical, and will cause system watchdog,
if user format 512GB/1TB class 10 card.
Change-Id: Idc6b00187b8800465fca4af8f720aaf87db5700b
Reviewed-on: https://gerrit.mot.com/1890338
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Disable cabc only when adjust to low brightnss.
Don't disable cabc when screen off/on, this causes big
voltage issue on pm6150l/7150l.
Change-Id: I510ea8d1e3de1cee1a612fec6a08d50792b8b0af
Signed-off-by: wangyq13 <wangyq13@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1873482
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Hua Tan <tanhua1@motorola.com>
Submit-Approved: Jira Key
Reason: zram-writeback will make 3 side effects
1. Swapcached too large
2. May cause CTS fail
3. May cause panic
This reverts commit db753c431b0b778e4f1824efe79718b5e3864839.
Change-Id: I61c6d2eb0222d8bd4d749971bdf5ccaacee854ab
Reviewed-on: https://gerrit.mot.com/1873703
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Zhizhong Ge <gezz1@motorola.com>
Reviewed-by: Bingqian Yang <yangbq1@lenovo.com>
Reviewed-by: Zhenxin Xi <xizx@motorola.com>
Submit-Approved: Jira Key
Remark:
vold doformat() will call ioctl(BLKDISCARD) before unmount
this blocked sdhci layer for current driver.
So, set max_timeout_counter to 0 to ensure larger discard size by
always setting max_busy_timeout to zero.
the change is from temp patch drop by QC SR:05069564
next QC drop will include the formal patch. that time we can
drop this commit.
Change-Id: I2950b42c01e04bd9cfb9a2a739d00cd35da800f3
Signed-off-by: fuxm1 <fuxm1@motorola.com>
Reviewed-on: https://gerrit.mot.com/1868453
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Chuanchun Zhu <zhucc2@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
GKI image should not support nfc. Nfc dirver is built to our kernel.
And nfc can't work after flashing GKI. So we change the nfc dirver as
a ko module.
Change-Id: I602e308fb636695aa6a4969341324bae11dca385
Signed-off-by: duqiu2 <duqiu2@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1846765
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Bin Liu <liubin7@motorola.com>
Reviewed-by: Weilong Wu <wuwl10@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Override the SDP current if it needs to increase for SDP USB2.0 500mA
or USB3.0 900mA.
Porting from (CR)
Change-Id: Ib0136a2674e8f9ac6e7e5646a82052971a4bbf08
Reviewed-on: https://gerrit.mot.com/1836523
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Haijian Ma <mahj8@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
According to debug, denver's unexpected RTC reset was caused by
PMIC issue. So I rever the monitor change.
This reverts commit 2a62d1dc1ccb40b698b33d4cff83f8cdf3d4c95c.
Change-Id: I6ef1049ccdfd32b1f12df3aef748c5755a469a64
Reviewed-on: https://gerrit.mot.com/1831952
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Because GKI, pmic-voter.o is included by both qcom-qpnp-qg.ko
and qpnp-smb5-main.ko, so can't export symbol in pmic-voter.c
Change-Id: I3c9266531de4a4e2461e872bade0bd7dfcaa0eec
Signed-off-by: mahj8 <mahj8@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1822938
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Export some pmic-voter interfaces for dlkm usage as well
as create access functions that are exported for dlkm to
manipulate the struct.
charging DLKM need some api of pmic vote, but pmic_voter.o
is included by both qpnp-smb5-main.ko and qcom-qpnp-qg.ko,
KMI don't allow double export one function in two DLKM modules.
Change-Id: I56f96b663d9ee2228d91bd2efc6977a13f270de4
Signed-off-by: mahj8 <mahj8@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1822930
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Haijian Ma <mahj8@motorola.com>
Submit-Approved: Jira Key
it will cause ion related ABI CRC mismatch, wrap
CONFIG_DEBUG_FS for them
Change-Id: I162143205847323eaa0fbb52e7b337607e57b07a
Signed-off-by: jixj <jixj@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1825354
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
According to the guideline from Qualcomm support, I add RTC log
in kernel so that we can trace the issue from unexpected RTC reset
Change-Id: Ia26f18ecebcf7627df167dd146582717c8e3414c
Signed-off-by: wangxf14 <wangxf14@motorola.com>
Reviewed-on: https://gerrit.mot.com/1824238
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Haijian Ma <mahj8@motorola.com>
Reviewed-by: Hujun Liao <liaohj@motorola.com>
Submit-Approved: Jira Key
CONFIG_LOG_BUF_SHIFT is default set as 17 =>128KB, however,
for sm4350, 128KB is not enough, after bringup, early bringup kermel
log is overwrite, we have to enlarge the valuse to 18=>256KB, to make
kernel bringup log complete.
Change-Id: Icae1058520b73fc0b979efa5977b5bdce73604a0
Reviewed-on: https://gerrit.mot.com/1817725
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
disable CONFIG_STATIC_USERMODEHELPER in userdebug
and factory version for orderly_poweroff api can work.
Change-Id: Ic71a8471cfd4228d32556f898eaecbbc6ec40b17
Signed-off-by: mahj8 <mahj8@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1817533
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Xiaojun Ji <jixj@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Improvements made to ION to add an additional debugfs file
to display allocation/reference information for all ION buffers.
rb tree was deleted becaused of unused, add it back to track
ion buffer alloc.
Migrated from (CR):
https://gerrit.mot.com/#/c/1535657/https://gerrit.mot.com/#/c/1535658/
Change-Id: I1e42d3dac61d4fc856ba8d749cfd2123e40529d9
Signed-off-by: liuwang2 <liuwang2@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1811670
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Zhilong Wang <wangzl30@motorola.com>
Reviewed-by: Ji Zhao <zhaoji1@lenovo.com>
Reviewed-by: Bolei Shang <shangbl1@lenovo.com>
Reviewed-by: Zilong Zhang <zhangzl7@lenovo.com>
Reviewed-by: Dawei Wang <wangdw10@motorola.com>
Reviewed-by: Zhenxin Xi <xizx@motorola.com>
Submit-Approved: Jira Key
Fix https://gerrit.mot.com/1778586 propagation error.
The "reason" is default PON_RESTART_REASON_UNKNOWN (0),
At the end, QC will set restart reg with "reason" so this reg
will be override to 0
Change-Id: I3a0092edb6a29a1d3edd9fa79428115b7c590ffb
Reviewed-on: https://gerrit.mot.com/1808858
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
On sm4350 R,the priority of do_msm_restart is 200,the priority of
restart_wdog_handler is 255. when kernel panic happens,
restart_wdog_handler will be invoked first and trigger a watchdog,
but do_msm_restart will not be invoked so bootloader can not read
reset info.
The panic notifier (panic_prep_restart) still invoke, so store the extra
reset info for kernel panic
Change-Id: Ia263ebfb2eda4424555ddb937239325048ea846f
Reviewed-on: https://gerrit.mot.com/1809656
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
For improve debug verison performance, remove some unnessary configs.
If some guys need debug the special issue, need enable them at local.
Change-Id: I120b4fdbd03fc72d61825c708897b90d2ef38b2e
Reviewed-on: https://gerrit.mot.com/1807723
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Jun Weng <wengjun1@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
some product all sku inbox charger is 10W, so don't
need config usb_dcp in vhw.xml.
add dcp max current by dts to config all sku.
some product which don't have 10W charger in all sku
can overlay dts by mmi,usb_dcp in vhw.xml
Change-Id: Ie9ddb6c47d42b039d6bfe306e1263168688dac36
Signed-off-by: mahj8 <mahj8@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1804249
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
kernel configs enabled to support PASR which can hotplug RAM banks
we don't have multiple RAM slots in devices, disable this feature
to avoid potential performance penalty
Change-Id: I399b0e45001679c7650715600cdbbc9fb8f75476
Signed-off-by: jiayh2 <jiayh2@motorola.com>
Reviewed-on: https://gerrit.mot.com/1786864
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Bingqian Yang <yangbq1@lenovo.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Now we don't use touchscreen_mmi in br-4350,
so this change is not necessary for us.
This reverts commit 899bedf4ac94d0c1b3769787d779226d107655f6.
Change-Id: I59f0ec8474350f2a796f9446c5cb9b1d77e9df9e
Signed-off-by: wengjun1 <wengjun1@motorola.com>
Reviewed-on: https://gerrit.mot.com/1799286
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Jianqiu Huang <huangjq9@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
The "rt_mutex_lock" and "rt_mutex_unlock" functions can
be found in the latest google whitelist, so update the qcom
whitelist for chipone touchscreen.
Change-Id: I01c538b544d130b7c0dfe6999219c9af7fd8836f
Signed-off-by: wengjun1 <wengjun1@motorola.com>
Reviewed-on: https://gerrit.mot.com/1797282
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Jianqiu Huang <huangjq9@motorola.com>
Reviewed-by: Xiaojun Ji <jixj@motorola.com>
Reviewed-by: Yeqing Wang <wangyq13@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
add "flip_open/filp_close" white list for aw882xx
All of them could be found in the latest abi_gki_aarch64*.xml file.
Change-Id: Ia89d6371a7c097dee12fa78dd9d5acb72e2f581b
Signed-off-by: liaohj <liaohj@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1794660
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Port the spi changes from bq-6125.
when unit suspend, pm_runtime_disalbe() would be called. And
then dev.power.disable_depth number will +1. And its value
will be -1 when pm_runtime_enable() is called.
And if spi bus want to work as soon as system resume, it will call
pm_runtime_get_sync(), which would check the value of
disable_depth. If its value is not 0, spi operation will fail.
The sequence is as following:
runtime_suspend
pm_runtime_disable()-> disable_depth +1
rumtime_resume
pm_runtime_eanble() -> disable_depth -1
spi_sync()
pm_runtime_get_sync -> check the value of disable_depth
But for sometimes, spi operation will earlier than pm_runtime_enable()
called. Then spi_sync() will fail duel to non-zero disable_depth value.
So we add a checking logic before pm_runtime_get_sync() to make sure
disable_depth is 0.
Change-Id: I673363bfd861402b5c54874137b12700ef2df14d
Signed-off-by: wengjun1 <wengjun1@motorola.com>
Reviewed-on: https://gerrit.mot.com/1793166
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Wei Wei <weiweij@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
