Merge branch 'omap/dt' into next/drivers

	- semantics and behavior of local atomic operations.

lockdep-design.txt

	- documentation on the runtime locking correctness validator.

lockup-watchdogs.txt

	- info on soft and hard lockup detectors (aka nmi_watchdog).

logo.gif

	- full colour GIF image of Linux logo (penguin - Tux).

logo.txt

	- directory with information on the NetLabel subsystem.

networking/

	- directory with info on various aspects of networking with Linux.

nmi_watchdog.txt

	- info on NMI watchdog for SMP systems.

nommu-mmap.txt

	- documentation about no-mmu memory mapping support.

numastat.txt

  shared across all System Controller members.

TC/TCLIB Timer required properties:

- compatible: Should be "atmel,<chip>-pit".

- compatible: Should be "atmel,<chip>-tcb".

  <chip> can be "at91rm9200" or "at91sam9x5"

- reg: Should contain registers location and length

- interrupts: Should contain all interrupts for the TC block

OMAP Counter-32K bindings

Required properties:

- compatible:	Must be "ti,omap-counter32k" for OMAP controllers

- reg:		Contains timer register address range (base address and length)

- ti,hwmods:	Name of the hwmod associated to the counter, which is typically

		"counter_32k"

Example:

counter32k: counter@4a304000 {

	compatible = "ti,omap-counter32k";

	reg = <0x4a304000 0x20>;

	ti,hwmods = "counter_32k";

};

OMAP Timer bindings

Required properties:

- compatible:		Must be "ti,omap2-timer" for OMAP2+ controllers.

- reg:			Contains timer register address range (base address and

			length).

- interrupts: 		Contains the interrupt information for the timer. The

			format is being dependent on which interrupt controller

			the OMAP device uses.

- ti,hwmods:		Name of the hwmod associated to the timer, "timer<X>",

			where <X> is the instance number of the timer from the

			HW spec.

Optional properties:

- ti,timer-alwon:	Indicates the timer is in an alway-on power domain.

- ti,timer-dsp:		Indicates the timer can interrupt the on-chip DSP in

			addition to the ARM CPU.

- ti,timer-pwm: 	Indicates the timer can generate a PWM output.

- ti,timer-secure: 	Indicates the timer is reserved on a secure OMAP device

			and therefore cannot be used by the kernel.

Example:

timer12: timer@48304000 {

	compatible = "ti,omap2-timer";

	reg = <0x48304000 0x400>;

	interrupts = <95>;

	ti,hwmods = "timer12"

	ti,timer-alwon;

	ti,timer-secure;

};

properties:

- compatible : Should be "ti,omap-ocp2scp"

- reg : Address and length of the register set for the device

- #address-cells, #size-cells : Must be present if the device has sub-nodes

- ranges : the child address space are mapped 1:1 onto the parent address space

- ti,hwmods : must be "ocp2scp_usb_phy"

Sub-nodes:

All the devices connected to ocp2scp are described using sub-node to ocp2scp

ocp2scp@4a0ad000 {

	compatible = "ti,omap-ocp2scp";

	reg = <0x4a0ad000 0x1f>;

	#address-cells = <1>;

	#size-cells = <1>;

	ranges;

	ti,hwmods = "ocp2scp_usb_phy";

	subnode1 {

	...

	};

	subnode2 {

	...

	};

};