video: mxc_hdmi: Use color space converter to limit output color range.

This patch enhances commit:9119f4982209edf12dee44240bcfaa52fba2b4d3 to change
the actual RGB color range itself. The previous solution would only allow to
change what is reported to the sink via AVI info frame. Since overriding the
color range is only supported by devices compliant to CEA-861D (i.e. HDMI1.3),
the previous method will fail on some TVs (mostly Sony Bravia). This patch
implements the following behavior:

mode 'full':     range 0..255 indicated via AVI info frame Q1,Q0 = 1,0
mode 'limited':  range 16..235 indicated via AVI info frame Q1,Q0 = 0,1
mode 'default':  range 16..235 for CEA modes, range 0..255 for non-CEA Q1,Q0 = 0,0

In DVI mode, the range is always 0..255 and the color space converter is bypassed.

Signed-off-by: Rudi <r.ihle@s-t.de>
video: mxc_hdmi: Use symbolic constant instead of 0.

Signed-off-by: Rudi <r.ihle@s-t.de>
Merge pull request #15 from warped-rudi/v3.14-mx6-colorspace

Enable video output using limited color range
ASOC: fsl_ssi: remove DMA_RESIDUE flag

This has been fixed in the SDMA driver so this flag is no longer needed.
pcie: imx6: Make no-msi a device-tree property

Currently MSI is not 100% working in the driver.  Rather than
deal with kernel config options or the kernel cmdline that
the user/distribution has to set, we flag it in the
device-tree.

This is the equivalent of setting pci=nomsi on the kernel
commandline.
dts: hummingboard: Revert unrelated dt entries

These were unfinished patches that mistakenly got included
with the no-msi patch.  Remove them.
Support for gpio connected ir senders/receivers

This module allows users to use a GPIO connected
IR receiver and/or sender with LIRC. The module
uses the sysfs gpio kernel functions to interact
with the gpio. You can configure the module from
inside the device tree like this:

lirc_gpio {
	compatible = "lirc_gpio";
	gpios = <&gpio3 6 1 &gpio3 7 2>;
	pinctrl-names = "default";
	pinctrl-0 = <&pinctrl_hummingboard_gpio3_6>;
	pinctrl-1 = <&pinctrl_hummingboard_gpio3_7>;
	linux,sense = <-1>;
	linux,softcarrier = <1>;
	linux,validgpios = <1 73 72 71 70 194 195 67>;
};

It should therefor work on all platforms.
Added newline at end of file
Merge pull request #18 from CurlyMoo/lirc_gpio

Support for gpio connected ir senders/receivers
Merge pull request #8 from linux4kix/linux-linaro-lsk-v3.14-mx6

Various small fixups
brcmfmac: kernel oops on wrong ifidx

When calling brcmf_rx_frame() ifidx might not get set and return non zero value.
Due to that ifp must not be set without proper ifidx otherwise it might get
a wrong pointer (since ifidx is not set correctly) causing ifp->ndev to access
an unmapped memory.

The fix initializes ifp to null and in case it doesn't get properly initialized
the skb will get deallocated in brcmu_pkt_buf_free_skb(skb) afterwards.

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
Merge pull request #10 from linux4kix/linux-linaro-lsk-v3.14-mx6

brcmfmac: kernel oops on wrong ifidx
arm: cubox-i and hummingboard defconfig

When CONFIG_JUMP_LABEL=y networking bridge code breaks.
This was observed on HummingBoard when creating a bridge between wlan0
and eth0.

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>
Merge pull request #11 from linux4kix/linux-linaro-lsk-v3.14-mx6

arm: cubox-i and hummingboard defconfig
brcmfmac: deal with NL80211_CHANWIDTH_20_NOHT setting

The driver can get a channel definition with bandwidth set to
NL80211_CHANWIDTH_20_NOHT. This was no handled in brcmfmac which
results in a warning splat. One scenario in which this is observed
was when running hostapd with configuration 'hw_mode=g'.

Cc: Jon Nettleton <jon.nettleton@gmail.com>
Signed-off-by: Arend van Spriel <arend@broadcom.com>
Merge pull request #12 from linux4kix/linux-linaro-lsk-v3.14-mx6

brcmfmac: deal with NL80211_CHANWIDTH_20_NOHT setting
add audio and wireless firmware
add fc20 .config