CHROMIUM : DPTF update to v8.0.10

Fixed:
        S3 Resume issue
        Kernel panic fix

BUG=chrome-os-partner:26591
BUG=chrome-os-partner:27086
BUG=chrome-os-partner:27463
TEST=Manually tested
CQ-DEPEND=CL:192637

Change-Id: I1b2076c694f92a5535a6d5f81b4816156a642e3d
Signed-off-by: Brad Geltz <brad.geltz@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/192022
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Derek Basehore <dbasehore@chromium.org>
Commit-Queue: Duncan Laurie <dlaurie@chromium.org>
(cherry picked from commit 1704f64a53dfb7ba2ac1e5a0c4e279511dfee4e0)
Reviewed-on: https://chromium-review.googlesource.com/192636
Tested-by: Duncan Laurie <dlaurie@chromium.org>
BACKPORT: ASoC: Maxim 98090: Add PLL lock irq handler

This patch will try to recover the PLL lock on PLL unlocked interrupt.

The PLL lock can be recovered by toggling the SHDN bit OFF/On and then re-checking
the PLL state. This patch also masks interrupt sources until their handlers complete.

Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
(cherry picked from commit 27b0e2a703fdd1ddfb69cc0b0ab3e89f0478a220)

BUG=chrome-os-partner:26948
TEST=Manual: Check that silent playback is rare

Change-Id: Id9e5cb1f244f6e5b54d03ed5d602cda27a54b9cb
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/191740
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Jim Bride <jim.bride@intel.com>
(cherry picked from commit d6ffa00d9e03a07d887424ff4a1f537f7ece4d1f)
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/193070
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
BACKPORT: ASoC: BYT-max98090: Enable the PLL interrupt source.

Enable the PLL lock failure interrupt source so that the codec driver
can handle PLL lock failures.

Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
(cherry picked from commit fdc5e37332fc7ff6e2ff72f60fb0d7c8452a995d)
Signed-off-by: Benson Leung <bleung@chromium.org>

Conflicts:

	sound/soc/intel/byt-max98090.c

BUG=chrome-os-partner:26948
TEST=Manual: Check that silent playback is rare

Change-Id: I77653f177b06f672c269137aeeafd6694c367de9
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/191741
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Jim Bride <jim.bride@intel.com>
(cherry picked from commit b9e82584475159c80655a63fa008e665281cc182)
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/193071
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
BACKPORT: ASoC: Intel: Add notifier methods to receive confirmation of stream start/stop

Add callbacks so that we can notify other users that the FW has started
the stream (and LRCLK and BCLK). This is run as scheduled work to avoid
locking problems (since IRQs are OFF).

This waits for receipt of stream start/stop message from the DSP FW so
clocks will be running at this point.

Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
(cherry picked from commit b62547e7320597afbcf10ecac78ff3c9fada6e80)

BUG=chrome-os-partner:26948
TEST=Manual: Check that silent playback is rare

Change-Id: Id929657b908d938c999b1b6e1f282d65565d2c94
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/191742
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Jim Bride <jim.bride@intel.com>
(cherry picked from commit aecff8e896edefdd6d72965ee7e851b1c95f81f0)
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/193072
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
BACKPORT: ASoC: Byt-max98090: Add callback for stream start.

Register a callback for stream start to enable SHDN bit after stream has
started.

Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
(cherry picked from commit ffb290a85f226e5678b6db18fca0e9a5ee4fbc33)
Signed-off-by: Benson Leung <bleung@chromium.org>

Conflicts:

	sound/soc/intel/byt-max98090.c

BUG=chrome-os-partner:26948
TEST=Manual: Check that silent playback is rare

Change-Id: I3a78c0f95ef0b0368480e790b03845001be12048
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/191743
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Jim Bride <jim.bride@intel.com>
(cherry picked from commit c05a0bf4a77d18a3cd749a6ec4af5d9ad18c1067)
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/193073
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
BACKPORT: HACK: i2c: designware: Slow down all buses for now

