Subject: [PATCH 1/3] arm/dt: Add Pandaboard devicetree support

Enable basic device tree support on Pandaboard

Signed-off-by: Grant Likely <grant.likely@linaro.org>
config introduce omap4_defconfig

Signed-off-by: Andy Green <andy.green@linaro.org>
config TPS62361

Signed-off-by: Andy Green <andy.green@linaro.org>
introduce linaro test status

Signed-off-by: Andy Green <andy.green@linaro.org>
omap dss2 dont die on null driver for display

Signed-off-by: Andy Green <andy.green@linaro.org>
config remove libertas

Signed-off-by: Andy Green <andy.green@linaro.org>
DRM: solve __linux__ missing on some toolchains

An ifdef in drm.h expects to be compiled with full-fledged Linux
toolchain, but it's common to compile kernel with just bare-metal
toolchain which doesn't define __linux__. So, also add __KERNEL__
check.

Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
kbuild: Introduce -D__linux_kernel__ to indicate building of the Linux kernel

The __linux__ macro is defined by gcc to indicate that the compiler
is configured for a target running Linux.  However, it also makes
sense to use a bare-metal-targeted compiler to build the kernel,
particularly when cross-building.  Such compilers won't (and
shouldn't) define __linux__.

Code which tests for __linux__ should only appear in code which
will never be built into the kernel, such as build-time tools and
some parts of userspace headers.

In general, it is reasonable for Linux to share some source code
with other projects which could predictably be using __KERNEL__ for
their own purposes.  This patch introduces a separate macro
__linux_kernel__ to help to disambiguate such cases.

Signed-off-by: Dave Martin <dave.martin@linaro.org>
acpi: avoid #ifdef __linux__ misuse in exportable headers

acpi: avoid #ifdef __linux__ misuse in exportable headers

Signed-off-by: Dave Martin <dave.martin@linaro.org>
coda: avoid #ifdef __linux__ misuse in exportable headers

Signed-off-by: Dave Martin <dave.martin@linaro.org>
ext2: avoid #ifdef __linux__ misuse in exportable headers

Signed-off-by: Dave Martin <dave.martin@linaro.org>
config PERF_EVENTS

Signed-off-by: Andy Green <andy.green@linaro.org>
config remove OMAP3 support add HW_PERF_EVENTS

HW_PERF_EVENTS is dependent on !ARCH_OMAP3 unfortunately...

Signed-off-by: Andy Green <andy.green@linaro.org>
omap: id: add chip id recognition for omap4430 es2.3

allow for the omap4430 es2.3 revision to be recognized in the
omap4_check_revision() function.

most aspects of all omap4430 es2.x versions are identical, however
a number of small variations such as default pullup or pulldown
resistor configurations vary between revisions.

detailed information on silicon errata for omap4430 revisions can
be found at http://focus.ti.com/pdfs/wtbu/swpz009D.pdf

Signed-off-by: David Anders <x0132446@ti.com>
scripts/package/builddeb: Support cross-building

Pay attention to the cross-building environment variables
used in the rest of the kernel build, so that you can
successfully make deb-pkg while cross-building.
smsc95xx: Add module parameter to override MAC address

Define a new module parameter 'macaddr' to override the MAC address
fetched either from eeprom, or randomly generated.

The expected MAC address shall be in the 01:23:45:67:89:AB format.

Signed-off-by: Sebastien Jan <s-jan@ti.com>
OMAP4: Redefine mandatory barriers for OMAP to include interconnect barriers.

On OMAP4 SOC intecronnects has many write buffers in the async bridges
and they can be drained only with stongly ordered accesses.

There are two ports as below from MPU and both needs to be drained.
	- MPU --> L3 T2ASYNC FIFO
	- MPU --> DDR T2ASYNC FIFO

Without the interconnect barriers, many issues have been observed
leading to system freeze, CPU deadlocks, random crashes with
register accesses, synchronization loss on initiators operating
on both interconnect port simultaneously.

Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Richard Woodruff <r-woodruff2@ti.com>
OMAP4: PM: Use custom omap_do_wfi() for suspend and default idle.

The omap_do_wfi() incorporates interconnect barriers to meet
OMAP44XX interconnect ordering requirements. Make use of this
hook in default idle, suspend and CPU hot-plug paths.

Without the interconnect barriers, many issues have been observed
leading to system freeze, CPU deadlocks, random crashes with
register accesses, synchronization loss on initiators operating
on both interconnect port simultaneously.

Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Kevin Hilman <khilman@ti.com>
OMAP4: Remove un-used do_wfi() macro.

With OMAP4 suspend, idle and hotplug series, we no longer need
do_wfi() macro.

Remove the same.

Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Kevin Hilman <khilman@ti.com>
OMAP4: Use WARN_ON() instead of BUG_ON() with graceful exit

OMAP4 L2X0 initialisation code uses BUG_ON() for the ioremap()
failure scenarios.

Use WARN_ON() instead and allow graceful function exits.

This was suggsted by Kevin Hilman <khilman@ti.com> during
OMAP4 PM code review.

Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Kevin Hilman <khilman@ti.com>