Automate some review style checking.

BUG=None
TEST=CQ passes

Change-Id: I20b1d853a489cf69f83776896707b111ead92609
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4247570


Reviewed-by: Ting Shen <phoenixshen@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>

This project isn't shipping, so drop it from the build to save time &
space.  If it ever picks up again, we can always pull it from the
history.

BUG=None
TEST=CQ passes

Change-Id: Ic2f21c6141c2c17e4a7934fb6c949823ae7d2e83
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4247565


Reviewed-by: Julius Werner <jwerner@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>

Add some details as to where this file came from.

BUG=None
TEST=CQ passes

Change-Id: I447d5a7056a280809b98d6538a56762bd9980ef6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4247569


Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Ting Shen <phoenixshen@chromium.org>
Auto-Submit: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Ting Shen <phoenixshen@chromium.org>

Should be no functional changes here.

BUG=None
TEST=CQ passes

Change-Id: I4dc7da91b055aee0c9c412521b9499b87619b216
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4247568


Auto-Submit: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Ting Shen <phoenixshen@chromium.org>
Reviewed-by: Ting Shen <phoenixshen@chromium.org>

Ran `cros format` on the files to fix a few minor issues.

BUG=None
TEST=CQ passes

Change-Id: Ic28943e591789b7fe73a6db0563715a9e2c66aa1
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4247566


Commit-Queue: Ting Shen <phoenixshen@chromium.org>
Auto-Submit: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Ting Shen <phoenixshen@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>

Sync the translation result of CL:3575512 and CL:4149759 from google3 to
cros repo.

This CL fixed most of the missing translations, will fix CL:2332240 in a
later CL after its translation ready.

BUG=b:268017053,b:264955991
TEST=manually checked zh and jp

Change-Id: Idbefcfdc59b627f65d49ebb2c40c1cecec6d253e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4229976


Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Ting Shen <phoenixshen@chromium.org>
Tested-by: Ting Shen <phoenixshen@chromium.org>

BUG=b:261824838
TEST=build factory shim and run it on Octopus

Change-Id: Ibea3ae6c523a7f704db6e12892a3ba0b2b834840
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4178208


Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Stimim Chen <stimim@chromium.org>
Tested-by: Stimim Chen <stimim@chromium.org>

In kernel v4.19 and earlier, the device-mapper won't be initialized by
kernel in the init stage when initramfs is used.  Therefore, we need to
`dmsetup create` the device-mapper by ourselves.

BUG=b:261824838
TEST=build factory_install shim, and boot from it in recovery+dev mode
     (using dev signed firmware)

Change-Id: I0936c31661db120c871df2066fa6ec93e3fb7f45
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4178207


Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Stimim Chen <stimim@chromium.org>
Tested-by: Stimim Chen <stimim@chromium.org>

BUG=b:261824838
TEST=With CL:4178208, change the max version to -1, and the factory shim
     will be locked.

Change-Id: I7e0b884825973e6c36e156e2f0fd1cfcd4cbfe68
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4178206


Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Stimim Chen <stimim@chromium.org>
Commit-Queue: Stimim Chen <stimim@chromium.org>

BUG=b:261824838
TEST=None

Change-Id: I72a636e4bc93b17b62c1ad80f6d5c679f1f878ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4178205


Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Stimim Chen <stimim@chromium.org>
Commit-Queue: Stimim Chen <stimim@chromium.org>

We are going to share the implementation of dmsetup functions with
factory_shim scripts. Refactor these functions first so we can verify
the new implementation with minimal changes.

BUG=b:261824838
TEST=None

Change-Id: If399a107451cd84e044a56b371e347a8642571e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4188237


Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Stimim Chen <stimim@chromium.org>
Tested-by: Stimim Chen <stimim@chromium.org>

Unify the funciton name so it is easier to share code between recovery
shim and factory shim.

To make it easier to debug factory shim, we make `dlog` the same as
`log` function.

