The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/ddd4280ea57743ab40ead63ab62a1dc4367757e5

commit ddd4280ea57743ab40ead63ab62a1dc4367757e5
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:05:44 2018

FROMGIT: phy: qcom-qusb2: Power-on PHY before initialization

PHY must be powered on before turning ON clocks and
attempting to initialize it. Driver is exposing
separate init and power_on routines for this.
Apparently USB dwc3 core driver performs power-on
after init. Also, poweron and init for QUSB2 PHY
need to be executed together always, hence remove
poweron callback from phy_ops and explicitly perform
this from init, similar changes needed for poweroff.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Reviewed-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 28adbcb441152db9d5f4f2a540b5a71294e3944b
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I2f5710eb910f727e7c18f5a0f5f401845f350c43
Reviewed-on: https://chromium-review.googlesource.com/932836
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/ddd4280ea57743ab40ead63ab62a1dc4367757e5/drivers/phy/qualcomm/phy-qcom-qusb2.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3f414bedc977dcdf5f716ce2b355a8b6949728e8

commit 3f414bedc977dcdf5f716ce2b355a8b6949728e8
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:05:47 2018

FROMGIT: phy: qcom-qmp: Fix PHY block reset sequence

PHY block or asynchronous reset requires signal
to be asserted before de-asserting. Driver is only
de-asserting signal which is already low, hence
reset operation is a no-op. Fix this by asserting
signal first. Also, resetting requires PHY clocks
to be turned ON only after reset is finished. Fix
that as well.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Reviewed-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit e847d29d5c77d2ef3e57956cea65600b70457fe3
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: Ic7344eb87e8413cd11d1f12278b333f07c3b1a83
Reviewed-on: https://chromium-review.googlesource.com/932837
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/3f414bedc977dcdf5f716ce2b355a8b6949728e8/drivers/phy/qualcomm/phy-qcom-qmp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/2c12a73cf2d3f0251f294386c53f3c500e485abc

commit 2c12a73cf2d3f0251f294386c53f3c500e485abc
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:05:49 2018

FROMGIT: phy: qcom-qmp: Move SERDES/PCS START after PHY reset

Driver is currently performing PHY reset after starting
SERDES/PCS. As per hardware datasheet reset must be done
before starting PHY. Hence, update the sequence.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 73fa3b10838602b8d779d69c14a82c0e0fa469b2
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I0701c797f8d87407a2b6030b14442b1c246bf20f
Reviewed-on: https://chromium-review.googlesource.com/932838
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/2c12a73cf2d3f0251f294386c53f3c500e485abc/drivers/phy/qualcomm/phy-qcom-qmp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/a45adef1cfb94e5af9d2bd485257cb0df5c9389b

commit a45adef1cfb94e5af9d2bd485257cb0df5c9389b
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:05:52 2018

FROMGIT: phy: qcom-qusb2: Add support for different register layouts

New version of QUSB2 PHY has some registers offset changed.
Add support to have register layout for a target and update
the same in phy_configuration.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Reviewed-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 48be0cf13bdbcdbd3575f6e740e2b5c50b0f1f13
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I5eaf3353b8700f8d0270edbd64bce5364aaa04fd
Reviewed-on: https://chromium-review.googlesource.com/932839
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/a45adef1cfb94e5af9d2bd485257cb0df5c9389b/drivers/phy/qualcomm/phy-qcom-qusb2.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7319f15b48cc9a9dcad88506f0a390697494caa8

commit 7319f15b48cc9a9dcad88506f0a390697494caa8
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:05:54 2018

FROMGIT: dt-bindings: phy-qcom-qusb2: Update binding for QUSB2 V2 version

Update generic compatible string for QUSB2 V2 PHY. This will allow
all targets using QUSB2 V2 use same string.

Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Reviewed-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 3d3704a9ca84905bd084747be4cfcd17574d2294
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I779bd2d8fa28407bfe2265a09b080e75a7f50b36
Reviewed-on: https://chromium-review.googlesource.com/932840
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/7319f15b48cc9a9dcad88506f0a390697494caa8/Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/c0c2c67b36c0237c5b5b27669f0bffd18e84d555

commit c0c2c67b36c0237c5b5b27669f0bffd18e84d555
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:05:57 2018

FROMGIT: phy: qcom-qusb2: Add support for QUSB2 V2 version

Use register layout to add additional registers present
on QUSB2 PHY V2 version for PHY initialization.
Other than new registers on V2, following two register's
offset and bit definitions are different: POWERDOWN control
and PLL_STATUS.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Reviewed-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 89b9a084c796a210ca7c303606b639131a1fd13c
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I34e33b782d3be5d6d3f15fc8f444567e7a0e4cb4
Reviewed-on: https://chromium-review.googlesource.com/932901
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/c0c2c67b36c0237c5b5b27669f0bffd18e84d555/drivers/phy/qualcomm/phy-qcom-qusb2.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/46d2a56408526a7b3a71405e28998dff7d0952e0

commit 46d2a56408526a7b3a71405e28998dff7d0952e0
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:06:00 2018

FROMGIT: phy: qcom-qmp: Move register offsets to header file

New revision (v3) of QMP PHY uses different offsets
for almost all of the registers. Hence, move these
definitions to header file so that updated offsets
can be added for QMP v3.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Reviewed-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 2f64fe9bca422a82d055267d2223e701ea73c6a9
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I56b2610e6b5351f310ce9b4134afbf47ba62df44
Reviewed-on: https://chromium-review.googlesource.com/932902
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/46d2a56408526a7b3a71405e28998dff7d0952e0/drivers/phy/qualcomm/phy-qcom-qmp.c
[add] https://crrev.com/46d2a56408526a7b3a71405e28998dff7d0952e0/drivers/phy/qualcomm/phy-qcom-qmp.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e790bb55659debd23c8304b73b4655e43ff7c422

commit e790bb55659debd23c8304b73b4655e43ff7c422
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:06:02 2018

FROMGIT: phy: qcom-qmp: Add register offsets for QMP V3 PHY

Registers offsets for QMP V3 PHY are changed from
previous versions (1/2), update same in header file.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 77ff7ceb8ffe4a50b7e30dcbcb7bbfadcd6b8526
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I293774b3c3408b2bf54ce2f1ed0b21a046e0f77f
Reviewed-on: https://chromium-review.googlesource.com/932903
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/e790bb55659debd23c8304b73b4655e43ff7c422/drivers/phy/qualcomm/phy-qcom-qmp.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/cdc5524d9c514b6d4b058d705a7fafd1001e2c69

commit cdc5524d9c514b6d4b058d705a7fafd1001e2c69
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:06:05 2018

FROMGIT: dt-bindings: phy-qcom-qmp: Update bindings for QMP V3 USB PHY

Update compatible string and clock names for QMP version V3
USB PHY.

Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 3136d6cd69791c804c3f276163eccbead25c7acc
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I4ad8db7309120a75d0f0124cb19a2742da9a8e9a
Reviewed-on: https://chromium-review.googlesource.com/932904
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/cdc5524d9c514b6d4b058d705a7fafd1001e2c69/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/c80e03d8b920ae444f9eefea103957c69ac81353

commit c80e03d8b920ae444f9eefea103957c69ac81353
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:06:07 2018

FROMGIT: phy: qcom-qmp: Add support for QMP V3 USB3 PHY

QMP V3 USB3 PHY is a DisplayPort (DP) and USB combo PHY
with dual RX/TX lanes to support type-c. There is a
separate block DP_COM for configuration related to type-c
or DP. Add support for dp_com region and secondary rx/tx
lanes initialization.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 198889e1e935d8c473dab6901553318c9546103f
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I842f91c9ea47e8422462e705ea99c938f72d03d5
Reviewed-on: https://chromium-review.googlesource.com/932905
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/c80e03d8b920ae444f9eefea103957c69ac81353/drivers/phy/qualcomm/phy-qcom-qmp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/4f809d6101c3dee3411e1d668e814bd7a8b927bd

commit 4f809d6101c3dee3411e1d668e814bd7a8b927bd
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:06:10 2018

FROMGIT: phy: Add USB speed related PHY modes

Add following USB speed related PHY modes:
LS (Low Speed), FS (Full Speed), HS (High Speed), SS (Super Speed)

Speed related information is required by some QCOM PHY drivers
to program PHY monitor resume/remote-wakeup events in suspended
state. Speed is needed in order to set correct polarity of wakeup
events for detection. E.g. QUSB2 PHY monitors DP/DM line state
depending on whether speed is LS or FS/HS to detect resume.
Similarly QMP USB3 PHY in SS mode should monitor RX terminations
attach/detach and LFPS events depending on SSPHY is active or not.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit c152626b720210bc17b4047906b47a46eda9dd78
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I4e7985acba59aba1b65d8c7e4478b333fa009a75
Reviewed-on: https://chromium-review.googlesource.com/932906
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/4f809d6101c3dee3411e1d668e814bd7a8b927bd/drivers/phy/phy-core.c
[modify] https://crrev.com/4f809d6101c3dee3411e1d668e814bd7a8b927bd/include/linux/phy/phy.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7997424084070f55f8cfa65d8f801f80695c9bb0

commit 7997424084070f55f8cfa65d8f801f80695c9bb0
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:06:12 2018

FROMGIT: phy: qcom-qusb2: Add support for runtime PM

Disable clocks and enable DP/DM wakeup interrupts when
suspending PHY.
Core driver should notify speed to PHY driver to enable
appropriate DP/DM wakeup interrupts polarity in suspend state.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 016430b1bf3ae0e5ec3b4bb857e273df4c717b5f
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I756dc9531071c091ec1d8e27fdd887203b0501c3
Reviewed-on: https://chromium-review.googlesource.com/932907
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/7997424084070f55f8cfa65d8f801f80695c9bb0/drivers/phy/qualcomm/phy-qcom-qusb2.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/437ebc2ac8b13a057baaeb67a29edbc4b67c83f4

commit 437ebc2ac8b13a057baaeb67a29edbc4b67c83f4
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:06:15 2018

FROMGIT: phy: qcom-qmp: Add support for runtime PM

Disable clocks and enable PHY autonomous mode to detect
wakeup events when PHY is suspended.
Core driver should notify speed to PHY driver to enable
LFPS and/or RX_DET interrupts.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit 40f3663cc08a03eb6944d5edd7acb0cc4d5aec96
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I5516bf6d55dd2024749986e7855e697abc4e989a
Reviewed-on: https://chromium-review.googlesource.com/932908
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/437ebc2ac8b13a057baaeb67a29edbc4b67c83f4/drivers/phy/qualcomm/phy-qcom-qmp.c
[modify] https://crrev.com/437ebc2ac8b13a057baaeb67a29edbc4b67c83f4/drivers/phy/qualcomm/phy-qcom-qmp.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/2aa9cc0656573e94a218125247537cf527550448

commit 2aa9cc0656573e94a218125247537cf527550448
Author: Manu Gautam <mgautam@codeaurora.org>
Date: Sat Feb 24 05:06:17 2018

FROMGIT: phy: add SPDX identifier to QMP and QUSB2 PHY drivers

The SPDX identifier is a legally binding shorthand, which
can be used instead of the full boiler plate text.

Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(cherry picked from commit e1e5420e0b3d7af86afcb6de7b3c5a6bf2787ab6
 https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next)
Change-Id: I1aef2fb3937b1ec2996621be250cb0d38831e7e0
Reviewed-on: https://chromium-review.googlesource.com/932909
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/2aa9cc0656573e94a218125247537cf527550448/drivers/phy/qualcomm/phy-qcom-qusb2.c
[modify] https://crrev.com/2aa9cc0656573e94a218125247537cf527550448/drivers/phy/qualcomm/phy-qcom-qmp.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/d141fda9a7c65d3ff92895cf805c66992a89d862

commit d141fda9a7c65d3ff92895cf805c66992a89d862
Author: Guenter Roeck <groeck@chromium.org>
Date: Sat Feb 24 05:06:51 2018

FIXUP: CHROMIUM: FROMLIST: tty: serial: msm_geni_serial: Add serial driver support for GENI based QUP

uart_console_device is not exported, and it is not supposed
to be exported since a console has to be available before
modules are loaded. Building the driver as module results
in a link error. Make the driver bool.

BUG=chromium:795946
TEST=Build and boot

Change-Id: Id54c5737b537f791a5071c5257d6423d43915f85
Signed-off-by: Guenter Roeck <groeck@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/934881
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/d141fda9a7c65d3ff92895cf805c66992a89d862/drivers/tty/serial/Kconfig

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7cc918446ca52a1b7448b131085e1ab88d0bf997

commit 7cc918446ca52a1b7448b131085e1ab88d0bf997
Author: Guenter Roeck <groeck@chromium.org>
Date: Tue Feb 27 03:28:41 2018

FIXUP: CHROMIUM: FROMLIST: soc: qcom: Add GENI based QUP Wrapper driver

