git.cascardo.eti.br Git - cascardo/linux.git/log

CHROMIUM: sd: Fix warning

drivers/scsi/sd.c:2676:2: warning: assignment from incompatible pointer type [enabled by default]
drivers/scsi/sd.c:2913:2: warning: assignment from incompatible pointer type [enabled by default]

Since there's no way to return an error, do a WARN_ON() in the error
case instead.

BUG=chromium-os:34287
TEST=none (we need an automated test for error injection here)

Change-Id: Idaf0c0184e81ef7bac63b1deeda1a7690aa48a42
Signed-off-by: Olof Johansson <olofj@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32830
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>

CHROMIUM: sbs-battery: Fixed wrong dev_err() call

The dev_err() call was missing the dev and so would crash
whenever it was called.

BUG=chrome-os-partner:13857
TEST=Hack the "if" statement to always hit and rebuild kernel.
See the error printed properly.

Change-Id: Ic2f33e8db3259847d120558542c1d47d8ff4c09c
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32775
Reviewed-by: Rong Chang <rongchang@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Reviewed-by: Jon Kliegman <kliegs@chromium.org>
Reviewed-by: Cheng-Yi Chiang <cychiang@chromium.org>

CHROMIUM: config: Renormalize splitconfig

Just ran: ./chromeos/scripts/kernelconfig oldconfig
...and hit return for everything. AKA: no functional change
here, this just tells us where we are.

BUG=None
TEST=Compiled and booted on one device.

Change-Id: I2221089cff75ea89150fa6981a7f5f97c5109eb6
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32765
Reviewed-by: Che-Liang Chiou <clchiou@chromium.org>
Reviewed-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Paul Taysom <taysom@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>

exynos5: usb: Fix EXYNOS5_USB_CFG to use SYSREG bank

The EXYNOS5_USB_CFG register is in the SYSREG bank of register.
Fix the define to point to that and move it into the setup-usb-phy.c
file next to the EXYNOS4_USB_CFG register

BUG=chrome-os-partner:13859
TEST=Changed dev_dbg to dev_info and validated correct output
Checked values of SYSREG(0x230) and PMUREG(0x230) and confirmed
correct settings on boot.
Signed-off-by: Jonathan Kliegman <kliegs@chromium.org>
Change-Id: I4d643ca982e3b92ed114d4651db9f98e7af7be0f
Reviewed-on: https://gerrit.chromium.org/gerrit/32773
Tested-by: Jon Kliegman <kliegs@chromium.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Commit-Ready: Jon Kliegman <kliegs@chromium.org>

drm/exynos: fimd: Disable all windows on power off

Make sure we disable all windows when we power off. We were seeing
crashes on HDMI hotplug, this occurred because we DPMS off on hotplug,
then resize the scanout buffer. This resize deletes the old buffer,
which calls fimd_win_disable. This function returns early and the window
is never disabled. Then when we try to delete the buffer, we get a crash
in iommu, presumably because the buffer is still being used by the
enabled window.

BUG=chrome-os-partner:13349
TEST=Tested boot with hdmi and hotplug

Change-Id: I134d510ae4abc5604606f565ce7d631d96918477
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32568
Tested-by: Shirish S <shirish@chromium.org>

drm/exynos: fimd: Fix compilation warning

This patch fixes a compilation warning (and possibly) use uninitialized
in fimd_display_power_on by returning early if we received an invalid
DPMS mode value.

BUG=chrome-os-partner:13349
TEST=Tested on snow

Change-Id: I30b8840c71d3f7239871836b184817fc23b25b7a
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32572

CHROMIUM: dm: bootcache Device mapper for bootcache

Missed the last set of changes in prevous delivery.
Changes from waitq to competion.

BUG=chromium-os:25441
TEST=boot the system with bootcache enabled

Change-Id: I452f8315f3e8544df72e7b202c2e365e39834a4b
Signed-off-by: Paul Taysom <taysom@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32427
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

ARM: SAMSUNG: use spin_lock_irqsave() in clk_set_rate

The clk_set_rate function has been modified to save and restore
IRQs during spin lock/unlock.

BUG=chrome-os-partner:13840
TEST=Booted kernel and ran video overnight.

Change-Id: I5c746303e141b8fc5e2ce1c0cb9943d5c8c6cd6d
Signed-off-by: Prathyush K <prathyush.k@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/32650
Tested-by: Prathyush Kalashwaram <prathyush@chromium.org>
Reviewed-by: Prashanth Godrehal <prashanth.g@samsung.com>
Reviewed-by: Abhinav Kochhar <kochhar.abhinav@gmail.com>
Tested-by: Abhinav Kochhar <kochhar.abhinav@gmail.com>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Doug Anderson <dianders@chromium.org>

Revert "UPSTREAM: dma: pl330: assign a new cookie when restarting tx descriptors in cyclic mode"

This reverts commit d49ef2b0f56719541fa06135379e8490e8544d41.

As Vinod Koul has suggested a better way to handle, this patch is not
required now and his patch already got merged in the mainline and gerrit.

chrome-os-partner:12565
TEST=built for emerge-daisy chromeos-kernel and booted on one board.

Change-Id: I1cea5efd08e29ed3ebea898595a5227bd925f748
Signed-off-by: Padmavathi Venna <padma.v@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/32505
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Commit-Ready: Doug Anderson <dianders@chromium.org>

arm: exynos: add busfreq trace events

Add exynos_busfreq_target_{mif,int} events to monitor operation
and remove printk that is now duplicate information.

Signed-off-by: Sam Leffler <sleffler@chromium.org>
BUG=chrome-os-partner:13801
TEST=monitor evevents while playing video

Change-Id: I0e82ad4afb72e6b4664dbd95d206186864a9266e
Reviewed-on: https://gerrit.chromium.org/gerrit/32560
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Commit-Ready: Sam Leffler <sleffler@chromium.org>
Tested-by: Sam Leffler <sleffler@chromium.org>

CHROMIUM: iio: isl29018: Support fractional ALS scaling.

The Industrial IO framework supports scaling ADC values by fractions,
but most drivers default to using whole numbers.
This change turns on fractional scaling in the isl29018 driver.

BUG=chrome-os-partner:11948
TEST='echo 1.5 > in_illuminance_calibscale', and verify it has the
expected effect on in_illuminance0_input.

Change-Id: Ie8e2e55a2a2fe008de513abd955615f5d16204ce
Signed-off-by: Bryan Freed <bfreed@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31683
Reviewed-by: Grant Grundler <grundler@chromium.org>

CHROMIUM: mac80211: prevent work queueing while quiescing on suspend

Do not emit a warning in that case, since there is nothing else in mac80211
that would effectively prevent more work from being queued.

BUG=chrome-os-partner:10785
TEST=per crosbug.com/p/10785#c54

Change-Id: Ic14aee400184772cbe19af65f01de11f683559fe
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32602

CHROMIUM: ath9k: improve resume reliability

Ensure that drv_start() always returns true, as a failing hw start usually
eventually leads to crashes when there's still a station entry present.
Call a power-on reset after resume and also if a hw reset fails, this should
bring the hardware back to life again.

BUG=chrome-os-partner:10785
TEST=per crosbug.com/p/10785#c54

Change-Id: Ib397e9b06f60f5de9bf1611f9c414f823e1770ff
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32599

CHROMIUM: ath9k: Change rateset calculation

Commit "ath9k: Change rate control to use legacy rate as last MRR"
resulted in the mixing of HT/legacy rates in a single rateset,
which is undesirable. Revert this behavior.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: I37a718181269181d78ac1a11f91e4971acd96920
Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32623

CHROMIUM: ath9k: Fix RTS/CTS rate selection

The current method of assigning the RTS/CTS rate is completely
broken for HT mode and breaks P2P operation. Fix this by using
the basic_rates provided to the driver by mac80211. For now,
choose the lowest supported basic rate for HT frames.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: I3ced4be51bec5b3f495df4cac1a6048b03e136f4
Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32622

CHROMIUM: ath9k: Fix a crash in 2 WIRE btcoex chipsets