In order to get rid of I2C timeout messages we see after S3 resume when
talking to the codec.

Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
(cherry picked from commit 0e09f781d3b087dacd273b174c0cf717a9dc9774)
Signed-off-by: Benson Leung <bleung@chromium.org>

Conflicts:

	drivers/i2c/busses/i2c-designware-platdrv.c

BUG=chrome-os-partner:26948
TEST=Manual: Check that silent playback is rare

Change-Id: I3ba31002ed75d82c137e7fe4e2edd0f0b95364f4
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/191744
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Jim Bride <jim.bride@intel.com>
(cherry picked from commit bdde7bf74cc49e94a67eb62cfc47fc3b6fb31bfb)
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/193074
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
BACKPORT: ASoC: Intel: Make sure sst_byt_notify_work is run before freeing the stream

There is possibility that sst_byt_notify_work() is run after
sst_byt_stream_free() which can lead to a kernel crash since struct
sst_byt_stream is freed at that point.

Fix this by calling cancel_work_sync() for the stream notify work before
freeing the stream structure.

Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
(cherry picked from commit 114c5b96e955a1d8fb340743eea376e9eee6ea77)

BUG=chrome-os-partner:26948
TEST=Manual: Check that silent playback is rare

Change-Id: Ib3d04b2b1d6491fffba6af6b7ebca8ee95570074
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/191745
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Brian J Lovin <brian.j.lovin@intel.com>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Jim Bride <jim.bride@intel.com>
(cherry picked from commit 3038d8dcee37729f31e7de2d8ff57a6199f447a8)
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/193075
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
CHROMIUM: memory: tegra124: init EMC driver earlier

Currently the init of EMC driver is later than DVFS driver. The DVFS
driver needs to query EMC table for updating its core DVFS table.
Therefore the EMC driver should be init earlier.

BUG=chrome-os-partner:27667
TEST=built kernel and boot

Change-Id: I3f4a0fbf18ffa6c6e54b00f7fe06ee5b4103b425
Signed-off-by: Danny Huang <dahuang@nvidia.com>
Reviewed-on: https://chromium-review.googlesource.com/192969
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Commit-Queue: Andrew Bresticker <abrestic@chromium.org>
(cherry picked from commit 379481625e95304323d2d650221a403022275830)
Reviewed-on: https://chromium-review.googlesource.com/193501
Tested-by: Andrew Bresticker <abrestic@chromium.org>
CHROMIUM: ARM: dts: nyan: big: add thermal zone for as3722 thermal

Add device node for as3722 thermal and add it to thermal-zones.
Bind this thermal zone with tj-temperature-throttling cooling device.

BUG=chrome-os-partner:27597
TEST=Can read temperature, detect thermal alarm and trigger throttling.

Change-Id: I8c689e91e8ff803ed7caa3af080be61c4b76d40a
Signed-off-by: Wei Ni <wni.nvidia@gmail.com>
Reviewed-on: https://chromium-review.googlesource.com/189802
Reviewed-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Commit-Queue: Andrew Bresticker <abrestic@chromium.org>
(cherry picked from commit 691fae2d74229a2605f7a19302c801b60df20a5b)
Reviewed-on: https://chromium-review.googlesource.com/193502
Tested-by: Andrew Bresticker <abrestic@chromium.org>
CHROMIUM: ASoC: max98090 - Clear shdn when going from off to standby.

Power off when going in to off and power back on when going from off to
standby.

BUG=chrome-os-partner:27606
TEST=aplay something.wav, hear audio.

Change-Id: Ibb00c65ef66e6cd10635520cc44df28c56708766
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/192885
Tested-by: Rhyland Klein <rklein@nvidia.com>
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Reviewed-by: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
(cherry picked from commit a5ac1c2ee250dad228a0f6dd40fa9ca5675e8827)
Reviewed-on: https://chromium-review.googlesource.com/193433
CHROMIUM: ARM: dts: nyan: update skin temp calibration data

Update the skin temperature calibration data (coeffs and toffset)
for Norrin.