Since commit d141fda9a7c6 ("FIXUP: CHROMIUM: FROMLIST: tty: serial:
msm_geni_serial: Add serial driver support for GENI based QUP"),
the QCOM serial driver is always built into the kernel. Since it depends
on QCOM_GENI_SE, it does not make sense to have QCOM_GENI_SE buildable
as module. Make it bool as well to avoid undefined references such as

qcom_geni_serial.c:(.text+0x1d0): undefined reference to `geni_read_reg_nolog'
qcom_geni_serial.c:(.text+0x804): undefined reference to `geni_se_resources_on'
qcom_geni_serial.c:(.text+0x820): undefined reference to `geni_se_resources_off'
qcom_geni_serial.c:(.text+0x91c): undefined reference to `geni_write_reg_nolog'

BUG=chromium:795946
TEST=Build arm64:allmodconfig

Change-Id: I2aa9c63676e6328e52167a6c7b6669c49ba177f0
Signed-off-by: Guenter Roeck <groeck@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/938156
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/7cc918446ca52a1b7448b131085e1ab88d0bf997/drivers/soc/qcom/Kconfig
[modify] https://crrev.com/7cc918446ca52a1b7448b131085e1ab88d0bf997/include/linux/qcom-geni-se.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/5c7b7a877a5380055bbc92270fb3e03fb3ce21b7

commit 5c7b7a877a5380055bbc92270fb3e03fb3ce21b7
Author: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Date: Tue Feb 27 20:09:03 2018

UPSTREAM: remoteproc: qcom: Fix error handling paths in order to avoid memory leaks

In case of error returned by 'q6v5_xfer_mem_ownership', we must free
some resources before returning.

In 'q6v5_mpss_init_image()', add a new label to undo a previous
'dma_alloc_attrs()'.
In 'q6v5_mpss_load()', re-use the already existing error handling code to
undo a previous 'request_firmware()', as already done in the other error
handling paths of the function.

Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

(cherry picked from commit 1a5d5c592e902191bfa091ec9169aa43299a7d0f)
Signed-off-by: Ben Chan <benchan@chromium.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ic890a64ae59f28948bfe6ff9fb087793fbf56663
Reviewed-on: https://chromium-review.googlesource.com/938568
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/5c7b7a877a5380055bbc92270fb3e03fb3ce21b7/drivers/remoteproc/qcom_q6v5_pil.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/760fb4c6a2b6057c3182d891ea977c32bf5ddc28

commit 760fb4c6a2b6057c3182d891ea977c32bf5ddc28
Author: Evan Green <evgreen@chromium.org>
Date: Thu Mar 01 05:30:14 2018

chiset-qc845: Set real kernel splitconfig

This change activates the real kernel splitconfig for Cheza.

BUG=chromium:795946
TEST=build and boot cheza

Change-Id: I6589bc5b74552241ab346e2ba936e73097744c1b
Reviewed-on: https://chromium-review.googlesource.com/887921
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/760fb4c6a2b6057c3182d891ea977c32bf5ddc28/chipset-qc845/profiles/base/make.defaults

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/1e7b26c569967771f2bee407982d050de3014993

commit 1e7b26c569967771f2bee407982d050de3014993
Author: Douglas Anderson <dianders@chromium.org>
Date: Thu Mar 01 07:54:25 2018

CHROMIUM: config: More SDM845 configs that can land today

These configs will all be needed for SDM845 and can already land
today.  This normalization was produced with:

 cat <<EOF | tee -a \
   chromeos/config/arm64/chromiumos-arm64.flavour.config \
   chromeos/config/arm64/chromiumos-qualcomm.flavour.config

 CONFIG_ARM_SMMU=y

 CONFIG_SPMI=y
 CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
 CONFIG_MFD_SPMI_PMIC=y

 CONFIG_DRM_MSM=y
 # CONFIG_DRM_MSM_DSI is not set
 # CONFIG_DRM_MSM_HDMI_HDCP is not set

 CONFIG_PHY_QCOM_QMP=y
 CONFIG_PHY_QCOM_QUSB2=y

 CONFIG_USB_DWC3_OF_SIMPLE=y

 CONFIG_SCSI_UFSHCD=y
 CONFIG_SCSI_UFSHCD_PLATFORM=y
 CONFIG_SCSI_UFS_QCOM=y

 CONFIG_QCOM_QFPROM=y

 EOF
 ./chromeos/scripts/kernelconfig olddefconfig

======

Justification below:

 CONFIG_ARM_SMMU=y

==> SMMU in SDM845 is v2, which needs this driver.

 CONFIG_SPMI=y
 CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
 CONFIG_MFD_SPMI_PMIC=y

==> In "sdm845.dtsi" in CAF I see "qcom,spmi-pmic-arb"

 CONFIG_DRM_MSM=y
 # CONFIG_DRM_MSM_DSI is not set
 # CONFIG_DRM_MSM_HDMI_HDCP is not set

==> We want to enable MSM graphics, but for now _not_ turning on
==> DRM_MSM_DSI (even though it's default=y).  In CAF tree we use some
==> other DRM_MSM_DSI_STAGING config anyway and if we turn on
==> DRM_MSM_DSI then suddenly lots of PHYs get turned on by default.
==> For DRM_MSM_HDMI_HDCP, leaving it off until someone says we need it.

 CONFIG_PHY_QCOM_QMP=y
 CONFIG_PHY_QCOM_QUSB2=y

==> These PHYs are used for USB2/3 in SDM845.

 CONFIG_USB_DWC3_OF_SIMPLE=y

==> QC845 uses DWC3 and uses this config.

 CONFIG_SCSI_UFSHCD=y
 CONFIG_SCSI_UFSHCD_PLATFORM=y
 CONFIG_SCSI_UFS_QCOM=y

==> SDM845 uses CONFIG_SCSI_UFS_QCOM

 CONFIG_QCOM_QFPROM=y

==> Yeah, we've got an QFPROM

BUG=chromium:795946
TEST=Build and boot

Change-Id: I7892ede1dc7f1b355e67c18b41d6e0662812aa2d
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/942232
Reviewed-by: Evan Green <evgreen@chromium.org>

[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/arm64/chromiumos-arm64.flavour.config
[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/armel/common.config
[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/arm64/common.config
[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/arm64/chromiumos-mediatek.flavour.config
[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/base.config
[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/i386/common.config
[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/arm64/chromiumos-rockchip64.flavour.config
[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/x86_64/common.config
[modify] https://crrev.com/1e7b26c569967771f2bee407982d050de3014993/chromeos/config/arm64/chromiumos-qualcomm.flavour.config

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/146ac81388f9a8e411bcf9da5ec5165870d2c181

commit 146ac81388f9a8e411bcf9da5ec5165870d2c181
Author: Douglas Anderson <dianders@chromium.org>
Date: Fri Mar 02 03:13:57 2018

FIXUP: FROMLIST: arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP

Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files

Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>

BUG=chromium:795946
TEST=Build and boot

NOTE: this is equivalent to a revert of commit e3385126ab50
("FROMLIST: arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845
SoC and MTP"), which is from v4 of the series, squashed together with
a pick of the v5 version.  Thus this commit fixes us up to match
what's posted in v5.  Link below is the post of v5.

Change-Id: I7369c58cb7a4a5c259339b3089fb694f231dcb78
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/10234697/)
Reviewed-on: https://chromium-review.googlesource.com/931746
Reviewed-by: Evan Green <evgreen@chromium.org>

[modify] https://crrev.com/146ac81388f9a8e411bcf9da5ec5165870d2c181/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/a3a329f59031a2d72b132ba4b5b131426bcd2117

commit a3a329f59031a2d72b132ba4b5b131426bcd2117
Author: Feng Kan <fkan@apm.com>
Date: Tue Mar 06 22:38:50 2018

UPSTREAM: iommu/arm-smmu: Enable bypass transaction caching for ARM SMMU 500

The ARM SMMU identity mapping performance was poor compared with the
DMA mode. It was found that enable caching would restore the performance
back to normal. The S2CRB_TLBEN bit in the ACR register would allow for
caching of the stream to context register bypass transaction information.

Reviewed-by: Robin Murphy <robin.murphy@arm.com>
Signed-off-by: Feng Kan <fkan@apm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>

(cherry picked from commit 74f55d34414c866dbf3a69e28a2f963abe61ca58)

BUG=chromium:795946
TEST=Build and boot

Change-Id: I074a9d887421e93cf8f97e318e537355a8b9d56e
Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Reviewed-on: https://chromium-review.googlesource.com/914662
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>

[modify] https://crrev.com/a3a329f59031a2d72b132ba4b5b131426bcd2117/drivers/iommu/arm-smmu.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/f7ab3cd5b8572b1f3fe5e2baf6c0e4cd8d9bf839

commit f7ab3cd5b8572b1f3fe5e2baf6c0e4cd8d9bf839
Author: Jordan Crouse <jcrouse@codeaurora.org>
Date: Tue Mar 06 22:38:52 2018

UPSTREAM: iommu: Check the result of iommu_group_get() for NULL

The result of iommu_group_get() was being blindly used in both
attach and detach which results in a dereference when trying
to work with an unknown device.

Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>

(cherry picked from commit 9ae9df035c274c89b7fe3dbc74cbe2fa63386668)

BUG=chromium:795946
TEST=Build and boot

Change-Id: Icef8f354e0e6bdc738f12a756f67d5ee8e8b7915
Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
Reviewed-on: https://chromium-review.googlesource.com/914663
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>

[modify] https://crrev.com/f7ab3cd5b8572b1f3fe5e2baf6c0e4cd8d9bf839/drivers/iommu/iommu.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e00a213e66188c3cbcaecd91d0d95591dbd43633

commit e00a213e66188c3cbcaecd91d0d95591dbd43633
Author: Douglas Anderson <dianders@chromium.org>
Date: Mon Mar 12 22:24:47 2018

FIXUP: FROMLIST: arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP

Add a skeletal sdm845 SoC dtsi and MTP board dts/dtsi files

Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>

BUG=chromium:795946
TEST=In CAF tree things work better now

NOTE: this gets up to v7 of the patch posted to list.  Previously we
were up to v5.  This was created by doing a revert of these three
patches:
  - 146ac81388f9 ("FIXUP: FROMLIST: arm64: dts: sdm845: Add minimal
    dts/dtsi files for sdm845 SoC and MTP")
  - 44c67616678e ("CHROMIUM: FROMLIST: arm64: dts: sdm845: Add serial
    console support")
  - e3385126ab50 ("FROMLIST: arm64: dts: sdm845: Add minimal dts/dtsi
    files for sdm845 SoC and MTP")
...then pick the new patch.  Then squash it with the revert of
e3385126ab50.  Then rebase -i and get rid of the revert of
44c67616678e.  Then finally squash it with the revert of
146ac81388f9.  Whew!  Patchwork link below is the v7 patch.

Change-Id: Icd61bf0be5d7390c78e9822ad47658a38f6c2064
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/10276419/)
Reviewed-on: https://chromium-review.googlesource.com/957473
Reviewed-by: Evan Green <evgreen@chromium.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>

[modify] https://crrev.com/e00a213e66188c3cbcaecd91d0d95591dbd43633/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/2bed422da47dbedecf88ed0885d865fa59857702

commit 2bed422da47dbedecf88ed0885d865fa59857702
Author: Douglas Anderson <dianders@chromium.org>
Date: Tue Mar 20 02:21:43 2018

CHROMIUM: config: turn on CONFIG_I2C_CHARDEV for Qualcomm

This was left off, but it's on everywhere else and Chrome OS expects
it in general.

NOTE: some boards have this as "=m" and others "=y".  In general "=m"
is preferred unless there's some urgent need for it to be "=y", like
if we need to do an I2C-based firmware device at bootup.  See
CL:422907 and CL:366000 as examples.

This is the equivalent of:
  echo 'CONFIG_I2C_CHARDEV=m' >> \
    chromeos/config/arm64/chromiumos-qualcomm.flavour.config
  ./chromeos/scripts/kernelconfig olddefconfig

...atop an already normalized config.

BUG=chromium:795946
TEST=Boot and "modprobe i2c-dev"; can use "i2cdetect"

Change-Id: I07911683f2ae7b0b17457fed53ee0451c98aa7e2
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/969594
Reviewed-by: Guenter Roeck <groeck@chromium.org>

[modify] https://crrev.com/2bed422da47dbedecf88ed0885d865fa59857702/chromeos/config/arm64/chromiumos-qualcomm.flavour.config

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/9ddbb671702048ebb8fd35e3eb3b38bfea2c592e

commit 9ddbb671702048ebb8fd35e3eb3b38bfea2c592e
Author: Wai-Hong Tam <waihong@google.com>
Date: Thu Apr 19 08:13:02 2018

servo: Deprecate the driver of rec_mode which sends EC host command

This driver also made us hard to repurpose the rec_mode for bring-up.

Found out this rec_mode driver in arm_ec_common.xml should be
deprecated. We no longer calls this driver to trigger recovery mode.
Instead, we call another abstraction power_state:rec.

I searched through the power_state drivers, the ones access the
rec_mode control doesn't use this arm_ec way (they access the native
servo pin). So it is safe to remove the arm_ec driver.

BUG=chromium:795946
TEST=Started servod on several ARM boards without error.

Change-Id: I541d77b46f9169a3f911ed693b492e36b082186e
Reviewed-on: https://chromium-review.googlesource.com/1018116
Commit-Ready: Wai-Hong Tam <waihong@google.com>
Tested-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Reviewed-by: Todd Broch <tbroch@chromium.org>

[delete] https://crrev.com/e8a9713f1375f776403b16b92094eba9bb896cf5/servo/drv/arm_ec.py
[modify] https://crrev.com/9ddbb671702048ebb8fd35e3eb3b38bfea2c592e/servo/data/arm_ec_common.xml
[modify] https://crrev.com/9ddbb671702048ebb8fd35e3eb3b38bfea2c592e/servo/drv/__init__.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/05660b480be56154ebfdcd6a95a506f5a259dbf3

commit 05660b480be56154ebfdcd6a95a506f5a259dbf3
Author: Rajendra Nayak <rnayak@codeaurora.org>
Date: Fri Apr 20 07:33:07 2018

CHROMIUM: arm64: dts: qcom: Add sdm845-cheza

This adds initial skeleton support for sdm845-cheza.  For now we just
enable serial.

BUG=chromium:795946
TEST=Use this dts on caf branch; force coreboot to use; can boot

Change-Id: Ic5af3aee8543cc3327ee95c53b4b37ec04b8cd03
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1016215
Reviewed-by: Stephen Boyd <swboyd@chromium.org>

[modify] https://crrev.com/05660b480be56154ebfdcd6a95a506f5a259dbf3/arch/arm64/boot/dts/qcom/Makefile
[add] https://crrev.com/05660b480be56154ebfdcd6a95a506f5a259dbf3/arch/arm64/boot/dts/qcom/sdm845-cheza.dts

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/81ac3e7984d797bd58395441098c5e0efd489280

commit 81ac3e7984d797bd58395441098c5e0efd489280
Author: Douglas Anderson <dianders@chromium.org>
Date: Fri Apr 20 19:57:22 2018

servo: Add initial Cheza overlay

BUG=chromium:795946
TEST=Manually started servod on servo-v4 and servo-v4 with servo-micro.
Tried dut-control to change cpu_boot_mode:sd and cpu_boot_mode:spi.

Change-Id: I2072078270d0c43e1ff5c729e666c7ddf9abaf72
Reviewed-on: https://chromium-review.googlesource.com/1008638
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Wai-Hong Tam <waihong@google.com>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@google.com>

[modify] https://crrev.com/81ac3e7984d797bd58395441098c5e0efd489280/servo/servo_interfaces.py
[add] https://crrev.com/81ac3e7984d797bd58395441098c5e0efd489280/servo/data/servo_cheza_overlay.xml

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/29db96db835e89d1d37955281b6f07b2ed7d5246

commit 29db96db835e89d1d37955281b6f07b2ed7d5246
Author: Stephen Boyd <swboyd@chromium.org>
Date: Thu Apr 26 06:00:50 2018

servod: cheza: Fix servod startup on v2 boards

Running "servod --board cheza_r0" fails because it's like cheza and
needs to be part of the jtag repurposing list. Add it so things work
again.

BUG=chromium:795946
TEST=Manually started servod on servo-v2

Change-Id: Ie9e86afcf54488ddbed69b33963e3a5c5b59d283
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1025328
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@google.com>

[modify] https://crrev.com/29db96db835e89d1d37955281b6f07b2ed7d5246/servo/servo_interfaces.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/2abc16b934adcea80c2b537e44fb870203745ef7

commit 2abc16b934adcea80c2b537e44fb870203745ef7
Author: Jitendra Sharma <shajit@codeaurora.org>
Date: Thu Apr 26 20:00:34 2018

UPSTREAM: remoteproc: Remove null character write of shared mem

remoteproc is writing '\0' in the shared mem region. This
region is shared among multiple clients that are also trying
to read. Hence they miss first character.

Remove this null character write, as this mem area is
supposed to be Read only.

Further during every subsystem reboot, this region is
initialized with default, hence no need to write this
region.

Signed-off-by: Jitendra Sharma <shajit@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ifcb8766def0490c953f726c7ed43342feda07b33
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 2d02d158047643060b7d6e0829fcc81518ce663d)
Reviewed-on: https://chromium-review.googlesource.com/1016186
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/2abc16b934adcea80c2b537e44fb870203745ef7/drivers/remoteproc/qcom_adsp_pil.c
[modify] https://crrev.com/2abc16b934adcea80c2b537e44fb870203745ef7/drivers/remoteproc/qcom_wcnss.c
[modify] https://crrev.com/2abc16b934adcea80c2b537e44fb870203745ef7/drivers/remoteproc/qcom_q6v5_pil.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/70042f5bf9d3627249dac0d13aa3a7e5ede52ff7

commit 70042f5bf9d3627249dac0d13aa3a7e5ede52ff7
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:36 2018

UPSTREAM: remoteproc: Remove depricated crash completion

The crash handling now happens in a single execution context, so there's
no longer a need for a completion to synchronize this.

Reviewed-By: Loic Pallardy <loic.pallardy@st.com>
Tested-By: Loic Pallardy <loic.pallardy@st.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Id02e022cc59de231bc4e94ae22b89f7436275df0
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit b26210cda63564a7478486faaea713f6ea965633)
Reviewed-on: https://chromium-review.googlesource.com/1016187
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/70042f5bf9d3627249dac0d13aa3a7e5ede52ff7/include/linux/remoteproc.h
[modify] https://crrev.com/70042f5bf9d3627249dac0d13aa3a7e5ede52ff7/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/d5a95c18f5c462d4129addf19b087eda42fc9d36

commit d5a95c18f5c462d4129addf19b087eda42fc9d36
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:37 2018

UPSTREAM: remoteproc: Cache resource table size

We don't re-read the resource table during a recovery, so it is possible
in the recovery path that the resource table has a different size than
cached_table. Store the original size of cached_table to avoid these
getting out of sync.

Reviewed-By: Loic Pallardy <loic.pallardy@st.com>
Tested-By: Loic Pallardy <loic.pallardy@st.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I13e1fc5aa9d1126418a6df9fdccbb7503ed648da
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit a4b24c7560ba64c3c54d8f90ee033a6f0565f8d3)
Reviewed-on: https://chromium-review.googlesource.com/1016188
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/d5a95c18f5c462d4129addf19b087eda42fc9d36/include/linux/remoteproc.h
[modify] https://crrev.com/d5a95c18f5c462d4129addf19b087eda42fc9d36/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e9e84803136efc411ce40288bfcdbb4626a08833

commit e9e84803136efc411ce40288bfcdbb4626a08833
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:39 2018

UPSTREAM: remoteproc: Clone rproc_ops in rproc_alloc()

In order to allow rproc_alloc() to, in a future patch, update entries in
the "ops" struct we need to make a local copy of it.

Reviewed-By: Loic Pallardy <loic.pallardy@st.com>
Tested-By: Loic Pallardy <loic.pallardy@st.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ib69c23f45afce8cc252b281cfe54e1716f5aff23
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit fb98e2bdbd5f5949459dcfe9976bdafdb0ed1948)
Reviewed-on: https://chromium-review.googlesource.com/1016189
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/e9e84803136efc411ce40288bfcdbb4626a08833/include/linux/remoteproc.h
[modify] https://crrev.com/e9e84803136efc411ce40288bfcdbb4626a08833/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5

commit 0316d373a5f0b33cc62b1860d0ad07b6210a3dc5
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:41 2018

UPSTREAM: remoteproc: Merge rproc_ops and rproc_fw_ops

There are currently a few different schemes used for overriding fw_ops
or parts of fw_ops. Merge fw_ops into rproc_ops and expose the default
ELF-loader symbols so that they can be assigned by the drivers.

To keep backwards compatibility with the "default" case, a driver not
specifying the "load" operation is assumed to want the full ELF-loader
suit of functions.

Reviewed-By: Loic Pallardy <loic.pallardy@st.com>
Tested-By: Loic Pallardy <loic.pallardy@st.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I494458504869a3d894c9ff893cc370956c711dc2
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 0f21f9cc9d868784c7564edc0cfeddd25ca9621a)
Reviewed-on: https://chromium-review.googlesource.com/1016190
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5/drivers/remoteproc/st_slim_rproc.c
[modify] https://crrev.com/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5/drivers/remoteproc/qcom_adsp_pil.c
[modify] https://crrev.com/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5/drivers/remoteproc/qcom_wcnss.c
[modify] https://crrev.com/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5/drivers/remoteproc/remoteproc_elf_loader.c
[modify] https://crrev.com/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5/include/linux/remoteproc.h
[modify] https://crrev.com/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5/drivers/remoteproc/remoteproc_core.c
[modify] https://crrev.com/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5/drivers/remoteproc/qcom_q6v5_pil.c
[modify] https://crrev.com/0316d373a5f0b33cc62b1860d0ad07b6210a3dc5/drivers/remoteproc/remoteproc_internal.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e31c187f9d882a36e6f59303fe169fd9a68e79fe

commit e31c187f9d882a36e6f59303fe169fd9a68e79fe
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:43 2018

UPSTREAM: remoteproc: Don't handle empty resource table

Allow a NULL table_ptr to have the same meaning as a table with 0
entries, allowing a subsequent patch to skip the assignment step.

A few other places in the implementation does dereference table_ptr, but
they are currently all coming from rproc_handle_resources().

Reviewed-By: Loic Pallardy <loic.pallardy@st.com>
Tested-By: Loic Pallardy <loic.pallardy@st.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I80f029f858c7e9a962c7ab0811950dd1f129c7f0
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit d4bb86f2c39cdd31338dd0274540596aa9ae82c3)
Reviewed-on: https://chromium-review.googlesource.com/1016191
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/e31c187f9d882a36e6f59303fe169fd9a68e79fe/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/386562ecd5fb64205fb43d424f4013b7c86273a5

commit 386562ecd5fb64205fb43d424f4013b7c86273a5
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:45 2018

UPSTREAM: remoteproc: Move resource table load logic to find

Extend the previous operation of finding the resource table in the ELF
with the extra step of populating the rproc struct with a copy and the
size. This allows drivers to override the mechanism used for acquiring
the resource table, or omit it for firmware that is known not to have a
resource table.

This leaves the custom, dummy, find_rsc_table implementations found in
some drivers dangling.

Reviewed-By: Loic Pallardy <loic.pallardy@st.com>
Tested-By: Loic Pallardy <loic.pallardy@st.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I81d1701e65ddd8272c9a3fd8db9a921e0ffe54fd
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 58b640906702bcc083ac783bf10325e22c67d9fc)
Reviewed-on: https://chromium-review.googlesource.com/1016192
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/386562ecd5fb64205fb43d424f4013b7c86273a5/include/linux/remoteproc.h
[modify] https://crrev.com/386562ecd5fb64205fb43d424f4013b7c86273a5/drivers/remoteproc/remoteproc_internal.h
[modify] https://crrev.com/386562ecd5fb64205fb43d424f4013b7c86273a5/drivers/remoteproc/remoteproc_elf_loader.c
[modify] https://crrev.com/386562ecd5fb64205fb43d424f4013b7c86273a5/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/fdaf09d17f9b396890ac5c71987e9471036333cf

commit fdaf09d17f9b396890ac5c71987e9471036333cf
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:47 2018

UPSTREAM: remoteproc: Drop dangling find_rsc_table dummies

As the core now deals with the lack of a resource table, remove the
dangling custom dummy implementations of find_rsc_table from drivers.

Reviewed-By: Loic Pallardy <loic.pallardy@st.com>
Tested-By: Loic Pallardy <loic.pallardy@st.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Iba12a630c44119bee70f6b19232f48e71e66a0de
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 4f6fd5a03779cefdf3401ed20690f67ff76cf1ff)
Reviewed-on: https://chromium-review.googlesource.com/1016193
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/fdaf09d17f9b396890ac5c71987e9471036333cf/drivers/remoteproc/st_slim_rproc.c
[modify] https://crrev.com/fdaf09d17f9b396890ac5c71987e9471036333cf/drivers/remoteproc/qcom_common.h
[modify] https://crrev.com/fdaf09d17f9b396890ac5c71987e9471036333cf/drivers/remoteproc/qcom_wcnss.c
[modify] https://crrev.com/fdaf09d17f9b396890ac5c71987e9471036333cf/include/linux/remoteproc.h
[modify] https://crrev.com/fdaf09d17f9b396890ac5c71987e9471036333cf/drivers/remoteproc/qcom_common.c
[modify] https://crrev.com/fdaf09d17f9b396890ac5c71987e9471036333cf/drivers/remoteproc/qcom_q6v5_pil.c
[modify] https://crrev.com/fdaf09d17f9b396890ac5c71987e9471036333cf/drivers/remoteproc/qcom_adsp_pil.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e2319a3f4d2b626301cb268b84cfa3e4aef4f90c

commit e2319a3f4d2b626301cb268b84cfa3e4aef4f90c
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:49 2018

UPSTREAM: remoteproc: Reset table_ptr on stop

The installed resource table is no longer accessible after stopping the
remote, so update table_ptr to point to the local copy.

Reviewed-By: Loic Pallardy <loic.pallardy@st.com>
Tested-By: Loic Pallardy <loic.pallardy@st.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Iaed5f1c937ce410a2425cc88654feb60ff4983bf
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 0a8b81cb2e413eff4cd9aeac7ef415150b699fb4)
Reviewed-on: https://chromium-review.googlesource.com/1016194
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/e2319a3f4d2b626301cb268b84cfa3e4aef4f90c/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/0496482947e583c27327c30e58e3c26f033e83b3

commit 0496482947e583c27327c30e58e3c26f033e83b3
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:51 2018

UPSTREAM: rpmsg: smd: Fix container_of macros

The container_of macros should not use the same name for the parameter
as the member to use for lookup, as this will result in a compilation
error unless the passed parameter has the same name as the member.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ie44bfd11029819493dd966d3eb4cf516ee18ee24
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 6ddf12d397aee75dbd24dd02be07c1372e3008f6)
Reviewed-on: https://chromium-review.googlesource.com/1016195
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/0496482947e583c27327c30e58e3c26f033e83b3/drivers/rpmsg/qcom_smd.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/6c9b5eb2ba4acc428c19e7de3fbfd69f0c1e7ac7

commit 6c9b5eb2ba4acc428c19e7de3fbfd69f0c1e7ac7
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:53 2018

UPSTREAM: rpmsg: Only invoke announce_create for rpdev with endpoints

For special rpmsg devices without a primary endpoint there is nothing to
announce so don't call the backend announce create function if we didn't
create an endpoint.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I72c56ed562bbcbee15b57f25c10eb14580569ba5
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 7586516ca043d55ed1ca563df72bc216c948cad4)
Reviewed-on: https://chromium-review.googlesource.com/1016196
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/6c9b5eb2ba4acc428c19e7de3fbfd69f0c1e7ac7/drivers/rpmsg/rpmsg_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9884c17f1e5cbe6f1232ed3461eebea18f5bbc39

