GPU: Backport from caf-jb_2.5.5

Change-Id: I40b383b9bab36bffbb14cfe38e6c4e75ffc43674
msm8660: update header export
vigor: enable ION

Change-Id: If67dd6ec4d953ac9945987286c812f18d9cace8b
clk: add helper functions clk_prepare_enable and clk_disable_unprepare

It's for migrating to generic clk framework API.

The helper functions  help cases clk_enable/clk_disable is used
in non-atomic context.
For example, Call clk_enable in probe and clk_disable in remove.

Signed-off-by: Richard Zhao <richard.zhao@linaro.org>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Cc: Russell King <linux@arm.linux.org.uk>
Acked-by: Marek Vasut <marek.vasut@gmail.com>
Don't treat warnings as errors
drivers: usb: gadget: Backport from caf-jb_mr1_chocolate

Change-Id: Ida5fd7b4f3ab48fee26a5090b39efad61c1f82b2
disable CONFIG_DEBUG_FS and open the pandora's box
While fixing the mess spilled out of the box,
all code changes are my fault, don't blame anyone else :)
To the devs who made this mess:
A kernel option is an option, you must know that it can be disabled.
If you need a kernel option, declare a dependence in one of the Kconfig files.
Otherwise, put your "professional" coding together
and handle the optional kernel features properly.
DEBUG_FS is not your scratch pad.
Sheesh!
-mrg666

Change-Id: I1f3aabd0f50f7f3287209eec1c4af04bfd3174aa
vigor: fix compile

Change-Id: I333123a448b186ebc47d1a4cc703c4ddcaabc481
update vidc to jb_chocolate

Change-Id: Ib27063ae6c3b2ebf7e268a439093d459208279ef