Generic timers for BTCOEX functionality is applicable
only for 3 WIRE BTCOEX (and MCI) chipsets.
Hence btcoex->no_stomp_timer is allocated only 3 WIRE
btcoex chipsets and in all the other cases its NULL.
Make sure we stop the generic timer only if
'btcoex->hw_timer_enabled' is true(only if its up and
running)

Fixes the following crash

[68757.020454] BUG: unable to handle kernel NULL pointer dereference at 0000000c
[68757.020916] IP: [<f9b055c3>] ath9k_hw_gen_timer_stop+0x13/0x80 [ath9k_hw]
[68757.021251] *pde = 00000000
[68757.024384] EIP: 0060:[<f9b055c3>] EFLAGS: 00010082 CPU: 0
[68757.024384] EIP is at ath9k_hw_gen_timer_stop+0x13/0x80 [ath9k_hw]
[68757.024384] EAX: d32d0000 EBX: d32d0000 ECX: 00000000 EDX: 00000000
[68757.024384] ESI: e67c24c0 EDI: 00000296 EBP: e137be2c ESP: e137be20
[68757.024384]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[68757.024384] CR0: 8005003b CR2: 0000000c CR3: 00b99000 CR4: 000407d0
[68757.024384] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[68757.024384] DR6: ffff0ff0 DR7: 00000400
[68757.024384] Process kworker/u:2 (pid: 8917, ti=e137a000 task=ea7a6860 task.ti=e137a000)
[68757.024384] Stack:
[68757.024384]  c06c4676 d32d0000 e67c24c0 e137be38 f81c9590 e67c1ca0 e137be40 f81c95d9
[68757.024384]  e137be64 f81cd1c5 00000246 00000002 d32d0000 e67c05e0 e67c1ca0 e67c05e0
[68757.024384]  00000000 e137beac f81cdfa0 e137be84 00000246 00000246 e67c1ca0 e67c1ca0
[68757.024384] Call Trace:
[68757.024384]  [<c06c4676>] ? _raw_spin_lock_irqsave+0x86/0xa0
[68757.024384]  [<f81c9590>] ath9k_gen_timer_stop+0x10/0x40 [ath9k]
[68757.024384]  [<f81c95d9>] ath9k_btcoex_stop_gen_timer+0x19/0x20 [ath9k]
[68757.024384]  [<f81cd1c5>] ath9k_ps_restore+0x85/0x110 [ath9k]
[68757.024384]  [<f81cdfa0>] ath9k_config+0x220/0x520 [ath9k]
[68757.024384]  [<f81cd47d>] ? ath9k_flush+0x15d/0x1b0 [ath9k]
[68757.024384]  [<f85c7ca5>] ieee80211_hw_config+0x135/0x2c0 [mac80211]
[68757.024384]  [<f860e3c8>] ieee80211_dynamic_ps_enable_work+0x198/0x5f0 [mac80211]

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: Id28cc37261ad7b29564f8a54dfc79284bde6bbad
Cc: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: Bala Shanmugam <bkamatch@qca.qualcomm.com>
Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32621

CHROMIUM: ath9k_hw: Wait BT calibration to complete

Whenever BT calibration requested, WLAN has to wait for the
calibration to be completed. Bt right now we defer the waiting
which is causing BT calibration failure. Fix that.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: I344d301c87e080d9d6efa079688b370b78b7eb22
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32620

CHROMIUM: ath9k: fix interrupt storms on queued hardware reset

commit b74713d04effbacd3d126ce94cec18742187b6ce
"ath9k: Handle fatal interrupts properly" introduced a race condition,
where
IRQs are being left enabled, however the irq handler returns IRQ_HANDLED
while the reset is still queued without addressing the IRQ cause.
This leads to an IRQ storm that prevents the system from even getting to
the reset code.

Fix this by disabling IRQs in the handler without touching intr_ref_cnt.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: I10a6c530dc3dbda66ed5f54e09251f6f109d43c2
Cc: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Cc: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32619

CHROMIUM: ath9k: Fix race in reset-work usage

Using work_pending() to defer certain operations when
a HW-reset work has been queued is racy since the check
would return false when the work item is actually in
execution. Use SC_OP_HW_RESET instead to fix this race.
Also, unify the reset debug statistics maintenance.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: Ia6240350542831d796c0374ac7eff71c96ec2a06
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32618

CHROMIUM: ath9k: Fix powersave locking

The 'ps_flags' is used/accessed in a variety of contexts
and requires proper locking. Use 'sc_pm_lock' appropriately.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: Ib3cf758dbd5518d60355069d6cd0be19d91dfee0
Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32617

CHROMIUM: ath9k: Fix work handling

* Currently, there is no synchronization between the reset
work and the tx-poll work. Fix this and make sure that we
bail out properly if a reset work is in progress.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: I4b1ca09bc9e6970c4e072e706f052245b60072c9
Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32616

CHROMIUM: ath9k: Prune ath9k_init_device

Instead of cluttering ath9k_init_device() with 'ath_softc'
specific initialization code, use ath9k_init_softc() to
setup driver-specific work routines, timers etc.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: I090c6bbaf2546e109af03c048e947fce25ca0c43
Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32615

CHROMIUM: ath9k_hw: Read and configure thermocal for AR9462

Read and configure thermometer calibration results read from
OTP card.

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: Ie908981882c62a778fe88b78212a87bc77755810
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32614

CHROMIUM: ath9k_hw: Read and apply thermometer settings from EEPROM

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: Ic7b2b8f52cd6fb5dc2de17dad874c73afd61af90
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32613

CHROMIUM: ath9k_hw: use peak detection for 5GHz

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: Ie2b38c9fba61aae7ba17e569c2b09a2a11d4e880
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32612

CHROMIUM: ath9k_hw: add 8 points for 5G temp slop

BUG=chrome-os-partner:12560
TEST=compile

Change-Id: Ieb82e296f4aa0b72319188c0b0c207c3e0a161d5
Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32611

CHROMIUM: ath9k: properly deal with imbalance in station add/remove calls

When this happens (usually in the suspend/resume path), invalid node list
pointers get dereferenced, leading to a crash.

BUG=chrome-os-partner:10785
TEST=compile

Change-Id: I7e731ad7004a1d9526808471d374e9646cbb0241
Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31985
Reviewed-by: Gary Morain <gmorain@chromium.org>

gpu: vithar: tune GPU clock governor

Address some issues in the GPU frequency selection algorithm.

The main change is to use a weighted average of the last 4 samples of the
GPU utilisation value to drive frequency step up/down's and do it based
on the number of samples instead of consecutive out-of-range samples.
This smooths transitions where the previous algorithm would not transition
because of a single sample that was out-of-range (which can happen for
various reasons outside the GPU).  Four samples is chosen as a compromise
between smoothing bumps and quickly identifying changes.

Increase the sampling frequency and tune the up/down step thresholds to
be more aggresive up-shifting and to happen faster.  The new values are
optimized for performance (over power) based on a set of workloads.

Remove the mechanism that caused a clock boost when the GPU goes !busy
after a period of being idle.  This caused anomalies such as clock ramping
at the login screen due to periodic short updates (e.g. to re-draw the
clock face).  Instead of we depend on the normal clock ramp up mechanism
which has been tuned for faster response.

Remove the special handling to speed up-shifting when seeing 100%
utilisation samples.  This happens rarely (based on stats collected) and
is now handled by more frequent sampling and shorter up-shift thresholds.

While here: move the up/down thresholds to the infotbl (simplifies
code), change the up/down thresholds to be the minimum value required
(> replaced by >=), simplify utilisation calculation, and fix a bunch
of checkpatch complaints.

Signed-off-by: Sam Leffler <sleffler@chromium.org>
BUG=chrome-os-partner:13355
TEST=open multiple webgl demo's, video playback, static html content, and a new tab; monitor gpu clock to verify the algorithm chooses an "optimal clock" (relative to performance w/o dvfs); switch between tabs and verify the clock is changed "quickly" and there is no instability in the frequency selection

Change-Id: I826e574d9215147399eb4c49844fbcd9500c3273
Reviewed-on: https://gerrit.chromium.org/gerrit/31745
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Tested-by: Sam Leffler <sleffler@chromium.org>
Commit-Ready: Sam Leffler <sleffler@chromium.org>

