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

drm/exynos: Adds 1920x1080 mode and fix for HPD

This patch adds 1920x1080 mode as a default mode
and fixes the hotplug issue.
The mixer needs to be reset before mode setting to
a new resolution, this was missing.

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

Change-Id: I998c19dea28ced949089de07ddeaf43e6a411060
Signed-off-by: Rahul Sharma <rahul.sharma@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26438
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Shirish S <s.shirish@samsung.com>
Commit-Ready: Shirish S <s.shirish@samsung.com>

CHROMIUM: Input: synaptics - use firmware data for Cr-48

The profile sensor clickpad in a Cr-48 Chromebook does a reasonable job of
tracking individual fingers. This tracking isn't perfect, but, experiments
show that it works better than just passing "semi-mt" data to userspace,
and making userspace try to deduce where the fingers are given a bounding box.

This patch tries to report correct two-finger positions instead of the
{(min_x, min_y), (max_x, max_y)} for profile sensor clickpads on Cr-48
chromebooks. Note that this device's firmware always reports the higher
(smaller y) finger in the "sgm" packet, and the lower (larger y) finger in the
"agm" packet. Thus, when a new finger arrives on the pad, the kernel driver
uses a simple Euclidean distance measure to deduce which of the two new fingers
should keep the tracking ID of the previous single finger. Similarly, when one
finger is removed, the same measure is used to determine which finger remained
on the pad.

Signed-off-by: Chung-yih Wang <cywang@chromium.org>
BUG=chromium-os:32257
TEST=on device; use mtplot to verify if fingers are reported correctly.

Change-Id: I94e1dbef9bae7aac2df1651c9974f3777a63e2fb
Reviewed-on: https://gerrit.chromium.org/gerrit/26404
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>

exynos5: dts: fix for hdmi hpd interupt with device tree

following patch updates the dt information for hpd, which
is an hdmi connect interrupt in exynos5 soc.

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

Change-Id: I3a0929383d45d2e52b703c9433d56642b8c759b0
Signed-off-by: Rahul Sharma <rahul.sharma@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26437
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Shirish S <s.shirish@samsung.com>
Commit-Ready: Shirish S <s.shirish@samsung.com>

drm/exynos: exynos5 hdmi driver name change and regulator init removed

driver name has to be changed to exynos-hdmi, so we can
sync with ARCH folders for exynos4 and exynos5 series of soc.
need name convention change.

Regulator init #ifdef, because it is not used.

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

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

drm/exynos: hdmi exynos5 series soc need layer sync update.

shadow registers in mixer gets updated only when, layer bit is updated.
in addition added in patch
a)Mixer Reset
b)Interrupt enable code.

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

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

drm/exynos: added sysmmu mapping for hdmi mixer.

Iommu mapping added for TV. patch creates shared mapping
between fimd and tv.Page tables are created in samsung ip
sysmmu.So mixer hardware can access virtually non contiguous buffers.

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

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

drm/exynos: hdmi porting for exynos5 soc.

exynos5 init is different, from exynos4 series of soc.
exynos5 series does not have video Processor.
The code has two init routine one for code with Video processor,
another without it.
Merged the mixer_resources_init into one for for exynos5 and exynos4

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

Change-Id: I077ccda4934162b448e71492111c3f8fb1d14204
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/26432
Reviewed-by: Prashanth Godrehal <prashanth.g@samsung.com>
Reviewed-by: Anush Elangovan <anush@google.com>

UPSTREAM: drm/i915: be more careful when returning -ENXIO in gmbus transfer

... flaky ddc hardware can cause a spurious NAK, resulting in the i2c
core and drm edid functions not trying to retry the edid transfer.

Luckily the gmbus quiescenting also times out for these cases, so we
can get out of this mess by returning -ETIMEDOUT for this specific
case. This way we keep the fast-fail of returning -ENXIO if there is
no device present, speeding up the boot process.

This regression has been introduced in

commit e646d5773572bf52017983d758bdf05777dc5600
Author: Daniel Kurtz <djkurtz@chromium.org>
Date: Fri Mar 30 19:46:38 2012 +0800

drm/i915/intel_i2c: always wait for IDLE before clearing NAK

v2: Return -ETIMEDOUT for this case and keep the -ENXIO for real NAKs,
suggested by Daniel Kurtz.

Cc: Daniel Kurtz <djkurtz@chromium.org>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=49518
Reported-and-Tested-by: Julian Simioni <julian.simioni@gmail.com>
Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
(cherry picked from commit 65e818660275ecda3702a4245f308923e3813a85)

Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
BUG=chromium-os:31301
TEST=builds clean; devices attached to gmbus still operate.

Change-Id: I16bcc866e9c04b1fc3add82d419e2ac2b13de4c8
Reviewed-on: https://gerrit.chromium.org/gerrit/27633
Reviewed-by: Simon Que <sque@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Commit-Ready: Daniel Kurtz <djkurtz@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Tested-by: Daniel Kurtz <djkurtz@chromium.org>

drm:exynos: HACK:rounds the pitch to 64 byte aligned

GPU performance is better with 64 byte align address as the DMA
burst transfer can be completed in minumum number of cycles.
This patch makes the buffer to be allocated be 64 byte aligned

stand alone glClear test app gives:
140-150 FPS with 2 byte align address
370-380 FPS with 64 byte align address

Refrence:Raymond Smith <raymond.smith@arm.com>

Change-Id: Ic482e9705502149ccea78520eedae1a6e2a63a3f
Signed-off-by: Akshu Agrawal <akshu.a@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27729
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Akshu Agrawal <akshu@chromium.org>
Commit-Ready: Akshu Agrawal <akshu@chromium.org>

drm/exynos: Removed DRM hdmi context dependency from platform device.

Subdrv need only to,directly access and initialize context information.
Removed complexity of adding,context information to plaform dev in drivers
exynos_hdmi,exynos_mixer and retrieving same information in common hdmi driver
ie, exynos_drm_hdmi.c

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

Change-Id: Iff60e1c67bbe4baba08fc5549a95ae768e36a2f0
Signed-off-by: Rahul Sharma <rahul.sharma@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26431
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Shirish S <s.shirish@samsung.com>
Commit-Ready: Shirish S <s.shirish@samsung.com>

exynos5: dts: Exynos5 HDMI platform data added to DT.

Mixer and Hdmi platform data added through device tree
for DRM HDMI.

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

Change-Id: I00b4ded9f62812a2a2783e31bdb8a7def86a903b
Signed-off-by: Rahul Sharma <rahul.sharma@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26430
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Shirish S <s.shirish@samsung.com>
Commit-Ready: Shirish S <s.shirish@samsung.com>

drm/exynos: added soc info for HDMI,exynos5 series of processor.

Added platform info to probe as exynos5 series in driver.exynos5
processors has no Video Processor and has differnet init routines.

BUG=chrome-os-partner:10851
TEST= tested hdmi on smdk5250

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

DRM:EXYNOS: Adding KDS support to exynos DRM

BUG=chrome-os-partner:10071
TEST=Tested WebGL and video playback

Change-Id: I2cf73c696546933df638382df93236a14527d145
Signed-off-by: Akshu Agrawal <akshu.a@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26996
Reviewed-by: Abhinav Kochhar <abhinav@chromium.org>
Reviewed-by: Sunil M <sunilm.samsung@gmail.com>
Tested-by: Akshu Agrawal <akshu@chromium.org>
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Anush Elangovan <anush@google.com>
Commit-Ready: Anush Elangovan <anush@google.com>

CHROMIUM: Config: Added KDS to config

Normalised config, uses defaults set in dma_buf Kconfig

BUG=None
TEST=emerge-daisy chromeos-kernel, boot

Change-Id: I15d694c892cb378bd559c4772c6ba689becd4cf7
Signed-off-by: Ray Smith <Raymond.Smith@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27732
Tested-by: David Garbett <David.Garbett@arm.com>
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Anush Elangovan <anush@google.com>
Commit-Ready: Anush Elangovan <anush@google.com>

dma-buf: Integrate KDS with dma-buf

Each dma-buf now has a KDS resource which can be retrieved with
get_dma_buf_kds_resource. The synchronisation is co-operative, drivers
must agree on what synchronisation to use with a particular buffer.