commit 9884c17f1e5cbe6f1232ed3461eebea18f5bbc39
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:55 2018

UPSTREAM: rpmsg: smd: Use announce_create to process any receive work

It is possible that incoming data arrives before the client driver has
reached a point in the probe method where adequate context for handling
the incoming message has been established.

In the event that the client's callback function returns an error the
message will be left on the FIFO and by invoking the receive handler
after the device has been probed the message will be picked off the FIFO
and the callback invoked again.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: If73b06ecce00351263c3534a68387348d7d1fa82
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 0d72038c303c616a63415a07366f916b5edc3830)
Reviewed-on: https://chromium-review.googlesource.com/1016197
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/9884c17f1e5cbe6f1232ed3461eebea18f5bbc39/drivers/rpmsg/qcom_smd.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9fb6a6b5e23bf61f3696bc8c96b2a24f3030f6f7

commit 9fb6a6b5e23bf61f3696bc8c96b2a24f3030f6f7
Author: Sarangdhar Joshi <spjoshi@codeaurora.org>
Date: Thu Apr 26 20:00:57 2018

UPSTREAM: remoteproc: Add remote processor coredump support

As the remoteproc framework restarts the remote processor after a fatal
event, it's useful to be able to acquire a coredump of the remote
processor's state, for post mortem debugging.