BUG=chrome-os-partner:27599
TEST=Verfied. Check /sys/device/soc0/therm-est.10/, the values
are right.

Change-Id: I775f754fc7d2d95de393af426726b38b6576d335
Signed-off-by: Wei Ni <wni@nvidia.com>
Reviewed-on: https://chromium-review.googlesource.com/187761
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Tested-by: Andrew Bresticker <abrestic@chromium.org>
Commit-Queue: Andrew Bresticker <abrestic@chromium.org>
(cherry picked from commit 87f81d3f8990bf1bcaf95ff9ae432787b2a58474)
Reviewed-on: https://chromium-review.googlesource.com/193710
CHROMIUM: ARM: dts: nyan: increase max current for vdd_core

Increase max current for vdd_core to 4A as its
powered by AS3729. Rest SD0 and SD6 by AS3728 with
max current as 3.5A

BUG=chrome-os-partner:27664
TEST=Booted and checked register 0x5a and 0x5b
to be 0x78 and 0x10

Change-Id: Ic450cca0e5d2bfa081e6995177c77d5e2720103e
Signed-off-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-on: https://chromium-review.googlesource.com/192958
Reviewed-by: Joseph Lo <josephl@nvidia.com>
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Commit-Queue: Andrew Bresticker <abrestic@chromium.org>
(cherry picked from commit 11483f181cff577d753f3a8e4b93d33931894b32)
Reviewed-on: https://chromium-review.googlesource.com/193711
Tested-by: Andrew Bresticker <abrestic@chromium.org>
CHROMIUM: regulator: as3722: increase max oc limit

With AS3729 and AS3722 combination, max coil peak
current limit is 4A. This patch add supports for that.

BUG=chrome-os-partner:27664
TEST=Booted and checked max current with dts changes

Change-Id: I48025e9e6e38e89bdca14d59fd673f1347b07854
Signed-off-by: Bibek Basu <bbasu@nvidia.com>
Reviewed-on: https://chromium-review.googlesource.com/192957
Reviewed-by: Joseph Lo <josephl@nvidia.com>
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Commit-Queue: Andrew Bresticker <abrestic@chromium.org>
(cherry picked from commit 7f5f2eeef9afc6cbd9655adcec5c2204e5c56d57)
Reviewed-on: https://chromium-review.googlesource.com/193623
Tested-by: Andrew Bresticker <abrestic@chromium.org>
BACKPORT: ASoC: Maxim98090: Move microphone bias voltage setting to probe function

Microphone bias level configuration register can configure voltage between
2.2 V and 2.8 V but doesn't manage is voltage on or off. Microphone bias
on/off state is controlled by "MICBIAS" DAPM widget.

Therefore there is no need to update bias voltage conditionally depending on
jack state each time when codec goes to SND_SOC_BIAS_ON state and setting
can be moved to max98090_probe() as driver currently doesn't support other
levels than 2.8 V.

Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
(cherry picked from commit 29e852c3f35dcee2d3a19654c2d85cc15bb7ad9b)

BUG=chrome-os-partner:27650
TEST=Manual: Record audio through apple headset and make sure playback
is recognizable

Original-Change-Id: I1e94474726b630895053039c2175c994cbffa029
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/192951
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
(cherry picked from commit 5c0f9884e72a2ad357e7f3a8bf238113fa553339)

Change-Id: Ib34743938424271218f6f158d95611383a8d412e
Reviewed-on: https://chromium-review.googlesource.com/193662
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
CHROMIUM: video: tegra: host: Fix PMU irq enable ordering.

Do not unmask PMU interrupts until after the PMU software
module is fully initialized. This ensures that all PMU
software context will be initialized when the first PMU
interrupt is handled.

BUG=chrome-os-partner:27803
TEST=10000 cycles LP0 stress passed(along with other changes)