Add option DMA_SHARED_BUFFER_USES_KDS:
This is enabled automatically when DMA_SHARED_BUFFER is enabled, but
allows modules to check whether the kernel has support for KDS in dma_buf

BUG=None
TEST=Tested on Daisy

Change-Id: I633a29acf1309b20847b876f985a3afd41845295
Signed-off-by: Tom Cooksey <Tom.Cooksey@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26442
Tested-by: David Garbett <David.Garbett@arm.com>
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Anush Elangovan <anush@google.com>
Commit-Ready: Anush Elangovan <anush@google.com>

KDS: Add new system to allow synchronizing access to resources.

The KDS framework allows multiple drivers (clients) wanting to access
the same resource to synchronize with each other. Resources are typically
2D image buffers (potentially shared using dma-buf)

See Documentation/kds.txt for more details.

Debugging to show who has a waiter when a KDS resource is destroyed.

KDS: Fix for not handling duplicate resources

BUG=None
TEST=None

Change-Id: I8738f5dff48593875e1916c81ebb00cdcbed2f15
Signed-off-by: Gabriele Paoloni <Gabriele.Paoloni@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26441
Tested-by: David Garbett <David.Garbett@arm.com>
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Anush Elangovan <anush@google.com>
Commit-Ready: Anush Elangovan <anush@google.com>

ARM: exynos: Change snow LCD timings to get 60Hz

Tweak the LCD timings on snow to get a 60Hz refresh rate. We were
previously running at 52Hz because the timings weren't correct.
We have to use out-of-spec horizontal margins (0 instead of 30) to
get up to 60Hz. The panel seems to work well with these values.

BUG=None
TEST=Tested on snow

Change-Id: If92f7a8bdacb811cbbe948393caa1b4ab248ba2f
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27681
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Anush Elangovan <anush@google.com>
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

video: exynos: dp: Get pll lock before pattern set

According to the exynos datasheet (Figure 49-10), we should wait for PLL
lock before programming the training pattern when doing software eDP
link training.

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

Change-Id: I0b7fe3e5904b6207cd329fb8d74de6ba78f828df
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27578
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

drm/exynos: Modify burst size based on overlay size

The BURST size of fimd is adjusted based on the number of bytes to be
read. This is calculated based on the overlay width and the number of
bits per pixel. There are three burst lengths supported - 4 words,
8 words and 16 words where each word is 8 bytes long.

BUG=chrome-os-partner:9395
TEST=Tested on Daisy. No corruption and no drop in performance while
running Samurai.

Change-Id: I1a950f6e8d9b7b497ca5c32ad4bd00fdfe34f50e
Signed-off-by: Prathyush K <prathyush.k@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27538
Reviewed-by: Abhinav Kochhar <abhinav@chromium.org>
Tested-by: Abhinav Kochhar <abhinav@chromium.org>
Reviewed-by: Akshu Agrawal <akshu@chromium.org>
Commit-Ready: John Sheu <sheu@chromium.org>

drm/exynos: Allow overlays with sub-sized contents

Overlays presently assume that the entire framebuffer is to be
displayed; the src_w and src_h arguments to exynos_update_plane
are ignored.

Fix this.

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

Change-Id: If9ecd7928bd9cbce1f73c7a9ac4ff825dfe690fd
Signed-off-by: John Sheu <sheu@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26770
Reviewed-by: Akshu Agrawal <akshu@chromium.org>
Reviewed-by: Abhinav Kochhar <abhinav@chromium.org>

video: exynos: dp: Clean up SW link training

Clean up some of the SW training code to make it more clear and reduce
duplicate code.

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

Change-Id: I22c572e4f856596b26178dff41c1bb0757fa9c16
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27548
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

video: exynos: dp: Check DPCD return codes

Add return code checks to the DPCD transactions in the SW link training.

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

Change-Id: I94caca28f96af20ecb777739ad4e922a81f02796
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27576
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>

UPSTREAM: drm/i915: Implement w/a for sporadic read failures on waking from rc6

As a w/a to prevent reads sporadically returning 0, we need to wait for
the GT thread to return to TC0 before proceeding to read the registers.

v2: adapt for Haswell changes (Eugeni).

v3: use wait_for_atomic_us for thread status polling.

v3: *really* use wait_for_atomic for polling.