This patch introduces a mechanism for extracting the memory contents
after the remote has stopped and before the restart sequence has begun
in the recovery path. The remoteproc framework builds the core dump in
memory and use devcoredump to expose this to user space.

Signed-off-by: Sarangdhar Joshi <spjoshi@codeaurora.org>
[bjorn: Use vmalloc instead of composing the ELF on the fly]
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I36a721533b589941ea54c9d97f522c31f6f792cc
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 2666ca9197e3d352f43b02d7dfb7c6dd72e7c614)
Reviewed-on: https://chromium-review.googlesource.com/1016198
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/9fb6a6b5e23bf61f3696bc8c96b2a24f3030f6f7/include/linux/remoteproc.h
[modify] https://crrev.com/9fb6a6b5e23bf61f3696bc8c96b2a24f3030f6f7/drivers/remoteproc/Kconfig
[modify] https://crrev.com/9fb6a6b5e23bf61f3696bc8c96b2a24f3030f6f7/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/cbb964420a04a78425323843e917f296128bfc8b

commit cbb964420a04a78425323843e917f296128bfc8b
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:00:59 2018

UPSTREAM: remoteproc: Rename "load_rsc_table" to "parse_fw"

The resource table is just one possible source of information that can
be extracted from the firmware file. Generalize this interface to allow
drivers to override this with parsers of other types of information.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Id29dfa924372b8e7d4a283fb19a1af15aa167dce
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit c1d35c1ab4242464a0e5953ae69de8aa78156c6c)
Reviewed-on: https://chromium-review.googlesource.com/1016199
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/cbb964420a04a78425323843e917f296128bfc8b/include/linux/remoteproc.h
[modify] https://crrev.com/cbb964420a04a78425323843e917f296128bfc8b/drivers/remoteproc/remoteproc_internal.h
[modify] https://crrev.com/cbb964420a04a78425323843e917f296128bfc8b/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3b0580ecc8bc0fa83a8db8f57626dd6fa2351cfe

commit 3b0580ecc8bc0fa83a8db8f57626dd6fa2351cfe
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:01 2018

UPSTREAM: soc: qcom: mdt-loader: Return relocation base

In order to implement support for grabbing core dumps in remoteproc it's
necessary to know the relocated base of the image, as the offsets from
the virtual memory base might not be based on the physical address.

Return the adjusted physical base address to the caller.

Acked-by: Andy Gross <andy.gross@linaro.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I7320ad2c19b2a984268451882bd0d6aae4363172
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 4dd27f544c84c4d079049dd716beee192fcc7e03)
Reviewed-on: https://chromium-review.googlesource.com/1016200
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/3b0580ecc8bc0fa83a8db8f57626dd6fa2351cfe/drivers/remoteproc/qcom_wcnss.c
[modify] https://crrev.com/3b0580ecc8bc0fa83a8db8f57626dd6fa2351cfe/include/linux/soc/qcom/mdt_loader.h
[modify] https://crrev.com/3b0580ecc8bc0fa83a8db8f57626dd6fa2351cfe/drivers/gpu/drm/msm/adreno/a5xx_gpu.c
[modify] https://crrev.com/3b0580ecc8bc0fa83a8db8f57626dd6fa2351cfe/drivers/remoteproc/qcom_adsp_pil.c
[modify] https://crrev.com/3b0580ecc8bc0fa83a8db8f57626dd6fa2351cfe/drivers/media/platform/qcom/venus/firmware.c
[modify] https://crrev.com/3b0580ecc8bc0fa83a8db8f57626dd6fa2351cfe/drivers/soc/qcom/mdt_loader.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9abe6d3475ce541c3b38ff9a7dd1e58358e9d53a

commit 9abe6d3475ce541c3b38ff9a7dd1e58358e9d53a
Author: Sarangdhar Joshi <spjoshi@codeaurora.org>
Date: Thu Apr 26 20:01:03 2018

UPSTREAM: remoteproc: qcom: Register segments for core dump

Register MDT segments with the remoteproc core dump functionality in
order to include them in a core dump, in case of a recovery of the remote
processor.

Signed-off-by: Sarangdhar Joshi <spjoshi@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Iec1f9d811e0e1eceba4ad5c97ee7dc8f16eb29ef
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit dcb57ed43d9ec5e16628c337143cd6b387f42778)
Reviewed-on: https://chromium-review.googlesource.com/1016201
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/9abe6d3475ce541c3b38ff9a7dd1e58358e9d53a/drivers/remoteproc/qcom_common.h
[modify] https://crrev.com/9abe6d3475ce541c3b38ff9a7dd1e58358e9d53a/drivers/remoteproc/qcom_common.c
[modify] https://crrev.com/9abe6d3475ce541c3b38ff9a7dd1e58358e9d53a/drivers/remoteproc/qcom_adsp_pil.c
[modify] https://crrev.com/9abe6d3475ce541c3b38ff9a7dd1e58358e9d53a/drivers/remoteproc/qcom_wcnss.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/067e1ac03185b5a0b9dafab4adba7c3181e96c70

commit 067e1ac03185b5a0b9dafab4adba7c3181e96c70
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:05 2018

UPSTREAM: rpmsg: glink: smem: Ensure ordering during tx

Ensure the ordering of the fifo write and the update of the write index,
so that the index is not updated before the data has landed in the fifo.

Acked-By: Chris Lew <clew@codeaurora.org>
Reported-by: Arun Kumar Neelakantam <aneela@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Iaf3781f63c90fee70b1164fdebaac67a8fca05d3
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 9d32497361ff89d2fc8306407de6f04b2bfb2836)
Reviewed-on: https://chromium-review.googlesource.com/1016202
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/067e1ac03185b5a0b9dafab4adba7c3181e96c70/drivers/rpmsg/qcom_glink_smem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/fba43e1853ca164db5dd354ed29f92ef43b22289

commit fba43e1853ca164db5dd354ed29f92ef43b22289
Author: Arvind Yadav <arvind.yadav.cs@gmail.com>
Date: Thu Apr 26 20:01:07 2018

UPSTREAM: rpmsg: glink: use put_device() if device_register fail

if device_register() returned an error! Always use put_device()
to give up the reference initialized. And unregister device for
other return error.

Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I538aee134d64fb2b0d7c175c3f743b8d32d3519a
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit a9011726c4bb37e5d6a7279bf47fcc19cd9d3e1a)
Reviewed-on: https://chromium-review.googlesource.com/1016203
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/fba43e1853ca164db5dd354ed29f92ef43b22289/drivers/rpmsg/qcom_glink_smem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e6cbc181e8c434420564ddcbbd3732f0eb164297

commit e6cbc181e8c434420564ddcbbd3732f0eb164297
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:09 2018

UPSTREAM: rpmsg: glink: Use spinlock in tx path

Switch the tx_lock to a spinlock we allow clients to use rpmsg_trysend()
from atomic context.

In order to allow clients to sleep while waiting for space in the FIFO
we release the lock temporarily around the delay; which should be
replaced by sending a READ_NOTIF and waiting for the remote to signal
us that space has been made available.

Tested-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I51a95d6ded2ab168980324f20ec6802d3fa28251
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 29fc9b3873607d01b1ff1ae077982cf5629010af)
Reviewed-on: https://chromium-review.googlesource.com/1016204
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/e6cbc181e8c434420564ddcbbd3732f0eb164297/drivers/rpmsg/qcom_glink_native.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/41a33107a478cd6a6a2a5a7efdc4b11b52aa88e8

commit 41a33107a478cd6a6a2a5a7efdc4b11b52aa88e8
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:11 2018

UPSTREAM: soc: qcom: rmtfs-mem: Add support for assigning memory to remote

On some platform the remote processor's memory map is not statically
configured in TrustZone, so each memory region that is to be accessed by
the remote needs a call into TrustZone to set up the remote's
permissions.

Implement this for the rmtfs memory driver, to give the modem on 8996
access to the shared file system buffers.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ib3a57edd39b6bda1445b13d0eaf19bf6bb01b271
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit fa65f8045137d061134c15233d35a089cc85b87e)
Reviewed-on: https://chromium-review.googlesource.com/1016205
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/41a33107a478cd6a6a2a5a7efdc4b11b52aa88e8/drivers/soc/qcom/Kconfig
[modify] https://crrev.com/41a33107a478cd6a6a2a5a7efdc4b11b52aa88e8/drivers/soc/qcom/rmtfs_mem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9f3e086c193226ce3fc5701f2e4bd20580e944a9

commit 9f3e086c193226ce3fc5701f2e4bd20580e944a9
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:13 2018

UPSTREAM: soc: qcom: Introduce QMI encoder/decoder

Add the helper library for encoding and decoding QMI encoded messages.
The implementation is taken from lib/qmi_encdec.c of the Qualcomm kernel
(msm-3.18).

Modifications has been made to the public API, source buffers has been
made const and the debug-logging part was omitted, for now.

Acked-by: Chris Lew <clew@codeaurora.org>
Tested-by: Chris Lew <clew@codeaurora.org>
Tested-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I05520eb5f21abc789a3a213816820f17e2e4cdfd
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 9b8a11e82615274d4133aab3cf5aa1c59191f0a2)
Reviewed-on: https://chromium-review.googlesource.com/1016206
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/9f3e086c193226ce3fc5701f2e4bd20580e944a9/drivers/soc/qcom/Kconfig
[add] https://crrev.com/9f3e086c193226ce3fc5701f2e4bd20580e944a9/include/linux/soc/qcom/qmi.h
[add] https://crrev.com/9f3e086c193226ce3fc5701f2e4bd20580e944a9/drivers/soc/qcom/qmi_encdec.c
[modify] https://crrev.com/9f3e086c193226ce3fc5701f2e4bd20580e944a9/drivers/soc/qcom/Makefile

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/619dd3356c4b5912d2e5e0246b31b8e49a17498e

commit 619dd3356c4b5912d2e5e0246b31b8e49a17498e
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:15 2018

UPSTREAM: soc: qcom: Introduce QMI helpers

Drivers that needs to communicate with a remote QMI service all has to
perform the operations of discovering the service, encoding and decoding
the messages and operate the socket. This introduces an abstraction for
these common operations, reducing most of the duplication in such cases.

Acked-by: Chris Lew <clew@codeaurora.org>
Tested-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Id8c3954c367f3a8d66f8e27e1a9fd51830268d96
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 3830d0771ef66a3bb9ab57b70630b3598593a4f0)
Reviewed-on: https://chromium-review.googlesource.com/1016207
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[add] https://crrev.com/619dd3356c4b5912d2e5e0246b31b8e49a17498e/drivers/soc/qcom/qmi_interface.c
[modify] https://crrev.com/619dd3356c4b5912d2e5e0246b31b8e49a17498e/include/linux/soc/qcom/qmi.h
[modify] https://crrev.com/619dd3356c4b5912d2e5e0246b31b8e49a17498e/drivers/soc/qcom/Makefile

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/4b560faa8b71c536556b3644c9c62f942e28ebb9

commit 4b560faa8b71c536556b3644c9c62f942e28ebb9
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:17 2018

UPSTREAM: remoteproc: Pass type of shutdown to subdev remove