Change-Id: Ic21fcf9c7f4efe798010ae5c996c024278176930
Signed-off-by: Neil Gabriel <ngabriel@nvidia.com>
Signed-off-by: Peer Chen <pchen@nvidia.com>
Tested-by: Peer Chen <pchen@nvidia.com>
Reviewed-on: https://chromium-review.googlesource.com/193574
Reviewed-by: Andrew Bresticker <abrestic@chromium.org>
Tested-by: Mark Zhang <markz@nvidia.com>
Commit-Queue: Andrew Bresticker <abrestic@chromium.org>
(cherry picked from commit cb2e88510db4a211731fde7f7a173fe5e7c3a023)
Reviewed-on: https://chromium-review.googlesource.com/193728
Tested-by: Andrew Bresticker <abrestic@chromium.org>
CHROMIUM: Input: elan_i2c - Add structure point checking

We add checking structure point is null or not before calling
input sub-system in elan_isr() to avoid excepted kernl panic.

Signed-off-by: Duson Lin <dusonlin@emc.com.tw>
BUG=chrome-os-partner:27191
TEST=on chromebook with Elan touchpad, boot and touchpad works.

Change-Id: I987151e41b985ee2b93b6468f40a73bf822143f9
Reviewed-on: https://chromium-review.googlesource.com/191666
Reviewed-by: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
(cherry picked from commit 109129a524d5c660e1746823ab14246be4390a8c)
Reviewed-on: https://chromium-review.googlesource.com/193774
Commit-Queue: Benson Leung <bleung@chromium.org>
UPSTREAM: mwifiex: fix spinlock bad magic bug

[ 6630.450908] BUG: spinlock bad magic on CPU#1,
               ksdioirqd/mmc1/355
[ 6630.450914] Unable to handle kernel NULL pointer dereference
               at virtual address 0000004f
[ 6630.450919] pgd = ecbd8000
[ 6630.450926] [0000004f] *pgd=00000000
[ 6630.450936]  lock: 0xeea4ab08, .magic: 00000000,
               .owner: <none>/-1, .owner_cpu: 0
[ 6630.450939] Backtrace:
[ 6630.450956] [<c010d354>] (unwind_backtrace+0x0/0x118) from
               [<c060c238>] (dump_stack+0x28/0x30)
