Enable basic modules on virtual platform for driver pass through,
including pinctrl, gpio, clock, regulator, i2c, spi etc.
Change-Id: I3d4917e754277e0c55c55154a2ddb2f967199b48
Signed-off-by: Zhiqiang Tu <ztu@codeaurora.org>
Move code into appropriate #ifdef, and add an "inline" so the compiler no
longer gives a defined-but-not-used warning.
CRs-Fixed: 2066432
Change-Id: I226242bf994e659d8018a885f20c3a3f80b9b8e5
Signed-off-by: Patrick Daly <pdaly@codeaurora.org>
Signed-off-by: Zhiqiang Tu <ztu@codeaurora.org>
Signed-off-by: Atul Raut <araut@codeaurora.org>
Add dummy clock and regulator stub for virutual platform to
bypass clock and regulator operations.
Change-Id: Ic2c15e4b939adc0ea492422c93e3f3eac2d01054
Signed-off-by: Ramachandran Venkataramani <ramavenk@codeaurora.org>
Signed-off-by: Zhiqiang Tu <ztu@codeaurora.org>
Back when this was first written, dma_supported() was somewhat of a
murky mess, with subtly different interpretations being relied upon in
various places. The "does device X support DMA to address range Y?"
uses assuming Y to be physical addresses, which motivated the current
iommu_dma_supported() implementation and are alluded to in the comment
therein, have since been cleaned up, leaving only the far less ambiguous
"can device X drive address bits Y" usage internal to DMA API mask
setting. As such, there is no reason to keep a slightly misleading
callback which does nothing but duplicate the current default behaviour;
we already constrain IOVA allocations to the iommu_domain aperture where
necessary, so let's leave DMA mask business to architecture-specific
code where it belongs.
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Git-commit: a1831bb9403720db6d4c033fe2d6bd0116dd28fe
Git-repo//git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
CRs-Fixed: 2040683
Change-Id: I67431608ce196bf5ca981fb9aea2afce826094f0
Signed-off-by: Atul Raut <araut@codeaurora.org>
Host wlan driver needs to know if the drive has been
reloaded and wiphy re-registered with the kernel.
Therefore add APIs to retrieve this information.
CRs-Fixed: 2058292
Change-Id: Ia323e31e9b6779e2f5279f42b6e1860a9259a189
Signed-off-by: Amar Singhal <asinghal@codeaurora.org>
This change adds the secure context bank child node in mdss
driver, this is required for having both the secure and non-secure
smmu context bank support in the driver. This change also renames
the child nodes to avoid compilation issues on the builds where
fb driver mdss device file is also present. As a part of this
change the smmu driver registration is called as a part of
msm driver probe.
CRs-Fixed: 2053654
Change-Id: I90cd31fd792b0fd9772689dc6561bb0b429e1e3a
Signed-off-by: Abhijit Kulkarni <kabhijit@codeaurora.org>
Enable CFG80211_INTERNAL_REGDB to support WiFi 5G channels.
Change-Id: I7d53d2a09c30173d121368ec2e3584217ddc5093
Signed-off-by: Zhaoyang Liu <zhaoyang@codeaurora.org>
When using QGIC MSI, the MSI controller is GIC not PCIe host
driver. Only set irq chip data if PCIe host is the MSI
controller.
Change-Id: I0ba9e78127424ab3da4b1f46b3ed3fa5d65d05f6
Signed-off-by: Tony Truong <truong@codeaurora.org>
Enable secondary USB port for HDK660 platform which use
host only mode.
Remove TCSR_QUSB2_PHY_CLAMP_DIG_N_1P8 resource entry for SDM660
which is not required to set now during disconnect as writing to this
register causes USB3.0 port and USB2.0 ports working independently.
Change-Id: I936a4012c30e0cd84144b12e34fb780cada541ae
Signed-off-by: Liangliang Lu <luliang@codeaurora.org>
Mhi node needs additional information for driver
probe to get success. This generic node is not
required and hence disable unwanted dtsi node for
msm8996.
Change-Id: I4dffd3d668ac065fc800e5e7d3b52fdf2733e03f
Signed-off-by: Rama Krishna Phani A <rphani@codeaurora.org>
Add 500ms before MDM enumeration, this delay is needed for
link establishment between switch and MDM.
Change-Id: I32c4a4f9ef68b7672465ced0401fbf6dc0db0002
Signed-off-by: Rama Krishna Phani A <rphani@codeaurora.org>
This reverts commit 45380e2241 ("msm: sde: add early
display handoff feature"). To avoid conflict when
syncing up with mainline, we revert this change.
Change-Id: I9652cd367d242c6f61ed0da3a36c55493cc7d34c
Signed-off-by: Zhiqiang Tu <ztu@codeaurora.org>
select_best_cpu() has previous CPU's cluster bias which overrides
the best_cpu with best_sibling_cpu when the power cost is same.
When the power table is configured incorrectly or static_cpu_pwr_cost/
static_cluster_pwr_cost tunables are set to a large value, the
power_cost() for all candidate CPUs can return INT_MAX. So the
stats.min_cost is never changed from it's initial value i.e INT_MAX.
In the above scenario, we find stats.best_cpu >= 0 && stats.min_cost =
stats.best_sibling_cpu_cost = INT_MAX && stats.best_sibling_cpu_cost = -1
and replace best_cpu with best_sibling_cpu i.e -1.
Change-Id: I09829e278e41daaaff959428ff50927aba29104c
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Re-phrase PD notification registration debug message and
change state name of SSR/PDR to avoid confusion.
CRs-Fixed: 2057789
Change-Id: I5b800982c0d8c4d5ba627e28f3c9fa8eab7ca074
Signed-off-by: Yuanyuan Liu <yuanliu@codeaurora.org>
Currently platform device is not enabled as a wakeup source, so
notifying the PM core for a wakeup event action will be no-op.
Hence enable it during driver probe.
CRs-Fixed: 2058010
Change-Id: Iefe5bcd4b498a9f02fca001ebcf8ad484f443217
Signed-off-by: Yuanyuan Liu <yuanliu@codeaurora.org>