exynos: busfreq: Lock the INT frequency to 200MHz

HDMI/Mixer needs a minimum of 200MHz INT frequency. Range locking
to 200MHz should ideally occur just before streaming starts and
unlocked down to 160MHz on stream stop. This can be done via
runtime pm call-backs or in the HDMI driver itself using the dev
framework introduced by the busfreq patches. Currently just hardcode
in the busfreq driver. Note: There will be a hit of ~30mW in INT
power due to this.

BUG=chromeos-partner:13356
TEST=Ensure when HDMI is active INT is at 200MHz and does not drop
to 160MHz.

Change-Id: I4ecee442f8111b74930ff98965c824c54d11930d
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/32017
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Sean Paul <seanpaul@chromium.org>
Commit-Ready: Sean Paul <seanpaul@chromium.org>

exynos5: usb: Disable device clocks after programming PHY

This patch adds clock disable calls and supporting code
to disable the device clocks, requested in phy_init()
and phy_exit(), after programing the PHY for usb 2.0
and usb 3.0. This clock disabling was missing until now.

BUG=chrome-os-partner:13038
TEST=emerge-daisy chromeos-kernel; test with usb 2.0 and usb 3.0
MSD and usb HID; expect reduced leakage current after driver probe
and during suspend mode since, clocks are now gated
after prgramming PHY.

Change-Id: I86966bf461f27b760c1b17397cdeddca6767a930
Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/31113
Reviewed-by: Bryan Freed <bfreed@chromium.org>

UPSTREAM: staging: gdm72xx: use list_move instead of list_del/list_add

Using list_move() instead of list_del() + list_add().

spatch with a semantic match is used to found this problem.
(http://coccinelle.lip6.fr/)

Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit 73295fe185e58b8c0b288fee61a8a994015ab4b2)

Change-Id: If2acdc5f7c17fdbb707b80e46e5e433733932454
Reviewed-on: https://gerrit.chromium.org/gerrit/32492
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>

UPSTREAM: staging: gdm72xx: use list_move_tail instead of list_del/list_add_tail

Using list_move_tail() instead of list_del() + list_add_tail().

spatch with a semantic match is used to found this problem.
(http://coccinelle.lip6.fr/)

Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit e5d2cb4a0b59fa3f4ecc2d47ca6afacada7794d2)

Change-Id: Id8f64de79515de4cb64ecb189f496b4d4482777d
Reviewed-on: https://gerrit.chromium.org/gerrit/32491
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>

UPSTREAM: staging: gdm72xx: Fix bogus test

Test the return as we should

Resolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id=46921
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit f1efd9fe08a9ada843cd99f949a130555df045bd)

Change-Id: I38d763f5a741d71349484b49c9dbff4702b72743
Reviewed-on: https://gerrit.chromium.org/gerrit/32490
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>

UPSTREAM: staging: gdm72xx: use kzalloc to allocate usb_tx structure

the code under alloc_tx_struct does the allocation of usb_tx structure
using kmalloc, and memsets the allocated pointer, instead we can
directly use kzalloc so that the allocated memory is set with
zeros

Signed-off-by: Devendra Naga <devendra.aaru@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit 07ad99c9e32173852997523eb920950902563941)

Change-Id: I623dd5512b116924c7a5fbaefbbd26296a14cdab
Reviewed-on: https://gerrit.chromium.org/gerrit/32489
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>

drm: edid: add support for E-DDC

The current logic for probing ddc is limited to
2 blocks (256 bytes), this patch adds support
for the 4 block (512) data.

To do this, a single 8-bit segment index is
passed to the display via the I2C address 30h.
Data from the selected segment is then immediately
read via the regular DDC2 address using a repeated
I2C 'START' signal.

BUG=chrome-os-partner:13173
TEST=Verified 4blk edid file is read properly in
HDMI protocol analyser.

Change-Id: Ifcd1a6de369c1cda5f341738373a1ed483d4b9fb
Signed-off-by: Shirish S <s.shirish@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/32378
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Shirish S <shirish@chromium.org>
Commit-Ready: Shirish S <shirish@chromium.org>

CHROMIUM: sbs-battery: probe should try talking to the device

