UPSTREAM: video/hdmi: Replace the payload length by their defines

Cc: Thierry Reding <thierry.reding@avionic-design.de>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Acked-by: Dave Airlie <airlied@gmail.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
(cherry picked from commit 3c6b054de1c0243a0f708abf337f2a0e270ce247)

Signed-off-by: Wayne Boyer <wayne.boyer@intel.com>

BUG=chrome-os-partner:26772
TEST=Connect Rambi via HDMI to ASUS VE228 monitor and verify correct
output on the monitor.

Change-Id: Ic02bf6da5f8bafadfd573a620c823dd012e3867d
Reviewed-on: https://chromium-review.googlesource.com/189621
Reviewed-by: Jim Bride <jim.bride@intel.com>
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Wayne Boyer <wayne.boyer@intel.com>
Tested-by: Wayne Boyer <wayne.boyer@intel.com>
(cherry picked from commit 7fcb09a50a1d5f44d8447ace5a48da5f3e2590d9)
Reviewed-on: https://chromium-review.googlesource.com/190150
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
UPSTREAM: video/hmdi: Clear the whole incoming buffer, not just the infoframe size

If the user if this API is providing a bigger buffer than the infoframe
size, it could be for a could reason. For instance it could be because
it gives the buffer that will be written to the hardware, up to the
maximum of an infoframe size.

Instead of just zeroing up to the infoframe size, let's zero the whole
incoming buffer as those extra bytes are also used to compute the
ECC and need to be 0.

Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Acked-by: Dave Airlie <airlied@gmail.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
(cherry picked from commit 3b390f62674eb70522057e58b1787f2cfa2f57c1)

Signed-off-by: Wayne Boyer <wayne.boyer@intel.com>

BUG=chrome-os-partner:26772
TEST=Connect Rambi via HDMI to ASUS VE228 monitor and verify correct
output on the monitor.

Change-Id: I84bceea4ff404bb1e15c05b6b146a4a81ef8d925
Reviewed-on: https://chromium-review.googlesource.com/189622
Reviewed-by: Jim Bride <jim.bride@intel.com>
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Wayne Boyer <wayne.boyer@intel.com>
Tested-by: Wayne Boyer <wayne.boyer@intel.com>
(cherry picked from commit 6cbf0dfd66206fb895a79e1475558bbba630dbc5)
Reviewed-on: https://chromium-review.googlesource.com/190151
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
UPSTREAM: coredump: add new %P variable in core_pattern

Add a new %P variable to be used in core_pattern.  This variable contains
the global PID (PID in the init namespace) as %p contains the PID in the
current namespace which isn't always what we want.