References: https://bugs.freedesktop.org/show_bug.cgi?id=50243
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
Acked-by: Ben Widawsky <ben@bwidawsk.net>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
(cherry picked from commit c4de7b0ffda2bb4843fd7f1052d0a2bb90bd08a5)
(from drm-next branch of git://people.freedesktop.org/~airlied/linux)

Changes to original patch:

* Removed Haswell stuff since we are on an older kernel.
* Copied wait_for_atomic_us from another patch.
* We need it but don't have the patch which introduced it.

BUG=chromium-os:32609
TEST=Multiple suspend/resume cycles.

Change-Id: Ic34c65420c902e9715c7142f57c22011561209c7
Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27571
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>

Revert "BACKPORT: drm/i915: Implement w/a for sporadic read failures on waking from rc6"

This reverts commit 0cb764f4e06de7fd5a648e37e37bfbd0893cbec8.

You can't busy loop waiting for jiffies to update with interrupts disabled.
You'll wait forever.

The fix is to revert this patch and use the version of this patch currently
in drm-next:

http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-next&id=c4de7b0ffda2bb4843fd7f1052d0a2bb90bd08a5

BUG=chromium-os:32609
TEST=none

Change-Id: I4ca416a9f20ccc53665bf31ee962af323b5f82bb
Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27570
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>

drm/exynos: Replace shmem with alloc_page

Use alloc_page to allocate pages from low mem
which will improve the cache sync performance

BUG=none
TEST=tested with video playback test application

Change-Id: I474bcad98072c0bc3fd25b4c99dde2104d404896
Signed-off-by: Abhinav Kochhar <abhinav@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27431
Reviewed-by: Pawel Osciak <posciak@google.com>

mali: Fix return value handling for dma_buf_map_attachment.

dma_buf_map_attachment may return PTR_ERR.

Signed-off-by: Pawel Osciak <posciak@chromium.org>
BUG=none
TEST=none

Change-Id: Ic6aa91dd5c1a1e79db4f8d81b1538e94dec75c12
Reviewed-on: https://gerrit.chromium.org/gerrit/27521
Reviewed-by: Ray Smith <Raymond.Smith@arm.com>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Commit-Ready: Pawel Osciak <posciak@chromium.org>
Tested-by: Pawel Osciak <posciak@chromium.org>

video: exynos: dp: Fix typo bug in SW link training

This patch fixes a typo bug in SW link training that causes the Equalizer
training step to run twice.

BUG=chrome-os-partner:11325
TEST=Tested on snow, ensured SW link training worked

Change-Id: I1bbec5b5ca4530bffe95c0081bd56f791b8cfbe6
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27423
Reviewed-by: Anush Elangovan <anush@google.com>

ath9k_hw: Fix wake queues when chip is reset by ath_reset

This patch fixes a bug where queues are not woken up at the end of ath_reset
logic. Due to this, whenever chip reset is done using ath_reset path, queues
are sleeping even after a chip reset. No packets are transmitted at this time.
This is the reason why we see intermittent disconnects as mac80211 was not able
to send nullfunc for probing AP. This patch also cleanup some reduntant code.

Signed-off-by: Ashok Nagarajan <ashok@cozybit.com>
Signed-off-by: Paul Stewart <pstew@chromium.org>
BUG=chrome-os-partner:10571,chrome-os-partner:10361
TEST=Test in similar environment to previously observed condition.
Jury is still out -- hang signature was never found during the run.

Change-Id: I750b6f14e276466d1690364de90027231e1676ce
Reviewed-on: https://gerrit.chromium.org/gerrit/27428
Reviewed-by: Gary Morain <gmorain@chromium.org>
Commit-Ready: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>

MALI: Print GPU fault info in release builds

TEST=emerge-daisy chromeos-kernel
BUG=None

Change-Id: Idba45dd40c2d5a67ed0301b2bbacbd1972e252f9
Signed-off-by: David Garbett <David.Garbett@arm.com>
Signed-off-by: Ray Smith <Raymond.Smith@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27399
Reviewed-by: Pawel Osciak <posciak@google.com>
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Anush Elangovan <anush@google.com>
Commit-Ready: Anush Elangovan <anush@google.com>

CHROMIUM: Input: atmel_mxt_ts - Remove input_free_device in create

In mxt_input_dev_create, if data->input_dev exists, we unregister
and then free the input device. This may be incorrect, as the unregister
should take care of freeing the input device when there are no longer any
references to the device.

BUG=chromium-os:32512
TEST=builds clean.
Use update_fw, and verify the input device is functional
after the firmware update.

Change-Id: Ic112803243c0e1904f7c8069693f9d0d17511482
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27250
Reviewed-by: Yufeng Shen <miletus@chromium.org>

CHROMIUM: ARM: exynos5250: I2C HDMI information, ddc and hdmiphy added

device-tree info added, hdmiphy and ddc channel is used by HDMI TV

BUG=chrome-os-partner:10851
TEST=build ok test HDMI on smdk5250, EDID read success as can see
HDMI resolutions changes run time.

Change-Id: I0466cf4b9fdcf61f66fb3cc04464cbb9aa5fdd1d
Signed-off-by: Shirish S <s.shirish@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26429
Reviewed-by: Doug Anderson <dianders@chromium.org>
Commit-Ready: Alim Akhtar <alim.akhtar@samsung.com>

arm: exynos5: Use Software Link Training in Displayport driver

This patch disables Hardware Link Training and
enables Software Link Training for Exynos5 DP based boards.

TEST=Agilent Oscilloscope test for DP compliance. Also tested chrome scenarios.
BUG=Issue 10409: Switch to software link training for eDP

Change-Id: Ic6c2febf53242f34b810614f141bce0c1c63a012
Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26919
Tested-by: Sean Paul <seanpaul@chromium.org>
Commit-Ready: Sean Paul <seanpaul@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>

video: exynos: dp: Fix Software Link training in Displayport driver

This patch fixes the Software Link Training routine
according to Displayport standard Specification.

TEST=Agilent Oscilloscope test for DP compliance. Also tested chrome scenarios.
BUG=Issue 10409: Switch to software link training for eDP

Change-Id: Ibd52b735114a65aad6477f26e011a9c9d361d6c6
Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26918
Commit-Ready: Sean Paul <seanpaul@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Tested-by: Sean Paul <seanpaul@chromium.org>

CHROMIUM: ARM: cros5250: I2C HDMI information, ddc and hdmiphy added

device-tree info added, hdmiphy and ddc channel is used by HDMI TV

BUG=chrome-os-partner:10851
TEST=build ok test HDMI on snow, EDID read success as can see
HDMI resolutions changes run time.

Change-Id: I5c7e9575343bc17b227b1084598574438e8d7acb
Signed-off-by: Shirish S <s.shirish@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26656
Reviewed-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>

CHROMIUM: low-mem: work with swap enabled

Without this patch, the notifier triggers too early, when no or
little swap space is used.

We add a contribution from the swap to the "available memory" concept
by introducing a "RAM vs. swap weight". We can't just add them
together because 1. using swap costs us RAM; and 2. freeing RAM by
swapping its content out takes longer than using already free
RAM.

Experiment on an Alex with 2Gb of RAM show that with a weight of
4 and a 50Mb threshold, the system does not thrash or OOM. (The
experiments are not a complete guarantee.)

BUG=chromium-os:32322
TEST=tested with a memory pressure autotest which I am not allowed to commit

Signed-off-by: Luigi Semenzato <semenzato@chromium.org>
Change-Id: I614aa3e1ab1186ccc715bd23a082e7f9379b181c
Reviewed-on: https://gerrit.chromium.org/gerrit/26616
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Ready: Luigi Semenzato <semenzato@chromium.org>
Tested-by: Luigi Semenzato <semenzato@chromium.org>

CHROMIUM: dt: Enable bus arbitration on i2c bus 4

Enable this feature so that the EC and AP can share the bus and both
access TPSCHROME and the battery.

BUG=chrome-os-partner:10955
TEST=boot on snow; see that i2c bus can still be accessed, and that
EC has to wait sometimes.

See previous commit for full tests.

Change-Id: Ie350b93ba0befe730adb14daabc43aedf1c82f2a
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26654
Reviewed-by: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>
Commit-Ready: Rong Chang <rongchang@chromium.org>

CHROMIUM: Config: Removed CONFIG_VITHAR

BUG=None
TEST=None

Change-Id: I9bfdf02ba46529ad9924ae8d496849c296dc404b
Signed-off-by: Ray Smith <Raymond.Smith@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27238
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: David Garbett <David.Garbett@arm.com>
Commit-Ready: Anush Elangovan <anush@google.com>

ARM MALI T6xx Graphic Driver: removed old version of the driver

Removed old version of the driver not used anymore

BUG=none
TEST=tested on Daisy Board

Change-Id: Ib6200405586e97c3033316422d088beb502c1393
Signed-off-by: David Garbett <David.Garbett@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27073
Reviewed-by: Anush Elangovan <anush@google.com>
Commit-Ready: Anush Elangovan <anush@google.com>

CHROMIUM: Config: Normalised Configs

BUG=None
TEST=None

Change-Id: I4d7ec3e3a9c6283c9c7a0e6b60640ace813b5456
Signed-off-by: Ray Smith <Raymond.Smith@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27237
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Anush Elangovan <anush@google.com>
Commit-Ready: Anush Elangovan <anush@google.com>

CHROMIUM: Config: Enable new T6xx driver

Disables old driver that uses the CONFIG_VITHAR* values

BUG=none
TEST=tested on Daisy board

Change-Id: I581c1ba8416ce2fb3395ea839906d0998c544e02
Signed-off-by: David Garbett <David.Garbett@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27071
Reviewed-by: Ray Smith <Raymond.Smith@arm.com>
Reviewed-by: Anush Elangovan <anush@google.com>
Commit-Ready: Anush Elangovan <anush@google.com>

ARM MALI T6xx Graphic Driver

Mali T6xx Driver updated based on W25 OpenGL ES release (TX011-BU-00000-r1p1-00dev3)

BUG=none
TEST=Tested on Daisy Board

Change-Id: I59fd6f91d6906b6164a6c661804096a7bde811b5
Signed-off-by: David Garbett <David.Garbett@arm.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/27070
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: David Garbett <davidgarbettarm@gmail.com>
Commit-Ready: David Garbett <davidgarbettarm@gmail.com>

exynos: i2c: Add bus arbitration implementation

The arbitrator is a general purpose function which uses two GPIOs to
communicate with another device to claim/release a bus. We use it to
arbitrate an i2c port between the AP and the EC.

BUG=chrome-os-partner:10955
TEST=boot on snow; see that i2c bus can still be accessed, and that
EC has to wait sometimes. Keyboard operates while the EC is talking to
the battery and PMU.

Torture test:

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

On EC:
pmu 10000

This runs the bus flat out in with both masters for about 9 minutes.
very roughly 150k i2c transactions on each side.

Observed that we got only 3 timeouts on the EC in that time, none
on the AP, and that the EC recovered from timeout events correctly.

Change-Id: I9dc9406f68b40bfbdec001514775731fa195a714
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26350
Commit-Ready: Grant Grundler <grundler@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>

CHROMIUM: drm/i915: Adjust the RPS thresholds

Lower the RPS thresholds and make them symmetric. This patch increases
the rate of change of the GPU clock, allowing it to clock up more
quickly, and more importantly, clock down when necessary. The problem
this patch solves is that a heavy workload would inflate the clock, and
then the clock would stick high when the workload went away because the
down threshold was too high. This should improve our thermals and power.

BUG=chrome-os-partner:11009
TEST=Tested with the PBS koala video, play it along with a GL demo to
get the clock up to 1150MHz. Remove the GL demo workload and ensure the
clock goes back down to 350MHz.

Change-Id: I9a489ffd4810fb2b3c2544d6165d664899ec0e54
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27184
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>

Revert "CHROMIUM: i915: disable GPU RC6 on ivybridge boards"

This reverts commit 7e5e38687f0582f3356fe148e77418a3027d8fe7

Change-Id: I1e5b4a6688620487108bdf6bfd429ef65c709c69
Reviewed-on: https://gerrit.chromium.org/gerrit/26923
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>
Commit-Ready: Sameer Nanda <snanda@chromium.org>
Tested-by: Sameer Nanda <snanda@chromium.org>

UPSTREAM: mmc: dw_mmc: Fixed sdio interrupt mask bit setting bug

The sdio interrupt mask bits are arranged in [31:16].
(1 << SDMMC_INT_SDIO(slot->id))) does 16 bits left shift twice.
So this patch changes to do 16 bits left shift only one time.

