it seems that there's conflict between samsung_iommu_v9 and trusty_log,
so load samsung_iommu_v9 in serial
Test: build pass and run 2000 times without error
Bug: 290561688
Change-Id: I6af250bbe3089f41229f6d674cc2e4a7eae3cbe1
Signed-off-by: Chungkai Mei <chungkai@google.com>
to mitigate potential kernel panic, load g2d only at the
same time.
Test: Build pass
Bug: 287727823
Change-Id: I8b4eac1875d3b394fc9ab651959db54c53967326
Signed-off-by: Chungkai Mei <chungkai@google.com>
This reverts commit d4c206cfcf.
Reason for revert: exynos_devfreq is fixed by pa/2512847, and add 2 shiba DVT and 1 Husky DVT to reboot 5000 times, only one device hit ramdumpg with reset message "itmon triggering err_tmout from HSI1 PCIE_GEN3_0 to NOCL0_", but according to b/283930792, even without parallely module loading, device still hit this issue. so currently parallel module loading seems to be stable enough.
Bug: 285064434
Change-Id: I0356075a60cc0224ac975b401654b424ff4b993e
This reverts commit 04716d5711.
Reason for revert: Now we can enter fastbootd normally.
Test: shiba rebooted 1000 times without failure
Bug: 280112517
Change-Id: I92736b1e535468083b35058f83a91ad153b6c5c6
Move shusky thermal .json files into thermal/
and perf configs into perf/.
Also move the configs into device-shusky-common.mk,
allowing override of the config file path.
Bug: 277993984
Change-Id: Ifa2882ee9c27c57d967c27f9f8e8edaff313e2d5
We will have a 'vendor' project containing proprietary blobs
to be able to build and flash Pixel device when vendor source is not
available.
The project names are
platform/vendor/aosp/google_devices/husky
platform/vendor/aosp/google_devices/shiba
and the paths are
vendor/google_devices/husky
vendor/google_devices/shiba
TEST:make and flash a husky device
BUG: 278968179
Change-Id: I1c5424dfddddb8ee29a86f2408a231aa5556a0bb
Same as P22, P23 do not have 32-bit address limitation in hardware, so
we would like to empty zone DMA32 for better performance and simplify
memory management.
Bug: 263239622
Test: b/270096808, b/270097444. Pass reboot test and run sst for 100+
hours without obvious issues.
Change-Id: Ib95223aafca17165e1b8d972448c5d66384d3ccc
Signed-off-by: liangjlee <liangjlee@google.com>
(cherry picked from commit 4584a04fe3)
Disable parallel module loading.
iommu driver loading parallel prevented boot to
fastbootd.
resolved with
fastboot oem cmdline set samsung-sysmmu-v9.load_sequential=1
disabling all parallel module loading for now, can re-enable
at a later stage with verification.
Bug: 268269286
Change-Id: Iccecff4ae552567f3a5fb8a421b8e1993657fbc7
Same as p22, we would like to disable swiotlb for shiba and husky.
Currently the swiotlb=noforce config is set in device tree, moving to userspace
would make the build process more flexible.
Bug: 263178695
Test: After adding noforce, /d/swiotlb/ is empty
Change-Id: I6505bfe8b465a0b2bcc6f39d1abaefe305bdc31f
Signed-off-by: Jack Lee <liangjlee@google.com>
enable load kernel modules in parallel but load some
specific modules in sequential
Test: Shiba Booted to home 1000 times without issue
Bug: 229794277
Change-Id: Idac2ae0765058a0eab718c976c1108292bd36669
Signed-off-by: Chungkai Mei <chungkai@google.com>
