Dump sync logs only when a fence is not signalled
for SYNC_DUMP_TIME_LIMIT or more. This is necessary
to reduce CPU hogging because of excessive sync logs
dumped due to fence timeouts which are less than
SYNC_DUMP_TIME_LIMIT and are harmless.
Change-Id: Id21a02925dd45a01361d096048a25d1879ebde9e
Signed-off-by: Deepak Kumar <dkumar@codeaurora.org>
Set the size of bitmap area properly to ensure the proper iova address
to be returned by the bitmap_() API's through alloc_iova(). The current
implementation causes the bitmap index search out of bounds of a page
which can lead to the randomn corruption issues.
Change-Id: Ie57ca0b7465c91d318145ed270b7d47d822c8eeb
Fixes:I88ddd98a76b ("arm/arm64: dma-mapping: Fix iova region size")
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
With fast mapping, the iova range is zero in the absence of
mapping object from the client. In such case, set the iova
space using the DOMAIN_ATTR_GEOMETRY dommain attribute.
CRs-Fixed: 2020868
Change-Id: I28790728c02ecb2d0a921bf5a218fb8b16662619
Signed-off-by: Sudarshan Rajagopalan <sudaraja@codeaurora.org>
This separates the kref for ion handles into two components.
Userspace requests through the ioctl will hold at most one
reference to the internally used kref. All additional requests
will increment a separate counter, and the original reference is
only put once that counter hits 0. This protects the kernel from
a poorly behaving userspace.
Bug: 34276203
Change-Id: Ibc36bc4405788ed0fea7337b541cad3be2b934c0
Signed-off-by: Daniel Rosenberg <drosen@google.com>
Git-repo: https://android.googlesource.com/kernel/msm/
Git-commit: 20abfcc16884a5af973a5e91dd013ddd789c44f4
[d-cagle@codeaurora.org: Resolve style issues]
Signed-off-by: Dennis Cagle <d-cagle@codeaurora.org>
Commit <be0960374> ("scsi: ufs: scale up the gear in 2 steps") introduced
a bug where we would not scale up the gear to HS-G3 if
UFS_DEVICE_QUIRK_HS_G1_TO_HS_G3_SWITCH quirk isn't enabled for UFS device.
Fix this by allowing HS-G3 scaling irrespective of quirk state.
Change-Id: Id6a958fb2908ae773283bcdd3dc871292e56f4ce
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
This patch segregates different PD data onto separate buffers
and then onto its own data stream.
CRs-Fixed: 2019189
Change-Id: I09c4e1a7da0ccd3ba3e025e9f13da0fbcb95f103
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
This snapshot is taken as of
msm-3.18 'commit 7e1165aac628 ("Merge drivers: iio: bmi160:
Enabled the buffering support for BMI160 Sensor")'
CRs-Fixed: 2035593
Change-Id: I2951e77f226062d82e84a26fce6ab932b9685223
Signed-off-by: Dhoat Harpal <hdhoat@codeaurora.org>
For some use cases, mdp clock source needs to be parked at a safe
frequency when it is disabled and force enabled in order to execute
a safe dynamic switch. Add support for the same by adding
non_local_children flag.
Change-Id: Idcbaef90fdfcb80e93b00c61a91e5eadaabfbf56
Signed-off-by: Amit Nischal <anischal@codeaurora.org>
When SMMU stage1 is enabled, set IOVA base and end in geometry
attr to allow PCIe driver to map the GIC MSI address.
Change-Id: I7826a941823a6204143ea077a45c71b22316699b
Signed-off-by: Maya Erez <merez@codeaurora.org>
Minidump only collect parts of memory which are registered
to its table. So add lpm_debug buffer to Minidump table.
Change-Id: I8635542411a560a88530ffbbfe033cd48d3507dc
Signed-off-by: Lingutla Chandrasekhar <clingutla@codeaurora.org>
Add Minidump support for clients to get minimum required data
at the time of system crash. The Minidump table resides in SMEM,
BOOT(SBL) will iterate the table entries and dumps out (to USB/Flash)
the data in address location.
Any client can register to this table with static or known addresses,
as currently Minidump doesn't support dumping of dynamic data structures.
To simplify post processing, we create an ELF header, where each entry in
the minidump table is a section in elf header.
If Memory dump table enabled, Dump all data entries registered with MDT.
Enable Minidump:
echo mini > /sys/kernel/dload/dload_mode
Change-Id: I0fc8d21aef71ded34a498426ee3d7f86b063a639
Signed-off-by: Lingutla Chandrasekhar <clingutla@codeaurora.org>
For branch clocks having aggr_sibling_rates flag as set, get_rate()
always returns the parents rate despite the branch clocks prepare
status. Fix the same by adding a check for branch prepare status
and aggr_sibling_rates flag value.
Change-Id: If0ba62e178f14bc5fd8ec6007a67538a9b97285b
Signed-off-by: Amit Nischal <anischal@codeaurora.org>