BUG=None
TEST=None

Change-Id: I701717d8bf877566f6600cc64e0be279e4eac381
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4188236


Commit-Queue: Stimim Chen <stimim@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Stimim Chen <stimim@chromium.org>

When we want to verify rootfs in factory shim, we need to mount
/dev/dm-0 instead of sdX3. And we can check by the root arg in
the kernel command line.

BUG=b:261824838
TEST=The built factory shim should work normally no matter the value
of root in kernel command line.

Change-Id: Idb64fc5a1ddc34ba3e4df1efdba9d2d11bcd340d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4160496


Reviewed-by: Allen Webb <allenwebb@google.com>
Tested-by: Chih-Yao Chuang <jasonchuang@google.com>
Reviewed-by: Andrey Pronin <apronin@chromium.org>
Reviewed-by: Stimim Chen <stimim@chromium.org>
Commit-Queue: Stimim Chen <stimim@chromium.org>
Auto-Submit: Chih-Yao Chuang <jasonchuang@google.com>

- Upate the steps for further clarification.
- Improve formatting.

BUG=None
TEST=None

Change-Id: Ib550de7ea2371af149cac5c7e2c91801768edd2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4153272


Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Richard Chui <richui@chromium.org>
Tested-by: Richard Chui <richui@chromium.org>

BUG=b:264955991
TEST=None

Change-Id: I17906d365b844174cf978edb6a3cf2ef9dcad10c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4149759


Reviewed-by: Ting Shen <phoenixshen@chromium.org>
Tested-by: Richard Chui <richui@chromium.org>
Commit-Queue: Richard Chui <richui@chromium.org>

After upgrading system-tmpfiles the install path changed from /bin to
/usr/bin.

BUG=b:249429693, b:260832836
TEST=CQ passes

Cq-Depend: chromium:4054004
Change-Id: I0443271b81883e63ba8b16a709295bb9ad70d4e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4062458


Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Allen Webb <allenwebb@google.com>
Tested-by: Allen Webb <allenwebb@google.com>

This reverts commit 6391c7ed.

Reason for revert: This breaks the builder with no gsctool binary.

Original change's description:
> factory_netboot: add gsc-constants.sh and gsctool to initramfs
>
> This CL adds gsc-constants.sh and gsctool to the initramfs since
> cros.sh needs them.
>
> BUG=b:263559279
> TEST=(1) USE="factory_netboot_ramfs" \
>          emerge-nissa chromeos-initramfs
>      (2) bsdtar tf \
>          /build/nissa/var/lib/initramfs/factory_netboot_ramfs.cpio.xz \
>          | grep gsc
>
> Change-Id: I8cad3e6c48bb2c6eafee449d87eacaff5c650ed9
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4123909


> Reviewed-by: Yu-An Wang <wyuang@google.com>
> Commit-Queue: Yu-An Wang <wyuang@google.com>
> Auto-Submit: Phoebe Wang <phoebewang@chromium.org>
> Tested-by: Phoebe Wang <phoebewang@chromium.org>

Bug: b:263559279
Change-Id: Id9ca7cff4714225544fb39d8d6260c7b7cfe9324
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4125280


Tested-by: Phoebe Wang <phoebewang@chromium.org>
Auto-Submit: Phoebe Wang <phoebewang@chromium.org>
Reviewed-by: Yu-An Wang <wyuang@google.com>
Commit-Queue: Yu-An Wang <wyuang@google.com>

This CL adds gsc-constants.sh and gsctool to the initramfs since
cros.sh needs them.

BUG=b:263559279
TEST=(1) USE="factory_netboot_ramfs" \
         emerge-nissa chromeos-initramfs
     (2) bsdtar tf \
         /build/nissa/var/lib/initramfs/factory_netboot_ramfs.cpio.xz \
         | grep gsc

Change-Id: I8cad3e6c48bb2c6eafee449d87eacaff5c650ed9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4123909