BUG=chrome-os-partner:10990
TEST=Build and boot; code inspection (old bit was clearly wrong).

Change-Id: I7e8d8f711e852d208cbbdebf0fd164fa8459b009
Signed-off-by: Kyoungil Kim <ki0351.kim@samsung.com>
Acked-by: Shashidhar Hiremath <shashidharh@vayavyalabs.com>
Acked-by: Will Newton <will.newton@imgtec.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Signed-off-by: Doug Anderson <dianders@chromium.org>
(cherry picked from commit 705ad0472bd55fa38e6c594b2d6318c31e86068a)
Reviewed-on: https://gerrit.chromium.org/gerrit/26726
Reviewed-by: Grant Grundler <grundler@chromium.org>
Commit-Ready: Grant Grundler <grundler@chromium.org>

UPSTREAM: mmc: dw_mmc: fix the IDMAC sw reset

IDMAC may not be cleaned in driver probe if it has been already used in
boot time. So IDMAC needs sw reset newly. And DMA interface reset
precedes the internal DMAC reset. Additionally SDMMC_IDMAC_SWRESET is
replaced with magic code.

BUG=chrome-os-partner:10990
TEST=Build and boot several times; code inspection.

Change-Id: If3a3f62ca3e90fa9301f19365f681d7d6a626824
Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com>
Acked-by: Will Newton <will.newton@gmail.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Signed-off-by: Doug Anderson <dianders@chromium.org>
(cherry picked from commit 141a712a4eb09639dd4973a7c5e6999e3b8ae04a)
(dianders resolved conflicts with https://gerrit-int.chromium.org/19870)
Reviewed-on: https://gerrit.chromium.org/gerrit/26728
Reviewed-by: Grant Grundler <grundler@chromium.org>
Commit-Ready: Grant Grundler <grundler@chromium.org>

CHROMIUM: mac80211: Abort bgscan when under load

Reapply a patch that causes the mac80211 module to abort background scans
when data is found in the tx buffer, rather than merely suspending the
scan. This patch was previously applied to a previous kernel version,
and reworked by Ashok from Cozybit.

BUG=chromium-os:31435
TEST=Reran network_WiFiMatFunc.090_BgScanAbort, hand tested patched img
Signed-off-by: Christopher Wiley <wiley@chromium.org>
Change-Id: I670ad51c0b9ceb10071175df01de3f141b5e43d3
Reviewed-on: https://gerrit.chromium.org/gerrit/26716

Disable VMX unless directed not to in the command line

With this patch, the kernel will by default disable VMX on all cores.
This is an improvement over what we had with earlier
systems, which only disabled it only on core 0.

There is a command line parameter called disablevmx.
If it is not specified in the command line VMX will be disabled.
If it is specified with no value, VMX will be disabled.
If it is specified with the value 'on', VMX will be disabled.
If it is specified with a value other than 'off', or 'on', the message
Malformed early option 'disablevmx'
will appear in the log, and VMX will *still* be disabled.

If the value is 'off' VMX will not be disabled.
At the same time, the kernel will
not specifically enable it. It takes no action, leaving
the management decision for later.

This has been tested on a 64-bit platform with and without the option,
with values (both incorrect and correct) for the option, and it works.
I don't have a 32-bit platform to test on.

Without the disablevmx=off option the kernel prints this:
[    0.000000] Disabling VMX on cpu 0
[    0.139521] Disabling VMX on cpu 1
[    0.153338] Disabling VMX on cpu 2
[    0.167148] Disabling VMX on cpu 3

BUG=chrome-os-partner:10449

TEST=build an image for 64-bit Chromeos platform as normal. Boot with as
normal and observe this output:

[    0.000000] Disabling VMX on cpu 0
[    0.139521] Disabling VMX on cpu 1
[    0.153338] Disabling VMX on cpu 2
[    0.167148] Disabling VMX on cpu 3

Add the do_not_disablevmx flag from the command line. There is no output,
but rdmsr commands for register 3a will show 0x0000000000000000, e.g.
localhost ~ # rdmsr 0 0x3a
0x0000000000000000
localhost ~ # rdmsr 1 0x3a
0x0000000000000000
localhost ~ # rdmsr 2 0x3a
0x0000000000000000
localhost ~ # rdmsr 3 0x3a
0x0000000000000000

UNLESS, on, e.g. a lumpy, the lock bit was set, in which case
the msrs will have whatever value they had last boot time.

We had a discussion with a kernel developer about upstreaming this option
and we did not reach closure. I'm assuming we'll be owning this patch
for a while, so I'd like to limit the footprint to one file.

Change-Id: I2aa6f258ffcc04f8d146f878b19f13a805d64f0b
Signed-off-by: Ronald G. Minnich <rminnich@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26688
Reviewed-by: Kees Cook <keescook@chromium.org>
Reviewed-by: Will Drewry <wad@chromium.org>

CHROMIUM: config: exynos5: enable MAX77686 RTC

Enable CONFIG_RTC_DRV_MAX77686 to use the PMIC RTC.

BUG=chrome-os-partner:8693
TEST=See the following RTC boot messages:
"max77686-rtc max77686-rtc: rtc core: registered max77686-rtc as rtc0"
Test the RTC using "hwclock"

Change-Id: I250e269d34b4fa5995114c2d584393c120004344
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26538
Commit-Ready: Grant Grundler <grundler@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>

Move video nodes for media devices up to not to conflict with cameras.

Moving MFC and GSC nodes to start with /dev/video10, so as not to conflict
with cameras and confuse Chrome.

BUG=chrome-os-partner:10650
TEST=Manual run and camera test in Chrome

Change-Id: Ic00179e0b068d572b8cb62b70e312efdcaf4d64f
Reviewed-on: https://gerrit-int.chromium.org/20574
Signed-off-by: Pawel Osciak <posciak@google.com>
Reviewed-by: Naveen Krishna Chatradhi <naveen@chromium.org>
Tested-by: Naveen Krishna Chatradhi <naveen@chromium.org>
Reviewed-by: Olof Johansson <olofj@google.com>
Tested-by: Pawel Osciak <posciak@google.com>
Reviewed-by: Kiran <kiran@chromium.org>
Commit-Ready: Pawel Osciak <posciak@google.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26870

CHROMIUM: ARM: exynos: add flip traces

While we generally plan to expand this set of traces to cover more of
the driver, these two for flip request/complete are 2 of the 3 traces
currently reported by the i915 driver being used as a point of
comparison (the other is for the pwrite_ioctl which isn't supported
here).

TEST=Booted the kernel on device and was able to observe believable
trace data from systrace (once it was set to whitelist these
tracepoints).
BUG=chrome-os-partner:11092

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

HACK: exynos5250: config/dtsi: Enable battery support on snow

This enables the battery on snow so that you can see the battery status
on the gui.

BUG=none
TEST=manual:
boot on snow; see that the battery gauge comes up after a few seconds

Change-Id: I4363674eca57d16201b4ddedd49a21fa44dd17de
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26835
Commit-Ready: Grant Grundler <grundler@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>

exynos: i2c: Leave the bus disabled unless it is in use

There is a rather odd feature of the exynos i2c controller that if it
is left enabled, it can lock itself up with the clk line held low.
This makes the bus unusable.

Unfortunately, the s3c24xx_i2c_set_master() function does not notice
this, and reports a timeout. From then on the bus cannot be used until
the AP is rebooted.

The problem happens when any sort of interrupt occurs (e.g. due to a
bus transition) when we are not in the middle of a transaction. We
have seen many instances of this when U-Boot leaves the bus apparently
happy, but Linux cannot access it.

The current code is therefore pretty fragile.

This fixes things by leaving the bus disabled unless we are actually
in a transaction. We enable the bus at the start of the transaction and
disable it at the end. That way we won't get interrupts and will not
lock up the bus.

It might be possible to clear pending interrupts on start-up, but this
seems to be a more robust solution. We can't service interrupts when
we are not in a transaction, and anyway would rather not lock up the
bus while we try.

BUG=chrome-os-partner:11124
TEST=manual:
Look up bus 4 in U-Boot by manually modifying the code to leave a
pending interrupt in the controller (stopping a transaction half-way
through with an error).

Boot into Linux and see that the bus is recovered and works normally
with:

$ i2cdump -f -y 4 0x48

Without this change, we see:

s3c-i2c s3c2440-i2c.4: cannot get bus (error -110)

in the kernel logs.

Check that the keyboard works also (which uses i2c4).

Change-Id: Iccc9777fa8576bd4491dfbfbad044cec3638debb
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26834
Commit-Ready: Grant Grundler <grundler@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>

chromium: enable DWC3 config for Exynos

Enable CONFIG_USB_DWC3 for Exynos to enable USB3.0 support.

BUG=chrome-os-partner:11030
TEST=emerge-daisy chromeos-kernel, boot kernel on snow,
verify lsusb shows device correctly

Change-Id: I1e0123a7e6d73d13329491126fedd508ad63beab
Reviewed-on: https://gerrit.chromium.org/gerrit/26867
Reviewed-by: Olof Johansson <olofj@chromium.org>
Tested-by: Katie Roberts-Hoffman <katierh@chromium.org>
Commit-Ready: Katie Roberts-Hoffman <katierh@chromium.org>

CHROMIUM: ALSA: hda/ca0132 - use same pcm index for analog capture and playback.

Change-Id: I17aea018e5bec48e8880b6ae0fccde11d7b7ccea
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26342

rtc: MAX77686: Add Maxim 77686 rtc driver

Add support for MAX77686 RTC. It supports features like AM/PM, 24/12
modes of operation as well as alarm interrupts.

BUG=chrome-os-partner:8693
TEST=See the following RTC boot messages:
"max77686-rtc max77686-rtc: rtc core: registered max77686-rtc as rtc0"
Test the RTC using "hwclock"

Change-Id: I2d18e9bf14a23ab4872339e338499bc96f556bbf
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26536
Reviewed-by: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>
Commit-Ready: Grant Grundler <grundler@chromium.org>

exynos5: dt: Setup MAX77686 pmic gpio

Initialize the gpio line for PMIC interrupt on Exynos5.

BUG=chrome-os-partner:8693
TEST=Test the RTC using "hwclock"

Change-Id: I27fe0f6657382341b9b84a048127e51ec34eacaf
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26537
Reviewed-by: Grant Grundler <grundler@chromium.org>
Tested-by: Grant Grundler <grundler@chromium.org>
Commit-Ready: Grant Grundler <grundler@chromium.org>

UPSTREAM: mmc: dw_mmc: fix incorrect setting of host->data of NULL

Setting host->data to NULL is incorrect sequence in
dw_mci_command_complete. This early setting makes the skip of
dma_unmap_sg in dw_mci_dma_cleanup.

BUG=chrome-os-partner:10990
TEST=Build and boot; code inspection.

Change-Id: Ibb328fd1747e282fbef966cad51afc510ac1a313
Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com>
Acked-by: Will Newton <will.newton@gmail.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Signed-off-by: Doug Anderson <dianders@chromium.org>
(cherry picked from commit fda5f736864c46324dbc50246ef1ca0e84ebf4ae)
Reviewed-on: https://gerrit.chromium.org/gerrit/26727
Commit-Ready: Grant Grundler <grundler@chromium.org>
Reviewed-by: Grant Grundler <grundler@chromium.org>

UPSTREAM: staging: gdm72xx: use %pM for MAC

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Ben Chan <benchan@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit e7ecb0fb40a5358646888720848787da34cfa33d)

