fixing broken overlay#4
Open
cobalt9 wants to merge 30 commits intoTeamReloaded:lineage-15.1from
cobalt9:lineage-15.1
Open
fixing broken overlay#4cobalt9 wants to merge 30 commits intoTeamReloaded:lineage-15.1from cobalt9:lineage-15.1
cobalt9 wants to merge 30 commits intoTeamReloaded:lineage-15.1from
cobalt9:lineage-15.1
Conversation
* Clean unused fp firmware since they directly load from /firmware Change-Id: I4f5f25ce193a54d243efd84fd8618ffe423f984c
Change-Id: I68a4bffc0e796f2b86e1af2a0771853e95dd7b1a
Change-Id: I4bfac85c64599ced45983a86d98cfd810a97db99
Change-Id: I4e61f928707a52a58c2fd5b89f81b0e5e8b46e11
Change-Id: I50d8173d24c4cab773824107b98929dbbc469783
This reverts commit 08ae0e1. Change-Id: I4881d00a1dbb12c33464b1f954daf6ed2349346a
Change-Id: I534266be2f93e221357030aa58634dbf87629b31
Surprisingly it is working very well while offline charging, same as MIUI Reference- https://review.lineageos.org/#/c/205385/ Change-Id: I1282a368bc9b0b9cd51cbbcde8d9973dce822de6
*From: xiaomi/tissot/tissot_sprout:8.1.0/OPM1.171019.019/8.4.28:user/test-keys Change-Id: If659529e64a65f7e96d94034ab53e1fb47d6e859
* The atfwd daemon is responsible for handling AT command forward requests from modem and should be enabled for all targets except sda, apq, qcs. Change-Id: I80a2c1dec415aeb31f9ed1cbb16749328397433e
Change-Id: I76c3b1c2a62d3586961b7944c664c02541a03de4
* Tag: LA.UM.6.6.r1-08300-89xx.0 Change-Id: Ie4759d0919200e9b38dbc017d0798fccb97aabe5
* After all, this still seems to be needed for ACDB MCS init,
as seen bellow. Just let ACDB loader be happy.
Without the tuning mixer file:
E ACDB-MCS: acdb_mcs_init: /vendor/etc/audio_tuning_mixer_tasha.txt not present, using /vendor/etc/audio_tuning_mixer.txt config file
E MCS-RT-CTL: Can't open the configuration file /vendor/etc/audio_tuning_mixer.txt.
E ACDB-MCS: acdb_mcs_init: MCS routing control initialization failed.
With the tuning mixer file:
E ACDB-MCS: acdb_mcs_init: /vendor/etc/audio_tuning_mixer_tasha.txt not present, using /vendor/etc/audio_tuning_mixer.txt config file
D : [ACPH]->MCS RTC service registered with ACPH
Change-Id: I6e4b1fe27547a354eaa4132aba8e3df04d6184b3
Change-Id: I7c5b240b4dd5c4c4aa9c481b19405a63c8ad5d83
RiteshSaxena
force-pushed
the
lineage-15.1
branch
from
f30dff1 to
afefb71
Compare
Change-Id: I710a9dbc4e6c76a5bcb06bc88e67dd7951bc5bc6
Change-Id: I192df8cce8da2f2dd33928cf4fe560b94c6fe805
Change-Id: I71a9b4b2876b5384c00056ca3465523fed6d41a7
Test: mma -j BOARD_VNDK_VERSION=current Bug: 33241851 Change-Id: I603e86e78c80e592e852da184ca021fe42a8ea9a
Instead of relying on the global include paths, use the header libraries. Global include paths are not available when building with BOARD_VNDK_VERSION. pthread.h is included explicitly since it isn't automatically available then. Bug: 37342627 Test: BOARD_VNDK_VERSION=current m -j camera.msm8998 Change-Id: I210629684ff3451512e2dc4391f6718d5ebdd19b
Change-Id: I7d5de847faf39413290719b2f2d2dc7c56e703da
Changes to fix QCameraDisplay compilation issue. Change-Id: Iaa28e2b0acff0556d6052945e446066aa27be5b1
Change-Id: I6b2430f72c3959d8aec6e1710c10992b12cee11a
Change-Id: I83a57d669438cfaf22683efc90fae2d61ca484a0
Some interfaces are unable to directly communicate with the binderized power HAL, either due to compiler limitations, or proprietary limitations. Our camera HAL for one, is unable to utilize the required c++14 & gnu++1z syntax in order to communicate with the binderized interface as GCC 4.9 does not support them. To workaround this, add a legacy module that translates legacy methods and directs them to the new ones. In other words we're doing the opposite of android.hardware power@1.0-impl; ironic isn't it? Change-Id: I42192a52c57a4d4c9c052f3eebf9136837d1eb23
RiteshSaxena
force-pushed
the
lineage-15.1
branch
from
4a6d312 to
45cb7c7
Compare
AyraHikari
pushed a commit
to AyraHikari/android_device_xiaomi_land
that referenced
this pull request
Dec 31, 2018
[ Upstream commit c5a94f434c82529afda290df3235e4d85873c5b4 ] It was observed that a process blocked indefintely in __fscache_read_or_alloc_page(), waiting for FSCACHE_COOKIE_LOOKING_UP to be cleared via fscache_wait_for_deferred_lookup(). At this time, ->backing_objects was empty, which would normaly prevent __fscache_read_or_alloc_page() from getting to the point of waiting. This implies that ->backing_objects was cleared *after* __fscache_read_or_alloc_page was was entered. When an object is "killed" and then "dropped", FSCACHE_COOKIE_LOOKING_UP is cleared in fscache_lookup_failure(), then KILL_OBJECT and DROP_OBJECT are "called" and only in DROP_OBJECT is ->backing_objects cleared. This leaves a window where something else can set FSCACHE_COOKIE_LOOKING_UP and __fscache_read_or_alloc_page() can start waiting, before ->backing_objects is cleared There is some uncertainty in this analysis, but it seems to be fit the observations. Adding the wake in this patch will be handled correctly by __fscache_read_or_alloc_page(), as it checks if ->backing_objects is empty again, after waiting. Customer which reported the hang, also report that the hang cannot be reproduced with this fix. The backtrace for the blocked process looked like: PID: 29360 TASK: ffff881ff2ac0f80 CPU: 3 COMMAND: "zsh" #0 [ffff881ff43efbf8] schedule at ffffffff815e56f1 TeamReloaded#1 [ffff881ff43efc58] bit_wait at ffffffff815e64ed TeamReloaded#2 [ffff881ff43efc68] __wait_on_bit at ffffffff815e61b8 TeamReloaded#3 [ffff881ff43efca0] out_of_line_wait_on_bit at ffffffff815e625e TeamReloaded#4 [ffff881ff43efd08] fscache_wait_for_deferred_lookup at ffffffffa04f2e8f [fscache] #5 [ffff881ff43efd18] __fscache_read_or_alloc_page at ffffffffa04f2ffe [fscache] #6 [ffff881ff43efd58] __nfs_readpage_from_fscache at ffffffffa0679668 [nfs] #7 [ffff881ff43efd78] nfs_readpage at ffffffffa067092b [nfs] #8 [ffff881ff43efda0] generic_file_read_iter at ffffffff81187a73 #9 [ffff881ff43efe50] nfs_file_read at ffffffffa066544b [nfs] #10 [ffff881ff43efe70] __vfs_read at ffffffff811fc756 #11 [ffff881ff43efee8] vfs_read at ffffffff811fccfa #12 [ffff881ff43eff18] sys_read at ffffffff811fda62 #13 [ffff881ff43eff50] entry_SYSCALL_64_fastpath at ffffffff815e986e Signed-off-by: NeilBrown <neilb@suse.com> Signed-off-by: David Howells <dhowells@redhat.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.