Turns out this driver doesn't actually try talking to the device at probe
time, so if it's incorrectly configured in the device tree or platform
data (or if it's been removed from the system), then probe will succeed
and every later access will sit there and time out. The end result is
a system that thinks it has a battery but can never read status, which
isn't very useful.

Instead, just read any register (I chose status) at boot, and if that
fails, don't register the device.

BUG=chrome-os-partner:11381
TEST=modify device tree to have battery at other address, try booting
and make sure the 2 minute timeout is gone (and dmesg has the error
string in it).

Change-Id: I728910968a40a55de3b3c9a10921a3684ace215f
Signed-off-by: Olof Johansson <olofj@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32406
Reviewed-by: Doug Anderson <dianders@chromium.org>

CHROMIUM: dmaengine: pl330: lock work_list in set residue.

This list can be changed due to cancelation or a completed transfer
while the set residue function is iterating over it.

BUG=chrome-os-partner:12565
TEST=aplay -B20000 file.wav, should be clear, run multimedia test from
vendor.

Change-Id: Idad680f9418734396daefa308b92337f4570349b
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32405
Reviewed-by: Olof Johansson <olofj@chromium.org>

CHROMIUM: ALSA: hda/ca0132 - update latency values of DSP

Update latency values and exposed noise reduction effect.

BUG=chrome-os-partner:13065
TEST=build and install, run latency test program, the difference between
measured and reported value should be less then or around 1ms.

Change-Id: I27eb8852f31bff7d19175ba727240301ae547da8
Signed-off-by: Hsinyu Chao <hychao@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32402
Reviewed-by: Dylan Reid <dgreid@chromium.org>

CHROMIUM: ath9k: Fix TX filter usage

The TX filter bit for a station would be set by the HW
when a frame is not acked. A frame would be completed with
ATH9K_TXERR_FILT status only when the corresponding filter bit
for the destination station is already set.

Currently, un-acknowledged packets are added to the pending queue
and retried, but the "clear_dest_mask" bit in the descriptor is
set only when the TX status has been ATH9K_TXERR_FILT. This results
in packet loss and the log shows:

wlan0: dropped TX filtered frame, queue_len=0 PS=0 @4309746071
wlan0: dropped TX filtered frame, queue_len=0 PS=0 @4309746076
wlan0: dropped TX filtered frame, queue_len=0 PS=0 @4309746377
...
...

This issue can be resolved by making sure that the destination
mask is cleared when the packet is being retried and the earlier
TX status is ATH9K_TXERR_XRETRY.

BUG=chrome-os-partner:12518
TEST=compile

Change-Id: I134194485dca81bafc0c7a2a167596c78e568260
Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Signed-off-by: mukesh agrawal <quiche@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32192
Reviewed-by: Gary Morain <gmorain@chromium.org>

CHROMIUM: dm: bootcache Device mapper for bootcache

Bootcache implements a simple cache for reading blocks sequentially
off the disk that would normally be read non-sequentially.

BUG=chromium-os:25441
TEST=boot the system with bootcache enabled

Change-Id: I97bd8ddb7740270b0ff0f207a66027158e77660e
Signed-off-by: Paul Taysom <taysom@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31712
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

Cleanup dpms

The fimd_dpms is just a dummy and its
functionality is achieved in
fimd_display_power_on.

BUG=chrome-os-partner:12049
TEST=Verified the
"DISPLAY=":0" xset dpms force off "
LCD goes black completely and return back when
"on"

Change-Id: Ie7c1c1488153512651289ee851ed667d90fe8154
Signed-off-by: Shirish S <s.shirish@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/31844
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Shirish S <shirish@chromium.org>
Commit-Ready: Shirish S <shirish@chromium.org>

UPSTREAM: ARM: 7438/1: fill possible PMD empty section gaps

On ARM with the 2-level page table format, a PMD entry is represented by
two consecutive section entries covering 2MB of virtual space.

However, static mappings always were allowed to use separate 1MB section
entries. This means in practice that a static mapping may create half
populated PMDs via create_mapping().

Since commit 0536bdf33f (ARM: move iotable mappings within the vmalloc
region) those static mappings are located in the vmalloc area. We must
ensure no such half populated PMDs are accessible once vmalloc() or
ioremap() start looking at the vmalloc area for nearby free virtual
address ranges, or various things leading to a kernel crash will happen.

Signed-off-by: Naveen Krishna Chatradhi <naveen@chromium.org>
(cherry picked from commit 19b52abe3c5d759661500a1dc810924369b2ad46)

BUG=None
TEST=built and booted on one board.

Change-Id: I3731dc511107f4b73e5cab047c80d28cd932022f
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Reported-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Tested-by: "R, Sricharan" <r.sricharan@ti.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: stable@vger.kernel.org
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Reviewed-on: https://gerrit.chromium.org/gerrit/32386
Commit-Ready: Olof Johansson <olofj@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Tested-by: Olof Johansson <olofj@chromium.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>

s5p: ehci: Add essential clock gating in suspend/resume

This patch adds missing clock gating support while the ehci
controller goes into S2R. This would save us some power
while the system is suspended.

BUG=chrome-os-partner:13500
TEST=emerge-daisy chromeos-kernel; Test system S2R using
"powerd_suspend"; expect reduced leakage current when clocks
are gated in suspend mode.

NOTE: haven't measured power saving yet with this change.

Change-Id: Id7c7b79215f1ab3c7696414e3e5715767c540b6d
Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/31471
Reviewed-by: Todd Broch <tbroch@chromium.org>

exynos: ohci: Add essential clock gating in suspend/resume

This patch adds missing clock gating support while the ohci
controller goes into S2R. This would save us some power
while the system is suspended.

BUG=chrome-os-partner:13500
TEST=emerge-daisy chromeos-kernel; Test system S2R using
"powerd_suspend"; expect reduced leakage current when clocks
are gated in suspend mode.

NOTE: haven't measured power saving yet with this change.

Change-Id: I1b03bd11677d50db7ab9d2a8f1a5385f577b7fa2
Signed-off-by: Vivek Gautam <gautam.vivek@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/31470
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Reviewed-by: Todd Broch <tbroch@chromium.org>

CHROMIUM: ALSA: hda/ca0132 - Change retry timeout method.

Originally we do 50 retries in chipio_send() and dspio_send().
Now it is changed to sleep for 1ms after each try, and timeout after 1 second.
Similar change is applied to wait for DMA done.

BUG=chrome-os-partner:12327
TEST=play youtube, suspend/resume 10 times.

Signed-off-by: Chih-Chung Chang <chihchung@chromium.org>
Change-Id: I59e9350a48721a8e426bfba1da2f2aad7ee907a0
Reviewed-on: https://gerrit.chromium.org/gerrit/32128

CHROMIUM: ALSA: hda/ca0132 - DMA patch from Creative.

Add support for DSP firmware transfer to CA0132 codec.
Add transfer handler functions.
Call the new snd_hda_codec_load_dsp_xxx loader ops to control download.
Add chip access routines.

BUG=chrome-os-partner:12327

Signed-off-by: Chih-Chung Chang <chihchung@chromium.org>
Change-Id: I2765f13c4209a55d3705e798cf016efe627de893
Reviewed-on: https://gerrit.chromium.org/gerrit/32127

CHROMIUM: ALSA: Add new DSP loader callback routines

BUG=chrome-os-partner:12327

Change-Id: I1dff2d4d672b0b03eb486fb97295367db4b07354
Signed-off-by: Chih-Chung Chang <chihchung@chromium.org>
Signed-off-by: Ian Minett <ian_minett@creativelabs.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/32126
Reviewed-by: Dylan Reid <dgreid@chromium.org>

CHROMIUM: ALSA: Make snd_sgbuf_get_{ptr|addr}() available for non-SG cases.

BUG=chrome-os-partner:12327

Change-Id: Iae062d860bc4044db79284290ff28b29c58b29ce
Signed-off-by: Chih-Chung Chang <chihchung@chromium.org>
Signed-off-by: Ian Minett <ian_minett@creativelabs.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/32134

CHROMIUM: ramoops: Copy the entire buffer to deal with bit rot

If unclean shutdown is done by yanking power rails, the RAM may be in a
state where it is not getting refreshed for a short period of time. This
can cause bit rotting in RAM and throw off the wraparound and buffer
size calculation logic. To get around this, copy the entire console
buffer. Note that this, of course, won't do anything to fix the bit
rotting but the intent here is that some logs are better than none.

BUG=chrome-os-partner:13249
TEST=on a snow or link system do a warm reboot by pressing
alt-volume_up-r keys together. The system should reboot. Upon bootup,
check contents of "/dev/pstore/console-ramoops" and ensure they are from
dmesg of the previous boot.

Change-Id: I68b2b10a6b3fc29329979cc0c659b440436b771f
Signed-off-by: Sameer Nanda <snanda@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32180
Reviewed-by: Doug Anderson <dianders@chromium.org>

exynos:gsc:modify number of output/capture buffers

gscaler src buffer count as well as destination buffer
count increased to 32.
This is required to interface to MFC for csc, as MFC
demands 32 capture buffers for some H264 streams

BUG=streams with more than 16 dpb buffers fail
TEST=tested through browser for streams with 20 dpbs

Change-Id: I817d65c122eb8974b6c658f65fe48e1e1131c83e
Signed-off-by: Kiran AVND <avnd.kiran@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/32133
Tested-by: kiran <kiran@chromium.org>
Reviewed-by: Shaik Ameer Basha <shaik.ameer@samsung.com>
Reviewed-by: Pawel Osciak <posciak@google.com>
Commit-Ready: Arun Mankuzhi <arun@chromium.org>
Reviewed-by: Arun Mankuzhi <arun@chromium.org>

CHROMIUM: dm: fix newlines in printouts

Turns out that we print double newlines:

[ 3.799802] device-mapper: init: attempting early device configuration.
[ 3.799807]

So, don't add the newline at the end of DM*() macros.

BUG=none
TEST=look at dmesg after booting

Change-Id: I039a3451c5a757641f1c0211845fc0bdc218b2bc
Signed-off-by: Olof Johansson <olofj@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32154
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

arm: exynos: Gracefully exit on suspend failure

As per Pg 641 Pt 7 of Exynos_5250_SCP_UM_REV1.00:

When there are pending interrupt events, WFI/WFE instruction are
ignored. To cancel the power-down sequence follow these steps:
1) Disable system power-down through CENTRAL_SEQ_CONFIGURATION
and CENTRAL_SEQ_CONFIGURATION_DMC registers
2) Clear WAKEUP_STAT and WAKEUP_MASK_DMC registers
3) Enable interrupt service routine for CPU

Code for early wakeup already exists; remove the panic on suspend
failure, clear the wakeup state register and return error from
cpu_suspend to indicate a failed suspend.

BUG=chrome-os-partner:12807
TEST=I still have not been able to reproduce this bug. I am on ToT
kernel, u-boot and ec running Jon's suspend_test.sh script. On
commenting out cpu_do_idle in the suspend code, the system resumes
successfully taking the early_wakeup path.
cat /sys/kernel/debug/suspend_stats shows
(success: 0
fail: 1
last_failed_errno: -16)

Change-Id: I082664ae77db6116bccff5555a8d43412c780277
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/30992
Reviewed-by: Jon Kliegman <kliegs@chromium.org>
Commit-Ready: Olof Johansson <olofj@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>

CHROMIUM: ALSA: hda/ca0132 - make initialization faster.

Remove unnecessary dspio_send() from dspio_write_wait().
Check dsp status before sleep and sleep for shorter periods.

BUG=chrome-os-partner:12307
TEST=build and install, check dmesg.

Signed-off-by: Chih-Chung Chang <chihchung@chromium.org>
Change-Id: I0e1d5b0d29c446f29beea704c1b2cca22524c142
Reviewed-on: https://gerrit.chromium.org/gerrit/32023
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Tested-by: Chih-Chung Chang <chihchung@chromium.org>
Commit-Ready: Chih-Chung Chang <chihchung@chromium.org>