[ 6630.450960] Internal error: Oops: 5 [#1] SMP ARM
[ 6630.450964] Modules linked in: uvcvideo videobuf2_vmalloc
[ 6630.450980] [<c060c238>] (dump_stack+0x28/0x30) from
               [<c0315ab4>] (spin_dump+0x80/0x94)
[ 6630.450988] [<c0315ab4>] (spin_dump+0x80/0x94) from
               [<c0315af4>] (spin_bug+0x2c/0x30)
[ 6630.450996] [<c0315af4>] (spin_bug+0x2c/0x30) from
               [<c0315b80>] (do_raw_spin_lock+0x28/0x15c)
[ 6630.451004] [<c0315b80>] (do_raw_spin_lock+0x28/0x15c) from
               [<c0610c24>] (_raw_spin_lock_irqsave+0x20/0x28)
[ 6630.451016] [<c0610c24>] (_raw_spin_lock_irqsave+0x20/0x28)
               from [<bf07a7f4>] (mwifiex_exec_next_cmd
                                  +0x6c/0x45c [mwifiex])
[ 6630.451030] [<bf07a7f4>] (mwifiex_exec_next_cmd+0x6c/0x45c
               [mwifiex]) from [<bf07834c>]
               (mwifiex_main_process+0x2c8/0x464 [mwifiex])
[ 6630.451047] [<bf07834c>] (mwifiex_main_process+0x2c8/0x464
               [mwifiex]) from [<bf0a093c>]
               (mwifiex_sdio_interrupt+0xc8/0x1cc [mwifiex_sdio]
[ 6630.451064] [<bf0a093c>] (mwifiex_sdio_interrupt+0xc8/0x1cc
               [mwifiex_sdio]) from [<c04bbde0>]
               (sdio_irq_thread+0x178/0x31c)
[ 6630.451079] [<c04bbde0>] (sdio_irq_thread+0x178/0x31c) from
               [<c0145514>] (kthread+0xc8/0xd8)
[ 6630.451095] [<c0145514>] (kthread+0xc8/0xd8) from
               [<c0106118>] (ret_from_fork+0x14/0x20)

This bug has introduced/exposed due to recent patch in which we
cancel pending commands before suspend (using hs_enabling flag).
The NULL pointer is dereferenced when both
mwifiex_cancel_all_pending_cmd() and mwifiex_exec_next_cmd()
try to access cmd pending queue simultaneously.

Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
Signed-off-by: Bing Zhao <bzhao@marvell.com>
Signed-off-by: Paul Stewart <pstew@chromium.org>

(cherry picked from commit 34421ad4527fef1c59a697933e8c220a491bf3e8)

BUG=chrome-os-partner:26770,26916
TEST=run "suspend_stress_test" overnight and don't get
"BUG: spinlock bad magic" kernel panic.

Change-Id: I14b5d41a62c935e2ac3e6eb2c0de89f0e5c2a227
Reviewed-on: https://chromium-review.googlesource.com/193871
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
Revert "CHROMIUM: cfg80211: hold BSS over association process"

This reverts commit a2612721d6b1a7e61a4d355d420c429e53418981.

Signed-off-by: Jason Abele <jabele@chromium.org>
Signed-off-by: Paul Stewart <pstew@chromium.org>

(cherry picked from commit d2426453b6ca152e88328d3708c954a33be8bdba)
Originally-Reviewed-on: https://chromium-review.googlesource.com/193603

BUG=chrome-os-partner:27738
TEST=On 8897+PCIe:
   test_that chromeos5-372g-host3.cros network_WiFi_Roam.wifi_roamNone \
       network_WiFi_Roam.wifi_roamWEP network_WiFi_VerifyRouter \
       network_WiFi_PMKSACaching
ensure that the PMKSACaching test passes and that "iw mlan0 scan" does
not return a ton of very old BSSes.

Change-Id: I7951038d582c5353e3dfed9c52787c1fa514d9da
Reviewed-on: https://chromium-review.googlesource.com/193863
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
CHROMIUM: mwifiex: Disable association in VHT where prohibited

Disable VHT association if the channel configuration does not
support 80MHz wide bands.  As a result of this change we no
longer need to assume VHT is disabled for IBSS except for this
channel condition test.  While here, modify the mwifiex world
regulatory settings to allow 80MHz bands by default.

Signed-off-by: Paul Stewart <pstew@chromium.org>

Originally-Reviewed-on: https://chromium-review.googlesource.com/193172
(cherry picked from commit a9b164742ab663f0f5c6c3b63d4bc2b4fe750b9f)

BUG=chrome-os-partner:26747
TEST=Associate under ideal circumstances to a VHT AP, but before
doing so do alternately: "iw reg set 00" and "iw reg set <domain
that doesn't support 80MHz wide bands in 5GHz>".  In the former
case, we see that the client associated supporting VHT and is
using that during on the link.  In the latter case, the system
associates using only 802.11n and does not use VHT rates even
under ideal circumstances.

Change-Id: I3166a348b4105edee1a23dbe671091902fb3b438
Reviewed-on: https://chromium-review.googlesource.com/193869
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
CHROMIUM: video: tegra: dc: set emc clocks to highest round rate

Currently, when there are multiple dc's or the bandwidth requested
is too high, the fallback frequency is ULONG_MAX, but it should be
set to the highest allowed emc frequency instead, using
clk_round_rate().  This fixes the HDMI flickering issue.

BUG=chrome-os-partner:27651
TEST=HDMI does not flicker after wakeup from idle or in docked mode

Signed-off-by: Isaac Simha <isimha@nvidia.com>
Change-Id: I3ea744ae29b23ab6c9f4b6eda62f3c92e138ecb8
Reviewed-on: https://chromium-review.googlesource.com/192953
Reviewed-by: Dylan Reid <dgreid@chromium.org>
(cherry picked from commit 6ecb17306b587656e6c25804a8a3a540ee235c12)
Reviewed-on: https://chromium-review.googlesource.com/194211