Change-Id: I924f74e892c12ba19f0341da386b4a4286b7a38a
Signed-off-by: Ben Chan <benchan@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26865
Reviewed-by: Olof Johansson <olofj@chromium.org>

CHROMIUM: exynos: dvfs: Fix Maxim 77686 to correctly check device-tree

The check for the dt property "max77686,buck_ramp_delay" was
incorrectly ignored. The of_property_read_u32() function returns 0
when the property is found, so fix this by inverting the test.

BUG=chrome-os-partner:10891
TEST=Ad hoc, ensure that the driver is using the correct value for
voltage slew rate

Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
Change-Id: I878108558510c0f07604d4a30366fe343ee8ac06
Reviewed-on: https://gerrit.chromium.org/gerrit/26853
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Ready: Sonny Rao <sonnyrao@chromium.org>

CHROMIUM: exynos: dvfs: fix default slew rate for Maxim 77686 PMIC

The device tree specifies the default voltage slew rate for the
Maxim 77686 regulator which is powering the CPU rail, but it is giving
the incorrect value. The value isn't well specified as it merely points
to a table in the regulator code, but the current value of 2 points to the
55 mv/usec rate instead of the actual default which is 27.5 mv/usec.
This happened to work because the maxim regulator code was incorrectly
ignoring the value coming from the device tree, and choosing the
appropriate default. Fix the first part by changing the default value
to 1 which is 27.5 mV/uS.

BUG=chrome-os-partner:10891
TEST=none, requires further driver fix to test

Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
Change-Id: I192a24d96f0642c58f555c89061df0a5e86508d9
Reviewed-on: https://gerrit.chromium.org/gerrit/26852
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Ready: Sonny Rao <sonnyrao@chromium.org>

CHROMIUM: exynos: dvfs: maxim: Fix unit conversion error when calculating delay

The Maxim 77686 driver specifies voltages for different regulators in different
units, using either milli-volts or micro-volts. It fails to account for this
unit difference when calculating the amount of time to wait in microseconds for
the voltage change to complete, so I changed the table of slew rates to be in
micro-volts per micro-second instead of milli-volts per micro-second, and
factor in the units into the calculation. I also made the table more
accurate than it was because we have more precision by using micro-volts.

BUG=chrome-os-partner:10891
TEST="ad hoc, run with ondemand or interactive governer, run perf top,
observe that __delay is no longer one of the top functions"

Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
Change-Id: Ic2ae82d92a86db503982b6cc29fdc2d68fa6ee9e
Reviewed-on: https://gerrit.chromium.org/gerrit/26851
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Ready: Sonny Rao <sonnyrao@chromium.org>

ARM: exynos: Don't free backlight enable GPIO

Move the lcd backlight enable GPIO to samsung_bl_init to
prevent issues with freeing and requesting it multiple times.
This fixes issues with enabling the blacklight on resume.

BUG=chrome-os-partner:11086
TEST=Resume device, observe backlight turns on

Change-Id: Ibac332202f77986f4f25b01d523d31f66ac92649
Signed-off-by: Jonathan Kliegman <kliegs@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26817
Reviewed-by: Olof Johansson <olofj@chromium.org>

UPSTREAM: mm: fix faulty initialization in vmalloc_init()

commit dbda591d920b4c7692725b13e3f68ecb251e9080 upstream.

The transfer of ->flags causes some of the static mapping virtual
addresses to be prematurely freed (before the mapping is removed) because
VM_LAZY_FREE gets "set" if tmp->flags has VM_IOREMAP set.  This might
cause subsequent vmalloc/ioremap calls to fail because it might allocate
one of the freed virtual address ranges that aren't unmapped.

va->flags has different types of flags from tmp->flags.  If a region with
VM_IOREMAP set is registered with vm_area_add_early(), it will be removed
by __purge_vmap_area_lazy().

Fix vmalloc_init() to correctly initialize vmap_area for the given
vm_struct.

Also initialise va->vm.  If it is not set, find_vm_area() for the early
vm regions will always fail.

BUG=None
TEST=emerge-daisy chromeos-kernel,
run 4 instances of 1080p h264 video multiple times without issues.