remoteproc instances can be stopped either by invoking shutdown or by an
attempt to recover from a crash. For some subdev types it's expected to
clean up gracefully during a shutdown, but are unable to do so during a
crash - so pass this information to the subdev remove functions.

Acked-By: Chris Lew <clew@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Iea615c43f623b9037e1338a0b93934c2a4f888f1
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 880f5b388252fedb26c70bb80ad1d7c8abbc0607)
Reviewed-on: https://chromium-review.googlesource.com/1016208
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/4b560faa8b71c536556b3644c9c62f942e28ebb9/include/linux/remoteproc.h
[modify] https://crrev.com/4b560faa8b71c536556b3644c9c62f942e28ebb9/drivers/remoteproc/qcom_common.c
[modify] https://crrev.com/4b560faa8b71c536556b3644c9c62f942e28ebb9/drivers/remoteproc/remoteproc_core.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3648b1b318bd4649a2d02eb21a71bde450e6e948

commit 3648b1b318bd4649a2d02eb21a71bde450e6e948
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:19 2018

UPSTREAM: remoteproc: qcom: Introduce sysmon

The sysmon client communicates either via a dedicated SMD/GLINK channel
or via QMI encoded messages over IPCROUTER with remote processors in
order to perform graceful shutdown and inform about other remote
processors shutting down.

Acked-By: Chris Lew <clew@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I0ae05047c5479cc4c78d5c35e9089c7e8976508d
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 1fb82ee806d170b92315f424eac9b5b34b9ead64)
Reviewed-on: https://chromium-review.googlesource.com/1016209
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/3648b1b318bd4649a2d02eb21a71bde450e6e948/drivers/remoteproc/qcom_common.h
[modify] https://crrev.com/3648b1b318bd4649a2d02eb21a71bde450e6e948/drivers/remoteproc/qcom_wcnss.c
[add] https://crrev.com/3648b1b318bd4649a2d02eb21a71bde450e6e948/drivers/remoteproc/qcom_sysmon.c
[modify] https://crrev.com/3648b1b318bd4649a2d02eb21a71bde450e6e948/drivers/remoteproc/Makefile
[modify] https://crrev.com/3648b1b318bd4649a2d02eb21a71bde450e6e948/drivers/remoteproc/Kconfig
[modify] https://crrev.com/3648b1b318bd4649a2d02eb21a71bde450e6e948/drivers/remoteproc/qcom_q6v5_pil.c
[modify] https://crrev.com/3648b1b318bd4649a2d02eb21a71bde450e6e948/drivers/remoteproc/qcom_adsp_pil.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/508c778482c173f014f33c27c8b78d3bd8608ea8

commit 508c778482c173f014f33c27c8b78d3bd8608ea8
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Apr 26 20:01:21 2018

UPSTREAM: samples: Introduce Qualcomm QMI sample client

Introduce a sample driver that register for server notifications and
spawn clients for each available test service (service 15). The spawned
clients implements the interface for encoding "ping" and "data" requests
and decode the responses from the remote.

Acked-By: Chris Lew <clew@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I811f941b465ac9b9ed32dd820f2c4042d45f0d4a
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 842891be96bd2b90f0e7d44192d45f61bab17926)
Reviewed-on: https://chromium-review.googlesource.com/1016210
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/508c778482c173f014f33c27c8b78d3bd8608ea8/samples/Makefile
[modify] https://crrev.com/508c778482c173f014f33c27c8b78d3bd8608ea8/samples/Kconfig
[add] https://crrev.com/508c778482c173f014f33c27c8b78d3bd8608ea8/samples/qmi/qmi_sample_client.c
[add] https://crrev.com/508c778482c173f014f33c27c8b78d3bd8608ea8/samples/qmi/Makefile

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/d4983a0540e95585bd7738689aa06108c4297294

commit d4983a0540e95585bd7738689aa06108c4297294
Author: Arnd Bergmann <arnd@arndb.de>
Date: Thu Apr 26 20:01:23 2018

UPSTREAM: soc: qcom: qmi: add CONFIG_NET dependency

Access to the socket API and the root network namespace is only available
when networking is enabled:

ERROR: "kernel_sendmsg" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "sock_release" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "sock_create_kern" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "kernel_getsockname" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "init_net" [drivers/soc/qcom/qmi_helpers.ko] undefined!
ERROR: "kernel_recvmsg" [drivers/soc/qcom/qmi_helpers.ko] undefined!

Adding a dependency on CONFIG_NET lets us build it in all randconfig
builds.

Fixes: 9b8a11e82615 ("soc: qcom: Introduce QMI encoder/decoder")
Acked-by: Andy Gross <andy.gross@linaro.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I1b161d3d72ac0878f1d56219f36380fbf912aaf1
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit dea4bd1975e36e3127a95e74c3670ea8d7f4796f)
Reviewed-on: https://chromium-review.googlesource.com/1016211
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/d4983a0540e95585bd7738689aa06108c4297294/drivers/soc/qcom/Kconfig
[modify] https://crrev.com/d4983a0540e95585bd7738689aa06108c4297294/samples/Kconfig
[modify] https://crrev.com/d4983a0540e95585bd7738689aa06108c4297294/drivers/remoteproc/Kconfig

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3ea7561e447c2117a4b7cfad6d5f6570c1a3ea5d

commit 3ea7561e447c2117a4b7cfad6d5f6570c1a3ea5d
Author: Sibi Sankar <sibis@codeaurora.org>
Date: Thu Apr 26 20:01:25 2018

UPSTREAM: remoteproc: fix null pointer dereference on glink only platforms

Currently calling list_del on smd subdev remove path results in
null pointer dereference on glink only platforms. Fix this by
adding safety checks in glink/smd subdev remove paths.

Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: I3da07f062043276b42534dc8d02a72934ecab618
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 730b2ad8f72898029160a6832141ba954122a0c8)
Reviewed-on: https://chromium-review.googlesource.com/1016212
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/3ea7561e447c2117a4b7cfad6d5f6570c1a3ea5d/drivers/remoteproc/qcom_common.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/479c10eaa55a85fb4bb4de32741f31f1dd78a31f

commit 479c10eaa55a85fb4bb4de32741f31f1dd78a31f
Author: Viresh Kumar <viresh.kumar@linaro.org>
Date: Thu May 03 05:20:46 2018

UPSTREAM: OPP: Allow OPP table to be used for power-domains

Power-domains can also have their active states and this patch enhances
the OPP binding to define those. The power domains can use the OPP
bindings as is, with one additional change to Allow
"operating-points-v2" property to contain multiple phandles for power
domain providers providing multiple domains.

Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ib62fc9234973f8d623d2ef5e79bedf25c685be58
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 972bc90ed8f6008f5e2d42c72d894b2401736519)
Reviewed-on: https://chromium-review.googlesource.com/1038763
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/479c10eaa55a85fb4bb4de32741f31f1dd78a31f/Documentation/devicetree/bindings/power/power_domain.txt
[modify] https://crrev.com/479c10eaa55a85fb4bb4de32741f31f1dd78a31f/Documentation/devicetree/bindings/opp/opp.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9dc9e18f470a9df1840a3407f7891ed7a8e7f4e9

commit 9dc9e18f470a9df1840a3407f7891ed7a8e7f4e9
Author: Viresh Kumar <viresh.kumar@linaro.org>
Date: Thu May 03 05:20:47 2018

UPSTREAM: OPP: Introduce "required-opp" property

Devices have inter-dependencies some times. For example a device that
needs to run at 800 MHz, needs another device (e.g. Its power domain) to
be configured at a particular operating performance point.

This patch introduces a new property "required-opp" which can be present
directly in a device's node (if it doesn't need to change its OPPs), or
in device's OPP nodes. More details on the property can be seen in the
binding itself.

Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Id64220d476848fdd86dc307d61033a7e7bb0c34a
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit e856f078bcf120e1627c750014d2612974ed81a2)
Reviewed-on: https://chromium-review.googlesource.com/1038764
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/9dc9e18f470a9df1840a3407f7891ed7a8e7f4e9/Documentation/devicetree/bindings/power/power_domain.txt
[modify] https://crrev.com/9dc9e18f470a9df1840a3407f7891ed7a8e7f4e9/Documentation/devicetree/bindings/opp/opp.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/203e24ff14c2c0aae90933fa1a4bc0b5642a865c

commit 203e24ff14c2c0aae90933fa1a4bc0b5642a865c
Author: Sudeep Holla <Sudeep.Holla@arm.com>
Date: Fri May 04 07:13:45 2018

UPSTREAM: PM / OPP: add missing of_node_put() for of_get_cpu_node()

Commit 762792913f8c (PM / OPP: Fix get sharing CPUs when hotplug
is used) moved away from using cpu_dev->of_node because of some
limitations.

However, commit 7467c9d95989 (of: return of_get_cpu_node from
of_cpu_device_node_get if CPUs are not registered) added support to
fall back to of_get_cpu_node() if called if CPUs are not registered
yet.

Add the missing of_node_put() for the CPU device nodes. Also go back
to using of_cpu_device_node_get() in dev_pm_opp_of_get_sharing_cpus()
to avoid scanning the device tree again.

Acked-by: Viresh Kumar <vireshk@kernel.org>
Fixes: 762792913f8c (PM / OPP: Fix get sharing CPUs when hotplug is used)
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ibcfd18f8e8dfc199cbb5a1318163711c45d5c5ec
Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
(cherry picked from commit 9867999f3a85b52f96ef05fca00cc8128eed01ce)
Reviewed-on: https://chromium-review.googlesource.com/1038765
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/203e24ff14c2c0aae90933fa1a4bc0b5642a865c/drivers/opp/of.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9a4ce07764813290e62137bb1b4f9ca159f48106

commit 9a4ce07764813290e62137bb1b4f9ca159f48106
Author: Stephen Boyd <swboyd@chromium.org>
Date: Sat May 05 03:37:47 2018

FROMLIST: mfd: qcom-spmi-pmic: Add support for pm8005,pm8998,pmi8998

Add the compatibles and PMIC ids for the pm8005, pm8998, and pmi8998
PMICS found on MSM8998 and SDM845 based platforms.

Cc: <devicetree@vger.kernel.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Signed-off-by: Stephen Boyd <swboyd@chromium.org>

BUG=chromium:795946
TEST=Works with later code that talks to PMIC

Change-Id: Ib081db9640672631a12eca9a1d00d063b63f70ef
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/10376089/)
Reviewed-on: https://chromium-review.googlesource.com/1022835

[modify] https://crrev.com/9a4ce07764813290e62137bb1b4f9ca159f48106/drivers/mfd/qcom-spmi-pmic.c
[modify] https://crrev.com/9a4ce07764813290e62137bb1b4f9ca159f48106/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/02b921f460fcaff7a21e9f2d4b35ecdf4281d49a

commit 02b921f460fcaff7a21e9f2d4b35ecdf4281d49a
Author: Amit Nischal <anischal@codeaurora.org>
Date: Wed May 09 04:15:37 2018

FIXUP: FROMLIST: clk: qcom: Clear hardware clock control bit of RCG

Note: This is a trivial fixup patch to upgrade from v1 to v2 of the
series.

For upcoming targets like sdm845, POR value of the hardware clock control
bit is set for most of root clocks which needs to be cleared for software
to be able to control. For older targets like MSM8996, this bit is reserved
bit and having POR value as 0 so this patch will work for the older targets
too. So update the configuration mask to take care of the same to clear
hardware clock control bit.

Signed-off-by: Amit Nischal <anischal@codeaurora.org>

BUG=chromium:795946
TEST=Build kernel for Cheza

