Use Vmax from play effect in haptics_set_gain() only if the effect
is valid. Otherwise, use Vmax from the haptics configuration instead.
Change-Id: I7ec0f8c869096bccb26f7fda0057e3db3a51225d
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
ignore lahaina-qgki-consolidate_defconfig file generated
by GKI scripts as this file auto-generated at build time.
Change-Id: I3edbbbf90b581642da81993a49fdc5264a4324a3
Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
consolidate fragment contains the all the debug features
on top of qgki fragment for regular debugging and debug
fragment contains memory debug features. Add support for
fragement merging support in the both generate_defconfig.sh
and fragement_menuconfig.sh scripts.
Change-Id: Iea90997eca060fdf86cd9da08106e7cf11460b21
Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Add initial consolidate defconfig fragment for the lahaina SoC.
Consolidate fragement contains all debug features needed on
top of lahaina_QGKI.config fragement and these flags should not
show significant performance impact. lahaina_debug.config fragment
contains memory debug features, which shows the performance
impact. This enables intenal testing to use the images based on
lahaina-qgki-consoldiate_defconfig defconfig instead of
lahaina-qgki_defconfig defconfig.
Change-Id: I3982e84dbe77abaf3afd741426f6f74ab2db1544
Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
Add support to assign static GPII0 for I2C LA Touch usecase on Lahaina.
Change-Id: Ib0ea811626796825e280bf77f04ef68ab5f833a8
Signed-off-by: Vipin Deep Kaur <vkaur@codeaurora.org>
Certain configs that are enabled in genericarmv8-64 are not
required for the usecases that the kernel is supposed to cater.
For example, IOMMU support is not required for genericarmv8-64,
yet, the drivers for it are built into the kernel image. This
leads to a bloated kernel image with a larger memory footprint,
as well as larger runtime memory footprint, as certain drivers
may allocate data structures that go by unused. Remove certain
extraneous configs.
Change-Id: Iefe8dd2a35a4a29ed97338ec5fea5c147da14eda
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Ftracing has been seen to take up a lot of memory (~16 MB).
On certain environments where the amount of memory is scarce,
this is not ideal as it can contribute to memory pressure,
so disable it for genericarmv8-64 for the time being.
Change-Id: I9a8cc66e70caadc53a5cf63a39842c9548fddf25
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Discard size calculation uses max_busy_timeout in deriving the
value. So, we can ensure a larger discard size by setting this
timeout as zero. If this timeout is zero then it takes max erase
timeout vlaue (which is 60sec) in the discard size calculation.
And qcom SDHC can support h/w based busy detection, So
we need set MMC_CAP_NEED_RSP_BUSY capability flag.
Since Qcom SDHC can support h/w based busy detection for R1b
commands, this timeout value is not relevant for us.
Setting it zero won't affect in any operation provied
MMC_CAP_NEED_RSP_BUSY cap is set.
Change-Id: Ib20a1e536d2e24cf8de1e927715a8a3aa7f0ae27
Signed-off-by: Veerabhadrarao Badiganti <vbadigan@codeaurora.org>
This change is for general scheduler improvements.
Change-Id: I511e49ea6c207378c66a580e29e89f28aaa9f7f3
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
There may be race condition between firmware assert and runtime PM
suspend. Hence make sure PCIe/MHI is up before collecting RAM dump.
Change-Id: I9a76bf96c4a72045d31449ed9f760e498ae78789
Signed-off-by: Yue Ma <yuem@codeaurora.org>
This change is for general scheduler improvements.
Change-Id: Iaefb893a84055748be7f2108179e3b869ac00318
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