CHROMIUM: config: exynos5: enable xfrm_user module

xfrm_user kernel module is needed for supporting LT2P/IPsec VPN via
strongSwan.

BUG=chromium-os:21495
TEST=Build chromeos-kernel and test L2TP/IPsec VPN.

Change-Id: Ic7635a1057642d8eaee0a15f6d1db210804a2912
Signed-off-by: Ben Chan <benchan@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32084
Reviewed-by: Darin Petkov <petkov@chromium.org>

HROMIUM: ALSA: hda/ca0132 - latency patch from Creative.

This change improves the latency and report the correct estimate
delay when dsp loaded or not. DSP parameter set incorrect issue has
also been fixed.

BUG=chrome-os-partner:12926
TEST=build kernel, record some sound by arecord command. Google hangout
should not hear echo.

Change-Id: Ibade3a0cfbd956379ff1690cd1e0f3f31eedd6f9
Signed-off-by: Hsinyu Chao <hychao@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31827
Reviewed-by: Puneet Kumar <puneetster@chromium.org>

UPSTREAM: [media] uvcvideo: Reset the bytesused field when recycling an erroneous buffer

Buffers marked as erroneous are recycled immediately by the driver if
the nodrop module parameter isn't set. The buffer payload size is reset
to 0, but the buffer bytesused field isn't. This results in the buffer
being immediately considered as complete, leading to an infinite loop in
interrupt context.

Fix the problem by resetting the bytesused field when recycling the
buffer.

Cc: <stable@vger.kernel.org>
Signed-off-by: Jayakrishnan Memana <jayakrishnan.memana@maxim-ic.com>
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
(cherry picked from commit 8a3f0ede2b3f5477122060af1a816c6bbf09fcd2)

BUG=chromium-os:33591
TEST=compile

Change-Id: Ibbb507bff1e57b7a92e84c36457de04d2115b3b8
Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32071
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: Pawel Osciak <posciak@google.com>

CHROMIUM: gobi: call usbnet_disconnect after qc_deregister

usbnet_disconnect should be called after qc_deregister and at the end of
qcnet_disconnect as qc_deregister may still need to access the
underlying usb_device during client_free -> cid_free -> write_sync.

BUG=chrome-os-partner:12812
TEST=Tested the following on a system with a Gobi modem:
1. Run suspend/resume stress test.
2. Manually connect to a cellular network, suspend and then resume the
system. Observe from syslog how qcusbnet is released and
re-initialized.

Change-Id: I0e5f2fd12896992e0da5b99e8b92274f87e1640c
Signed-off-by: Ben Chan <benchan@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/32063
Reviewed-by: Gary Morain <gmorain@chromium.org>

media:gscalar: fix csc RGB out/in format settings

macros used to set RGB output and input csc aren't correct.
This causes RGB(16,16,16) to appear where we expect RGB(0,0,0).

BUG:chrome-os-partner:13370
TEST: http://code.entropywave.com/test-media/gamut/gamut-theora-bt470.ogv
      Transcode using ffmpeg: to gamut-theora-bt470.mp4(h264 content)
      Play on snow; with HW decode enabled
      checkboard pattern not observed, playback similar to software decoding.

Change-Id: Ia12390e39f68bde6cb4a5a6202324b96761dd26e
Signed-off-by: Kiran AVND <avnd.kiran@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/32020
Reviewed-by: Shaik Ameer Basha <shaik.ameer@samsung.com>
Tested-by: Shaik Ameer Basha <shaik.ameer@samsung.com>
Reviewed-by: Sunil Mazhavanchery <sunilm@samsung.com>
Reviewed-by: Pawel Osciak <posciak@google.com>
Commit-Ready: Kiran Avnd <kiran@chromium.org>

Revert "CHROMIUM: ramoops: Copy the entire buffer to deal with bit rot"

This reverts commit 4aa82798833de5023d60a81cd1abd118da03a0f1

Change-Id: Ie3272c25d9c0f2aced79588faac172395d07afb4
Reviewed-on: https://gerrit.chromium.org/gerrit/32061
Commit-Ready: Andrew de los Reyes <adlr@chromium.org>
Reviewed-by: Andrew de los Reyes <adlr@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>

gpu: vithar: Fix compilation error when disabling T6XX_DVFS

This patch fixes the build errors that occur when T6XX_DVFS is disabled.

Signed-off-by: Shariq Hasnain <shariq.786@samsung.com>
BUG=None
TEST=Build tested with T6XX_DVFS disabled.

Change-Id: I999489ac6e55a92fc68bac5ff67fb91cf926865c
Reviewed-on: https://gerrit.chromium.org/gerrit/29584
Commit-Ready: shariq hasnain <shariq.786@samsung.com>
Reviewed-by: shariq hasnain <shariq.786@samsung.com>
Tested-by: shariq hasnain <shariq.786@samsung.com>
Commit-Ready: Sam Leffler <sleffler@chromium.org>
Reviewed-by: Sam Leffler <sleffler@chromium.org>

gpu: vithar: GPU ASV code added

This patch select the appropiate supply voltage for GPU.

Signed-off-by: Shariq Hasnain <shariq.786@samsung.com>
BUG=chrome-os-partner:11795
TEST=Build and boot snow. A group is chosen from ASV voltage
table and webGL applications are running without any issues.

Change-Id: I96faafc4e5d3a6654be54e55d60d887b01643614
Reviewed-on: https://gerrit.chromium.org/gerrit/31694
Commit-Ready: shariq hasnain <shariq.786@samsung.com>
Reviewed-by: shariq hasnain <shariq.786@samsung.com>
Tested-by: shariq hasnain <shariq.786@samsung.com>
Commit-Ready: Sam Leffler <sleffler@chromium.org>
Reviewed-by: Sam Leffler <sleffler@chromium.org>

UPSTREAM: dmaengine: pl330: dont complete descriptor for cyclic dma