Signed-off-by: Evan Green <evgreen@chromium.org>
(am from https://patchwork.kernel.org/patch/10267105/)
Change-Id: I016bea9fc4fb3f579495247b78d9a35e5a0160e8
Reviewed-on: https://chromium-review.googlesource.com/956101
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/02b921f460fcaff7a21e9f2d4b35ecdf4281d49a/drivers/clk/qcom/clk-rcg2.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/f1fa6dee04b99affe5a6673f1c3b9bff28d4bd12

commit f1fa6dee04b99affe5a6673f1c3b9bff28d4bd12
Author: Douglas Anderson <dianders@chromium.org>
Date: Wed May 09 04:15:38 2018

FIXUP: FROMGIT: clk: qcom: Add support for controlling Fabia PLL

---

This fixes up what we landed before to what actually landed
upstream.

---

Fabia PLL is a Digital Frequency Locked Loop (DFLL) clock
generator which has a wide range of frequency output. It
supports dynamic updating of the output frequency
("frequency slewing") without need to turn off the PLL
before configuration. Add support for initial configuration
and programming sequence to control fabia PLLs.

Signed-off-by: Amit Nischal <anischal@codeaurora.org>
[sboyd: Shorten code a little]
Signed-off-by: Stephen Boyd <sboyd@kernel.org>

BUG=chromium:795946
TEST=Build kernel for Cheza

Change-Id: I5fea2d00c031e43e82596a37554c7b10214661fb
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(cherry picked from commit 687d7a0caa7736de53e3c5efdef6b5343d1470ac
 git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next)
Reviewed-on: https://chromium-review.googlesource.com/956223

[modify] https://crrev.com/f1fa6dee04b99affe5a6673f1c3b9bff28d4bd12/drivers/clk/qcom/clk-alpha-pll.h
[modify] https://crrev.com/f1fa6dee04b99affe5a6673f1c3b9bff28d4bd12/drivers/clk/qcom/clk-alpha-pll.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/910dbfcbd7c9794f325d53b57f8353f4fd1d209b

commit 910dbfcbd7c9794f325d53b57f8353f4fd1d209b
Author: Douglas Anderson <dianders@chromium.org>
Date: Thu May 10 22:09:04 2018

FIXUP: FROMGIT: clk: qcom: Configure the RCGs to a safe source as needed

---

This is a squash of a revert of commit c12ab6b3da04 ("FROMLIST: clk:
qcom: Configure the RCGs to a safe source as needed") together with
the new version.

This will not compile.  You need a few more fixups too.  See CQ-DEPEND.

---

For some root clock generators, there could be child branches which are
controlled by an entity other than application processor subsystem. For
such RCGs, as per application processor subsystem clock driver, all of
its downstream clocks are disabled and RCG is in disabled state but in
reality downstream clocks can be left enabled before.

So in this scenario, when RCG is disabled as per clock driver's point of
view and when rate scaling request comes before downstream clock enable
request, then RCG fails to update its configuration because in reality
RCG is on and it expects its new source to already be in enable state but
in reality new source is off. In order to avoid having the RCG to go into
an invalid state, add support to update the CFG, M, N and D registers
during set_rate() without configuration update and defer the actual RCG
configuration update to be done during clk_enable() as at this point of
time, both its new parent and safe source will be already enabled and RCG
can safely switch to new parent.

During clk_disable() request, configure it to safe source as both its
parents, safe source and current parent will be enabled and RCG can
safely execute a switch.

Signed-off-by: Taniya Das <tdas@codeaurora.org>
Signed-off-by: Amit Nischal <anischal@codeaurora.org>
Signed-off-by: Stephen Boyd <sboyd@kernel.org>

CQ-DEPEND=CL:Ic5ef1ec300bc08c7d5fa6e895d60cedd87652878
BUG=chromium:795946
TEST=With more patches atop, boot sdm845-mtp to UI

Change-Id: I1cdf1ab1d69377ced5a0d82dda3a3382cbd26506
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(cherry picked from commit 7ef6f11887bd3676fc64517ca685f613d7f230ef
 git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next)
Reviewed-on: https://chromium-review.googlesource.com/956222
Reviewed-by: Evan Green <evgreen@chromium.org>

[modify] https://crrev.com/910dbfcbd7c9794f325d53b57f8353f4fd1d209b/drivers/clk/qcom/clk-rcg.h
[modify] https://crrev.com/910dbfcbd7c9794f325d53b57f8353f4fd1d209b/drivers/clk/qcom/clk-rcg2.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3364daccf32f93e1e13ff5c6ad07ea85a414204a

commit 3364daccf32f93e1e13ff5c6ad07ea85a414204a
Author: Andy Gross <andy.gross@linaro.org>
Date: Fri May 11 16:30:39 2018

FROMGIT: arm64: dts: qcom: sdm845: Fixup clocks to use raw values

This patch removes the reference to the clk dt-bindings include file
and instead usees the raw values.  Once the clk includes are taken
through the clk tree, we'll switch back to using the includes.

Signed-off-by: Andy Gross <andy.gross@linaro.org>

BUG=chromium:795946
TEST=No changes

Change-Id: Ib8f4abbf8d34fe0d1dd72e6ce284efcbc8b2b0c2
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(cherry picked from commit 4ecc30460c7816a065c613e1f48543a35163bb74
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)
Reviewed-on: https://chromium-review.googlesource.com/1054774
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/3364daccf32f93e1e13ff5c6ad07ea85a414204a/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/d3caed75ed3efc9c7c3c94dd34dcfa0e79cca76d

commit d3caed75ed3efc9c7c3c94dd34dcfa0e79cca76d
Author: Douglas Anderson <dianders@chromium.org>
Date: Fri May 11 16:30:41 2018

FROMLIST: arm64: dts: qcom: sdm845: Sort nodes in the soc by address

This is pure-churn and should be a no-op.  I'm doing it in the hopes
of reducing merge conflicts.  When things are sorted in a sane way
(and by base address seems sane) then it's less likely that future
patches will cause merge conflicts.

Signed-off-by: Douglas Anderson <dianders@chromium.org>

BUG=chromium:795946
TEST=Everything works the same

Change-Id: If6ae31eafb9c11b20e7c0026263e04629ed78b87
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/10381745/)
Reviewed-on: https://chromium-review.googlesource.com/1054775
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/d3caed75ed3efc9c7c3c94dd34dcfa0e79cca76d/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/cdc165d052b6220332a8043f962f0405b2bf8693

commit cdc165d052b6220332a8043f962f0405b2bf8693
Author: Evan Green <evgreen@chromium.org>
Date: Tue May 15 06:57:02 2018

CHROMIUM: Revert "FROMGIT: arm64: dts: qcom: sdm845: Fixup clocks to use raw values"

This change reverts and fixes a previous change that used raw
clock numbers in order to land the device tree before the clock
driver had landed. Since that change was made, the clock numbers
have changed, so in addition to being good housekeeping, it's
needed in order to boot.

Apparently, the upstream change it was based on has vanished entirely
from Andy's tree. So simply reverting this from ours.

Fixes: 3364daccf32f93e1e13ff5c6ad07ea85a414204a

BUG=chromium:795946
TEST=Boot kernel with Cheza

Change-Id: Ibfbf67a8c4713de9ecb4ee8ddf6d8d4531f020ae
Signed-off-by: Evan Green <evgren@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1058600
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Evan Green <evgreen@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/cdc165d052b6220332a8043f962f0405b2bf8693/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/834af73dcaa6f732b28a01c358c448ac220be36e

commit 834af73dcaa6f732b28a01c358c448ac220be36e
Author: Douglas Anderson <dianders@chromium.org>
Date: Tue May 15 09:30:21 2018

FROMGIT: arm64: dts: sdm845: Fix xo_board clock name and speed

The RPMh clock driver assumes that the xo_board clock is named
"xo_board", not "xo-board".  Add a "clock-output-names" property to
the device tree to get the right name.

Also add the proper speed for the xo-clock as 38400000.  This is
internally divided in RPMh clock driver to get "bi_tcxo" at 19200000.

After this change the clock tree in /sys/kernel/debug/clk/clk_summary
looks much better.

NOTES:
- Technically you could argue that this clock could belong in board
  .dts files, not in the SoC one.  However at the moment it's believed
  that 100% of sdm845 boards will have an external clock at 38.4.  It
  can always be moved later if necessary.
- We could rename the "xo-board" device tree node to "xo_board" to
  achieve the same effect as this patch.  Presumably device-tree folks
  would rather keep node names using dashes though.
- We could change the RPMh clock driver to use a dash to achieve the
  same effect as this patch, but all other clocks in the clock tree
  use underscores.  It seems silly to change just this one.

Fixes: 7bafa643647f ("arm64: dts: sdm845: Add minimal dts/dtsi files for sdm845 SoC and MTP")
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>

BUG=chromium:795946
TEST=Works as part of sandbox

Change-Id: I2d9d1063df6b024e327a17e2d457ee7021f3e53e
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(cherry picked from commit 34673c5500ba382f16766caf698facbc1b9c18ff
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)
Reviewed-on: https://chromium-review.googlesource.com/1054776

[modify] https://crrev.com/834af73dcaa6f732b28a01c358c448ac220be36e/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/96ee0e67a9e76cf2ed11325358e04171c8e40568

commit 96ee0e67a9e76cf2ed11325358e04171c8e40568
Author: Sibi S <sibis@codeaurora.org>
Date: Wed May 16 19:41:20 2018

BACKPORT: FROMGIT: arm64: dts: qcom: Add APSS shared mailbox node to SDM845

This patch add the node to support APSS shared
mailbox on SDM845

Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>

Conflicts:
   arch/arm64/boot/dts/qcom/sdm845.dtsi
...we landed things in different orders.

BUG=chromium:795946
TEST=Works as part of sandbox

Change-Id: I67dbf2ad2452a1bafc17a9a565196fc653102962
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(cherry picked from commit 0bdd8566c8520d30e2cffd15668a80cbe119a43c
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)
Reviewed-on: https://chromium-review.googlesource.com/1058982
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/96ee0e67a9e76cf2ed11325358e04171c8e40568/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/956556f58b8461d5f30761869d3a7adf6cc991a9

commit 956556f58b8461d5f30761869d3a7adf6cc991a9
Author: Sibi S <sibis@codeaurora.org>
Date: Wed May 16 19:41:22 2018

BACKPORT: FROMGIT: arm64: dts: qcom: Add SDM845 SMEM nodes

Add all the necessary dt nodes to support SMEM driver
on SDM845. It also adds the required memory carveouts
so that the kernel does not access memory that is in
use.

Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>

Conflicts:
   arch/arm64/boot/dts/qcom/sdm845.dtsi
...we landed things in different orders.

BUG=chromium:795946
TEST=Works as part of sandbox

Change-Id: I7edcb7fb3872ad2a3656b1d4b434da6888334c50
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(cherry picked from commit 4ae21f182b5dfa96fd5ece81fdd210e010e489d8
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)
Reviewed-on: https://chromium-review.googlesource.com/1058983
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/956556f58b8461d5f30761869d3a7adf6cc991a9/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/8ce06a150275dc2d8d7383ec7f4ae3ccc68d6b16

commit 8ce06a150275dc2d8d7383ec7f4ae3ccc68d6b16
Author: Douglas Anderson <dianders@chromium.org>
Date: Wed May 16 19:41:24 2018

FROMLIST: arm64: dts: qcom: sdm845: Sort nodes in the reserved mem by address

Let's keep the reserved-memory node tidy and neat and keep it sorted
by address.  This should have no functional change.

Signed-off-by: Douglas Anderson <dianders@chromium.org>

BUG=chromium:795946
TEST=Works as part of sandbox

Change-Id: Ie71eaae940588476a28bf60d3486efb4b2718b10
Signed-off-by: Douglas Anderson <dianders@chromium.org>
(am from https://patchwork.kernel.org/patch/10399881/)
Reviewed-on: https://chromium-review.googlesource.com/1058984
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/8ce06a150275dc2d8d7383ec7f4ae3ccc68d6b16/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/46f7ea78d206d6474403f458e12730ca885bcc7e

commit 46f7ea78d206d6474403f458e12730ca885bcc7e
Author: Douglas Anderson <dianders@chromium.org>
Date: Wed May 16 19:41:35 2018

CHROMIUM: arm64: dts: qcom: sdm845: Sort includes in sdm845.dtsi

Let's keep the #include files sorted.  CHROMIUM patch for now since
the gcc include file hasn't been added upstream.

BUG=chromium:795946
TEST=Code still compiles

Change-Id: I42e61e6753ecf24c2b4600ce6ded658fe4938778
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1060101
Reviewed-by: Evan Green <evgreen@chromium.org>

[modify] https://crrev.com/46f7ea78d206d6474403f458e12730ca885bcc7e/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e6762f2fd91fad5e3e0db407ba37dcd186d5e3e4

commit e6762f2fd91fad5e3e0db407ba37dcd186d5e3e4
Author: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Date: Fri Jun 08 06:33:11 2018

UPSTREAM: net: ipv6: Generate random IID for addresses on RAWIP devices

RAWIP devices such as rmnet do not have a hardware address and
instead require the kernel to generate a random IID for the
IPv6 addresses.

Signed-off-by: Sean Tranchetti <stranche@codeaurora.org>
Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ic46b85f43e4e87cc463d214f8085ffc5584e31f0
(cherry picked from commit 9deb441c113ae9e761e42f78d90736d762ff49a3)
Reviewed-on: https://chromium-review.googlesource.com/1088244
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Douglas Anderson <dianders@chromium.org>
Tested-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/e6762f2fd91fad5e3e0db407ba37dcd186d5e3e4/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c
[modify] https://crrev.com/e6762f2fd91fad5e3e0db407ba37dcd186d5e3e4/net/ipv6/addrconf.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/804f99050f72cadadcec475a93692003bfb81b62

commit 804f99050f72cadadcec475a93692003bfb81b62
Author: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Date: Fri Jun 08 06:33:09 2018

UPSTREAM: net: qualcomm: rmnet: Add support for ethtool private stats

Add ethtool private stats handler to debug the handling of packets
with checksum offload header / trailer. This allows to keep track of
the number of packets for which hardware computes the checksum and
counts and reasons where checksum computation was skipped in hardware
and was done in the network stack.

Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ie0a28ec1e74ce7bbdd9271afd49f0f47d8df98a0
(cherry picked from commit bbde32d38bfbbc4a6970498c7470a8a817122735)
Reviewed-on: https://chromium-review.googlesource.com/1088307
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/804f99050f72cadadcec475a93692003bfb81b62/drivers/net/ethernet/qualcomm/rmnet/rmnet_vnd.c
[modify] https://crrev.com/804f99050f72cadadcec475a93692003bfb81b62/drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c
[modify] https://crrev.com/804f99050f72cadadcec475a93692003bfb81b62/drivers/net/ethernet/qualcomm/rmnet/rmnet_config.h

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/ca9faf50a2b42880d0f86df6ce59fd3d53c81e35

commit ca9faf50a2b42880d0f86df6ce59fd3d53c81e35
Author: Rajendra Nayak <rnayak@codeaurora.org>
Date: Thu Jun 14 21:40:51 2018

UPSTREAM: pinctrl: qcom: spmi-gpio: Add pmi8994 gpio support

Update the binding and driver for pmi8994-gpios

Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
(cherry picked from commit 8d6cfb14088e340acd56264f52a60c8f8f735854)

BUG=chromium:795946
TEST=I can haz the bindings

Change-Id: I7d51e6c67b97d03ffe42760d202381d88a925514
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1100071

[modify] https://crrev.com/ca9faf50a2b42880d0f86df6ce59fd3d53c81e35/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
[modify] https://crrev.com/ca9faf50a2b42880d0f86df6ce59fd3d53c81e35/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e421e5e9422cade6074ba954a1180bacf7bb9757

commit e421e5e9422cade6074ba954a1180bacf7bb9757
Author: Douglas Anderson <dianders@chromium.org>
Date: Fri Jun 15 17:56:33 2018

CHROMIUM: arm64: dts: qcom: sdm845: Reorder cheza dts using new rules

The guiding rule proposed here is:

  If a node was defined in "parent" device tree (sdm845.dtsi in this
  case) and we need to modify it, we should always refer to it by
  label.  An exception will be made for well-defined nodes "aliases"
  and "chosen" which may or may not be defined in the parent.

The rule above is easy to understand and requires no judgement calls.
It places things in a predictable place.

This CL also starts getting the cheza dts sorted using these rules:
* Where possible, sort by unit address.
* If there is no unit address, sort by node name.
* If we're referring to a node by a label from the parent dtsi,
  sort by the label the parent gave as a node name.
* If it makes sense to group certain things together through a
  different ordering, that's OK but the section should be delineated
  so it's clear what goes in that section.  For instance, we'll start
  with pinctrl going at the bottom instead of interspersed.

BUG=chromium:795946
TEST=No functional changes

Change-Id: If7fbda15833759293665af3b37e4675395a4c659
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1069604
Reviewed-by: Stephen Boyd <swboyd@chromium.org>

[modify] https://crrev.com/e421e5e9422cade6074ba954a1180bacf7bb9757/arch/arm64/boot/dts/qcom/sdm845-cheza.dts

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/bd6a43ee7679fb6e232585fdca9f5a97fa60e2a1

commit bd6a43ee7679fb6e232585fdca9f5a97fa60e2a1
Author: Douglas Anderson <dianders@chromium.org>
Date: Fri Jun 15 17:56:34 2018

CHROMIUM: arm64: dts: qcom: Introduce cheza-r1 dts

There's no much checked in yet, so for now just add the structure and
pin names.

BUG=chromium:795946
TEST=Boot ramdisk on cheza-r0

Change-Id: I8a8c12801db9590a89178b209cc184f11009e659
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1082232
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Evan Green <evgreen@chromium.org>

[modify] https://crrev.com/bd6a43ee7679fb6e232585fdca9f5a97fa60e2a1/arch/arm64/boot/dts/qcom/Makefile
[add] https://crrev.com/bd6a43ee7679fb6e232585fdca9f5a97fa60e2a1/arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi
[rename] https://crrev.com/bd6a43ee7679fb6e232585fdca9f5a97fa60e2a1/arch/arm64/boot/dts/qcom/sdm845-cheza-r1.dts
[copy] https://crrev.com/bd6a43ee7679fb6e232585fdca9f5a97fa60e2a1/arch/arm64/boot/dts/qcom/sdm845-cheza-r0.dts

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/b373575a8e328b41c899c060b7c6af8c8711a8b6

commit b373575a8e328b41c899c060b7c6af8c8711a8b6
Author: Stephen Boyd <swboyd@chromium.org>
Date: Fri Jun 15 17:58:15 2018

FROMLIST: arm64: dts: qcom: Add pm8005 and pm8998 support

Add basic support for the pm8005 and pm8998 PMICs. For now just support
the GPIO controllers.

Signed-off-by: Stephen Boyd <swboyd@chromium.org>

BUG=chromium:795946
TEST=Build and boot, no change

Change-Id: I33b4f49b32c00970aa36764031dc2ca1c07cb2e5
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
(am from https://patchwork.kernel.org/patch/10462579/)
Reviewed-on: https://chromium-review.googlesource.com/1099052
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[add] https://crrev.com/b373575a8e328b41c899c060b7c6af8c8711a8b6/arch/arm64/boot/dts/qcom/pm8005.dtsi
[add] https://crrev.com/b373575a8e328b41c899c060b7c6af8c8711a8b6/arch/arm64/boot/dts/qcom/pm8998.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/48b8ec11547c82c1c59d3a533f3b26220a2464df

commit 48b8ec11547c82c1c59d3a533f3b26220a2464df
Author: Stephen Boyd <swboyd@chromium.org>
Date: Fri Jun 15 17:58:07 2018

FROMLIST: pinctrl: qcom: spmi-gpio: Add pm8998 and pm8005 to binding

Update the binding for two more PMICs supported by the same driver.
While we're here, remove the duplicate pmi8994 lines because that
support got merged twice.

Cc: Rajendra Nayak <rnayak@codeaurora.org>
Cc: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: <devicetree@vger.kernel.org>
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-by: Rob Herring <robh@kernel.org>
(am from https://patchwork.kernel.org/patch/10461341/)

BUG=chromium:795946
TEST=I can haz the bindings

Change-Id: Ia42874364d271517e64b6508955b5150adfe3d52
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1100072
Tested-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>

[modify] https://crrev.com/48b8ec11547c82c1c59d3a533f3b26220a2464df/Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/4f7748dad41b62f47efaeff5b85e344e4e682305

commit 4f7748dad41b62f47efaeff5b85e344e4e682305
Author: Stephen Boyd <swboyd@chromium.org>
Date: Sat Jun 16 01:50:58 2018

CHROMIUM: arm64: dts: qcom: Add pm8005 and pm8998 to Cheza

Include the PMIC dtsi files and they automatically appear on the spmi
bus.

CQ-DEPEND=CL:1099052
BUG=chromium:795946
TEST=Build and boot, see pmics probe and gpioinfo show more gpios

Change-Id: Iaa792561729cec4e6d50fdc0025530c0c3d7c7eb
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1099053
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/4f7748dad41b62f47efaeff5b85e344e4e682305/arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/f8d1e60b0dbc6f2c25855ec1fc4bc6d4754a3f78

commit f8d1e60b0dbc6f2c25855ec1fc4bc6d4754a3f78
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Jun 28 07:58:00 2018

UPSTREAM: mailbox: qcom: Add msm8998 hmss compatible

The Qualcomm MSM8998 platform has a APCS HMSS GLOBAL block, add the
compatible for this.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
(cherry picked from commit 61a2f6db77ab119930910bad0d507d680bdf0d77)

BUG=chromium:795946
TEST=Build and boot

Change-Id: Iff97b81c120a39e13626d425cda269d16cc34a99
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1115805
Reviewed-by: Sibi Sankar <sibis@codeaurora.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/f8d1e60b0dbc6f2c25855ec1fc4bc6d4754a3f78/drivers/mailbox/qcom-apcs-ipc-mailbox.c
[modify] https://crrev.com/f8d1e60b0dbc6f2c25855ec1fc4bc6d4754a3f78/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/de10fd0109ff79618bab8438e84b102da043aa88

commit de10fd0109ff79618bab8438e84b102da043aa88
Author: Sibi Sankar <sibis@codeaurora.org>
Date: Thu Jun 28 07:58:02 2018

UPSTREAM: dt-bindings: mailbox: Add APSS shared binding for SDM845 SoCs

Include SDM845 APSS shared to the list of possible bindings

Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
(cherry picked from commit 01355092b24556afefed556c179aa20a0cdfcd19)

BUG=chromium:795946
TEST=Build and boot

Change-Id: I724f6be626907c6208a56eb38bcf3e19e520b1cf
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1115806
Reviewed-by: Sibi Sankar <sibis@codeaurora.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/de10fd0109ff79618bab8438e84b102da043aa88/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.txt

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/4b769eed2d9a086113e9164d644310265cac62cf

commit 4b769eed2d9a086113e9164d644310265cac62cf
Author: Sibi Sankar <sibis@codeaurora.org>
Date: Thu Jun 28 07:58:04 2018

UPSTREAM: mailbox: Add support for Qualcomm SDM845 SoCs

Add the corresponding APSS shared offset for SDM845 SoC

Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Jassi Brar <jaswinder.singh@linaro.org>
(cherry picked from commit 05e99a7d143eb2fbbd0f03bfd8748ba0d90c1c44)

BUG=chromium:795946
TEST=Build and boot

Change-Id: I4a9b6604bb2540af02339221cda641a039f1e962
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1115807
Reviewed-by: Sibi Sankar <sibis@codeaurora.org>
Reviewed-by: Ben Chan <benchan@chromium.org>

[modify] https://crrev.com/4b769eed2d9a086113e9164d644310265cac62cf/drivers/mailbox/qcom-apcs-ipc-mailbox.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/0e299115a381f9672f2319a38457c2ab67cbc6a4

commit 0e299115a381f9672f2319a38457c2ab67cbc6a4
Author: Ben Chan <benchan@chromium.org>
Date: Sat Jun 30 09:14:17 2018

Revert "UPSTREAM: soc: qcom: rmtfs-mem: Add support for assigning memory to remote"

This reverts commit 41a33107a478cd6a6a2a5a7efdc4b11b52aa88e8.

CL:1016205 didn't cherry-pick the exact upstream commit [1] as another
upstream commit [2] touches the same block of code and thus needs to be
cherry-picked first. This CL reverts CL:1016205, so that we can first
cherry pick [1] and then [2] again.

[1] commit fa65f8045137 ("soc: qcom: rmtfs-mem: Add support for assigning memory to remote")
[2] commit d771d62e3139 ("soc: qcom: remove unused label")

BUG=chromium:795946
BUG=b:79668211
TEST=Build and boot cheza.

Change-Id: If9dc752c6d6f755659930ae8d75be3c3f2c8a55b
Signed-off-by: Ben Chan <benchan@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1119402
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/0e299115a381f9672f2319a38457c2ab67cbc6a4/drivers/soc/qcom/Kconfig
[modify] https://crrev.com/0e299115a381f9672f2319a38457c2ab67cbc6a4/drivers/soc/qcom/rmtfs_mem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/daa1453be564fb7f71d2bfcb2c8b531064147ece

commit daa1453be564fb7f71d2bfcb2c8b531064147ece
Author: Arnd Bergmann <arnd@arndb.de>
Date: Sat Jun 30 09:14:18 2018

UPSTREAM: soc: qcom: remove unused label

The newly added driver comes with a harmless warning:

drivers/soc/qcom/rmtfs_mem.c: In function 'qcom_rmtfs_mem_probe':
drivers/soc/qcom/rmtfs_mem.c:211:1: error: label 'remove_cdev' defined but not used [-Werror=unused-label]

This removes the unused label to avoid the warning.

Fixes: 702baebb8e00 ("soc: qcom: Remote filesystem memory driver")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
(cherry picked from commit d771d62e3139986cc62d2067b37ebbe33a6d3b08)

BUG=chromium:795946
BUG=b:79668211
TEST=Build and boot cheza.

Change-Id: I3b3624f5c984bf425553a2cf9876021b52e67e27
Signed-off-by: Ben Chan <benchan@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1119403
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/daa1453be564fb7f71d2bfcb2c8b531064147ece/drivers/soc/qcom/rmtfs_mem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/094c6006c2d30c01293767229c89daffbfb52b3c

commit 094c6006c2d30c01293767229c89daffbfb52b3c
Author: Jesse Chan <jc@linux.com>
Date: Sat Jun 30 09:14:20 2018

UPSTREAM: soc: qcom: rmtfs_mem: add missing MODULE_DESCRIPTION/AUTHOR/LICENSE

This change resolves a new compile-time warning
when built as a loadable module:

WARNING: modpost: missing MODULE_LICENSE() in drivers/soc/qcom/rmtfs_mem.o
see include/linux/module.h for more information

This adds the license as "GPL v2", which matches the header of the file.

MODULE_DESCRIPTION and MODULE_AUTHOR are also added.

Signed-off-by: Jesse Chan <jc@linux.com>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit 3b229bdb54cc83061b4b7840e3532316cb1ac7ce)

BUG=chromium:795946
BUG=b:79668211
TEST=Build and boot cheza.

Change-Id: I9e7f3293bc1cc11373af9160e507e1ed40f13a8a
Signed-off-by: Ben Chan <benchan@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1119404
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/094c6006c2d30c01293767229c89daffbfb52b3c/drivers/soc/qcom/rmtfs_mem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e0e856951f269e023d281dc280313796b241fafb

commit e0e856951f269e023d281dc280313796b241fafb
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Sat Jun 30 09:14:22 2018

UPSTREAM: soc: qcom: rmtfs-mem: Add support for assigning memory to remote

On some platform the remote processor's memory map is not statically
configured in TrustZone, so each memory region that is to be accessed by
the remote needs a call into TrustZone to set up the remote's
permissions.

Implement this for the rmtfs memory driver, to give the modem on 8996
access to the shared file system buffers.

Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit fa65f8045137d061134c15233d35a089cc85b87e)

BUG=chromium:795946
BUG=b:79668211
TEST=Build and boot cheza.

Change-Id: Ie7876df1eb0edc096685359a302cc8ca9a79deb4
Signed-off-by: Ben Chan <benchan@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1119465
Reviewed-by: Douglas Anderson <dianders@chromium.org>

[modify] https://crrev.com/e0e856951f269e023d281dc280313796b241fafb/drivers/soc/qcom/Kconfig
[modify] https://crrev.com/e0e856951f269e023d281dc280313796b241fafb/drivers/soc/qcom/rmtfs_mem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3a550ef38930c75a640f9272b4afe2ad8e698cfa

commit 3a550ef38930c75a640f9272b4afe2ad8e698cfa
Author: Stephen Boyd <swboyd@chromium.org>
Date: Tue Jul 24 07:46:39 2018

FROMGIT: arm64: dts: qcom: Add pmu node to sdm845

Add the CPU PMU on sdm845 to get perf support for hardware events.

Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit 000c4662ab3ef70789f724d44c55f69476fe6aa8
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)

BUG=chromium:795946
TEST="perf list | grep -i pmu" is a no longer empty

Change-Id: I8661da53c5eff962e698e38d36e3a102ec1eec5b
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1147211
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>

[modify] https://crrev.com/3a550ef38930c75a640f9272b4afe2ad8e698cfa/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/8644fe338fdc953b0a4fde388cb8b0053b18ff90

commit 8644fe338fdc953b0a4fde388cb8b0053b18ff90
Author: Johan Hovold <johan@kernel.org>
Date: Tue Jul 24 07:46:36 2018

FROMGIT: soc: qcom: rmtfs-mem: fix memleak in probe error paths

Make sure to set the mem device release callback before calling
put_device() in a couple of probe error paths so that the containing
object also gets freed.

Fixes: d1de6d6c639b ("soc: qcom: Remote filesystem memory driver")
Cc: stable <stable@vger.kernel.org>     # 4.15
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit 78ee559d7fc65e37670a46cfbeaaa62cb014af67
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)