Reviewed-by: Yu-An Wang <wyuang@google.com>
Commit-Queue: Yu-An Wang <wyuang@google.com>
Auto-Submit: Phoebe Wang <phoebewang@chromium.org>
Tested-by: Phoebe Wang <phoebewang@chromium.org>

The coordinated PM patches are not yet ported to v5.19, therefore
temporary switch it off.

BUG=b:255912146
TEST=Boot ManaTEE with v5.19 kernel and check that devices within
ChromeOS VM are fully functional.

Change-Id: I26a1b4150cabf17682603f18d01552bc850f2af9
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4111176


Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Tested-by: Tomasz Nowicki <tnowicki@google.com>
Commit-Queue: Tomasz Nowicki <tnowicki@google.com>

As of now, the configuration file is identical to brya-manatee

BUG=b:255912146
TEST=Boot ManaTEE with v5.19 kernel and brya-manatee-kernelnext image and
check that devices within ChromeOS VM are fully functional.

Change-Id: I2310254da2566b867b6ea3fdd98daca0f559db37
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4111175


Commit-Queue: Tomasz Nowicki <tnowicki@google.com>
Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Tested-by: Tomasz Nowicki <tnowicki@google.com>

The VFIO PCI parameter paths have changed during VFIO_PCI refactoring
for v5.19 kernel revision. Support new paths and keep backward
compatibility.

BUG=b:255912146
TEST=Boot ManaTEE with v5.19 kernel and check that devices within
ChromeOS VM are fully functional.

Change-Id: I00f3bb46bce9146019b75e88910236f8f5c08302
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4111174


Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Tested-by: Tomasz Nowicki <tnowicki@google.com>
Commit-Queue: Tomasz Nowicki <tnowicki@google.com>

This is a reland of commit a6d14b9d

This fixes the revert issue where pre-unibuild boards attempt to query
cros config.

Original change's description:
> Implement support for detachable USE flag in cros-config
>
> This USE flag prevents unified builds across all form factors for some devices.
> Using config data rather than relying on a USE flag will fix this.
>
> BUG=b:249619243, b:251058313
> TEST=recovery ramfs checks config files and enables the correct input method
>
> Cq-Depend: chromium:3936480, chromium:3935669, chromium:3937064
> Change-Id: If88cfd921f596b9cd56b11ac49393ac913cb3354
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3929936


> Reviewed-by: Sam McNally <sammc@chromium.org>
> Tested-by: Liam Flaherty <liamflaherty@chromium.org>
> Commit-Queue: Liam Flaherty <liamflaherty@chromium.org>
> Reviewed-by: Shelley Chen <shchen@chromium.org>

Bug: b:249619243, b:251058313
Cq-Depend: chromium:4074358, chromium:4078585
Change-Id: Ie73c9fd725314a568da059faf6b74d873522df00
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4074698


Reviewed-by: Sam McNally <sammc@chromium.org>
Commit-Queue: Liam Flaherty <liamflaherty@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Tested-by: Liam Flaherty <liamflaherty@chromium.org>

Neither the recovery process nor the factory netboot image uses mosys
anymore, so this can be removed from initramfs.

BUG=b:187790074
TEST=CQ

Change-Id: Ided002ed5f8505078b50701eca8a3b94e7df6296
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4104422


Commit-Queue: Jack Rosenthal <jrosenth@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Ting Shen <phoenixshen@chromium.org>
Tested-by: Jack Rosenthal <jrosenth@chromium.org>
Commit-Queue: Ting Shen <phoenixshen@chromium.org>
Auto-Submit: Jack Rosenthal <jrosenth@chromium.org>

This reverts commit a6d14b9d.

Reason for revert: The probable cause of b/257510430.

