Do initial CPU reservation before starting VM, to
avoid any resource contention, while booting guest
VM. Remove the reservation after a configured timeout,
which defaults to 8 seconds.
Change-Id: Id49b07edd3e558dee074eafb729423ad8f8ff98d
Signed-off-by: Murali Nalajala <mnalajal@codeaurora.org>
Use a6x crashdumper register memory end location to know
the crashdumper status completion. This will avoid AHB
traffic while crashdumper was active in snapshot dumping
and fixes the slave timeout issue.
Change-Id: Ic24e75557297c6a1a3f2ad7893f4d8d308f9943c
Signed-off-by: Hareesh Gundu <hareeshg@codeaurora.org>
Enable LPM and SoC sleep stats drivers for gen3auto.
Change-Id: I7dd08d1044054d5b330d149aa1f26f13d9d7b9bf
Signed-off-by: Maulik Shah <mkshah@codeaurora.org>
When stop command comes during FIFO refill, it would free custom_effect
FIFO sample memory and set the pointer to NULL, and this would cause
the NULL pointer dereference during FIFO refill. To fix this, add a
mutex lock between FIFO stop and FIFO refill sequence to avoid a race.
Change-Id: I8792c2183f06e84fca3a7c4dddfed667b25f2528
Signed-off-by: Fenglin Wu <fenglinw@codeaurora.org>
This is to help the hardware configured in world
roaming mode to save power when not connected to
any AP.
CRs-Fixed: 542802
Change-Id: Ia643d0e9848dcd486832973bd6dd186edd7bd4ea
Signed-off-by: Mihir Shete <smihir@codeaurora.org>
Signed-off-by: Will Huang <wilhuang@codeaurora.org>
QUP common registers should not be accessed from SVM as that
memory is assigned to PVM. So, bypass the reading of hw version
registers and rely on PVM for the specific HW initialization done
based on different hw versions.
Change-Id: I1f18c80aaf143daf4da1402aa617d3b8f52f9b95
Signed-off-by: Vipin Deep Kaur <vkaur@codeaurora.org>
Add the PMIC clocks required to be requested from clients via RPMH clock
driver.
Change-Id: I75b02fd3283ea0c459c6e28f06cfb45f04ece214
Signed-off-by: Taniya Das <tdas@codeaurora.org>
With GPIO, UART and others, allow specifying the device index via the
aliases node in the device tree.
On embedded devices, there is often a combination of removable (e.g.
SD card) and non-removable MMC devices (e.g. eMMC).
Therefore the index might change depending on
* host of removable device
* removable card present or not
This makes it difficult to hardcode the root device, if it is on the
non-removable device. E.g. if SD card is present eMMC will be mmcblk1,
if SD card is not present at boot, eMMC will be mmcblk0.
Alternative solutions like PARTUUIDs do not cover the case where multiple
mmcblk devices contain the same image. This is a common issue on devices
that can boot both from eMMC (for regular boot) and SD cards (as a
temporary boot medium for development). When a firmware image is
installed to eMMC after a test boot via SD card, there will be no
reliable way to refer to a specific device using (PART)UUIDs oder
LABELs.
The demand for this feature has led to multiple attempts to implement
it, dating back at least to 2012 (see
https://www.spinics.net/lists/linux-mmc/msg26586.html for a previous
discussion from 2014).
All indices defined in the aliases node will be reserved for use by the
respective MMC device, moving the indices of devices that don't have an
alias up into the non-reserved range. If the aliases node is not found,
the driver will act as before.
This is a rebased and cleaned up version of
https://www.spinics.net/lists/linux-mmc/msg26588.html .
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
Git-commit: fa2d0aa96941e8dc347e49a04c75468e3002ee20_
Change-Id: I88c11705c8b66022e67b38a64bbc91625357a4bc
Based-on-patch-by: Sascha Hauer <s.hauer@pengutronix.de>
Link: https://lkml.org/lkml/2020/8/5/194
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Signed-off-by: Ram Prakash Gupta <rampraka@codeaurora.org>