BUG=chromium:795946
TEST=Things still work

Change-Id: I1cc393bb4029c61c30dec02bcf45a4e5f2a2452a
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1147240
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/8644fe338fdc953b0a4fde388cb8b0053b18ff90/drivers/soc/qcom/rmtfs_mem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/4dbdb7d0ef5fadb688a180f1929888dfa62a0967

commit 4dbdb7d0ef5fadb688a180f1929888dfa62a0967
Author: Niklas Cassel <niklas.cassel@linaro.org>
Date: Tue Jul 24 07:46:41 2018

FROMGIT: soc: qcom: llc-slice: Add missing MODULE_LICENSE()

Add missing MODULE_LICENSE().
According to the SPDX-License-Identifier, the license is GPL v2.

Fixes the following warning:
WARNING: modpost: missing MODULE_LICENSE() in drivers/soc/qcom/llcc-slice.o

Fixes: a3134fb ("drivers: soc: Add LLCC driver")
Signed-off-by: Niklas Cassel <niklas.cassel@linaro.org>
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit 4da3b0452bc66af8feca71b176668faf3d0e750d
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)

BUG=chromium:795946
TEST=Things still work

Change-Id: I20ce984933c3353302ae0bfdc1606402c4f1920f
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1147242
Reviewed-by: Guenter Roeck <groeck@chromium.org>