Original change's description:
> Implement support for detachable USE flag in cros-config
>
> This USE flag prevents unified builds across all form factors for some devices.
> Using config data rather than relying on a USE flag will fix this.
>
> BUG=b:249619243, b:251058313
> TEST=recovery ramfs checks config files and enables the correct input method
>
> Cq-Depend: chromium:3936480, chromium:3935669, chromium:3937064
> Change-Id: If88cfd921f596b9cd56b11ac49393ac913cb3354
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3929936


> Reviewed-by: Sam McNally <sammc@chromium.org>
> Tested-by: Liam Flaherty <liamflaherty@chromium.org>
> Commit-Queue: Liam Flaherty <liamflaherty@chromium.org>
> Reviewed-by: Shelley Chen <shchen@chromium.org>

Bug: b:249619243, b:251058313
Change-Id: I54ea5871c8d8555b8bee40f8626bf381c5322a28
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/4011579


Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Shelley Chen <shchen@chromium.org>
Auto-Submit: Liam Flaherty <liamflaherty@chromium.org>
Commit-Queue: Shelley Chen <shchen@chromium.org>

This USE flag prevents unified builds across all form factors for some devices.
Using config data rather than relying on a USE flag will fix this.

BUG=b:249619243, b:251058313
TEST=recovery ramfs checks config files and enables the correct input method

Cq-Depend: chromium:3936480, chromium:3935669, chromium:3937064
Change-Id: If88cfd921f596b9cd56b11ac49393ac913cb3354
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3929936


Reviewed-by: Sam McNally <sammc@chromium.org>
Tested-by: Liam Flaherty <liamflaherty@chromium.org>
Commit-Queue: Liam Flaherty <liamflaherty@chromium.org>
Reviewed-by: Shelley Chen <shchen@chromium.org>

Add the default set of test rules.

V2 test plans will be verified in staging before being enabled in prod.

See go/cros-cq-test-config for more details.

BUG=b:249150178
TEST=dirmd validate

Change-Id: I45c98032dde32d4e8fdeda1117878e46831bd114
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3925043


Tested-by: Navil Perez <navil@google.com>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: Navil Perez <navil@google.com>

Since the VVU sound (crrev.com/3807188), wayland (crrev.com/c/3723177)
and GPU (crrev.com/c/3723178) were enabled for ManaTEE sibling VMs
at the almost same time so we haven't tested all of the devices together
well. We needed to add more pre-allocated VVU proxy devices.

BUG=b:245550339
TEST=CQ

Change-Id: I5871dbff025c50b3785b7b150ed3b4b3a95aa0dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3920621


Tested-by: Keiichi Watanabe <keiichiw@chromium.org>
Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>

Normally we don't do this, but enough changes have accumulated that
we're doing a tree-wide one-off update of the name & style.

BUG=chromium:1098010
TEST=`repo upload` works

Change-Id: I2e275d4293a6d81c6121a472914e5af5a5e740a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3891202


Tested-by: Mike Frysinger <vapier@chromium.org>
Auto-Submit: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Commit-Queue: Hung-Te Lin <hungte@chromium.org>

The on_error message handler should kill progress bar.

Also did a small refacroe to move the kill & wait lines into a
separate function.

BUG=b:242228054
TEST=1. build recovery imagg
     2. remove usb stick during recovery install to trigger error
        page.
     3. verify that progress bar disappearred when showing error page

Change-Id: Ib7d6ece39407ac42392575be279af70435926e5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3834436


Reviewed-by: Shelley Chen <shchen@chromium.org>
Commit-Queue: Ting Shen <phoenixshen@chromium.org>
Tested-by: Ting Shen <phoenixshen@chromium.org>

ChromeOS receives RTC interrupts (along with RTC acpi events),
so ChromeOS VM in ManaTEE should be able to receive them too.

That said, this fix might be completely optional: RTC wakeup seems
to work as well with RTC acpi events passthrough only, without RTC
interrupts. Also from rtc-cmos driver source in kernel it looks like
it is actually redundant: cmos_interrupt() is called by the acpi event
handler as well as by the irq handler.
However, let's keep it close to the non-virtualized behavior.

