4K panel uses split control path setup, so there is no need to correct
the panel width when updating the mixer width resolution during
destination scalar disabling.
CRs-Fixed: 1093549
Change-Id: I064987534124e025abaccec05ab70acf93538bce
Signed-off-by: Benjamin Chan <bkchan@codeaurora.org>
scm_call2 is printing the input arguments if TZ ret value is < 0
leading to information leak. Remove printing input arguments.
Change-Id: I21dd6d83fa979aed2c79ebb2c9c8de63a247dded
CRs-Fixed: 1076407
Signed-off-by: Swetha Chikkaboraiah <schikk@codeaurora.org>
Signed-off-by: Paresh Purabhiya <ppurab@codeaurora.org>
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
In existing HDMI PLL driver the VCO frequency value is truncated
so following PLL calculation could be impacted. Use 64 bit value
instead to maintain the necessary precision.
CRs-Fixed: 1086894
Change-Id: Iec3f65942dd152b0b7aa32af1a90039fff06cb34
Signed-off-by: Ray Zhang <rayz@codeaurora.org>
Clients of VADC_HC and BTM include reading voltage phone
power, system thermistors for thermal mitigation such as
msm_therm, case_therm, XO therm. Add the supported VADC
and BTM channels for the msm8998-qrd-vr1 platforms.
CRs-Fixed: 1090542
Change-Id: I4cda24b1be20310f54ceba1297f424ede1c5d889
Signed-off-by: King Li <kjli@codeaurora.org>
Clients of VADC_HC and BTM include reading voltage phone
power, system thermistors for thermal mitigation such as
msm_therm, case_therm, XO therm. Add the supported VADC
and BTM channels for the msm8998-qrd-skuk platforms.
CRs-Fixed: 1090579
Signed-off-by: King Li <kjli@codeaurora.org>
Change-Id: I7b7c0ec59e9a3ce8a3526bdc8eb7359a0c98ccd7
Clock recovery and dynamic resolution change require changing
HDMI clock rate while HDMI PLL is on. There are two paths while
clock is changed, one is atomic update which doesn't require
PLL tear down, the other is when clock rate change is too big
and a full PLL tear down is needed.
CRs-Fixed: 1086894
Change-Id: Ia202e0aee09f506a7bbe4e13702f30dee119ce8e
Signed-off-by: Ray Zhang <rayz@codeaurora.org>
Addition of Ngid breaks some third party applications, which
are dependent on a particular order of fields. This change
moves the field to the end, to fix this issue.
Change-Id: Ifdc781aca49dcb535d5fa5005b85dc87604560dc
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
If ERRATIC event irq is triggered by USB controller, it requires to perform
block reset USB controller as recovery mechanism as per SNPS data book.
Error recovery happens through allowing USB entering low power mode and
exit low power mode. We might see recovery failing as check for P3 state is
true as part of suspend and results in USB not entering low power mode.
Fix this issue by allowing USB enter low power mode in case of recovery
flag mdwc->in_restart set.
CRs-Fixed: 1060831
Change-Id: I41f935da3d4af1dd04eb4b3299e36a0f528633da
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Commit 18cd808986ba101d ("usb: dwc3-msm: Make power collapse
and power-on-reset mandatory") removed the device tree properties
for power-collapse due to which the dwc3_restart_usb_work() which
was supposed to do a full POR sequence by simulating a cable
disconnection-reconnection sequence now only does a dbm reset.
Fix this, so that dwc3_restart_usb_work(), does a full POR.
CRs-Fixed: 975249
Change-Id: Iaabe9283ec80954a2e504a55f2b4cdf93ca8ae46
Signed-off-by: Azhar Shaikh <azhars@codeaurora.org>
Currenlty driver is clearing mdwc->inrestart flag only if vbus_active
is high only after making sure USB entered low power mode. There is a
chance cable is disconnected during execution of restart work and endup
not clearing mdwc->in_restart flag if disconnect happens. Hence fix this
by clearing mdwc->in_restart flag always irrespective of vbus_active set
or cleared.
Change-Id: I15fa1893c798946c7514bf8cb23773b5784e671e
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
If the qos value is increased only for a subset of cpu's
aggregated qos for those cpu's is still the previous value.
This is because the qos request list is maintained per
request and not per cpu. In this case as there is no change
in aggregated qos value, these cpu's are not wokenup to
take the new qos value into effect.
So wakeup cpu's even if the aggregated qos value does not change
but the cpumask changes.
Change-Id: If5a4a100108e85e04beb77e5249bd6c452672edf
Signed-off-by: Anil Kumar Mamidala <amami@codeaurora.org>
Add required changes for LDOs for msm8998-interposer-msmfalcon
for USB functionality to be working.
Change-Id: I121651a49ef27ba02f1960ed5c95baf93b00d1f5
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Add required USBPD PHY device node for msmfalcon for USB PD
functionality to be working.
Change-Id: I8cd2981f176e08c1ea4f8a9b7ff42887b590d941
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Core-ctl module by default, manages cpus instead of msm_performance
module. Set this config to allow msm_performance manage(hot-plug) cores
in the absence of core-ctl.
Change-Id: I02a1007edfc63ad2c2dd99616cb1a64432b08d13
Signed-off-by: Dilip Gudlur <dgudlur@codeaurora.org>
In common clock framework, API for registering clk
provider for a node is changed to of_clk_add_provider.
Add new audio ext clock file to use new API to register
audio clk provider.
Crs-Fixed: 1090500
Change-Id: I1d7ecc6a3d4c48d0de9645043d5e5bfdfa1d1f5f
Signed-off-by: Meng Wang <mwang@codeaurora.org>
Prepare driver for FTM/AOA while unassociated.
1. Added attributes allowing user space to specify the frequency
where FTM/AOA peer is listening. When specified it will override
the entry in the kernel scan results cache. If not specified,
the kernel scan results cache will be used like today.
This gives user space location framework more flexibility - it
can maintain its own cache of peers, or perform scans less
often (since entries in the kernel scan results cache expire
quickly)
2. Remove associated check when starting FTM session, so session
can start even when unassociated.
Change-Id: Ib0ba52c506e1d8d59ab8c12043acd792405d69a0
CRs-Fixed: 1094147
Signed-off-by: Lior David <liord@codeaurora.org>
This change adds the UFS_RESET pin ctrl data for UFS controller node.
This will enable UFS driver to issue reset to UFS device.
Change-Id: I61561fb7e395671d2bc52c6a9c0c71e0351114ea
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
Some platforms may have a SOC pin/gpio connected to UFS device's
RST_n to allow the UFS device reset. This change adds support to
trigger device reset on such platforms.
Change-Id: Ie4faa47fb76837dba909f9a3d0dfe11bc69659e1
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
UFS_RESET is a single purpose output only pin which can be used
to send reset to connected UFS device. This change adds the
UFS_RESET pin data.
Change-Id: Iec5e70e3f57a8dd06c0ceda3a6e67e47e043f2d1
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
The phy initialization sequence assumes a POR state but
the bootloaders can leave PHY at an already initialized
state, hence there could potentially be issues with the
initialization from ufs driver. Perform a full reset to
start from a power on reset state. Also a reset is
required by the UFS hardware programming guide.
Change-Id: I0118b0d3013166aeec0bb0bc0ef181e48998e758
Signed-off-by: Venkat Gopalakrishnan <venkatg@codeaurora.org>
