Current default governor is schedutil, make performance default instead.
Change-Id: I4c889d49187df12985e1f367e4330c2070d7cb74
Signed-off-by: Shaleen Agrawal <shalagra@codeaurora.org>
Remove use of hw init as it is set to NULL
during clk register.
Change-Id: I98bf43b7aac11691a71a54a6bacefa25d92c3b76
Signed-off-by: Vivek Aknurwar <viveka@codeaurora.org>
Add debug cc measure nodes for Lahaina to support
debugfs clk measure.
Change-Id: Id7fc4d63fdf4ed32b63bdb5b410649f1779ad290
Signed-off-by: Vivek Aknurwar <viveka@codeaurora.org>
lahaina_QGKI.config takes care of enabling CONFIG_SPS and CONFIG_USB_BAM
in lahaina_debug.config. CONFIG_USB_BAM depends on CONFIG_SPS. Currently
CONFIG_SPS is enabled in both lahaina_debug.config and lahaina_QGKI.config
whereas CONFIG_USB_BAM is enabled only in lahaina_QGKI.config and also
explicitly marked as "not set" in lahaina_debug.config. This conflict
between the fragments results into CONFIG_USB_BAM remaining disabled in
the combined lahaina-qgki-debug_defconfig. Clean this up by removing
their redundant entries from lahaina_debug.config so that both CONFIG_SPS
and CONFIG_USB_BAM are only enabled in the lahaina_QKI.config fragment.
Change-Id: I5dba04e64a04bc16aa6603ca617681decaf19c36
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
Change adds compat ioctl to listen driver for supporting 32 bit userspace
client when kernel is compiled for 64 bit.
Change-Id: Ie6a6fb1f2b6ea569e03b02bc520ef79b95c1009c
Signed-off-by: Gopikrishnaiah Anandan <agopik@codeaurora.org>
Signed-off-by: Banajit Goswami <bgoswami@codeaurora.org>
Signed-off-by: Meng Wang <mwang@codeaurora.org>
ECM_CONNECT/ECM_DISCONNECT name looks specific to ECM offload
scenarios. As IPA supports other peripherals like ETH/AQC/RNDIS
use a more generic name.
Change-Id: I09bb640734f2ea0bf2d47ed95d03290db50b5770
Signed-off-by: Chaitanya Pratapa <cpratapa@codeaurora.org>
This fix stops the remote IPA MHIP channels from probe if tethering is
not enabled, before unvoting host IPA clocks.
Change-Id: Iae12f13a3297e2ed7898e7c3a5e0b39ab6793e55
Acked-by: Jyothi Jayanthi <jyothij@qti.qualcomm.com>
Signed-off-by: Michael Adisumarta <madisuma@codeaurora.org>
Firmware version check is not needed in Lahaina. Remove it and
deprecated functions.
Change-Id: I4d3f8eaad1b4d49f762f534b8a7f76ddc32fa230
Signed-off-by: Ruofei Ma <ruofeim@codeaurora.org>
SCM driver has changed its interfaces. This requires corresponding
change in qseecom driver.
Change-Id: I9e55ed1bbbe04d25679f2e90d80e5913581887de
Signed-off-by: Dinesh K Garg <dineshg@codeaurora.org>
Address an unlikely null pointer dereference.
Fixes commit 7b5df13bc4b3 ("mm: swap: free up swap on mm reap").
The expected usage of free_swap_slot is that the caller has already
checked that the swap_entry_t is valid.
Change-Id: I85331f817458df7f6cb0c0b387ca34c345f8c513
Signed-off-by: Patrick Daly <pdaly@codeaurora.org>
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
The avc allocations are marked with GFP_NOWAIT and thus
considered to be non-fatal allocations. This also makes
these allocations easy to fail thus filling the log buffer
with page allocation failure messages. There are no known
cases of these messages being of any importance for
debugging. Disable them.
Change-Id: I3517a134ad0e8deb307f0d140f4b16cb303a9f7f
Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
When a buffer is added to the LRU list, a reference is taken which is
not dropped until the buffer is evicted from the LRU list. This is the
correct behavior, however this LRU reference will prevent the buffer
from being dropped. This means that the buffer can't actually be dropped
until it is selected for eviction. There's no bound on the time spent
on the LRU list, which means that the buffer may be undroppable for
very long periods of time. Given that migration involves dropping
buffers, the associated page is now unmigratible for long periods of
time as well. CMA relies on being able to migrate a specific range
of pages, so these these types of failures make CMA significantly
less reliable, especially under high filesystem usage.
Rather than waiting for the LRU algorithm to eventually kick out
the buffer, explicitly remove the buffer from the LRU list when trying
to drop it. There is still the possibility that the buffer
could be added back on the list, but that indicates the buffer is
still in use and would probably have other 'in use' indicates to
prevent dropping.
Change-Id: I253f4ee2069e190c1115afc421dadd27a7fa87dc
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
