Enable CONFIG_FREE_PAGES_RDONLY for 32bit sdm660, that
marks freed kernel pages as read-only.
Change-Id: I532dc10fc6aee5200275550eb1df7d1e6cf195e9
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
CONFIG_FREE_PAGES_RDONLY, which marks freed kernel pages
as read-only missed the Kconfig and an interface to mark
pages as read-only for 32 bit system. Add them.
Change-Id: Ibb5020a44323fb50febd66e16ca448da8ecb352c
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
Align arm32 and arm64 sdm660 defconfig with respect to
iommu configs and remove cma size selection as it is to be
moved to device tree.
Change-Id: I5c5f88c05dce9f58d29d56d9cfea2b0d785d665a
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
CTS malloc tests on Android 'N' expects higher entropy in
mmap returned address. Present value of mmap random bits
is not providing enough variations for 32 bit tasks.
Increase mmap_rnd_bits for 32bit and mmap_rnd_compat_bits
for 64bit targets to value of 16.
Change-Id: I1cb88cb1f1fc2a8dc7e27eb54b8c0b2a3eb37843
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
CONFIG_RODATA allows strict kernel mapping permissions to
be followed and accordingly maps regions as read-only,
not-executable etc. correspondingly. CONFIG_RODATA however
assumes all memory regions to be SECTION_SIZE aligned and
section mapped for performance reasons.
With CONFIG_FORCE_PAGES, we force all kernel mappings as
page mapped thus breaking CONFIG_RODATA.
Provide provision to apply permissions at page (pte)
level, if CONFIG_RODATA does not find section mapping.
Change-Id: I8dbf5c3741836bc63a231d8a471cf0306662993b
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
sched_group_upmigrate tunable can accept values greater than
100%. Don't limit it to 100% while doing the auto adjustment.
Change-Id: I3d1c1e84f2f4dec688235feb1536b9261a3e808b
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
If disconnect happens before connect_work start executing, then
there is a chance that connect_work returns with port_usb NULL.
Due to this, port->is_connected will be NULL and disconnect_work
returns with this check, but not decremented pm_usage count, which
is incremented before scheduling connect_work in ipa_data_connect.
Hence fix this by decrementing pm_usage count in connect_work if
port_usb is NULL.
Change-Id: Ic60f2addcf07375429e0858d3c7a376a35132750
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Use NOM ACC settings up to TURBO voltage corner for APC0/1 for
sdm660.
CRs-Fixed: 2003900
Change-Id: Id1c82a7e1681e028d0426fe0565d88faa6588ab5
Signed-off-by: Tirupathi Reddy <tirupath@codeaurora.org>
The highmem code provides kmap_flush_unused to ensure all kmap
mappings are really removed if they are unused. This code does not
handle kmap_atomic mappings since they are managed separately.
This prevents an issue for any code which relies on having absolutely
no mappings for a particular page. Rather than pay the penalty of
having CONFIG_DEBUG_HIGHMEM on all the time, add functionality
to remove the kmap_atomic mappings in a similar way to kmap_flush_unused.
Change-Id: Ieb25da809b377b1fae1629e2cb75f8aebc1c1bca
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Configure the size of the default CMA region to 32 MB in
DT for sdm630.
Configuring the default CMA region in the DT is cleaner
than using CONFIG_CMA_SIZE_MBYTES since it is easier to
configure per target and the alloc ranges can be specified
in DT.
Change-Id: I329ae0aa9cffeed7c30e44749c15fbb83c58b599
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
This config is already enabled in all other variants but missed
in the 32 bit debug defconfig.
Change-Id: I7b1cb538eaf63305eba171c7453c1459c802eb41
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Power supply framework expects all registered power_supply
entities(except "battery" psy) to support ONLINE property.
"usb-main" psy doesn't support ONLINE property and prints
error for unsupported properties in get_property function.
Update error prints to debug in get-property function of
"usb-main" to prevent log flooding.
Change-Id: I270a93fe2e48d368f13e74e63c48613c1a4fb693
Signed-off-by: Ashay Jaiswal <ashayj@codeaurora.org>
Currently hardware based OTG soft start will fail when enabling OTG with
high capacitance.
Fix this by implementing a software based OTG soft start sequence in
addition to the underlying hardware OTG soft start.
This soft start workaround will begin when an OTG over-current interrupt
is triggered.
Change-Id: I2f3fd5f1bb6e792b2b353eb241d83548e33f563b
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The threshold comparators should be set to "<=". Set them.
Change-Id: I45cf6dd7f165d20e2f2dbc6fce7fd321b4ac145a
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The temperature change IRQ is used to update the parallel power supply
when the temperature of the connector changes. Enable it.
Change-Id: I26582ffc2c98183c75f5c302386416e840bd6ed0
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The connector thermal regulation source must be enabled in order to
receive temperature-change interrupts. Enable it.
Change-Id: I9bb2d3eaf3bba1b1f40bfd724060f2fa437235b5
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
Add a device tree property qcom,connector-temp-max-mdegc to configure
the connector temperature at which mitigation should start.
This will set the thresholds for when the temperature-change IRQ will
fire.
Change-Id: I47df477b56a6654fbf94b5bb0f7dfdfb80e2f16e
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
Use the CONNECTOR_THERM_ZONE property to show the current thermal zone
of the USB connector temperature.
Change-Id: Ia9a85055d68ed08aa9be5b2b66e3e6389ec2e6c3
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The CONNECTOR_THERM_ZONE property shows which thermal zone the
connector temperature is currently in.
Change-Id: I669344feea13f34f98ee808cae5649766543201a
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The temperature change IRQ is used to notify the CTM driver that the
connector temperature has changed. Enable it.
Change-Id: Ibda88fcac6044c0f9a1db96be70b7e7f99e6fb73
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The charger temperature threshold should be configured for thermal
balancing. Add a device tree property to configure the temperature
threshold. A default value will be used in the absence of this property.
Change-Id: I5d64a8012a9c13c578714d91f1e7e4426cef235a
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The hardware conversion triggers are required for thermal regulation.
Enable them.
Change-Id: I4172f7ae8df437ba3a49e6abae587298bc11d78b
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The TADC hardware supports configuring temperature thresholds. Add
support for configuring these thresholds via the IIO framework.
Change-Id: Ib673965eb9b8265874580c8c26f72c85590151c2
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
Update the nt35597 truly panel init sequence to reduce the
high latency issue seen across suspend resume cycles on
SDM660 target.
Change-Id: I0d71cebd5571fac293a8b0f401d882342fbd9106
Signed-off-by: Sandeep Panda <spanda@codeaurora.org>
Recovery can be initiated any time and can happen during driver
register also. With current implementation, if recovery starts
just before driver register then probe call back will not be
called as FW is not ready yet but probe call back will not be
called even after FW ready indication. Fix this case by calling
probe call back after FW ready if driver is registered but probe
call back is not called during driver register.
CRs-fixed: 2002797
Change-Id: Ia1ea812a1bac3204ad95a62b7c6e55511753f2db
Signed-off-by: Prashanth Bhatta <bhattap@codeaurora.org>
Update truly FHD panel init sequence to fix corruption
issues. Also enable dfps feature for the video mode panel
on SDM660 target with the updated sequence.
Change-Id: Ife010a0fccefad802877fd50f222587be36d24aa
Signed-off-by: Sandeep Panda <spanda@codeaurora.org>
Display port pixel clock source is required to propagate the set rate to
parent, so update the flags for the same. The lowsvs frequency has got
updated to 154MHz, update the same.
Change-Id: I67a5ff3b5fb18c2ce986c5f431f4e41a78fe13a5
Signed-off-by: Taniya Das <tdas@codeaurora.org>
The display port PLL generates only limited set of frequency combinations.
As fractional dividers are not required to be used, update the RCG ops to
take care of the same.
Change-Id: I601273fee044ef128dbc7c2e23bc2d8ce10e31dc
Signed-off-by: Taniya Das <tdas@codeaurora.org>
Add a property to the PD PHY peripheral to specify the default
sink capabilities for USB PD as 5V @ 3A, 9V @ 3A and 12V @ 2.25A.
These are common values that should be supported on most boards,
but can be overridden as necessary.
Change-Id: I5ea95d2f0532c59f7d83cb608d939ad28a8bb28e
Signed-off-by: Jack Pham <jackp@codeaurora.org>
Add a device tree property to allow specifying the supported
set of sink capabilities. If not specified, fall back to a
single capability of 5V @ 3A.
Change-Id: I394061d9f3070099e35b651ce4b63a7993343bf1
Signed-off-by: Jack Pham <jackp@codeaurora.org>
Factory QNOVO IADC OFFSET trim values are wrong polarity. To fix it,
update both (reg QNOVO_IADC_OFFSET_0 and QNOVO_IADC_OFFSET_1) with
their two's compliment, respectively.
Factory setting of QNOVO_STRM_CTRL is also wrong. It controls
polarity of the raw IADC bitstream. To get the correct IADC bitstream
polarity, set 0 to register QNOVO_STRM_CTRL.
Set range [1,255] for QNOVO PPCNT parameter, so the right value can
be written.
Change-Id: I7be948b09c96aae4077a8f010c951c6ebd22a0fa
Signed-off-by: Harry Yang <harryy@codeaurora.org>
Current driver read if any nrt vbif is present
and if it is not, the number of qos priority
levels gets wiped out, causing the driver
not to program the vbif qos priority levels for
the rt client. Fix this problem by making sure
that if a vbif nrt does not exist in the platform,
driver only ignore the nrt settings, but keeps
programming the vbif rt.
Change-Id: I2fe5eea5a2ff852b22a59cdb0139b17f3dd7c494
Signed-off-by: Ingrid Gallardo <ingridg@codeaurora.org>
