* It is started in the on init phase in /system/etc/init/hw/init.rc

Change-Id: Ie10e1d4c520329a76627a965ca139f9ad0f71875

* Drop foreground and top-app cpus
* Set 0-3 as background cpus
* Drop xiaomi iolimit and custom types for shima

Change-Id: I3733e196a8ed090c15d6867b0722425435f31474

Change-Id: I813e6893475caf8196f7c81f6ae237bd1d4b73d1

Change-Id: I685a215927b445bb2fac9229a1f41de5f88741ef

Change-Id: I6831d37d02012e3ce2d58a9c45818e594a658883

While at it, update lahaina one from odin V12.5.12.0.RKMCNXM

Apply the following commits to all scripts:
commit a7efe9f3
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Tue Sep 28 09:15:41 2021 +0300

    sm8350-common: rootdir: remove cpu 7 from foreground tasks

commit 52fde070
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Fri Sep 24 02:44:34 2021 +0300

    sm8350-common: rootdir: do not touch sleep disabled

commit 30ddf5a8
Author: Cosmin Tanislav <demonsingur@gmail.com>
Date:   Sat Sep 18 02:57:51 2021 +0300

    sm8350-common: rootdir: cleanup

Change-Id: Ibd4e8717b52c35faa4d43ade170dbde58c04ed37

If we set 2048KB ra value in the beginning of the
boot process, services initialized at this time would
keep 2048KB ra value even though we adjust the ra value
to 128KB after boot completion.

This may cause memory pressure.

Bug: 174700194
Signed-off-by: Randall Huang <huangrandall@google.com>
Change-Id: I97ee0ee9511eaada011f2634afd68d68cdca4570

Init doesn't handle all dm devices

This reverts commit 17d09b70.

Change-Id: I2b42c286307e8fd41140bca8f893ccdf13ebfc06

Change-Id: I5c65e0df255853eb2b3018a27ceb807c111bc4df

Change-Id: I4353249682aaa0c08b5af462656974bcb6fdf14a

* From odin V12.5.12.0.RKMCNXM

Change-Id: I5509271b0cdb23e40f8fb4186b740c66d79fe069

This depends on caf BoostFramework

Change-Id: I1d3e6750ecb88db83f265cc06b175cbc0cfb9726

This depends on caf BoostFramework

Change-Id: Ie3ea41f7be323472124a395b8fee52aa7333c2fc

Change-Id: Ia37b752c369d8b0dc48aba33898ce7e245f4de2d

Change-Id: I44004a3c1377d91e887f66905df5f8c61b0d5639

This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:

W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)

AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.

https://android.googlesource.com/platform/frameworks/base/+/c78a463e875d91eae2cf256042fd99d130217c38

Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581

Change-Id: I7c0a9ad622a0c42966d84024c22cd03e033fd09b

Specifying avb=<vbmeta-partition> is only necessary for first entry of
partition groups that use same vbmeta partition. The following entry can have
<vbmeta-parititon> part omitted.

Test: None
Link: https://source.android.com/devices/architecture/kernel/mounting-partitions-early#fstab-entries


Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I5a42fd3de72c400acfae56d6a1e1b85c22a79537

Change-Id: I0ca98738e4964d23614df797b1faaebe0058a451

The copyright header has been modified by caf while the initial lahaina
tree whose fstab we use.
Specifically from https://source.codeaurora.org/quic/la/platform/vendor/qcom/lahaina/tree/fstab.qcom?h=LA.UM.9.14.r1-18900-LAHAINA.QSSI12.0&id=b403cbb26431c57a8590f94307f12443a55e29e2

Change-Id: I1dd07a729feeded6478e095573070fde532f2f02

Remove start console

Change-Id: I1041fa446499cd82bcbf6d5b86cb25a9a88fa90c
CRs-Fixed: 2977860

Disabling UFS clkgate and ah8 during boot time helps in reducing
IO delays, which helps in reducing the total boot time. This change
will disable UFS clkgate and ah8 during early-init and then enable
it back after boot completion.

Change-Id: I6a10cd57a30fe3bdc4fba72a0d84cdfa3b1fd513

Two fstabs are needed to support different data unit number (dun)
size for ufs and emmc hardwares. This needs different encryption
flag in fstab to address the difference in dun size.

[ArianK16a: don't add the emmc fstab since all our devices are ufs]

Test: Verified bootup, vts_kernel_encryption, fscryptctl.

Change-Id: Iff03422d39c789c544bdd86faef070ae46eb4e0e

Remove the hard-coded path for /dev/block/bootdevice.
Instead use the bootdevice property.

Change-Id: I194587e250f1d24f677c6fd3f34a23f146d4bc7e

Removing command to load ipa fw from post-fs, where FW mount
is not guaranteed.

Change-Id: I426bcfd2d9e0fb9f09a360374fe05b653676cf4b
CRs-Fixed: 2819603

QMCS partition is not a read only partition, and risks the danger
of causing unnecessary disk churn when QMCS files are read.

Update QMCS partition to be mounted with the noatime option.

Change-Id: Icf7e565d0e1c990131ad090c2f466bea419b4ad4

move spunvm partition out of fstab and mount in init.target.rc
only for lahaina as shima doesn't have spunvm partition.

Change-Id: I2b19c7cf84f23c0f73103fff2a2a7ae5a7dd186a
CRs-Fixed: 2801834

Change-Id: I929324ff494ecbf5a0672e503980a547ee0c66ce