Signed-off-by: KyongHo Cho <pullip.cho@samsung.com>
Cc: Olav Haugan <ohaugan@codeaurora.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: Arjun KV <arjun.kv@samsung.com>
Change-Id: Ib951f26497e6929978ce169230a97e7961535ecf
Reviewed-on: https://gerrit.chromium.org/gerrit/26814
Reviewed-by: kiran <kiran@chromium.org>
Tested-by: kiran <kiran@chromium.org>
Reviewed-by: Sunil M <sunilm.samsung@gmail.com>
Reviewed-by: Pawel Osciak <posciak@google.com>

exynos: drm: mfc: gsc: Increase the IOMMU memory size from 128MB to 256MB

This change is required for 1080p multiple instance video playback.
We need to increase the MFC, GSC and DRM-FIMD IOMMU memory size
from 128MB to 256MB.
With this change all VDA scenarios including multi instance playback
are handled.

BUG=None
TEST=emerge-daisy chromeos-kernel,
run 4 instance 1080p h264 video.

Change-Id: Iaa410a29addea565ae7cca65360ba909b26a795e
Signed-off-by: Arjun KV <arjun.kv@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26813
Reviewed-by: kiran <kiran@chromium.org>
Tested-by: kiran <kiran@chromium.org>
Reviewed-by: Sunil M <sunilm.samsung@gmail.com>
Reviewed-by: Subash Patel <subash@chromium.org>
Reviewed-by: Pawel Osciak <posciak@google.com>

exynos/gsc: modify number of output and capture buffers

gscaler src buffer count increased to 16
This is required for H264 streams

BUG=None
TEST=Utc OMX test app and Chrome unit test works fine.

Change-Id: I5a3cb6800b31b9816129317cdba3d7b5333560ee
Signed-off-by: Arun Mankuzhi <arun.m@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26810
Reviewed-by: Sunil M <sunilm.samsung@gmail.com>
Reviewed-by: kiran <kiran@chromium.org>
Tested-by: kiran <kiran@chromium.org>
Reviewed-by: Pawel Osciak <posciak@google.com>
Commit-Ready: kiran <kiran@chromium.org>

CHROMIUM: Input: cyapa - return -ENOMEM if kasprintf fails in probe

"ret" is being returned unitialized in this error path.

Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
BUG=chromium-os:32389
TEST=builds without this warning:
cyapa.c: In function 'cyapa_probe':
cyapa.c:1779:6: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized]

Change-Id: I8ba5ecf03a99d13df808cf83b7a68a13d3891fab
Reviewed-on: https://gerrit.chromium.org/gerrit/26803
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Tested-by: Daniel Kurtz <djkurtz@chromium.org>
Commit-Ready: Daniel Kurtz <djkurtz@chromium.org>

CHROMIUM: Input: cyapa - fix "no return statement..."

cyapa_start_runtime() doesn't return anything, so make it return void.

Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
BUG=chromium-os:32389
TEST=builds without this warning:
cyapa.c: In function 'cyapa_start_runtime':
cyapa.c:1771:1: warning: no return statement in function returning non-void [-Wreturn-type]

Change-Id: I56ca2c62fb15c0a0e98b6277f8d3721c457eb9a5
Reviewed-on: https://gerrit.chromium.org/gerrit/26802
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Tested-by: Daniel Kurtz <djkurtz@chromium.org>
Commit-Ready: Daniel Kurtz <djkurtz@chromium.org>

CHROMIUM: ARM: cros5250: Invert power button signal

The power button is currently inverted on snow. This inverts the signal.

BUG=chrome-os-partner:11112
TEST=Quick power button press no longer screen logs or shuts down
power manager logs report correct state on presses

Change-Id: Iecd95fde5ddc67ec09cd6bd35fcf8948bd0be2f5
Signed-off-by: Jonathan Kliegman <kliegs@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26788

UPSTREAM: HID: magicmouse: Implement Multi-touch Protocol B (MT-B)

The driver for Apple Magic Trackpad/Mouse currently uses
Multi-touch Protocol A (MT-A) to report touch events and uses
ABS_MT_TRACKING_ID to do finger tracking. The fact of the device
being able to track individual finger makes it possible to
report touch events using MT-B. This patch converts the driver
to use MT-B as it is preferred to MT-A.

V4: Removed BTN_TOUCH evnet.
V3: Removed the single touch related logic.
V2: Converting entirely to MT-B as Henrik Rydberg suggested.

Signed-off-by: Yufeng Shen <miletus@chromium.org>
Reviewed-and-tested-by: Henrik Rydberg <rydberg@euromail.se>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
cherry-picked from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
commit a6d1bc1d5fb0f6ce817bef188a3d93255db03992

BUG=chromium-os:29435
TEST=Use evtest/mtplot to check that Apple Magic Trackpad is
reporting MT-B touch events correctly.

Change-Id: I1d51ace4f05d86d39a7012bf43b659ccb26eae7e
Reviewed-on: https://gerrit.chromium.org/gerrit/26791
Reviewed-by: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
Commit-Ready: Yufeng Shen <miletus@chromium.org>

UPSTREAM: HID: magicmouse: Removing report_touches switch

Remove the report_touches switch as it is not so useful to turn
off reporting touch events for a touch device. Let the userspace
to do the filtering if the turning off is needed.

V2: Remove report_touches as suggeted by Chase Douglas

Signed-off-by: Yufeng Shen <miletus@chromium.org>
Reviewed-and-tested-by: Henrik Rydberg <rydberg@euromail.se>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
cherry-picked from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
commit 6264307ed090cc41a47a1e55be713d75e81f1b27

BUG=None
TEST=Module compiles and magic trackpad still emits touch
events correctly.

Change-Id: I93170af98da55401a2a29a92f8f0a3a136646c48
Reviewed-on: https://gerrit.chromium.org/gerrit/26790
Reviewed-by: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
Commit-Ready: Yufeng Shen <miletus@chromium.org>

UPSTREAM: ARM: EXYNOS: Remove the L2 cache latency setting for EXYNOS5

Since SYSRAM set the L2 cache latency on EXYNOS5 SoCs,
no longer need that in the kernel. It helps to reduce
booting time (no need cache disable and cache enable).

BUG=None
TEST=Run /opt/punybench/bin/memcpy_test before and after.
No significant diference noticed in numbers.  For reference,
numbers look like:
  L1 cached data:
  memcpy_trivial:  (4096 bytes copy) =  800.2 MiB/s /  800.5 MiB/s
  memcpy        :  (4096 bytes copy) = 3085.0 MiB/s / 7019.3 MiB/s
  memcpy_trivial:  (6144 bytes copy) =  790.0 MiB/s /  787.4 MiB/s
  memcpy        :  (6144 bytes copy) = 3062.4 MiB/s / 7207.7 MiB/s

  L2 cached data:
  memcpy_trivial:  (65536 bytes copy) =  785.6 MiB/s /  791.6 MiB/s
  memcpy        :  (65536 bytes copy) = 3009.0 MiB/s / 5818.0 MiB/s
  memcpy_trivial:  (98304 bytes copy) =  783.7 MiB/s /  784.4 MiB/s
  memcpy        :  (98304 bytes copy) = 2977.7 MiB/s / 5784.4 MiB/s

  SDRAM:
  memcpy_trivial:  (8388608 bytes copy) =  772.8 MiB/s /  760.5 MiB/s
  memcpy        :  (8388608 bytes copy) = 2228.6 MiB/s / 2558.6 MiB/s
  memcpy_trivial:  (12582912 bytes copy) =  770.9 MiB/s /  772.7 MiB/s
  memcpy        :  (12582912 bytes copy) = 2209.3 MiB/s / 2527.8 MiB/s

Change-Id: I314bd2d6644e18aa64221b816079bf84e6c80959
Signed-off-by: Boojin Kim <boojin.kim@samsung.com>
Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
Signed-off-by: Doug Anderson <dianders@chromium.org>
(cherry picked from commit c8dd5110dead436b178bb2d8976290fd5f77a2ee)
Reviewed-on: https://gerrit.chromium.org/gerrit/26539

media: gscaler: fixed multi instance video playback issue

