meizuosc/m75

This change is part of an effort to enable the installation
and running of .snap packages on the Ubuntu Phone. The Snappy
package format is soon moving to utilize a squashfs image per
package; installing such packages requires kernel support.

These config changes were copied from the trusty kernel, though
a few options weren't available and BCJ filter decoding was only
enabled for ARM. Still verified to work for the Snappy use-case.

Change-Id: I8d72b7910bd322b5c0700959109fe39e82ffec1f
Signed-off-by: Kyle Fazzari <kyle@canonical.com>

== For publish kernel ==

sync the latest code in 2015-12-17

kernel: 201674ff4ebf1b94bcce2a0f95a286b7da714bc5
mediatek: 1b3457489b21524f92597c92afea9ba931199897

Change-Id: I3b5b7612ae5101d053d17318ad969d2354a16e75

The FORM_FACTOR variable will be used for different aspects in the
system where we need to find out what kind of device we're running
on. One of the first things which will use this is the Bluetooth
subsystem in order to determine which class of device we have to
set for the device it's running on.

This also renames the file stored in repo to its proper name
android.conf as which it is install as later on.

Change-Id: Ida0f12ca71f9cac3d5a0b83134c9d85e253ae580
Signed-off-by: Simon Fels <simon.fels@canonical.com>

* disable old bluetooth stack
* enable backports integration layer and newer bluetooth stack
* enable all dependencies for the bluetooth stack
* enable HCI STP driver

Change-Id: I713aadd9e8cb5825a83bd016142d15dc6a2fd01d
Signed-off-by: Simon Fels <simon.fels@canonical.com>

The global variables uibckbd and uibc_input_dev have been allocated in probe
function, it's not needed to reallocate them in open fucntion.

Change-Id: I2821a5153d7953b7cdc60b4ea7e50fb11e5069aa
Signed-off-by: Liming Wang <liming.wang@canonical.com>

Change-Id: I7c92b5c46a371c0795161579a77dd3026e19dafd
Signed-off-by: Liming Wang <liming.wang@canonical.com>

Based on the request from LP#1462917.

Change-Id: I37e9a416de24cf042205d98c89cf0ca61df81ecc

…004. Patched by Meizu.

Change-Id: I748c7aa4e97a8af4a834068facd2ba08d9e06139
Signed-off-by: Chunsang Jeong <chunsang.jeong@canonical.com>

The wait sequence for STP was added to be able to run the driver as a
kernel module rather than bundling it only within the kernel. This
doesn't work well and prevent us from enabling bluetooth when booting
with the WiFi driver being unloaded.

Change-Id: I2afececd5f6c44796cca77b3ce7c8a37174859ab
Signed-off-by: Simon Fels <simon.fels@canonical.com>

Some chips seem to report a different maximum page number than they
allow us to read. Therfor we check for the status code after each
read and skip those reporting out-of-range reads.

Change-Id: Ifd35b1e1e61df855ffd3f6d29b540701986cf229
Signed-off-by: Simon Fels <simon.fels@canonical.com>

With 9380f9eacfbbee701daa416edd6625efcd3e29e1 the order of unsetting
the HCI_USER_CHANNEL flag of the HCI device was reverted to ensure
the device is first closed before making it available again.

Due to hci_dev_close checking for HCI_USER_CHANNEL being set on the
device it was never really closed and was kept opened. We're now
calling hci_dev_do_close directly to make sure the device is correctly
closed and we keep the correct order to unset the flag on our device
object.

Signed-off-by: Simon Fels <simon.fels@canonical.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
(cherry picked from bluetooth-next 4c63f83c2c2e16a13ce274ee678e28246bd33645)
BugLink: http://bugs.launchpad.net/bugs/1489327

Change-Id: Ic9ec7560d631ee1d0f56d942d134290ab2e5f0fc

The HCI_OP_GET_MWS_TRANSPORT_CONFIG command isn't properly handled by
the BT chip and causes our BT initialization to fail. To workaround
this we're not sending this command for now as MWS isn't used anywhere
yet.

Change-Id: If370a35c8691fa0abb9b4370b36efae15875ccb9
Signed-off-by: Simon Fels <simon.fels@canonical.com>

Adjusted driver code where needed to fit the changed APIs for the BT
management stack.

Change-Id: Ib9d2397f65cd9f6ca8b9be3364a4bf65ff10e4d5
Signed-off-by: Simon Fels <simon.fels@canonical.com>

backports tree was automatically generated and integrated with the following command:

$ ./gentree.py --integrate --clean --git-revision v4.2-rc7 \
    <path>/linux-next <path>/linux-mako

(we're using a slightly modified backports tree to adjust every export automatically for
 our needs).

See https://backports.wiki.kernel.org/index.php/Documentation/integration for
documentation and https://github.com/ubuntu-phonedations/backports for the used backports
tree.

All uncessary parts (bcma, wifi, nfc etc.) were dropped and just the bluetooth relevant
parts are kept.

BugLink: http://bugs.launchpad.net/bugs/1489327

Change-Id: Ic32b3b2299a29cf260bf243f7b6cc10e77dd7d93
Signed-off-by: Simon Fels <simon.fels@canonical.com>
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>

Th AF_ALG socket was missing a security label (e.g. SELinux)
which means that socket was in "unlabeled" state.

This was recently demonstrated in the cryptsetup package
(cryptsetup v1.6.5 and later.)
See https://bugzilla.redhat.com/show_bug.cgi?id=1115120

This patch clones the sock's label from the parent sock
and resolves the issue (similar to AF_BLUETOOTH protocol family).

Change-Id: I7e2bf6fcefcbf6910312eb2139132e6294c2d0ff
Cc: stable@vger.kernel.org
Signed-off-by: Milan Broz <gmazyland@gmail.com>
Acked-by: Paul Moore <paul@paul-moore.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

Signed-off-by: MEIZU <patchwork@meizu.com>

Signed-off-by: MEIZU <patchwork@meizu.com>

Signed-off-by: MEIZU <patchwork@meizu.com>