fastboot: Add missing USB ID

Change-Id: I1616e9e6a57652aa919f979833c0e19479343966
adb/fastboot: Support SuperSpeed USB devices

When enumerating USB 3.0 devices, a 6-byte SuperSpeed companion
descriptor follows each standard descriptor. The ADB and Fastboot
Linux clients currently fail to interpret these additional
descriptors and simply bail. Fix this by skipping over them.

Change-Id: I254dad8ed81e8de74a4fac36e8ce54b5da9715fe
system: core: Fix a race condition leading to a fence deadlock

When SurfaceFlinger gets an event that needs a recomposition, it just
asks to be woken up on the next vsync. When it wakes up, it steps
through the list of layers acquiring the next available buffer for each
one (if any) and releasing the previous buffer. Because a new buffer
can become available for a layer asynchronously, it's possible that a
layer might not have a pending buffer when SurfaceFlinger starts
stepping through the list, but does have a pending buffer by the time
SurfaceFlinger gets to that layer.

Buffers incoming to SurfaceFlinger are accompanied by a fence that will
signal when rendering to the buffer is complete. Outgoing buffers are
accompanied by a fence that will signal when the display is done reading
from the buffer -- effectively, when the incoming buffer replaces the
outgoing buffer on screen.

All of that allows deadlock, though the timing and CPU scheduling
events that would cause it to happen are extremely unlikely.

Bug: 15347379
CRs-fixed: 647619
Change-Id: I76a5fc48b4b68a853c99f44a1570307da048b6a9
init: add more wifi firmware paths

Some devices' wifi firmware is under /data/misc/wifi.
Wlan module won't be loaded successfully if we don't change this.

Change-Id: Idcbd337c090acb86aefad8c6c69537c8ba8faec6
Signed-off-by: dianlujitao <dianlujitao@gmail.com>
system: core: Add Sensors group

Defining group for sensors.

CRs-Fixed: 431081

Change-Id: I58151f2fd727bded1b16adb3caeac85e27e44036
(cherry picked from commit 5d31680ee750ff6bae40c55175ad7ad6876d5774)
Revert "system: core: Add Sensors group"

This reverts commit d694815f0defca4c0f2c109611ae28470e7d3060.

Change-Id: I040a309671563c0db7162397ba10c33eebdc2f38
fs_mgr: support multiple file systems on a mount point
This is a combination of 3 commits pulled from Motorola's github for
allowing f2_mgr to have "fallback" handling for a mount point.  This
is most useful in the case of f2fs where some variants may be formatted
ext4 and some f2fs.  These device can now be supported in 1 fstab.

Example snippet of fstab.* for userdata mount point:
/dev/block/platform/msm_sdcc.1/by-name/userdata    /data        ext4    rw,discard,nosuid,nodev,noatime,nodiratime,noauto_da_alloc,nobarrier    wait,check,encryptable=footer
/dev/block/platform/msm_sdcc.1/by-name/userdata    /data        f2fs    rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr                 wait,encryptable=footer

Changes in logic ignore 1st failure as an automatic assumption of encryption.
Instead fstab is checked for another line describing mount point (2 retries)
Once all retries fail, encryption is assumed.

NOTE: Some logic was removed from the original sources: If userdata failed to mount
and was not encrypted a format of the filesystem was forced as a way of recovering
the device.  Most custom ROM users have access to recovery where they can decide
what to do in this case.

REFERENCE COMMITS:

IKJBMR2-6556: don't assume that mount failure implies encryption
MotorolaMobilityLLC/system-core@f3c3b19

fs_mgr: support multiple file systems on a mount point
MotorolaMobilityLLC/system-core@84ea2cd

fs_mgr: rename "recover_userdata" relic to join fs_mgr
MotorolaMobilityLLC/system-core@a4ef7c2

Change-Id: I682580d2a756bff4dba75760e0f117d95613e790
init: add a new charger-fs trigger in the power off charging mode

Add the charger-fs trigger and mount the charger file system earlier
than the propery service init in the power off charging mode.

Change-Id: Iecc0fcdabca836365d6822ca6ef9e0944258d687
healthd: increase healthd fast timer to 10mins instead of 1min

healthd 1 min wakeups are causing significant power impact
during static display use case. so increasing the timer to 10min.

Change-Id: If7a514e4152789144242e198175918b6687c3bcf

healthd: Disable the RTC wakeup timer

The timer is used here to avoid battery drained to zero. But the periodic
wakeup during suspend should not be needed as MSM PMIC already support
that by trigger interrupt to avoid the critical low battery situation.
This will save more power. And if the design is not support HW interrupt
of low battery, need to enable the timer to periodic check.

Change-Id: I040b4bc8548dc59b5e7cacb9a5a8a3557604f458
(cherry picked from commit 4a1b26bbaba823bbb13ca38bbb5e5f17b22c9db2)
(cherry picked from commit f61383a7688104668380caed7ba7197c5504e932)
Merge branch 'du44' of https://github.com/DirtyUnicorns-KitKat/system_core into HEAD