Add minidump entry and dump memory around addresses
contained in registers in panic.
Change-Id: Id4857e3b08838838d8aa3a51cb9d6961be37b579
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
Add minidump collection for cpu runqueues, on panic.
Change-Id: Ib9d313c25cb53547fff075587b3fdd9297a74756
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
Register and dump ftrace buffer on kernel panic, to minidump
table. The dumps are collected in parsed format.
Change-Id: I10605467d2b566425cc2cb4fd67dbc59fcd592e7
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
Both eMMC and UFS share the regulators (vdd & vdd-io).
On UFS based devices this regulator can be turned off after the eMMC
probe fails.
Override vdd-io-always-on flag as false.
Change-Id: I2e2abb14512d5e3f8fc0cb67d1aa734c78674cfa
Signed-off-by: Sarthak Garg <sartgarg@codeaurora.org>
As to set_cs takes effect immediately, power spi
is needed when setup spi.
Bug: 167938264
Cc: Mark Brown <broonie@kernel.org>
Signed-off-by: Luhua Xu <luhua.xu@mediatek.com>
Link: https://lore.kernel.org/r/1572426234-30019-1-git-send-email-luhua.xu@mediatek.com
Signed-off-by: Mark Brown <broonie@kernel.org>
(cherry picked from commit d948e6ca189985495a21cd622c31e30e72b6b688)
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I4ed7f854419901f9537916096b941135796956d1
PIL secures pages are using direct scm call, mark these pages using a magic
flag so that it can be easily identified.
add one check for removing carve out pages, that's already excluded.
Change-Id: If75ab6b4537323e7202c1dd52e2e6677cb61e437
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
The codec interface node is allocated during the codec
addition during dp connect. These changes will free the
node after the dp disconnect.
Change-Id: I6f1fc5639f1a5fa61ef04557b888b3389800dce1
Signed-off-by: Sankeerth Billakanti <sbillaka@codeaurora.org>
Apply the configuration to force HFRC off when WLED module
is disabled.
Change-Id: Iff1df47fd26a620664087eb4c9140cc4e45251bc
Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
The change limits the low_latency flag selection to binder
transactions of the foreground high priority tasks.
Change-Id: Id191e63ba2ccf5537cb45711c20bc22831129a18
Signed-off-by: Kishore Sri venkata Ganesh Bolisetty <bsrivenk@codeaurora.org>
Enable QoS for the master ports on Shima with predefined
values for priority and urgency.
Change-Id: I587306831ef3dea0855230d4316a68060f9f223b
Signed-off-by: Odelu Kukatla <okukatla@codeaurora.org>
Correct scaling function for SMB1398 to ensure
temperature is calculated accurately.
Change-Id: I7ec497ef9d1171da7a08a97730912727c583830a
Signed-off-by: Jishnu Prakash <jprakash@codeaurora.org>
During SPSS firmware update by fota, SPSS SSR causes cryptographic erase
of Secure Processor user data. To mitigate this, instead of related
SSR, platform reboot requested during fota update. In the end of fota
update, SPSS SSR re-enabled.
This change adds ioctl() to update internal driver configuration
(functionally disable or enable SSR).
Change-Id: I1d8362b4691e1a335f7f1f29bc2358d3f9b1cb21
Signed-off-by: Konstantin Dorfman <kdorfman@codeaurora.org>
Signed-off-by: Nurit Lichtenstein <nuritl@codeaurora.org>
commit fce2ff728f95b8894db14f51c9274dc56c37616f upstream.
In nl80211_set_station(), we check NL80211_ATTR_HE_6GHZ_CAPABILITY
and then use NL80211_ATTR_HE_CAPABILITY, which is clearly wrong.
Fix this to use NL80211_ATTR_HE_6GHZ_CAPABILITY as well.
Cc: stable@vger.kernel.org
Fixes: 43e64bf301fd ("cfg80211: handle 6 GHz capability of new station")
Link: https://lore.kernel.org/r/20200805153516.310cef625955.I0abc04dc8abb2c7c005c88ef8fa2d0e3c9fb95c4@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit fce2ff728f95b8894db14f51c9274dc56c37616f)
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Ib3951a485537514e26a9ac70ad9773580ecc4f53
Enable cpufreq hw debug support for HOLI and SHIMA.
Change-Id: I62b3404b918a738addeada83a1069712c55ebc21
Signed-off-by: Jagadeesh Kona <jkona@codeaurora.org>
Certain TEMP_ALARM GEN2 PMIC peripherals need over-temperature
stage 2 automatic PMIC partial shutdown to be enabled in order to
avoid repeated faults in the event of reaching over-temperature
stage 3. Modify the stage 2 shutdown control logic to ensure that
stage 2 shutdown is enabled on all affected PMICs. Read the
digital major and minor revision registers to identify these
PMICs.
Change-Id: Ieefbd4c9478f99d407da5ff12df593d56cbc1092
Signed-off-by: David Collins <collinsd@codeaurora.org>
Now that dma-buf has switched to handling its release from the
file_operations' release function to the dentry_operations' d_release
function there is a potential use-after-free when accessing the
buf_obj->file->f_inode as the path called by __fput eventually calls
__dentry_kill which frees the inode before calling the dentry_operations'
d_release function, so buf_obj->file->f_inode may no longer be valid.
It doesn't look like there is a clean way to check if the inode is valid.
For example using dentry->d_lock to look at the dentry inode would first
involve getting the dentry via a call to file_dentry which potentially
uses buf_obj->file->f_inode and it may no longer be valid.
It looks safer to simply cache the inode number since it is a useful value
to have as it identifies dma-buf objects.
KASAN log gave the following:
KASAN: use-after-free in dma_buf_debug_show+0x190/0x660
E : Read of size 8 at addr ffffff81051d7740 by task cat/19499
I Call trace:
I : dump_backtrace+0x0/0x2c8
I : show_stack+0x20/0x2c
I : dump_stack+0x154/0x1f4
I : print_address_description+0x84/0x580
I : __kasan_report+0x1b8/0x218
I : kasan_report+0x10/0x18
I : __asan_load8+0x90/0x98
I : dma_buf_debug_show+0x190/0x660
I : seq_read+0x2dc/0x830
I : full_proxy_read+0xbc/0x110
I : __vfs_read+0xd8/0x3d0
I : vfs_read+0x158/0x278
I : ksys_read+0x114/0x1e0
I : __arm64_sys_read+0x4c/0x5c
I : el0_svc_common+0x130/0x294
I : el0_svc_handler+0xdc/0xec
I : el0_svc+0x8/0xc
E : Allocated by task 912:
I : __kasan_kmalloc+0xfc/0x1b8
I : kasan_slab_alloc+0x14/0x1c
I : kmem_cache_alloc+0x320/0x3c4
I : new_inode_pseudo+0xbc/0x168
I : alloc_anon_inode+0x28/0x170
I : dma_buf_export+0x1e0/0x3ec
I : ion_dmabuf_alloc+0x168/0x1d4
I : ion_ioctl+0x24c/0x5c8
I : do_vfs_ioctl+0x55c/0xcb4
I : __arm64_sys_ioctl+0xa0/0xe4
I : el0_svc_common+0x130/0x294
I : el0_svc_handler+0xdc/0xec
I : el0_svc+0x8/0xc
E : Freed by task 40:
I : __kasan_slab_free+0x160/0x22c
I : kasan_slab_free+0x10/0x1c
I : slab_free_freelist_hook+0xdc/0x15c
I : kmem_cache_free+0xf8/0x350
I : i_callback+0x48/0x220
I : rcu_do_batch+0x2e8/0x594
I : nocb_cb_wait+0x158/0x930
I : rcu_nocb_cb_kthread+0x20/0x44
I : kthread+0x1ec/0x204
Change-Id: Ic3cfabf3524d2d34fe8b341e84f2ff259e4fad63
Signed-off-by: Liam Mark <lmark@codeaurora.org>
Enabled configurations for pil modem support on sdxlemur.
Change-Id: I517c3f3b81d650338625cc4c48539b67a7e43ac3
Signed-off-by: Melody Olvera <molvera@codeaurora.org>
On some device memory used by msm_qmp, there can be an early ack of a
write to memory succeeding. This may cause the outgoing interrupt to be
triggered before the msgram reflects the write.
Add a readback to ensure the data is flushed to device memory before
triggering the ipc interrupt.
Change-Id: I37618f2921dc34d969a04de80badf1820a188351
Signed-off-by: Chris Lew <clew@codeaurora.org>
In the case where the 'qcom,perf-lock-support' feature is enabled the
memory region bases would be required to be provided from the device
node. Any DCVS request requires the shared memory region to be updated
before the cpufreq-hw perf desired register is updated.
Change-Id: I16d068d3311edf8e32654ab29070d4721a7c1493
Signed-off-by: Taniya Das <tdas@codeaurora.org>
Add support to dump initial dmesg buffer into a
buffer available in minidump and fulldump.
Make logs copying from log_buf at configurable.
This is required to avoid memory sensitive target
from using this.
Change-Id: I7e4d0ddc138ff09c9cbe7679db5e790cdaf1db5c
Signed-off-by: Prateek Sood <prsood@codeaurora.org>
