CHERRY-PICK: BACKPORT: Bluetooth: Add support for Acer [13D3:3432]

Add support for the QCA6174 chip.

    T:  Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 30 Spd=12  MxCh= 0
    D:  Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
    P:  Vendor=13d3 ProdID=3432 Rev=00.02
    C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
    I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
    I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

BUG=chrome-os-partner:29640
TEST=manual: hciconfig to show device, hcitool scan to look for remote

Signed-off-by: Anantha Krishnan <ananthk@codeaurora.org>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
(cherry picked from commit fa2f1394fe9c1a217213f02df77812701de6362f)
Signed-off-by: Shan-Fu Chiou <shan-fu.chiou@intel.com>

Change-Id: I9de00a0543801f4b7ea90198e881842bfb3edc42
Original-Change-Id: Ie353912d03b7d97749987c7e8789550c9342e0bb
Reviewed-on: https://chromium-review.googlesource.com/209730
Tested-by: Shan-fu Chiou <shan-fu.chiou@intel.com>
Reviewed-by: Mohammed Habibulla <moch@google.com>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Shan-fu Chiou <shan-fu.chiou@intel.com>
storm: Introduce the device tree

Storm device tree is based on the ap148 device tree present in the
vendor branch. Both of the device trees are added here.

BUG=chromium:30705
TEST=with the rest of kernel and depthacharge patches, the 3.14 FIT
     image successfully boots on storm Proto0.

Change-Id: I4d3f2bfd23ccdd747fb9b2d64ca51cbce6466316
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/212882
Reviewed-by: Grant Grundler <grundler@chromium.org>
UPSTREAM: ARM: dts: Move the PMIC interrupt pinctrl line to rk3288-evb common

The PMIC interrupt pinctrl line was added to the rk3288-evb-act8846,
but it's the same line on both the ACT8846 version and the RK808
version.  This makes a lot of sense since they share the same SoC
daugherboard.  Move the pinctrl definition to the common file so we
can use it for the RK808 version.

NOTE: The PMIC interrupt doesn't _actually_ go to the PMIC on the
ACT8846 version of the board (it does on the RK808), but our
convention is to label things as they're labelled on the schematics.
In the very least you can argue that this is the interrupt from the
PMIC daughtercard even if it doesn't actually go to the PMIC chip.

BUG=chrome-os-partner:30167
TEST=Used by future change.

Change-Id: I7249b902f87a6e3c251a162ea9de5252c0f0cd3b
Signed-off-by: Doug Anderson <dianders@chromium.org>
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
(cherry picked from github.com/mmind/linux-rockchip/ wip/v3.18-next/dts
 commit e8e9a41d8c425c2c55074f2266dcd334a0f5bfde)
Reviewed-on: https://chromium-review.googlesource.com/211634
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
FROMLIST: Documentation: dt-bindings: add dt binding info for dwc2 dr_mode

Indicate that the generic dr_mode binding should be used for dwc2.

BUG=chrome-os-partner:30973
TEST=With series can use OTG port on pinky-rev1.

Change-Id: I4d63a838fa970504ce17535a1df34682037592c8
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Signed-off-by: Doug Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/4682701/)
FROMLIST: usb: dwc2: add 'mode' which based on Kconfig select or dts setting

According to the "dr_mode", the otg controller can work as
device role and host role. Some boards always want to use host mode
and some other boards want to use gadget mode. We use the dts setting
to set dwc2's mode, rather than fixing it to whatever hardware says.

BUG=chrome-os-partner:30973
TEST=With series can use OTG port on pinky-rev1.

Change-Id: I5f424ae6b80284468b53bd5544a8cac8cd2aae41
Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
Acked-by: Paul Zimmerman <paulz@synopsys.com>
Tested-by: Dinh Nguyen <dinguyen@opensource.altera.com>
Signed-off-by: Doug Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/4682711/)
ARM: dts: Turn on the OTG port on pinky-rev1

BUG=chrome-os-partner:30973
TEST=With series can use OTG port on pinky-rev1.

Change-Id: I760ba0864d5adae5896922a57e782c8f192caa4d
Signed-off-by: Doug Anderson <dianders@chromium.org>
Merge commit 'refs/changes/56/211856/6' of https://chromium.googlesource.com/a/chromiumos/third_party/kernel into ectool2

Conflicts:
	arch/arm/boot/dts/rk3288-pinky-rev1.dts

Change-Id: I6390d1adff071f870e64acd98bbf4d1bffa5b40e