[modify] https://crrev.com/4dbdb7d0ef5fadb688a180f1929888dfa62a0967/drivers/soc/qcom/llcc-slice.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/028641b96a004a5442db772ec25e78bf2fd26147

commit 028641b96a004a5442db772ec25e78bf2fd26147
Author: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
Date: Tue Jul 24 07:46:31 2018

FROMGIT: drivers: qcom: rpmh: fix unwanted error check for get_tcs_of_type()

The patch fixes the bug reported by Dan Carpenter.
It removes the unnecessary err check for tcs reported by
static checker warning:

drivers/soc/qcom/rpmh-rsc.c:111 tcs_invalidate()
warn: 'tcs' isn't an ERR_PTR
See also:
drivers/soc/qcom/rpmh-rsc.c:178 get_tcs_for_msg() warn: 'tcs' isn't
an ERR_PTR
drivers/soc/qcom/rpmh-rsc.c:180 get_tcs_for_msg() warn: 'tcs' isn't
an ERR_PTR

https://www.spinics.net/lists/linux-soc/msg04624.html

Fixes: 9a3afcf ("drivers: qcom: rpmh-rsc: allow invalidation
of sleep/wake TCS")
Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
Reviewed-by: Lina Iyer <ilina@codeaurora.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit 6c805adf17d491ea66d3cf80db3ada75b7180268
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)

BUG=chromium:795946
TEST=Things still work

Change-Id: Ia75141cb2163e20149458461006bb9c4d8b52e16
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1147420
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/028641b96a004a5442db772ec25e78bf2fd26147/drivers/soc/qcom/rpmh-rsc.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/2527cf47b87d962c254e856b33bae813039d1a79

commit 2527cf47b87d962c254e856b33bae813039d1a79
Author: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
Date: Tue Jul 24 07:46:33 2018

FROMGIT: drivers: qcom: rpmh-rsc: fix the loop index check in get_req_from_tcs

get_req_from_tcs introduced in patch[1] returns tcs_request from
tcs_group. The size of tcs (of type - tcs_group) array in rsc_drv is
TCS_TYPE_NR. So the loop index needs to be iterated up to TCS_TYPE_NR only.

[1] https://patchwork.kernel.org/patch/10477547/

Signed-off-by: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit efa1c257b3fc7ef2a1db604b260784cc8bcdfd23
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)

BUG=chromium:795946
TEST=Things still work

Change-Id: I0c2129863854efac7be5a146ad09209c8da07d3a
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1147421
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/2527cf47b87d962c254e856b33bae813039d1a79/drivers/soc/qcom/rpmh-rsc.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e1d4d3fe5dac336d6f5d7eaea1be77959a05d30a

commit e1d4d3fe5dac336d6f5d7eaea1be77959a05d30a
Author: Douglas Anderson <dianders@chromium.org>
Date: Tue Jul 24 19:44:09 2018

CHROMIUM: arm64: boot: dts: Mark qupv3_id_0 "okay" for sdm845-cheza

In the commit ("arm64: dts: sdm845: Default qupv3_id_0 as "disabled"
like _id_1") AKA CL:Ia7345869796d079756d0e579bfd5f2e151592cf0 I'm
fixing the main sdm845.dtsi file to have qupv3_id_0 disabled by
default.  Mark is "okay" for cheza since we need it.

BUG=chromium:795946
TEST=Things still work

Change-Id: I28b53445a8c186b8edeb6e56c4ae951470c382b2
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1147118
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/e1d4d3fe5dac336d6f5d7eaea1be77959a05d30a/arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/0fbaba410f9c60ee1ace0a7374dcf45dd1753eab

commit 0fbaba410f9c60ee1ace0a7374dcf45dd1753eab
Author: Douglas Anderson <dianders@chromium.org>
Date: Tue Jul 24 19:44:11 2018

FROMGIT: arm64: dts: sdm845: Default qupv3_id_0 as "disabled" like _id_1

In commit 8e4947ee477d ("arm64: dts: qcom: sdm845: Add I2C, SPI, and
UART9 nodes") I accidentally forgot to add the line:

  status = "disabled";

to qupv3_id_0 to match qupv3_id_1.  Add it now.  NOTE: right now the
only sdm845 board with a device tree in mainline is MTP and that board
currently doesn't have any peripherals under qupv3_id_0.  If any board
was currently using peripherals under qupv3_id_0 then that board would
need to add this snippet to their board dts file:

  &qupv3_id_0 {
     status = "okay";
  };

Signed-off-by: Douglas Anderson <dianders@chromium.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit 499ff1165df172c6da56ff2dccfec0a58dfaf7b3
 git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git for-next)

BUG=chromium:795946
TEST=Things still work

Change-Id: Ia7345869796d079756d0e579bfd5f2e151592cf0
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1147119
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/0fbaba410f9c60ee1ace0a7374dcf45dd1753eab/arch/arm64/boot/dts/qcom/sdm845.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/e76c7e3726c6bd58b10fff0b173e9ff2c1a868ac

commit e76c7e3726c6bd58b10fff0b173e9ff2c1a868ac
Author: Stephen Boyd <swboyd@chromium.org>
Date: Wed Aug 08 09:00:33 2018

CHROMIUM: arm64: dts: qcom: Introduce cheza-r2 dts

Very similar to -r1.  Also add the revision into the model name to
make debugging easier.

BUG=chromium:795946
TEST=Boot up while plugging your nose.

Change-Id: I2b2374882eb8c9d0edc3109ad24a2ec0aa146e76
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1166241

[modify] https://crrev.com/e76c7e3726c6bd58b10fff0b173e9ff2c1a868ac/arch/arm64/boot/dts/qcom/Makefile
[add] https://crrev.com/e76c7e3726c6bd58b10fff0b173e9ff2c1a868ac/arch/arm64/boot/dts/qcom/sdm845-cheza-r2.dts
[modify] https://crrev.com/e76c7e3726c6bd58b10fff0b173e9ff2c1a868ac/arch/arm64/boot/dts/qcom/sdm845-cheza-r1.dts
[modify] https://crrev.com/e76c7e3726c6bd58b10fff0b173e9ff2c1a868ac/arch/arm64/boot/dts/qcom/sdm845-cheza-r0.dts

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7c5bce80ba7b19b2692565415f198a1bbb8f41ad

commit 7c5bce80ba7b19b2692565415f198a1bbb8f41ad
Author: Douglas Anderson <dianders@chromium.org>
Date: Sat Aug 25 19:01:43 2018

CHROMIUM: arm64: dts: qcom: sdm845-cheza en_pp3300_dx_edp drive str = 2

Getting rid of this stray "drive strength = 2" that was left in.

BUG=chromium:795946
TEST=Display still works OK.

Change-Id: I592b70b6d7b4aaa709eaa2681d55011d8decde35
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1188782
Reviewed-by: Stephen Boyd <swboyd@chromium.org>

[modify] https://crrev.com/7c5bce80ba7b19b2692565415f198a1bbb8f41ad/arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/3752bac97a7a02be4927fc8af31d899bbaab0f55

commit 3752bac97a7a02be4927fc8af31d899bbaab0f55
Author: Douglas Anderson <dianders@chromium.org>
Date: Wed Sep 05 04:03:56 2018

CHROMIUM: config: Turn on CONFIG_RESET_QCOM_AOSS configs

This is the equivalent of:

  echo 'CONFIG_RESET_QCOM_AOSS=y' | tee -a \
    chromeos/config/arm64/chromiumos-qualcomm.flavour.config \
    chromeos/config/arm64/chromiumos-arm64.flavour.config
  ./chromeos/scripts/kernelconfig olddefconfig

...atop a config that was normalized before the patches introducing
the new option.

BUG=chromium:795946
TEST=Build and boot

Change-Id: Ie93f8c08ac32ae8136cd864d231f65859e759fa4
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1204751
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>

[modify] https://crrev.com/3752bac97a7a02be4927fc8af31d899bbaab0f55/chromeos/config/arm64/chromiumos-arm64.flavour.config
[modify] https://crrev.com/3752bac97a7a02be4927fc8af31d899bbaab0f55/chromeos/config/arm64/chromiumos-qualcomm.flavour.config

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/c5ebe7c65ab5fafee4802625bd3445da7158ba4e

commit c5ebe7c65ab5fafee4802625bd3445da7158ba4e
Author: Bjorn Andersson <bjorn.andersson@linaro.org>
Date: Thu Nov 01 04:59:20 2018

UPSTREAM: soc: qcom: rmtfs-mem: Validate that scm is available

The scm device must be present in order for the rmtfs driver to
configure memory permissions for the rmtfs memory region, so check that
it is probed before continuing.

Cc: stable@vger.kernel.org
Fixes: fa65f8045137 ("soc: qcom: rmtfs-mem: Add support for assigning memory to remote")
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit 137dc5843faeacabf48fc22a8dc58c4e0b4f0927)

BUG=chromium:795946
TEST=build for cheza

Change-Id: I92b45c11430eb2119202e56779a4af260d417b1c
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1310512
Commit-Ready: Evan Green <evgreen@chromium.org>
Reviewed-by: Evan Green <evgreen@chromium.org>

[modify] https://crrev.com/c5ebe7c65ab5fafee4802625bd3445da7158ba4e/drivers/soc/qcom/rmtfs_mem.c

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/kernel/+/2f65c90d623abaed4b6854a7fc983a797077b8e5

commit 2f65c90d623abaed4b6854a7fc983a797077b8e5
Author: Lina Iyer <ilina@codeaurora.org>
Date: Thu Nov 01 04:59:21 2018

UPSTREAM: drivers: qcom: rpmh-rsc: clear wait_for_compl after use

The wait_for_compl register ensures the request sequence is maintained
when sending requests from the TCS. Clear the register after sending
active request and during invalidate of the sleep and wake TCS.

Reported-by: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
Signed-off-by: Lina Iyer <ilina@codeaurora.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
(cherry picked from commit 09e97b6c8754c91470455e69ebd827b741f80af5)

BUG=chromium:795946
TEST=build for cheza

Change-Id: I6ef8f03d7f0d7fa859442e4a0b35d85a04428532
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1310953
Commit-Ready: Evan Green <evgreen@chromium.org>
Reviewed-by: Evan Green <evgreen@chromium.org>

[modify] https://crrev.com/2f65c90d623abaed4b6854a7fc983a797077b8e5/drivers/soc/qcom/rpmh-rsc.c