Commit eab215855803 ("dmaengine: pl330: dont complete descriptor for
cyclic dma") wrongly completes descriptor for cyclic dma, hence following
BUG_ON is still hit with cyclic DMA operations.

kernel BUG at drivers/dma/dmaengine.h:53!

BUG=chrome-os-partner:12565
TEST=built for emerge-daisy chromeos-kernel and booted on one board.

Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
Acked-by: Jassi Brar <jaswinder.singh@linaro.org>
Signed-off-by: Vinod Koul <vinod.koul@linux.intel.com>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Alim Akhtar <alim.akhtar@gmail.com>
(cherry picked from commit 30c1dc0ff30b5552e8af555265dbeac5637cbb48)

Change-Id: Ia705fcbb3b19b0d3a51295bf273d039fb76a1a72
Reviewed-on: https://gerrit.chromium.org/gerrit/31830
Commit-Ready: naveen krishna chatradhi <naveen@chromium.org>
Tested-by: naveen krishna chatradhi <naveen@chromium.org>
Reviewed-by: Hatim Ali R.V <hatim.rv@samsung.com>
Reviewed-by: naveen krishna chatradhi <naveen@chromium.org>

UPSTREAM: DMA: PL330: Fix racy mutex unlock

pl330_update() stores a pointer to the thrd->req that finished, which
contains a pointer to the corresponding pl330_req.  This is done with
the pl330_lock held.  Then, it iterates through the req_done list,
calling the callback for each of the requests that are done.  The
problem is that the driver releases the lock before calling the
callback for each of the callbacks.  pl330_submit_req() running in
another processor can then acquire the lock and insert another request
in one of the thrd->req that hasn't been processed yet, replacing the
pointer to pl330_req there.  When the callback returns in
pl330_update() and the next rqdone is popped from the list, it
dereferences the pl330_req pointer to the just scheduled pl330_req,
instead of the one that has finished, calling pl330 with the wrong r.

This patch fixes this by storing the pointer to pl330_req directly in
the list.

BUG=chrome-os-partner:12565
TEST=built for emerge-daisy chromeos-kernel and booted on one board.

Signed-off-by: Javi Merino <javi.merino@arm.com>
Cc: Jassi Brar <jaswinder.singh@linaro.org>
Acked-by: Jassi Brar <jaswinder.singh@linaro.org>
Signed-off-by: Vinod Koul <vinod.koul@linux.intel.com>
Signed-off-by: Alim Akhtar <alim.akhtar@gmail.com>
(cherry picked from commit fdec53d5203ee3d44be7c09d1524e3a6287d46a7)

Change-Id: If0f7f4dd93dc12acf38047c8d90406bd172eb875
Reviewed-on: https://gerrit.chromium.org/gerrit/31829
Commit-Ready: naveen krishna chatradhi <naveen@chromium.org>
Tested-by: naveen krishna chatradhi <naveen@chromium.org>
Reviewed-by: Hatim Ali R.V <hatim.rv@samsung.com>
Reviewed-by: naveen krishna chatradhi <naveen@chromium.org>

CHROMIUM: ASoC: Samsung: Don't reset playing streams.

b796fed30720 "Asoc: Samsung: Add I2S S/W RST in startup function"
introduced a bug where whenever a new stream was started, all i2s
streams would be reset. This caused all full-duplex use cases to fail,
no hangouts, no GTalk.

Instead of always resetting, only reset if nothing is active. The reset
will still happen when it is needed, but won't if something is already
playing.

BUG=chrome-os-partner:13282
TEST=aplay and arecord at the same time should work.

Change-Id: I1bc7c87b8deff710f408565b2b834c25d4d0053d
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31681
Reviewed-by: Doug Anderson <dianders@chromium.org>

CHROMIUM: ramoops: Copy the entire buffer to deal with bit rot

If unclean shutdown is done by yanking power rails, the RAM may be in a
state where it is not getting refreshed for a short period of time. This
can cause bit rotting in RAM and throw off the wraparound and buffer
size calculation logic. To get around this, copy the entire console
buffer. Note that this, of course, won't do anything to fix the bit
rotting but the intent here is that some logs are better than none.

Also squeezed in a minor cleanup of renaming headp to tailp since it
really tracks the tail, not head.

BUG=chrome-os-partner:13249
TEST=on a snow system do a warm reboot by either issuing the
"warm_reboot" command from servo ec console or by pressing
alt-volume_up-r keys together. The system should reboot. Upon bootup,
check contents of "/dev/pstore/console-ramoops" and ensure they are from
dmesg of the previous boot.

Change-Id: I999e95bf854fff26265404a680255f25cc2f7fe6
Signed-off-by: Sameer Nanda <snanda@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31909
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

CHROMIUM: Correct i2c wait free time calculation

We should be using usecs_to_jiffies() for microsecond values. Correct
this.

BUG=chrome-os-partner:12420
BRANCH=snow
TEST=manual
On kernel:

while true; do i2cdump -f -y 4 0x48; done >/dev/null

On EC:

pmu 1000

See that there are no errors.

Change-Id: I589721e200ad9ad7d872ee952aece84ca2bec923
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31924
Reviewed-by: Doug Anderson <dianders@chromium.org>

CHROMIUM: Increase i2c arbitration wait time

We currently intend to wait 50ms for the EC to release the i2c bus
(although due to a bug soon to be fixed, we wait longer).

The longest transaction we expect the EC to perform is 4 bytes, which
should be about 0.5ms, but if there is a bug in the EC driver the time
could wind out significantly.

Change the wait time to 500ms.

BUG=chrome-os-partner:12420
BRANCH=snow
TEST=manual
On kernel:

while true; do i2cdump -f -y 4 0x48; done >/dev/null

On EC:

pmu 1000

See that there are no errors.

Change-Id: I2ab5c6f0ac1182485ac1a4f60e4e76ba83fb3987
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31923
Reviewed-by: Doug Anderson <dianders@chromium.org>

CHROMIUM: dts: Set no-ack-irq for tps65090

Set no-ack-irq to prevent the tps from acknowledging interrupts
on the tps chip.

BUG=chrome-os-partner:13109
TEST=Tested with and without devicetree flag set.
  Validated message in probe matches devicetree setting
  Unplugged and replugged power cable, confirmed battery icon
    updated correctly and debug messages (removed in CL) outputted
    the correct logic path.

Change-Id: I90df39c9fa4f7fa34df9701dc3e50522361cddea
Signed-off-by: Jonathan Kliegman <kliegs@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31896
Reviewed-by: Doug Anderson <dianders@chromium.org>

drivers: mfd: tps65090: Add devicetree flag to not ack tps interrupts

On some systems the tps65090 chip can be connected to multiple masters.
Add a device tree option to disable checking interrupts if a configuration
is present to prevent race conditions with only one device seeing the
interrupt.

BUG=chrome-os-partner:13109
TEST=Tested with and without devicetree flag set.
  Validated message in probe matches devicetree setting
  Unplugged and replugged power cable, confirmed battery icon
    updated correctly and debug messages (removed in CL) outputted
    the correct logic path.

Change-Id: I1d196373d65b36def67eeeb053f60c2471729d9c
Signed-off-by: Jonathan Kliegman <kliegs@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31895
Reviewed-by: Doug Anderson <dianders@chromium.org>

CHROMIUM: Input: cyapa - skip cyapa_dump_data if no DEBUG

ftrace shows this debugging function is still consuming several ~10 usec
even with DEBUG disabled.

Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
BUG=chromium-os:33910
TEST=cd /sys/kernel/debug/tracing/
TEST=echo 'cyapa*' > set_ftrace_filter
TEST=echo 'cyapa_irq' > set_graph_function
TEST=echo function_graph > current_tracer
TEST=move finger on touch surface
TEST=less trace
=> cyapa_dump_data() only present when DEBUG defined in cyapa.c

Change-Id: Ia8c789dfb01dda52c31167174a8a4731c965b603
Reviewed-on: https://gerrit.chromium.org/gerrit/31464
Commit-Ready: Daniel Kurtz <djkurtz@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Tested-by: Daniel Kurtz <djkurtz@chromium.org>

UPSTREAM: ARM: Remove current_mm per-cpu variable

The current_mm variable was used to store the new mm between the
switch_mm() and switch_to() calls where an IPI to reset the context
could have set the wrong mm. Since the interrupts are disabled during
context switch, there is no need for this variable, current->active_mm
already points to the current mm when interrupts are re-enabled.

Reviewed-by: Will Deacon <will.deacon@arm.com>
Tested-by: Will Deacon <will.deacon@arm.com>
Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
Tested-by: Marc Zyngier <Marc.Zyngier@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
(cherry picked from commit e323969ccda2d69f02e047c08b03faa09215c72a)

BUG=chromium-os:34007
TEST=generic system testing

Change-Id: I3ba9043520e275d593526f97aa2ecdd877effa4a
Signed-off-by: Olof Johansson <olofj@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31852
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

CHROMIUM: mfd: tps65090 uses rising edge interrupt

This is to avoid a conflict with the EC, which uses the preceding
falling edge for interrupts.

BUG=chrome-os-partner:13109
TEST=udevadm monitor, plug and unplug AC. Should see power_supply
events.

Change-Id: If4a8740a6ca55821928410f693c2ad9b128e66b5
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31735
Reviewed-by: Simon Glass <sjg@chromium.org>

CHROMIUM: dts: Configure BUCK2,3,4 to standby opmode.

BUCK2,3,4 drive vdd_arm, vdd_int and vdd_g3d respectively.  These
exynos regulators can safely be turned off during standby.  They were
previously off during S3 but recent op_mode additions to the device
tree have set them to always on.

CL disables these regulators in standby.

BUG=chrome-os-partner:11256
TEST=manual,
enter standby ... measure power on arm,int,g3d to be zero.  Resume
from suspend without issues.

Signed-off-by: Todd Broch <tbroch@chromium.org>
Change-Id: Ib714e1fe166afbd2607574eaabc4819a492b3fa1
Reviewed-on: https://gerrit.chromium.org/gerrit/31660
Reviewed-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-by: Bryan Freed <bfreed@chromium.org>

CHROMIUM: leds: Fix chromeos keyboard LED suspend behavior

Should use the built-in suspend/resume functions in led-class.c instead.

Also renamed the set function to correctly reflect the device type.

BUG=chrome-os-partner:13273
TEST=set the keyboard backlight to various levels (low, medium, full)
and run powerd_suspend. The backlight should turn off. Resume. The
backlight should be restored to its previous value (maybe with a delay).

Change-Id: Ifd56debd6f157b71729bf563b4242c58709549f7
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31722
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>

CHROMIUM: Input: atmel_mxt_ts - disable input_dev when updating FW & Config

When the FW update is in progress, the linux input layer may
call open/close on the driver, which translates to writing
certain values into the device T9 control register, which does
not exist at all when the system is in bootloader mode and the
writing to register will make the firmware update corrupted.

So unregister the input device from input subsystem when doing
FW update and re-create it when update finishes. Also doing the
same for config update.

Signed-off-by: Yufeng Shen <miletus@chromium.org>
BUG=chromium-os:33981
TEST=Boot system and let the device auto-update the FW and make
sure the update is successful.

Change-Id: If8f7ea2953f1a825cbcad4a548cf563345518c7d
Reviewed-on: https://gerrit.chromium.org/gerrit/31638
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Ready: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>

arm: exynos: tweak busfreq sysfs support

Silence console msgs generated when reading the cur_freq data due
to null pointers.

Signed-off-by: Sam Leffler <sleffler@chromium.org>
BUG=none
TEST=cat busfreq/cur_freq and note no console messages

Change-Id: I14867d8d29aee92f3dd2a5daf0eef0bda2fffcf3
Reviewed-on: https://gerrit.chromium.org/gerrit/31618
Reviewed-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Commit-Ready: Sam Leffler <sleffler@chromium.org>
Tested-by: Sam Leffler <sleffler@chromium.org>

UPSTREAM: ARM: 7445/1: mm: update CONTEXTIDR register to contain PID of current process

This patch introduces a new Kconfig option which, when enabled, causes
the kernel to write the PID of the current task into the PROCID field
of the CONTEXTIDR on context switch. This is useful when analysing
hardware trace, since writes to this register can be configured to emit
an event into the trace stream.

The thread notifier for writing the PID is deliberately kept separate
from the ASID-writing code so that we can support newer processors using
LPAE, where the ASID is stored in TTBR0. As such, the switch_mm code is
updated to perform a read-modify-write sequence to ensure that we don't
clobber the PID on CPUs using the classic 2-level page tables.

Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
(cherry picked from commit 575320d625d5b5eb115575a1f5e17af456e69577)

BUG=chromium-os:34007
TEST=general system testing

Change-Id: I4a4ba8b8911efac06914ed0c2974d16b502d78f2
Signed-off-by: Olof Johansson <olofj@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31715
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

UPSTREAM: ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on ASID-capable CPUs

Since the ASIDs must be unique to an mm across all the CPUs in a system,
the __new_context() function needs to broadcast a context reset event to
all the CPUs during ASID allocation if a roll-over occurred. Such IPIs
cannot be issued with interrupts disabled and ARM had to define
__ARCH_WANT_INTERRUPTS_ON_CTXSW.

This patch changes the check_context() function to
check_and_switch_context() called from switch_mm(). In case of
ASID-capable CPUs (ARMv6 onwards), if a new ASID is needed and the
interrupts are disabled, it defers the __new_context() and
cpu_switch_mm() calls to the post-lock switch hook where the interrupts
are enabled. Setting the reserved TTBR0 was also moved to
check_and_switch_context() from cpu_v7_switch_mm().

Reviewed-by: Will Deacon <will.deacon@arm.com>
Tested-by: Will Deacon <will.deacon@arm.com>
Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
Tested-by: Marc Zyngier <Marc.Zyngier@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
(cherry picked from commit 7fec1b57b8a925d83c194f995f83d9f8442fd48e)

BUG=chromium-os:34007
TEST=general system testing

Change-Id: I0628afd963eb7af1dfa0c3230f08f670feba9e9d
Signed-off-by: Olof Johansson <olofj@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31714
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

UPSTREAM: ARM: Use TTBR1 instead of reserved context ID

On ARMv7 CPUs that cache first level page table entries (like the
Cortex-A15), using a reserved ASID while changing the TTBR or flushing
the TLB is unsafe.

This is because the CPU may cache the first level entry as the result of
a speculative memory access while the reserved ASID is assigned. After
the process owning the page tables dies, the memory will be reallocated
and may be written with junk values which can be interpreted as global,
valid PTEs by the processor. This will result in the TLB being populated
with bogus global entries.

This patch avoids the use of a reserved context ID in the v7 switch_mm
and ASID rollover code by temporarily using the swapper_pg_dir pointed
at by TTBR1, which contains only global entries that are not tagged
with ASIDs.

Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
Tested-by: Marc Zyngier <Marc.Zyngier@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
[catalin.marinas@arm.com: add LPAE support]
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
(cherry picked from commit 3c5f7e7b4a0346de670b08f595bd15e7eec91f97)

BUG=chromium-os:34007
TEST=general system testing

Change-Id: I853a937d0a045c0487e97d74783064329d42eaf0
Signed-off-by: Olof Johansson <olofj@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31713
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

Add implementation of poll() to dma_buf using KDS

BUG=chrome-os-partner:11949
TEST=local build, run on ARM

Change-Id: I955e12be4d52e771eccc267befff8b42f316c150
Signed-off-by: Ray Smith <Raymond.Smith@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27056
Commit-Ready: John Sheu <sheu@chromium.org>
Reviewed-by: John Sheu <sheu@chromium.org>
Tested-by: John Sheu <sheu@chromium.org>

KDS: Fix incorrect timeout

kds_waitall uses wait_event_interruptible() and
wait_event_interruptible_timeout() incorrectly.

BUG=chrome-os-partner:11949
TEST=build, run on ARM

Change-Id: Ide44ccff6e902c6d8b5483d67335e36e094da5d2
Signed-off-by: David Garbett <David.Garbett@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/29878
Commit-Ready: John Sheu <sheu@chromium.org>
Reviewed-by: John Sheu <sheu@chromium.org>
Tested-by: John Sheu <sheu@chromium.org>

CHROMIUM: ALSA: hda/ca0132 - cache firmware on first load.

So we won't load it from at resume time.
Also remove the size check for the speakereq file.

BUG=chrome-os-partner:12927
TEST=build and install, audio still works.

Change-Id: Ic1eb133f5d5a33fbf0e823736a62ff391648d939
Signed-off-by: Chih-Chung Chang <chihchung@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31093
Reviewed-by: Dylan Reid <dgreid@chromium.org>

drm/exynos: Implement fimd_display_power_on

Also fix fimd_power_on to turn the panel off in the off case.

BUG=chromium-os-partner:12832
TEST=by hand, screen goes completely black after the timeout.

Change-Id: Ia79f5e53009110715395a5984e3e3f96809c7aed
Signed-off-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31634
Reviewed-by: John Sheu <sheu@chromium.org>

drm/exynos: Fix doxygen comment for the event.

BUG=none
TEST=compiles

Change-Id: I505539c5cb25ae38f672d21dac3bda837a6c66ec
Signed-off-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31390

leds: chromeos keyboard name should contain "kbd_backlight"

The driver sysfs directory should be "chromeos::kbd_backlight"
This is to match how other keyboard backlight drivers do it.

BUG=chromium-os:32959
TEST=See /sys/class/leds, there should be "chromeos::kbd_backlight"

Change-Id: Icaed85f110211a1e51f15ebcbb90b9e9b5e63291
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31626
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>

CHROMIUM: chromeos_laptop: Use LEDs for keyboard backlight

Previously using regular backlight driver, now using LEDs driver.

BUG=chromium-os:32959
TEST=Go to /sys/class/leds/keyboard_leds, make sure you can change
keyboard backlight by writing to "brightness"

Change-Id: I780629a014030639dae1497712b7a4d7ed599e26
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31543
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>

CHROMIUM: config: Enable keyboard backlight LEDs

BUG=chromium-os:32959
TEST=None (see later patch(es))

Change-Id: I487688054743eae0743201d923ba8f2c1ebc3ff5
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31542
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>

CHROMIUM: leds: Add Chrome OS keyboard LEDs driver

It is ACPI-based keyboard backlight LEDs.

BUG=chromium-os:32959
TEST=None (see next patch(es) for build/test info)

Change-Id: I0871851b1c67af33a9b9bd83c1dc93b1f8253ac5
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/31541
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>

regulator: max77686: Add support for various operating modes

MAX77686 supports a low power mode as well as a standby mode for
its LDOs and BUCKs. Initially add LDO8 standby mode as it leaks
~160mW through a suspend/resume cycle. The idea would be to set
these modes for the rest of the LDOs and BUCKs as well.
Note: The device tree bindings have been taken from the upstream
MFD driver with the new optional bindings for operating mode and
buck ramp delay added.

BUG=chrome-os-partner:12522
TEST=Verify 1350_ldoin power during suspend along with follow-on
patches.

Change-Id: I1144254ebf6cf096bc5b11217c3045aff41d8db0
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/30257
Reviewed-by: Todd Broch <tbroch@chromium.org>

CHROMIUM: dts: Add regulator operating mode bindings

Some of the LDOs and BUCKs on the MAX77686 PMIC can be put
into a low power or standby state. Add bindings to control
the operating mode (primarily enabling the standby mode for
LDO8).

BUG=chrome-os-partner:12660
TEST=Verify that the standby mode bit is being set using:
i2cget -y -f 0 0x9 0x47 (get a value of 0x48).
Suspend the system (rtcwake -m mem -s 25) and measure 1350_ldoin_mw
power. Prior to the patches 1350_ldoin_mw showed ~95mW and after it
showed ~2mW. Verified DP across 20 suspend/resume cycles.
HDMI S2R support is on-going; with or without these patches the
behaviour of HDMI is identical (corrupted images on cable insertion
post-resume).

Change-Id: I58f7975e9cb14a051139988b6237d3f5599589c2
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/31596
Reviewed-by: Todd Broch <tbroch@chromium.org>

exynos: Store mwifiex_ds_misc_subsc_evt in mwifiex_private

Since mwifiex_ds_misc_subsc_evt is used in an asynchronous case, store
the structure in the long-lived mwifiex_private instead of on the
calling stack.
Ideally, we would use this storage for the synchronous case, as well,
and explicitly clear the buffer on the "end" of the operation such that
we could prove only one message was in flight and that we were never
corrupting another. That would require a more invasive change to create
such an "end".
This fixes a problem where the response of the asynchronous operation
would corrupt a stack frame potentially in use by a different thread.

BUG=chrome-os-partner:12367
TEST=Walked back and forth between Wifi access points on the same
network while poster circle was actively animating on the screen (this
constant flushing of KDS resources creates an easy-to-recognize panic
when this corruption occurs), watching the wifi reset without panic.

Change-Id: I06b9c522d1f50e0de1c5754399d154cfd93830a4
Signed-off-by: Jeff Disher <disher@google.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/31473
Reviewed-by: Sam Leffler <sleffler@chromium.org>
Commit-Ready: Jeff Disher <disher@chromium.org>
Tested-by: Jeff Disher <disher@chromium.org>

DRM: HDMI: Initialized AUI and AVI Header info for HDMI IP

Audio and Video Header information has to be initialized to HDMI IP,

Fix: For compliance test suite TestID 7-19
Test: AVI Info Frame missing
AVI InfoFrame is transmitted on every two video field.
Test: AUI InfoFrame missing
Audio InfoFrame is transmitted on every two video fields.

Added code for getting VIC.

BUG=chrome-os-partner:13173
TEST=Verified that all the compliance tests pass
for 480p,720p and 1080p in
Agilent Technologies,N5998A
protocol analyser.

Change-Id: I2b1aeedeb33818f839f395d5f9097f3d50f76cc6
Signed-off-by: Fahad Kunnathadi <fahad.k@samsung.com>
Signed-off-by: Shirish S <s.shirish@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/31429
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Shirish S <shirish@chromium.org>
Commit-Ready: Shirish S <shirish@chromium.org>

drm/exynos: enable dvi mode for dvi monitor

Hdmi monitor and dvi monitor can be distinguished with edid.
This patch enables dvi mode if dvi monitor is connected and does
not enable audio feature for dvi mode because dvi has no audio
feature.

This patch is inspired from commit id:
872d20d66c0b7de0787675dce8569a61e4d9bc0 in drm-next branch.

BUG=chrome-os-partner:13173
TEST=Verified that all the dvi related compliance tests pass
Agilent Technologies,N5998A
protocol analyser.

Change-Id: I94c7ba951512bb9f1926880e9b8b41d8668495a3
Signed-off-by: Shirish S <s.shirish@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/31428
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Shirish S <shirish@chromium.org>
Commit-Ready: Shirish S <shirish@chromium.org>

CHROMIUM: Input: synaptics - add retry mechanism for reconnect

On the Samsung Series 5 Chromebook, the Synaptics ClickPad will sometimes not
send an "0xFA" PS/2 ACK in response to a command byte during the reconnect
sequence following a resume from suspend. From our experiments, the failure can
happen during any byte of any of the commands in the reconnect batch.

This failure results in a timeout in the psmouse driver. In addition, the
ClickPad will often also respond to the next PS/2 command byte with an "0xFE"
PS/2 RESEND response.

This patch makes the synaptics reconnect-at-resume more tolerant to such
failures.

Signed-off-by: Chung-yih Wang <cywang@chromium.org>
BUG=chromium-os:31522
TEST=on device; run platform_TouchpadResume test

Change-Id: Ic13d67fc8f3cad72fb5e6f6146f81060bfee5474
Reviewed-on: https://gerrit.chromium.org/gerrit/31099
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Commit-Ready: Chung-yih Wang <cywang@chromium.org>
Reviewed-by: Chung-yih Wang <cywang@chromium.org>
Tested-by: Chung-yih Wang <cywang@chromium.org>

CHROMIUM: config: exynos5: Enable busfreq support

Enable support for Samsung's busfreq driver which controls VDD_INT.

BUG=chrome-os-partner:11792
TEST=Measurements for variation in VDD_INT on Daisy show a reduction
of ~70-80mW at home screen.

Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Change-Id: I875e5d2ea9c80e777a1ac1d2b57c88acb70cb59b
Reviewed-on: https://gerrit.chromium.org/gerrit/28944
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Tested-by: Arjun.K.V <arjun.kv@samsung.com>

arm: exynos: Add busfreq support for smdk5250

The busfreq driver controls the MIF and INT frequencies and
voltages.
Note: MIF cannot be varied for DDR3 boards and hence has been
disabled.

BUG=chrome-os-partner:11792
TEST=Measurements for variation in VDD_INT on Daisy show a reduction
of ~70-80mW at home screen.

Change-Id: I02e6cae2c1aec2b88c17b5bcccd3ebfc9d439f98
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/28943
Reviewed-by: Sam Leffler <sleffler@chromium.org>
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Tested-by: Arjun.K.V <arjun.kv@samsung.com>

arm: exynos: Add ppmu support for Exynos5

Platform Performance Monitoring Unit (PPMU) is used to monitor and
gather performance information for custom IPs such such as MFC. This
information is used by the busfreq driver to vary/control VDD_INT.

BUG=chrome-os-partner:11792
TEST=Build and boot Snow

Change-Id: I0c94bfb23c2715afa0d26ca8595b59c7780f3a45
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/28942
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Tested-by: Arjun.K.V <arjun.kv@samsung.com>

cpufreq: exynos: Updated the DVFS table with ASV for EXYNOS5250

Choose from the newly added DVFS/ASV table for EXYNOS5250 based on
4/30 released guide. Different lot samples are supported.

BUG=chrome-os-partner:11794
TEST=Check that the ASV group is chosen based on lot

Change-Id: I392eae626cbee0f6ed7962cfecea5614296fd92b
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/28393
Reviewed-by: Prashanth Godrehal <prashanth.g@samsung.com>
Reviewed-by: Bryan Freed <bfreed@chromium.org>
Tested-by: Arjun.K.V <arjun.kv@samsung.com>
Commit-Ready: Arjun.K.V <arjun.kv@samsung.com>