BUG=b:225285399
TEST=Boot ManaTEE, verify that RTC wakeup works and rtc0 interrupt
count in /proc/interrupts increases along with acpi event count in
/sys/firmware/acpi/interrupts/ff_rt_clk.

Change-Id: I6109ec4f2e76b7dd87496b02b23da4cfd1eeeb59
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3632105


Tested-by: Dmytro Maluka <dmaluka@google.com>
Commit-Queue: Dmytro Maluka <dmaluka@google.com>
Reviewed-by: Dmitry Torokhov <dtor@chromium.org>

ChromeOS VM takes control over physical communication with RTC
hardware, so and RTC events should be passed through to the VM.

BUG=b:225285399
TEST=Suspend via "powerd_dbus_suspend --suspend_for_sec=5", check that
the system wakes up after 5 secs and
/sys/firmware/acpi/interrupts/ff_rt_clk counter in CrOS increases.

Change-Id: Iaa71d7704883f1541535c05160146f7265c1b074
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3613811


Reviewed-by: Micah Morton <mortonm@chromium.org>
Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Tested-by: Dmytro Maluka <dmaluka@google.com>
Commit-Queue: Dmytro Maluka <dmaluka@google.com>

- Removed the following legacy ports not used by ChromeOS (the below is
  their source ACPI description in
  src/soc/intel/common/block/acpi/acpi/lpc.asl in Coreboot):

        IO (Decode16, 0x61, 0x61, 0x1, 0x01) // NMI Status
        IO (Decode16, 0x63, 0x63, 0x1, 0x01) // CPU Reserved
        IO (Decode16, 0x65, 0x65, 0x1, 0x01) // CPU Reserved
        IO (Decode16, 0x67, 0x67, 0x1, 0x01) // CPU Reserved
        IO (Decode16, 0x80, 0x80, 0x1, 0x01) // Port 80 Post
        IO (Decode16, 0x92, 0x92, 0x1, 0x01) // CPU Reserved
        IO (Decode16, 0xb2, 0xb2, 0x1, 0x02) // SWSMI

- Removed legacy DMA ports 0x81-0xef except port 0x87 (DMA_PAGE_0 reg)
  which just returns 0xff value indicating that there is no legacy DMA
  controller, so that ChromeOS doesn't try to use legacy DMA.
  See i8237A_init_ops() in Linux kernel.
  TODO: emulate this port in crosvm instead of pass-through?

- TODO: do we need Super I/O ports 0x2e-0x2f,0x4e-0x4f? ChromeOS does
  access them for some reason during bootup, as well as during resume
  from suspend, but is it really needed?

BUG=none
TEST=ManaTEE boots and works fine.

Change-Id: Ib9bd5bb7b53473267005efb15b28c40cff06783d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3827427


Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Commit-Queue: Dmytro Maluka <dmy@semihalf.com>
Tested-by: Dmytro Maluka <dmy@semihalf.com>

On ADL with DPT enabled in passthrough seems to cause pipe fault errors.
This tries to disable it temporary to restore current ManaTEE testing.

BUG=b:237052709
TEST=start ManaTEE and check screen flicker issue after starting crostini

Cq-Depend: chromium:3759928
Change-Id: I6aaded85268772af7800e569f7c3512405a7e803
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3759139


Reviewed-by: Zhenyu Z Wang <zhenyuw@linux.intel.com>
Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
Tested-by: Junichi Uekawa <uekawa@chromium.org>
Commit-Queue: Junichi Uekawa <uekawa@chromium.org>

intel-lpss devices need special handling during BAR accesses due to PV
operations in the guest. Identify such devices for crosvm so it can tag
them for PV handling.

BUG=b:232887201
TEST=boot manatee and verify cmdargs for crosvm