This patch fixes the multi instance video playback crash issue
when kernel preemption is disabled.
pm_runtime_xxx() functions are moved from the irq_handler context
to vb2 ops functions, namely stop_streaming and start_streaming.
workqueue related functionality is deleted from gscaler as it is
redundant now.

BUG=chrome-os-partner:10424
TEST=emerge-daisy chromeos-kernel,
check multi instance playback.

Change-Id: I05680c0548d7e7da399befbd6f84da8941eda682
Signed-off-by: Shaik Ameer Basha <shaik.ameer@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26781
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
Reviewed-by: Pawel Osciak <posciak@google.com>
Tested-by: Arjun.K.V <arjun.kv@samsung.com>
Commit-Ready: Arjun.K.V <arjun.kv@samsung.com>

s5p-mfc: Fix a bug in open and close instance cmd

The open_instance_cmd and close_instance_cmd are working on the wrong
context number. This patch fixes the bug.

BUG=Playing bigger streams fails at gsc_m2m_try
TEST=Tested Multi instance with google test app

Change-Id: I6f216a872213ae7485939904ec14f509c427914b
Signed-off-by: Arun Kumar <arun.kk@samsung.com>
Signed-off-by: Naveen krishna Chatradhi <ch.naveen@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26515
Tested-by: naveen krishna chatradhi <naveen@chromium.org>
Reviewed-by: Pawel Osciak <posciak@google.com>
Commit-Ready: naveen krishna chatradhi <naveen@chromium.org>

Revert "TEMP: s5p-mfc: Set display delay to 0x8"

Proper fix has been preposed and merged already

This reverts commit 2b06222227681b13b3c25b25fbf3fa21997e64af.

BUG=None
TEST=Verified with OMX application

Change-Id: I3fe35fdb243730a33f5f53b530424adf4f9a3da5
Signed-off-by: Naveen krishna Chatradhi <ch.naveen@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26514
Tested-by: naveen krishna chatradhi <naveen@chromium.org>
Reviewed-by: Pawel Osciak <posciak@google.com>
Commit-Ready: naveen krishna chatradhi <naveen@chromium.org>

CHROMIUM: chromeos_laptop - Add cyapa on Parrot

Add cyapa touchpad for Parrot board.

BUG=chrome-os-partner:10369
TEST=Check that cyapa comes up correctly on Parrot
with Coreboot system firmware.

Change-Id: Ie9d0560da5d8dcbfa092db41f5e80d328bc69989
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26130
Reviewed-by: Jay Kim <yongjaek@chromium.org>

ARM: exynos: Remove __initdata from smdk5250_dp_data structure

platform_data structures are assumed by the exynos_dp driver to be
valid after initialization. Remove the __initdata tag to keep
the data valid.

BUG=chrome-os-partner:11063
TEST=power_Resume test @10 iterations with no panics

Change-Id: Ifc8d38cd0150ec1116ee37310df399508c5624e1
Signed-off-by: Jonathan Kliegman <kliegs@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26696
Reviewed-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>

mac80211: don't forget to wake queues

This patch is written by Johannes that helps to wake tx
queues when there is a change in channel type. This could
be found from "http://p.sipsolutions.net/3e89ee42463d6cc9.txt".

Signed-off-by: Ashok Nagarajan <ashok@cozybit.com>
Signed-off-by: Paul Stewart <pstew@chromium.org>
BUG=chrome-os-partner:10361
TEST=Run with new kernel on 5GHz net with invalid HT40

Change-Id: Ic730583ebd6ca65871072a9025b74574368d0280
Reviewed-on: https://gerrit.chromium.org/gerrit/26623
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Commit-Ready: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>

video: exynos: Add function to aux failures

Add the function name to the aux transaction failure messages so we can
tell which transaction is failing.

BUG=None
TEST=Tested on snow, saw function in error.

Change-Id: Ib395c474785f06d281f23c45f27129497ec00bfb
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26687
Reviewed-by: Doug Anderson <dianders@chromium.org>

ath9k: fix interrupt storm due to watchdog hw reset

Return IRQ_HANDLED when the hw reset is in progress
due to fatal or watchdog interrupt. Not doing so, leads to
interrupt storm.

Signed-off-by: Rajkumar Manoharan <rmanohar@qca.qualcomm.com>
Signed-off-by: Paul Stewart <pstew@chromium.org>
BUG=chrome-os-partner:11037
TEST=Boot kernel with this change, observe no disconnects over
a 1 hour run.

Change-Id: Ib08cd3a3e460355336b300da46b1a820e171dab1
Reviewed-on: https://gerrit.chromium.org/gerrit/26621
Commit-Ready: Paul Stewart <pstew@chromium.org>
Reviewed-by: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>

CHROMIUM: ARM: exynos: Use 200Hz Exynos 4 and 5

The special-case for the 200 Hz Exynos4 clock should apply for Exynos5,
as well.

TEST=checked change in tracing resolution in chrome://tracing after a
successful boot.
BUG=chrome-os-partner:10818

Change-Id: I456999135428d4aebda07eaaf46cd14527befa1d
Signed-off-by: Jeff Disher <disher@google.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26446
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Jeff Disher <disher@chromium.org>
Tested-by: Jeff Disher <disher@chromium.org>

CHROMIUM: drm/i915: Adjust the down threshold.

The thresholds for GPU reclocking are highly asymetrical. This creates an
interesting phenomenon on Chrome startup where the clock ramps up very
quickly, and then the blinking cursor is enough to keep it up. Obviously
having the max GPU clock on the login screen is very bad for thermals.

With this change, the clock goes back to its minimum frequency after a couple
of seconds.

BUG=chrome-os-partner:11009
TEST=checked that a blinking cursor lets the GPU clock go back to 350Mhz

Change-Id: I3b8de74864907abdb3c7c4aeb0ab4fcf2eaf0b2c
Reviewed-on: https://gerrit.chromium.org/gerrit/26641
Tested-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Reviewed-by: Sameer Nanda <snanda@chromium.org>
Commit-Ready: Stéphane Marchesin <marcheu@chromium.org>

CHROMIUM: config: exynos5 uses 200Hz scheduler

The special-case for the 200 Hz Exynos4 clock should apply for Exynos5,
as well. This change corresponds to one made in Kconfig.

TEST=checked change in tracing resolution in chrome://tracing after a
successful boot.
BUG=chrome-os-partner:10818

Change-Id: Icb126ba9daf09a249099b3ca4533a108553d5d7e
Signed-off-by: Jeff Disher <disher@google.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26682
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Jeff Disher <disher@chromium.org>
Tested-by: Jeff Disher <disher@chromium.org>

CHROMIUM: config: remove chromiumos-exynos5

Removing the Chromium OS kernel config for exynos. It's causing confusion
at this time to have two of them, we can split them later again if needed.

BUG=none
TEST=none

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

CHROMIUM: ALSA: hda - Update ca0132 driver.

Updated driver supports loading code to the DSP and an EQ for the
speaker. Code provided by Creative.

BUG=chrome-os-partner:10985
TEST=build and run kernel on link. Test audio with youtube and gtalk.

Change-Id: I7222bb577c340b27cae34238775c78a07806912b
CQ-DEPEND: Iff6805b02319cb36b9c256110c78b3b48911fb7e
CQ-DEPEND: Iae8742f8add1b4b846663dc06aba1f61005c3914
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/24522
Reviewed-by: Olof Johansson <olofj@chromium.org>

CHROMIUM: config - Disable CA0132.

Disable the ca0132 driver before merging the newer version of the
driver. A subsequent change to chromiumos-base will add a config
fragment to turn it on based on a use flag.

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

CHROMIUM: zsmalloc: add MODULE_LICENSE

It won't load as a module without MODULE_LICENSE.

BUG=chromium-os:32328
TEST=modprobe zsmalloc works with this change

Change-Id: Ic62fe20816e5079d92ce1da6a9d8a9cdbc7a5074
Signed-off-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26627
Reviewed-by: Olof Johansson <olofj@chromium.org>

CHROMIUM: ARM: cros5250: Turn off pullups for i2c2

Disabled pullups since external part has its own pullups and
double-pulling gets us out of spec in some cases.

BUG=chrome-os-partner:11039
TEST=Boot kernel and was able to still read EDID using:
i2cdump -y -f -r 0-0xff 2 0x50

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

