Qcom introduces new watchdog architecture on 4350/8350, so use
"qcom_wdt_trigger_bite" to trigger wdog when enable CONFIG_QCOM_WDT_CORE
Change-Id: Ide2ccb0e5a498454359fd6544e832f109251df5c
Reviewed-on: https://gerrit.mot.com/1782962
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Ryan Lattrel <ryanl@motorola.com>
Reviewed-by: Zhenxin Xi <xizx@motorola.com>
Submit-Approved: Jira Key
$TOP was not defined on Kernel msm-5.4.
Need to update Kbuild to fix the build error.
Change-Id: I6cb80d3e0eff819572b7eb82fad97fc6d3b7a36e
Signed-off-by: wuwl10 <wuwl10@motorola.com>
Reviewed-on: https://gerrit.mot.com/1779665
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Refer to https://gerrit.mot.com/#/c/1721469/
On latest kernel wakeup_source_init API remove,
Need to use wakeup_source_register for the same.
This fix replaces wakeup_source_init to wakeup_source_register
wakeup_source_trash to wakeup_source_unregister
Change-Id: I0ae76f3f942237fc89c943fbd65ed48eefd9b698
Signed-off-by: huangjq9 <huangjq9@motorola.com>
Reviewed-on: https://gerrit.mot.com/1778411
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
After flashing GKI, https://gerrit.mot.com/#/c/1439246/ is not available.
Export API to match "mmi,status" rules, the other modules can use this
API to check if driver is available at the begining of probe() function.
Change-Id: I58413e071e32b82037c72c688a7bbbadce28007c
Reviewed-on: https://gerrit.mot.com/1772580
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Konstantin Makariev <kmakariev@motorola.com>
Submit-Approved: Jira Key
fixed exfat compliling failed on kernel 5.4 , due to MS_RDONLY and
MS_NODIRATIME flag is just used for mounting, if file system need
used SB_*.
Change-Id: Icf8bb0595bd2aacefcc3bbf6bc81c48f103af6bf
Signed-off-by: yuedl1 <yuedl1@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1773673
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Dongliang Yue <yuedl1@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Capri plus: support NT36525b NT36525c both in evt
Add ic config to match fw name with ic info
NO_PROP_NEEDED: needn't for shm2018
Change-Id: I83a33b8770dbbd0a10c4500323e20ef94e7dc386
Signed-off-by: hujing3 <hujing3@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1766028
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Xiangpo Zhao <zhaoxp3@motorola.com>
Submit-Approved: Jira Key
Cherry-picked from (CR)
Probably on the Gold Core, Athene is not applicable to the nq
handler when Trustonic TEE sheduler is being called. As per the
test results, device will be hung if the tbase is working on e.g
core#6 which belongs to QC Kryto Gold core. workaround to bind
the TEE scheduler with CPU core #0, #1, #2, and #3.
Included logic to select silver CPU and clock mode based on device config:
- RSU_SELECT_SILVER_CORES is set to force Trustonic TEE schedule
run in Silver cores.
- RSU_INTERNAL_CLOCK is set for platforms that use internal clock for
qcom_seecom. Example: In lagoon.dtsi, node
"qcom_seecom: qseecom@c1700000" has entry "qcom,no-clock-support;"
Change-Id: I7d767d42070fbbbd26859ce1a9dca8ead0664dd6
Reviewed-on: https://gerrit.mot.com/1765894
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Igor Kovalenko <igork@motorola.com>
Submit-Approved: Jira Key
- Fixed kernel_read/kernel_write error.
- Since input_get_new_minor has been removed from the whitelist
of GKI, so change the new api to alloc_chrdev_region for compatibile
with all kernel version.
Change-Id: Ia232358a283f9f26d0602f50e063f2ddb5c5c24d
Signed-off-by: wengjun1 <wengjun1@motorola.com>
Reviewed-on: https://gerrit.mot.com/1761835
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Jianqiu Huang <huangjq9@motorola.com>
Reviewed-by: Yeqing Wang <wangyq13@motorola.com>
Reviewed-by: Huosheng Liao <liaohs@motorola.com>
Submit-Approved: Jira Key
Error:
1. /focaltech_ts.c:1055:3: warning: misleading indentation; statement is
not part of the previous 'if' [-Wmisleading-indentation]
2. focaltech_ts.c:2543:11: warning: format string is not a string
literal (potentially insecure) [-Wformat-security]
Change-Id: I78772d7fc6fcdd12c91e0cd4e49e4b1287e69dc4
Reviewed-on: https://gerrit.mot.com/1760981
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Reviewed-by: Jun Weng <wengjun1@motorola.com>
Reviewed-by: Jichao Zou <zoujc@motorola.com>
Submit-Approved: Jira Key
Tested-by: Jira Key
Because the input_get_new_minor function is not in the whitelist, and
Google thinks that a normal input driver should not use those functions,
so use the alloc_chrdev_region function to obtain the device number,
which is used to create node under the path /sys/class/touchscreen/.
Change-Id: Iedd2abdc6b772b62ea95c1edcd9eabc4b1256eec
Reviewed-on: https://gerrit.mot.com/1758757
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Jichao Zou <zoujc@motorola.com>
Reviewed-by: Konstantin Makariev <kmakariev@motorola.com>
Submit-Approved: Jira Key
the battery charge is considered complete when the charge current
reaches the iterm value, but before that it should be charged in
taper-charger until current actually reaches iterm.
However, https://gerrit.mot.com/#/c/1731691/ from smith changed
mmi_has_current_tapered() which use to confirm whether to reach iterm
that cause the battery charging was cut-off immediately after the SOC
was reporting 100%
Change-Id: I3f2b8134624ceca471c4cd5eecfd817002c4e865
Signed-off-by: xuwt2 <xuwt2@lenovo.com>
Reviewed-on: https://gerrit.mot.com/1761003
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Lu Chai <chailu1@motorola.com>
Reviewed-by: Haijian Ma <mahj8@motorola.com>
Reviewed-by: Jianqi Yang <yangj@motorola.com>
Submit-Approved: Jira Key
Add a flush function that returns success. This is
needed to pass VTS testing.
Change-Id: I0550eb39694b4bf33ed7ba872107a135edf27a71
Reviewed-on: https://gerrit.mot.com/1759290
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Konstantin Makariev <kmakariev@motorola.com>
Submit-Approved: Jira Key
WHY: Chipone fps driver should be working on different Android version
WHAT:Add compability support in chipone driver
Change-Id: Ic3d3cf0fafd11b5dbd600170ca0044bc4c70b3a9
Reviewed-on: https://gerrit.mot.com/1758615
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: liujian <liujian24@lenovo.com>
Reviewed-by: Xiangpo Zhao <zhaoxp3@motorola.com>
Submit-Approved: Jira Key
WHY: Need support chipone fps on capri/caprip
WHAT:Add necessary for driver based on Android R
Change-Id: Ib826c6bfd1d3a328b6d56a175e46e18a98076d6e
Reviewed-on: https://gerrit.mot.com/1757677
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Xiangpo Zhao <zhaoxp3@motorola.com>
Submit-Approved: Jira Key
orderly_poweroff is a function from kernel/reboot.c that does not work since
poweroff binary was removed from /sbin/.
Factory Kill still worked because qcom smb5 power supply driver disables
motorola factory kill and implements its own (with kernel_power_off). Since
they removed their own implementation it falls back to the broken one.
This commit replace orderly_poweroff by kernel_power_off the same way qcom
used to do.
Change-Id: Iee78e729add3e31b29c192adc7bcfbab46b1462e
Reviewed-on: https://gerrit.mot.com/1753065
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Wentao Xu <xuwt2@motorola.com>
Reviewed-by: Zhenxin Xi <xizx@motorola.com>
Submit-Approved: Jira Key
On Smith, charging current is positive and discharging current is
negative. The flipped sign would always report discharging, so the
current would always report as tapered.
Change-Id: Ia2b93a1e943d20a52956e6068acae879d1934a8d
Reviewed-on: https://gerrit.mot.com/1731691
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Ling Jin <lingjin@motorola.com>
Submit-Approved: Jira Key
Reviewed-by: Bernie Moreno <berniem@motorola.com>
v5 increases the taper rate of flip battery to 140mA and decreases that
of the main battery to 80mA. This will allow for reaching 100% around 20
minutes earlier than the charger stops.
Change-Id: Ia2f6a9997c41e1a1dca1c755982125b3635c4096
Reviewed-on: https://gerrit.mot.com/1731692
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Bernie Moreno <berniem@motorola.com>
Reviewed-by: Ling Jin <lingjin@motorola.com>
Submit-Approved: Jira Key
The driver currently only prints the first 8 Ra tables, this will allow
for printing all 15.
Change-Id: I3524dd73789d8fba274e6e96f1254bf400189335
Reviewed-on: https://gerrit.mot.com/1750383
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Bernie Moreno <berniem@motorola.com>
Reviewed-by: Ling Jin <lingjin@motorola.com>
Submit-Approved: Jira Key
kallsyms_lookup_name is not exported in kernel 5.4 and the driver should
work for qcom , samsung and MTK, so use a specially way to distinguish it.
Change-Id: Ic9d89a1af48b4e03481f2aaf38f3bf5dbdafc2cd
Reviewed-on: https://gerrit.mot.com/1689258
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Ryan Lattrel <ryanl@motorola.com>
Reviewed-by: Guobin Zhang <zhanggb@motorola.com>
Submit-Approved: Jira Key
When importing the Modules.symvers in fix path, the GKI module will import an
incorrect one and cause module load fail in boot-gki kernel mode.
Change-Id: Ie17e494821dafcc1fad147202dae445b9250875b
Reviewed-on: https://gerrit.mot.com/1743517
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Jichao Zou <zoujc@motorola.com>
Submit-Approved: Jira Key
Adding the battery number in log messages allows for determining which
charger produced the log output.
Change-Id: Ie3394185626fdc2181e2c2e3d734fd6c1725ce30
Reviewed-on: https://gerrit.mot.com/1731690
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Ling Jin <lingjin@motorola.com>
Submit-Approved: Jira Key
Values were not being set properly after initializatoin, this change
will update them for proper logging
Change-Id: I09675258e2c7acf6d5724a5211dc0d593d27ef53
Reviewed-on: https://gerrit.mot.com/1731689
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Ling Jin <lingjin@motorola.com>
Submit-Approved: Jira Key
kernel_read and kernel_write are exported with specific ANDROID_GKI_VFS_EXPORT_ONLY
namespace, so the DLKM should import the namespace.
error log:
[ 35.634756] sec_mmi: module uses symbol (kernel_read) from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it.
[ 35.648698] sec_mmi: Unknown symbol kernel_read (err -22)
Change-Id: Ic333a4c66115c15aa0994c1d2210eea62db88d32
Reviewed-on: https://gerrit.mot.com/1749485
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Jichao Zou <zoujc@motorola.com>
Reviewed-by: Jianqi Yang <yangj@motorola.com>
Submit-Approved: Jira Key
kernel_read and kernel_write are exported with specific ANDROID_GKI_VFS_EXPORT_ONLY
namespace, so the DLKM should import the namespace.
error log:
[ 12.547678] utags: module uses symbol (kernel_read) from namespace VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver, but does not import it.
[ 12.561432] utags: Unknown symbol kernel_read (err -22)
Change-Id: I14607da4198c41ddb989d63cc02e560ffc50be11
Reviewed-on: https://gerrit.mot.com/1749451
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Guobin Zhang <zhanggb@motorola.com>
Submit-Approved: Jira Key
There was a build error due to wake API changes, so we took the
oportunity to refactor it to use the new API from linux/mmi_wake_lock.h
Change-Id: I19854604e339d1e986f434be4afd78fac584adda
Signed-off-by: Eduardo Ferreira <edufb@motorola.com>
Reviewed-on: https://gerrit.mot.com/1737197
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Ling Jin <lingjin@motorola.com>
Submit-Approved: Jira Key
Driver was not resuming from suspend as it was using a panel event
that is not reliable. Use PANEL_EVENT_DISPLAY_ON instead.
NO_PROP_NEEDED: <only applies to bo>
Change-Id: I435686b53453e18fbcfd864ab355c8817779f27a
Reviewed-on: https://gerrit.mot.com/1737310
SME-Granted: SME Approvals Granted
SLTApproved: Slta Waiver
Tested-by: Jira Key
Reviewed-by: Eduardo Ferreira Barbosa <edufb@motorola.com>
Reviewed-by: Ling Jin <lingjin@motorola.com>
Submit-Approved: Jira Key
Cherry-picked from: (CR)
Updated mcp.c, mcp.h and platform.h to make driver
compatible to kernel 4.19.
Add the Trustonic TEE driver module to the kernel. This is needed
to run trusted applications in the Trustonic TEE.
Updated Kbuild with current files.
Kinibi version t-base-QC8996-Android-410a-V106.
Change-Id: Id237e0acb2b0e6fe37045796106e3d1e5cb4b1b0
Reviewed-on: https://gerrit.mot.com/1685214
SLTApproved: Slta Waiver
SME-Granted: SME Approvals Granted
Tested-by: Jira Key
Reviewed-by: Joel Voss <jvoss@motorola.com>
Reviewed-by: Konstantin Makariev <kmakariev@motorola.com>
Reviewed-by: Igor Kovalenko <igork@motorola.com>
Submit-Approved: Jira Key