Disallow-Recycled-Builds: test-failures
Change-Id: Id5c889605d7ed74fc8d7ce12ba94d344f728b58c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3762511


Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
Tested-by: Tomasz Nowicki <tnowicki@google.com>
Commit-Queue: Tomasz Nowicki <tnowicki@google.com>

Initialize MMS and trichechus to monitor TEE app memory usage via memory
control groups.

BUG=b:229176768
TEST=boot brya-manatee, start manatee shell, allocate memory

Cq-Depend: chromium:3828333
Change-Id: I9fdcd88cb570d8ea08c161722bd0f7c063700432
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3826606


Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
Tested-by: David Stevens <stevensd@chromium.org>
Commit-Queue: David Stevens <stevensd@chromium.org>

ChromeOS VM takes control over physical communication with the EC,
so power button events should be passed through to the VM.

BUG=b:228445196
TEST=Boot ManaTEE, check that CrOS correctly responds to power button
pressed (both at runtime and at wakeup from suspend via power button)
and /sys/firmware/acpi/interrupts/ff_pwr_btn counter in CrOS increases.

Cq-Depend: chromium:3599200
Change-Id: Ie967764c998c1749be2957b30d5cc45f370e9382
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3645408


Commit-Queue: Dmytro Maluka <dmy@semihalf.com>
Reviewed-by: Micah Morton <mortonm@chromium.org>
Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Tested-by: Dmytro Maluka <dmy@semihalf.com>

Similarly to passthrough GPEs, add possibility to specify the list
of fixed events assigned directly to CrOS on a given board.

Perhaps it would be better to specify the same list of passthrough
fixed events (e.g. power button and RTC event) unconditionally for
all boards, rather than in manatee.conf per board (since unlike GPEs,
fixed events are rather standard). On the other hand, maybe some
boards may lack hardware for enabling some of those events.

BUG=b:228445196
TEST=boot with BOARD_FIXED_EVENTS in manatee.conf and check
--direct-fixed-event args in the command line of crosvm-direct process

Change-Id: Id81fd7386846ae6719e5050446581ae1dcb153c3
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3613810


Reviewed-by: Micah Morton <mortonm@chromium.org>
Tested-by: Dmytro Maluka <dmy@semihalf.com>
Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Commit-Queue: Dmytro Maluka <dmy@semihalf.com>

HWP feature has been decoupled from ITMT and we can expose them to
CrOS by default.

Add BOARD_MSR_READ_WRITE_PASS for MSRs need R/W permissions.

Append "intel_pstate=hwp_only" to CrOS kernel to force intel_pstate
being loaded only if HWP is supported, since it works for sibling VMs
only if intel_pstate works in Active Mode with HWP enabled.

Add "enable-hwp" to enable HWP feature on CrOS.

BUG=b:199380745
TEST=boot Redrix manatee and verified that intel_pstate driver works

Cq-Depend: chromium:3814317
Change-Id: Id0a3e11a62f81485d0648f1621cf2a7a1e9bad4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3705927


Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
Tested-by: Daniel Verkamp <dverkamp@chromium.org>

Isolating hotplug devices behind viommu was made optional in crosvm, to
avoid the need to always instantiate a viommu device. Set the new flag,
so TBT devices continue to be isolated.

BUG=b:231365736
TEST=boot ManaTEE

Change-Id: I01ed992c57556807ea70b09bf394bfd53c1dbeef
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3803945


Tested-by: David Stevens <stevensd@chromium.org>
Commit-Queue: Junichi Uekawa <uekawa@chromium.org>
Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
Auto-Submit: David Stevens <stevensd@chromium.org>

BUG=b:222371705
TEST=verified that this option shows in hypervisor kernel

Change-Id: I03b37fda1d71e49a91551217aec499f14fb2efb6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/initramfs/+/3796270


Reviewed-by: Dmitry Torokhov <dtor@chromium.org>
Commit-Queue: Dmitry Torokhov <dtor@chromium.org>
Tested-by: Dmitry Torokhov <dtor@chromium.org>