ZRAM is being disabled on tuivm due to observed stability issues due to
ZRAM's use of GFP_MEMALLOC. Increase maximum movable zone size to
compensate.
When kswapd swaps out pages, PF_MEMALLOC is set, which results in zram
ignoring the min_watermark, and lowmem_reserve. This is problematic
because we intend for movable memory to stay in ZONE_MOVABLE, rather
than falling back to ZONE_NORMAL. If the later occurs to such a high
degree that all ZONE_NORMAL memory is consumed, as is observed to be
the case during a "C2PA" testcase, attempts to plug in additional
ZONE_MOVABLE memory may fail due to requiring a small amount of
GFP_KERNEL memory.
Change-Id: Ic847e90514f80ccb91daa98849440d7a9b97f156
Signed-off-by: Patrick Daly <quic_pdaly@quicinc.com>
"qcom,initial-movable-zone-size" creates a movable zone of the given size
before userspace starts. This is useful in a system where a userspace
component (psi-daemon) is used to hotplug in memory on a on-demand basis.
With swap disabled, the current tvm carveout size (68 Mb) hits
out-of-memory condition before psi-deamon is started.
Once psi-daemon is running, it detects the number of blocks added to the
movable zone via "qti_virtio_mem/kernel_plugged" sysfs file, and
can reduce or increment the number as necessary.
Change-Id: I5b62b6227e8a357ba3012979ed4bf937f1810437
Signed-off-by: Patrick Daly <quic_pdaly@quicinc.com>
This property describes how large of a movable zone should be created
when the virtio_mem device probes.
Also, fix all errors reported by make dt_binding_check.
Change-Id: I487ad7592d54021ddbb3caddb20774d3e076c766
Signed-off-by: Patrick Daly <quic_pdaly@quicinc.com>
The virtio-mem device has always had a dependency on mem-buf for plugging
in memory. Previously, the ordering was not a concern, since hotplug was
not done until userspace was up. However, in subsequent patches we
will instead hotplug in memory as soon as the virtio-mem device probes.
Change-Id: I9c4e4728a15ab32d65ffaea0ba2681a816a4abf0
Signed-off-by: Patrick Daly <quic_pdaly@quicinc.com>
Child node support for SCID heuristics compatible device.
Change-Id: Id1fb1e190181d39053dce629c6807262032744ad
Signed-off-by: Avinash Philip <quic_avinashp@quicinc.com>
Add support for CAMCC and CAM_BIST_MCLK_CC clock controller nodes
on Tuna platform. While at it, move camcc gdsc's to real.
Change-Id: I14e7add272a549cd21c39083a26baac4c50de31e
Signed-off-by: Ajit Pandey <quic_ajipan@quicinc.com>
Child node support for SCID heuristics compatible device.
Change-Id: Id1fb1e190181d39053dce629c6807262032744ad
Signed-off-by: Avinash Philip <quic_avinashp@quicinc.com>
Remove cpu pause action on boot core in Parrot.
Change-Id: I59e4e6cfec9073cd94a5bf0fcff96158d4061835
Signed-off-by: Nitesh Kumar <quic_nitekuma@quicinc.com>
SW drv3 may be used sometimes by display panel. Add it.
Change-Id: I03fc0bee08c44447caf689b747b054f4aa62ffca
Signed-off-by: Maulik Shah <quic_mkshah@quicinc.com>
ZRAM is being disabled on tuivm due to observed stability issues due to
ZRAM's use of GFP_MEMALLOC. Increase maximum movable zone size to
compensate.
When kswapd swaps out pages, PF_MEMALLOC is set, which results in zram
ignoring the min_watermark, and lowmem_reserve. This is problematic
because we intend for movable memory to stay in ZONE_MOVABLE, rather
than falling back to ZONE_NORMAL. If the later occurs to such a high
degree that all ZONE_NORMAL memory is consumed, as is observed to be
the case during a "C2PA" testcase, attempts to plug in additional
ZONE_MOVABLE memory may fail due to requiring a small amount of
GFP_KERNEL memory.
Change-Id: Ic847e90514f80ccb91daa98849440d7a9b97f156
Signed-off-by: Patrick Daly <quic_pdaly@quicinc.com>
"qcom,initial-movable-zone-size" creates a movable zone of the given size
before userspace starts. This is useful in a system where a userspace
component (psi-daemon) is used to hotplug in memory on a on-demand basis.
With swap disabled, the current tvm carveout size (68 Mb) hits
out-of-memory condition before psi-deamon is started.
Once psi-daemon is running, it detects the number of blocks added to the
movable zone via "qti_virtio_mem/kernel_plugged" sysfs file, and
can reduce or increment the number as necessary.
Change-Id: I5b62b6227e8a357ba3012979ed4bf937f1810437
Signed-off-by: Patrick Daly <quic_pdaly@quicinc.com>
This property describes how large of a movable zone should be created
when the virtio_mem device probes.
Also, fix all errors reported by make dt_binding_check.
Change-Id: I487ad7592d54021ddbb3caddb20774d3e076c766
Signed-off-by: Patrick Daly <quic_pdaly@quicinc.com>
The virtio-mem device has always had a dependency on mem-buf for plugging
in memory. Previously, the ordering was not a concern, since hotplug was
not done until userspace was up. However, in subsequent patches we
will instead hotplug in memory as soon as the virtio-mem device probes.
Change-Id: I9c4e4728a15ab32d65ffaea0ba2681a816a4abf0
Signed-off-by: Patrick Daly <quic_pdaly@quicinc.com>