The main use for this is to make it easier to handle crashes that happened
within a container.  With that new variables it's possible to have the
crashes dumped into the container or forwarded to the host with the right
PID (from the host's point of view).

BUG=chromium:351568
TEST=`cbuildbot amd64-generic-full` passes

Signed-off-by: Stphane Graber <stgraber@ubuntu.com>
Reported-by: Hans Feldt <hans.feldt@ericsson.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Eric W. Biederman <ebiederm@xmission.com>
Cc: Andy Whitcroft <apw@canonical.com>
Acked-by: Serge E. Hallyn <serge.hallyn@ubuntu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Mike Frysinger <vapier@chromium.org>
(cherry picked from commit 65aafb1e7484b7434a0c1d4c593191ebe5776a2f)

Change-Id: I3521e781c226c9fb73b16be6f207fd0dcece9229
Previous-Reviewed-on: https://chromium-review.googlesource.com/190012
(cherry picked from commit 5c69102929e6662d77fad20a56c57a8e2fcca6e6)
Reviewed-on: https://chromium-review.googlesource.com/190502
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BACKPORT: ASoC: Intel: Fix corruption in BYT PCM driver.

The PCM ops in BYT PCM driver are over writing the RTD driver data causing
corruption after first playback or capture has been opened. Fix this by not
using snd_soc_pcm_set_drvdata(). There are no other users of
snd_soc_pcm_set_drvdata upstream so this needs to be removed uptream too.

BUG=chrome-os-partner:26908
TEST=apply full patch set. Run aplay and arecord simulteneously, see
no kernel crash.

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

Original-Change-Id: I595f795ec128e4b0b185cfcbfb9a56332f01a8c3
Signed-off-by: Hsin-Yu Chao <hychao@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/190462
Reviewed-by: Benson Leung <bleung@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
(cherry picked from commit e4d3d89595057559b43952ef0ee284bcd7514dac)

Change-Id: I20695a0fa72b4b5d1e6d4fd727521ee11075c78d
Reviewed-on: https://chromium-review.googlesource.com/190570
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
CHROMIUM: ASoC: Intel: Use stream direction to access pcm_data

Originally the private data of sst-baytrail driver keeps
two copy of pcm_data and letting streams access it using the
id of cpu_dai.  This causes a problem when doing capture and
playback to the same device simultaneously, since these two
streams are sharing the same pcm_data.

Change to use stream direction as index to access the two
pcm_data, so that we can open two streams of different
direction on the same device concurrently.

BUG=chrome-os-partner:26908
TEST=Manual: Run aplay and arecord concurrently on rambi.
See no kernel crash.

Original-Change-Id: I084434faa165e440d8106d50e7533ff4e0b31ae8
Signed-off-by: Hsin-Yu Chao <hychao@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/190297
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
(cherry picked from commit d25161da8f2daa92285ac5b7630e777cdb37114e)
Signed-off-by: Benson Leung <bleung@chromium.org>

Change-Id: I4e4e45acc711fdbfe78cd9a4f7f38509cb07480d
Reviewed-on: https://chromium-review.googlesource.com/190572
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
CHROMIUM: DPTF kernel driver update to 8.0.9

Added support for UI tuning overrides.

Added primitive to set depth limit for P/T states and
	RAPL power limit.

Modified handling for suspend/resume events for S3.

Minor code clean-up and incremented the version to 8.0.9.

BUG=chrome-os-partner:25110,chrome-os-partner:26955
TEST=Manually tested
CQ-DEPEND=CL:191071

Change-Id: I60851d4021e43ffab8bdb01b7bc385d95ff3b41f
Signed-off-by: Brad Geltz <brad.geltz@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/190334
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
(cherry picked from commit a8e52e5e969e025ead36d0bb89ad7e414264d7c1)
Reviewed-on: https://chromium-review.googlesource.com/191090
Tested-by: Duncan Laurie <dlaurie@chromium.org>
CHROMIUM: ASoC: max98090 - Fix dmic table entries for 19.2MHz sysclk.

Fix the dmic divisor and compensation values for at 19.2 MHz sysclk.
Rambi uses 19.2MHz always so it's important they are correct.

BUG=chrome-os-partner:25855
TEST=Record audio from DMIC on rambi and listen for noise.

Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/187687
Reviewed-by: Benson Leung <bleung@chromium.org>
(cherry picked from commit 6f5a1d310042d870ac0b9b25de0f58f51cc200d2)

Change-Id: I48be92f0d53785c607b2a15cea6376d886582aa5
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/190526
Reviewed-by: Benson Leung <bleung@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
(cherry picked from commit eeab17d31a77be0fc2e8a3ec4f3ab7b7b2c53ca7)
Reviewed-on: https://chromium-review.googlesource.com/191234
CHROMIUM: ASoC: Intel: rambi: Fix max98090 master clock setting

Currently we set max98090 master clock to params_rate(params) * 256,
which should actually be BYT_PLAT_CLK_3_HZ, that is, 19.2MHz.

BUG=chrome-os-partner:25855,chrome-os-partner:26051
TEST=Record and play sound on rambi board. Check noise of recorded
  sound is reduced.

Signed-off-by: Cheng-Yi Chiang <cychiang@chromium.org>

[bleung : modified Cheng-Yi's change to reflect change to 19.2MHz
 in coreboot ]
Signed-off-by: Benson Leung <bleung@chromium.org>

Reviewed-on: https://chromium-review.googlesource.com/187586
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Dylan Reid <dgreid@chromium.org>
(cherry picked from commit e2b4cc974a017bb92ae1233408cd58ccf702ccbd)

Conflicts:

	sound/soc/mid-x86/byt_rambi_max98090.c

Change-Id: I33a3bc176c740896a575cf0bb15f50ffc36bbb90
Signed-off-by: Kevin Strasser <kevin.strasser@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/190527
Reviewed-by: Benson Leung <bleung@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
(cherry picked from commit bfe1d01ecb303eacd89e79606fdc5bd3005453e3)
Reviewed-on: https://chromium-review.googlesource.com/191236
Revert "CHROMIUM: Partial revert of 24929352481f085c5f85d4d4cbc919ddf106d381"

This reverts commit ca2784b79f2616468781635abe5cdb06bcab2aa0.

Signed-off-by: Brian J Lovin <brian.j.lovin@intel.com>

BUG=chrome-os-partner:26454
TEST=Manual, attach an HDMI monitor and sleep/resume the system.

Change-Id: I3ed4bd6c882d11d38516085475e035519e2b0cfe
Previous-Reviewed-on: https://chromium-review.googlesource.com/190298
(cherry picked from commit 18b46440d17dffd3a234dc3aa5c126c1539eeacd)
Reviewed-on: https://chromium-review.googlesource.com/191372
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
UPSTREAM: perf/x86: Add Silvermont (22nm Atom) support

Compared to old atom, Silvermont has offcore and has more events
that support PEBS.

Signed-off-by: Yan, Zheng <zheng.z.yan@intel.com>
Reviewed-by: Stephane Eranian <eranian@google.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1374138144-17278-2-git-send-email-zheng.z.yan@intel.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
(cherry picked from commit 1fa64180fbf7a33b7a30636a2f174a5cad68d48f)
Signed-off-by: Benson Leung <bleung@chromium.org>

BUG=chromium:355165
TEST=dmesg | grep Silvermont
Check that this is returned:
Performance Events: no PEBS fmt2+, 8-deep LBR, Silvermont events, Intel PMU driver.

perf stat -x, -a -d sleep 1
Check that for L1-dcache-load-misses, LLC-loads, and LLC-load-misses there are
counts, and not <not supported>.

Original-Change-Id: I8c4f7a05cef17f9db4d333209fbadd1b116e0605
Reviewed-on: https://chromium-review.googlesource.com/191170
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
(cherry picked from commit 1e178b84ba01494d7ee528b451ee9dda7dee0383)

Change-Id: Ie3188a2e24dfaf36f57678f5dee319c87194ae92
Reviewed-on: https://chromium-review.googlesource.com/191500
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
CHROMIUM: iwl7000: mac80211: fix suspend vs. authentication race

Since Stanislaw's patch removing the quiescing code, mac80211 had
a race regarding suspend vs. authentication: as cfg80211 doesn't
track authentication attempts, it can't abort them. Therefore the
attempts may be kept running while suspending, which can lead to
all kinds of issues, in at least some cases causing an error in
iwlmvm firmware.

Fix this by aborting the authentication attempt when suspending.

(iwlwifi commit a7c16e04bd3f21d7ced589f8faf1d9a78f3f8d2b)

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

BUG=chrome-os-partner:26697
TEST=didn't reproduce the SYSASSERT but a WARNING in this scenario,
the warning goes away with this patch and so should the SYSASSERT
(hitting the SYSASSERT is only due to races if we're past the WARN
point in the code)

Change-Id: I963cfb8effe7723408b26cad13571e1bc8022af6
Originally-Reviewed-on: https://chromium-review.googlesource.com/190988
Reviewed-on: https://chromium-review.googlesource.com/191948
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
CHROMIUM: iwl7000: bugfixes and small updates

Update iwl7000 to include bugfixes for various scenarios:
 * some APs don't like a long listen interval, reduce it
 * fix association to 20/40 MHz VHT networks
 * fix spurious station removal messages
 * fix scheduled scan restart during suspend/resume
 * fix some error paths (memory leaks or other missing cleanups)
 * make connection more stable by not disconnecting immediately
   on beacon loss

(iwlwifi commit 82aa548c936792d70260e056aaae2fa067baa0ba)
(cherry picked from commit a673ac7ddecc321033dab7b877c3d80487e21f14)

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Paul Stewart <pstew@chromium.org>

BUG=chrome-os-partner:26941
TEST=connect to 80 MHz AP with 40 MHz only CRDA database

Change-Id: Id195c501fed26331baf42cf2ad5eba412098afa8
Reviewed-on: https://chromium-review.googlesource.com/192165
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
CHROMIUM: iwl7000: delay enabling smart FIFO until after beacon RX

If we have no beacon data before association, delay smart FIFO
enablement until after we have this data.

Not doing so can cause association failures in extremely silent
environments (usually only a shielded box/room) as beacon RX is
not sent to the host immediately, and then the association time
event ends without the host receiving any beacon even though it
was on the air - it's just stuck on the FIFO.

(iwlwifi commit 5b60eb1ccb9316884873a6b9360283dbcd554df8)
(cherry picked from commit f61ec1f6369807c4052a434cae40409082eca3fa)

Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Paul Stewart <pstew@chromium.org>

BUG=chrome-os-partner:25861
TEST=connection/roaming tests in shielded box

Change-Id: I097e56b18cb74e7ffb6894c19a7f212a6185ffb9
Reviewed-on: https://chromium-review.googlesource.com/192166
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
CHROMIUM: iwl7000: enable LP XTAL to reduce power consumption

Enable the LP XTAL to avoid a hardware bug that leads to increased
power consumption when no firmware is loaded. The LP XTAL is disabled
by default after a device reset, but should be enabled.

Enable it after device reset to reduce power consumption.

(cherry picked from commit aa15067663af68181fa2cbda34c214328102be18)

Signed-off-by: Alexander Bondar <alexander.bondar@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Todd Broch <tbroch@chromium.org>
Signed-off-by: Paul Stewart <pstew@chromium.org>

BUG=chrome-os-partner:25592
TEST=measure device power consumption in S3

Change-Id: Ifbbee878eb0f2eadf6b1d053197cc0afe9ff248f
Reviewed-on: https://chromium-review.googlesource.com/192167
Reviewed-by: Paul Stewart <pstew@chromium.org>
Commit-Queue: Paul Stewart <pstew@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
CHROMIUM: Input: elan_i2c - Add retry mechanism.

When send initialize, disable, enable and sleep commands,
driver add retry machenism (3 times) to avoid host I2C occured
execption error (maybe tx timeout or no clock/data signal)
let TP no function.

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

Change-Id: I6d0285f3cdb716124980fa4df1c71f3c99c1df22
Previous-Reviewed-on: https://chromium-review.googlesource.com/190460
(cherry picked from commit 0bc80d15627ad5b4e19731b9165b6f2975b59ac0)
Reviewed-on: https://chromium-review.googlesource.com/192350
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
BACKPORT: drm/i915/hdmi: Read the HPD status before trying to read the EDID

If you unplug the hdmi connector slowly enough, the hotplug interrupt
fires but then the kernel code tries to read the EDID and succeeds
(because the connector is still half connected, the HPD pin is shorter
than the others, and DDC works). Since EDID succeeds it thinks the
monitor is still connected.

To prevent that, read the live HPD status in the hotplug handler before
trying to read the EDID.

v2: Rename the function to ibx_ (Chris Wilson)

BUG=chrome-os-partner:26363
TEST=unplug HDMI slowly, verify with xrandr display is disconnected \
when image on screen disappears
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=55372
Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
(cherry picked from commit b0ea7d37a8f63eeec5ae80b4a6403cfba01da02f)
Change-Id: I85ac910852322c6b139fa079f83e253530a68471
Signed-off-by: Dominik Behr <dbehr@chromium.org>
Previous-Reviewed-on: https://chromium-review.googlesource.com/191367
(cherry picked from commit a8bdc9bc04b52fe8dce9698a050c6b462707ac3a)
Reviewed-on: https://chromium-review.googlesource.com/192630
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
CHROMIUM : DPTF update to v8.0.10

Fixed:
        S3 Resume issue
        Kernel panic fix

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

Change-Id: I1b2076c694f92a5535a6d5f81b4816156a642e3d
Signed-off-by: Brad Geltz <brad.geltz@intel.com>
Reviewed-on: https://chromium-review.googlesource.com/192022
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-by: Derek Basehore <dbasehore@chromium.org>
Commit-Queue: Duncan Laurie <dlaurie@chromium.org>
(cherry picked from commit 1704f64a53dfb7ba2ac1e5a0c4e279511dfee4e0)
Reviewed-on: https://chromium-review.googlesource.com/192634
Tested-by: Duncan Laurie <dlaurie@chromium.org>
Revert "BACKPORT: drm/i915/hdmi: Read the HPD status before trying to read the EDID"

This reverts commit b8e0b4362c8ffb7fbcab2bd4270c50bdf7c9057b.

This was breaking the kernel build, apparently it has some non obvious dependencies that do not cause any cherry-pick conflicts. http://chromegw/i/chromeos_release/builders/expresso%20full%20release-R34-5500.B/builds/2/steps/BuildPackages/logs/stdio

Change-Id: I7084fbf725168b881196963255258118d489d5d7
Reviewed-on: https://chromium-review.googlesource.com/192650
Reviewed-by: Benson Leung <bleung@chromium.org>
Commit-Queue: Benson Leung <bleung@chromium.org>
Tested-by: Benson Leung <bleung@chromium.org>
Revert "CHROMIUM: uvcvideo: Handle status_start while status_stop is in progress."

This reverts commit 6915b4e1414246e483a80ea83e48aa5092b8d0d4.

Reverting and backporting race fixes from upstream instead.

Signed-off-by: Pawel Osciak <posciak@chromium.org>

BUG=chrome-os-partner:27361
TEST=camera capture

Change-Id: I9081f0c7a06788f2a53a151b650e74ec7a2c4963
Previous-Reviewed-on: https://chromium-review.googlesource.com/180233
(cherry picked from commit c142a52f9e7a8ef62b4e2bcb4522a3ab952ba801)
Previous-Reviewed-on: https://chromium-review.googlesource.com/192024
(cherry picked from commit 0dfed561d0cc5344c0134311b07e1d2a223c9d88)
Reviewed-on: https://chromium-review.googlesource.com/192690
Reviewed-by: Pawel Osciak <posciak@chromium.org>
Tested-by: Pawel Osciak <posciak@chromium.org>
UPSTREAM: [media] uvcvideo: Fix open/close race condition

Maintaining the users count using an atomic variable makes sure that
access to the counter won't be racy, but doesn't serialize access to the
operations protected by the counter. This creates a race condition that
could result in the status URB being submitted multiple times.
Use a mutex to protect the users count and serialize access to the
status start and stop operations.

Reported-by: Shawn Nematbakhsh <shawnn@chromium.org>
Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Signed-off-by: Pawel Osciak <posciak@chromium.org>
(cherry picked from commit 17706f5653a90ff277b5b36c2eb60ff872df5e7a)

BUG=chrome-os-partner:27361
TEST=Build, test camera capture

Change-Id: Ica6cc935960d9c6b796ab953f9b4e45551c7979c
Previous-Reviewed-on: https://chromium-review.googlesource.com/180236
(cherry picked from commit 11fc118b9fdb6a9c7b98c5291c21a4b34056e150)
Previous-Reviewed-on: https://chromium-review.googlesource.com/192025
(cherry picked from commit cb0bfbe3a88aeb5ffc7005f9d5fc65e7b71b676d)
Reviewed-on: https://chromium-review.googlesource.com/192666
Reviewed-by: Pawel Osciak <posciak@chromium.org>
Tested-by: Pawel Osciak <posciak@chromium.org>