exynos5: dt: Increase the speed of i2c channel 0

The MAX77686 PMIC chip is connected to i2c0 and was running at 65KHz.
Better its performance by increasing the maximum bus speed on i2c0 to
378KHz (which is the closest possible speed to the maximum 400KHz
supported by the legacy i2c controller).

BUG=chrome-os-partner:10995
TEST=Boot Snow and see the following bootup messages:
"s3c-i2c s3c2440-i2c.0: bus frequency set to 378 KHz"
Also, ensure the MAX77686 regulator driver has completed its initial
configuration without failure.

Change-Id: I7d031ad25c6f458ebc41417f882f36b2f8b4d83a
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26540
Reviewed-by: Prashanth Godrehal <prashanth.g@samsung.com>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Commit-Ready: Doug Anderson <dianders@chromium.org>

exynos5: dt: Fix gpio for bluetooth on Snow/Daisy

Fix incorrect gpio line for Bluetooth in Snow/Daisy device tree.

BUG=None
TEST=Build and boot Snow

Change-Id: I0ef1718a32a29506d92b97bfc0727d8709c0a33a
Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
Reviewed-on: https://gerrit.chromium.org/gerrit/26535
Reviewed-by: Prashanth Godrehal <prashanth.g@samsung.com>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Tested-by: Doug Anderson <dianders@chromium.org>
Commit-Ready: Doug Anderson <dianders@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: Ibfba477842e52652c10e427a2ef56147ad326de2
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26574
Reviewed-by: Olof Johansson <olofj@chromium.org>
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>

BACKPORT: drm/i915: add min freq control to debugfs

This makes for easier benchmarking and testing. One can set a fixed
frequency by setting min and max to the same value.

v2: fix whitespace & comment (Eugeni)

Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
TEST=compiled, tried setting the min frequency.
BUG=none

Change-Id: Ic3c65ea2f9853baa305f598321619e66e5a0019b
Reviewed-on: https://gerrit.chromium.org/gerrit/26521
Tested-by: Stéphane Marchesin <marcheu@chromium.org>
Reviewed-by: Puneet Kumar <puneetster@chromium.org>
Commit-Ready: Stéphane Marchesin <marcheu@chromium.org>

CHROMIUM: ARM: cros5250: Turn on video_mid regulator

Required for enabling/reading the HDMI EDID
and for HDMI hot plug

BUG=chrome-os-partner:11013
TEST=verify with new kernel image

localhost ~ # grep "video_mid" /sys/class/regulator/*/name
/sys/class/regulator/regulator.19/name:video_mid
localhost ~ # grep "" /sys/class/regulator/regulator.19/*
/sys/class/regulator/regulator.19/max_microvolts:5000000
/sys/class/regulator/regulator.19/min_microvolts:5000000
/sys/class/regulator/regulator.19/name:video_mid
/sys/class/regulator/regulator.19/num_users:0
/sys/class/regulator/regulator.19/state:enabled
/sys/class/regulator/regulator.19/type:voltage
/sys/class/regulator/regulator.19/uevent:OF_NAME=VFET2
/sys/class/regulator/regulator.19/uevent:OF_FULLNAME=/i2c@12CA0000/power-regulator/voltage-regulators/VFET2
/sys/class/regulator/regulator.19/uevent:OF_COMPATIBLE_N=0

Change-Id: I0e8fce30c74f764573806ac9b7e531ed4ef8b0a9
Signed-off-by: Anush Elangovan <anush@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26519
Commit-Ready: Anush Elangovan <anush@google.com>
Reviewed-by: Anush Elangovan <anush@google.com>
Tested-by: Anush Elangovan <anush@google.com>
Reviewed-by: Olof Johansson <olofj@chromium.org>

CHROMIUM: config: enable interactive governor

Include the interactive governor for testing.

Signed-off-by: Sam Leffler <sleffler@chromium.org>
BUG=chromium-os:17379 chromium:118032
TEST=build+boot on alex+lumpy; smoke suite (had been failing due to hung task timeout issue)

Change-Id: I0031a74ac6d829410de5e1768f3c92f19677fa8f
Reviewed-on: https://gerrit.chromium.org/gerrit/25845
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Ready: Sam Leffler <sleffler@chromium.org>
Tested-by: Sam Leffler <sleffler@chromium.org>

CHROMIUM: chromeos_laptop - Add missing __init annotations

Now that we no longer have exported functions in this driver,
we can annotate most of the other structures and functions
as __initdata or __init.

BUG=chromium-os:31877
TEST=build with CONFIG_DEBUG_SECTION_MISMATCH=y
Check no warnings in building chromeos_laptop.
Verify that touchpad and light sensors keep working on various platforms.

Change-Id: Ib412ee7f5b04de7e09194d4d26550c11acd56900
Signed-off-by: Benson Leung <bleung@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/26154
Reviewed-by: Olof Johansson <olofj@chromium.org>

CHROMIUM: arm: config: disable CMA for exynos5 SoC

CMA is not needed for the chrome-daisy platform as all the IP's have
their own IOMMU's. Also, it was found that leaving CMA enabled by
default, it will affect the kernel to do the routine free page
maintainenance due to a known issue.

BUG=chrome-os-partner:10745
TEST=kernel builds, boots, and doesn't have memory-allocation
failures during chromeos-install

Signed-off-by: Subash Patel <subash.rp@samsung.com>
Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
Change-Id: I4019aa6ebee9442f42fe4408d8788eb00dd570b2
Reviewed-on: https://gerrit.chromium.org/gerrit/26413
Tested-by: Sonny Rao <sonnyrao@chromium.org>
Reviewed-by: Subash Patel <subash@chromium.org>
Tested-by: Subash Patel <subash@chromium.org>
Commit-Ready: Doug Anderson <dianders@chromium.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>

CHROMIUM: ARM: dma-mapping: remove unconditional dependency on CMA

CMA has been enabled unconditionally on all ARMv6+ systems to solve the
long standing issue of double kernel mappings for all dma coherent
buffers. This however created a dependency on CONFIG_EXPERIMENTAL for
the whole ARM architecture what should be really avoided. This patch
removes this dependency and lets one use old, well-tested dma-mapping
implementation also on ARMv6+ systems without the need to use
EXPERIMENTAL stuff.

Reported-by: Russell King <linux@arm.linux.org.uk>
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: Subash Patel <subash.rp@samsung.com>
(sonnyrao: this is based on an upstream patch, but our tree has additional
patches which cause the upstream to no apply anymore, so this
is a CHROMIUM patch now)
Signed-off-by: Sonny Rao <sonnyrao@chromium.org>
BUG=chrome-os-partner:10745
TEST=kernel still builds on arm

Change-Id: I2a16e5a97796066d840c37745d67abb0f1c7a542
Reviewed-on: https://gerrit.chromium.org/gerrit/26412
Tested-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Ready: Doug Anderson <dianders@chromium.org>
Reviewed-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Subash Patel <subash@chromium.org>
Tested-by: Subash Patel <subash@chromium.org>

CHROMIUM: ARM: add idle notifications

Add idle_notifier callbacks to cpu_idle.

Signed-off-by: Sam Leffler <sleffler@chromium.org>
BUG=none
TEST=run with ondemand and interactive governors

Change-Id: Iff408362c753aabf731fa9f5de1622377dc29779
Reviewed-on: https://gerrit.chromium.org/gerrit/26334
Tested-by: Sam Leffler <sleffler@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Sam Leffler <sleffler@chromium.org>

CHROMIUM: cpu: add idle notifiers

Promote idle_notifier_register/unregister support from x86.
Add idle_notifier_call_chain to complete encapsulation.

Signed-off-by: Sam Leffler <sleffler@chromium.org>
BUG=none
TEST=build+boot on lumpy with ondemand and interactive governors

Change-Id: Id134d2bf5371a9f281b2f916fef861b08d8233bd
Reviewed-on: https://gerrit.chromium.org/gerrit/26333
Tested-by: Sam Leffler <sleffler@chromium.org>
Reviewed-by: Olof Johansson <olofj@chromium.org>
Commit-Ready: Sam Leffler <sleffler@chromium.org>