Merge branch 'vexpress-dt-v3.3-rc4' of git://git.linaro.org/people/pawelmoll/linux into next/dt

!Iinclude/linux/device.h

     </sect1>

     <sect1><title>Device Drivers Base</title>

!Idrivers/base/init.c

!Edrivers/base/driver.c

!Edrivers/base/core.c

!Edrivers/base/syscore.c

!Edrivers/base/class.c

!Idrivers/base/node.c

!Edrivers/base/firmware_class.c

!Edrivers/base/transport_class.c

<!-- Cannot be included, because

     exceed allowed 44 characters maximum

X!Edrivers/base/attribute_container.c

-->

!Edrivers/base/sys.c

!Edrivers/base/dd.c

<!--

X!Edrivers/base/interface.c

-->

!Iinclude/linux/platform_device.h

!Edrivers/base/platform.c

!Edrivers/base/bus.c

     </sect1>

     <sect1><title>Device Drivers DMA Management</title>

!Edrivers/base/dma-buf.c

!Edrivers/base/dma-coherent.c

!Edrivers/base/dma-mapping.c

     </sect1>

     <sect1><title>Device Drivers Power Management</title>

!Edrivers/base/power/main.c

  <chapter id="uart16x50">

     <title>16x50 UART Driver</title>

!Edrivers/tty/serial/serial_core.c

!Edrivers/tty/serial/8250.c

!Edrivers/tty/serial/8250/8250.c

  </chapter>

  <chapter id="fbdev">

ARM Versatile Express boards family

-----------------------------------

ARM's Versatile Express platform consists of a motherboard and one

or more daughterboards (tiles). The motherboard provides a set of

peripherals. Processor and RAM "live" on the tiles.

The motherboard and each core tile should be described by a separate

Device Tree source file, with the tile's description including

the motherboard file using a /include/ directive. As the motherboard

can be initialized in one of two different configurations ("memory

maps"), care must be taken to include the correct one.

Required properties in the root node:

- compatible value:

	compatible = "arm,vexpress,<model>", "arm,vexpress";

  where <model> is the full tile model name (as used in the tile's

    Technical Reference Manual), eg.:

    - for Coretile Express A5x2 (V2P-CA5s):

	compatible = "arm,vexpress,v2p-ca5s", "arm,vexpress";

    - for Coretile Express A9x4 (V2P-CA9):

	compatible = "arm,vexpress,v2p-ca9", "arm,vexpress";

  If a tile comes in several variants or can be used in more then one

  configuration, the compatible value should be:

	compatible = "arm,vexpress,<model>,<variant>", \

				"arm,vexpress,<model>", "arm,vexpress";

  eg:

    - Coretile Express A15x2 (V2P-CA15) with Tech Chip 1:

	compatible = "arm,vexpress,v2p-ca15,tc1", \

				"arm,vexpress,v2p-ca15", "arm,vexpress";

    - LogicTile Express 13MG (V2F-2XV6) running Cortex-A7 (3 cores) SMM:

	compatible = "arm,vexpress,v2f-2xv6,ca7x3", \

				"arm,vexpress,v2f-2xv6", "arm,vexpress";

Optional properties in the root node:

- tile model name (use name from the tile's Technical Reference

  Manual, eg. "V2P-CA5s")

	model = "<model>";

- tile's HBI number (unique ARM's board model ID, visible on the

  PCB's silkscreen) in hexadecimal transcription:

	arm,hbi = <0xhbi>

  eg:

  - for Coretile Express A5x2 (V2P-CA5s) HBI-0191:

	arm,hbi = <0x191>;

  - Coretile Express A9x4 (V2P-CA9) HBI-0225:

	arm,hbi = <0x225>;

Top-level standard "cpus" node is required. It must contain a node

with device_type = "cpu" property for every available core, eg.:

	cpus {

		#address-cells = <1>;

		#size-cells = <0>;

		cpu@0 {

			device_type = "cpu";

			compatible = "arm,cortex-a5";

			reg = <0>;

		};

	};

The motherboard description file provides a single "motherboard" node

using 2 address cells corresponding to the Static Memory Bus used

between the motherboard and the tile. The first cell defines the Chip

Select (CS) line number, the second cell address offset within the CS.

All interrupt lines between the motherboard and the tile are active

high and are described using single cell.

Optional properties of the "motherboard" node:

- motherboard's memory map variant:

	arm,v2m-memory-map = "<name>";

  where name is one of:

  - "rs1" - for RS1 map (i.a. peripherals on CS3); this map is also

            referred to as "ARM Cortex-A Series memory map":

	arm,v2m-memory-map = "rs1";

  When this property is missing, the motherboard is using the original

  memory map (also known as the "Legacy memory map", primarily used

  with the original CoreTile Express A9x4) with peripherals on CS7.

Motherboard .dtsi files provide a set of labelled peripherals that

can be used to obtain required phandle in the tile's "aliases" node:

- UARTs, note that the numbers correspond to the physical connectors

  on the motherboard's back panel:

	v2m_serial0, v2m_serial1, v2m_serial2 and v2m_serial3

- I2C controllers:

	v2m_i2c_dvi and v2m_i2c_pcie

- SP804 timers:

	v2m_timer01 and v2m_timer23

Current Linux implementation requires a "arm,v2m_timer" alias

pointing at one of the motherboard's SP804 timers, if it is to be

used as the system timer. This alias should be defined in the

motherboard files.

The tile description must define "ranges", "interrupt-map-mask" and

"interrupt-map" properties to translate the motherboard's address

and interrupt space into one used by the tile's processor.

Abbreviated example:

/dts-v1/;

/ {

	model = "V2P-CA5s";

	arm,hbi = <0x225>;

	compatible = "arm,vexpress-v2p-ca5s", "arm,vexpress";

	interrupt-parent = <&gic>;

	#address-cells = <1>;

	#size-cells = <1>;

	chosen { };

	aliases {

		serial0 = &v2m_serial0;

	};

	cpus {

		#address-cells = <1>;

		#size-cells = <0>;

		cpu@0 {

			device_type = "cpu";

			compatible = "arm,cortex-a5";

			reg = <0>;

		};

	};

	gic: interrupt-controller@2c001000 {

		compatible = "arm,cortex-a9-gic";

		#interrupt-cells = <3>;

		#address-cells = <0>;

		interrupt-controller;

		reg = <0x2c001000 0x1000>,

		      <0x2c000100 0x100>;

	};

	motherboard {

		/* CS0 is visible at 0x08000000 */

		ranges = <0 0 0x08000000 0x04000000>;

		interrupt-map-mask = <0 0 63>;

		/* Active high IRQ 0 is connected to GIC's SPI0 */

		interrupt-map = <0 0 0 &gic 0 0 4>;

	};

};

/include/ "vexpress-v2m-rs1.dtsi"

class/input/event*/device/capabilities/, and the properties of a device are

provided in class/input/event*/device/properties.

Types:

==========

Types are groupings of codes under a logical input construct. Each type has a

set of applicable codes to be used in generating events. See the Codes section

for details on valid codes for each type.

Event types:

===========

Event types are groupings of codes under a logical input construct. Each

type has a set of applicable codes to be used in generating events. See the

Codes section for details on valid codes for each type.

* EV_SYN:

  - Used as markers to separate events. Events may be separated in time or in

* EV_FF_STATUS:

  - Used to receive force feedback device status.

Codes:

==========

Codes define the precise type of event.

Event codes:

===========

Event codes define the precise type of event.

EV_SYN:

----------

EV_PWR events are a special type of event used specifically for power

mangement. Its usage is not well defined. To be addressed later.

Device properties:

=================

Normally, userspace sets up an input device based on the data it emits,

i.e., the event types. In the case of two devices emitting the same event

types, additional information can be provided in the form of device

properties.

INPUT_PROP_DIRECT + INPUT_PROP_POINTER:

--------------------------------------

The INPUT_PROP_DIRECT property indicates that device coordinates should be

directly mapped to screen coordinates (not taking into account trivial

transformations, such as scaling, flipping and rotating). Non-direct input

devices require non-trivial transformation, such as absolute to relative

transformation for touchpads. Typical direct input devices: touchscreens,

drawing tablets; non-direct devices: touchpads, mice.

The INPUT_PROP_POINTER property indicates that the device is not transposed

on the screen and thus requires use of an on-screen pointer to trace user's

movements.  Typical pointer devices: touchpads, tablets, mice; non-pointer

device: touchscreen.

If neither INPUT_PROP_DIRECT or INPUT_PROP_POINTER are set, the property is

considered undefined and the device type should be deduced in the

traditional way, using emitted event types.

INPUT_PROP_BUTTONPAD:

--------------------

For touchpads where the button is placed beneath the surface, such that

pressing down on the pad causes a button click, this property should be

set. Common in clickpad notebooks and macbooks from 2009 and onwards.

Originally, the buttonpad property was coded into the bcm5974 driver

version field under the name integrated button. For backwards

compatibility, both methods need to be checked in userspace.

INPUT_PROP_SEMI_MT:

------------------

Some touchpads, most common between 2008 and 2011, can detect the presence

of multiple contacts without resolving the individual positions; only the

number of contacts and a rectangular shape is known. For such

touchpads, the semi-mt property should be set.

Depending on the device, the rectangle may enclose all touches, like a

bounding box, or just some of them, for instance the two most recent

touches. The diversity makes the rectangle of limited use, but some

gestures can normally be extracted from it.

If INPUT_PROP_SEMI_MT is not set, the device is assumed to be a true MT

device.

Guidelines:

==========

The guidelines below ensure proper single-touch and multi-finger functionality.

BTN_{MOUSE,LEFT,MIDDLE,RIGHT} must not be reported as the result of touch

contact. BTN_TOOL_<name> events should be reported where possible.

For new hardware, INPUT_PROP_DIRECT should be set.

Trackpads:

----------

Legacy trackpads that only provide relative position information must report

on the trackpad. Where multi-finger support is available, BTN_TOOL_<name> should

be used to report the number of touches active on the trackpad.

For new hardware, INPUT_PROP_POINTER should be set.

Tablets:

----------

BTN_TOOL_<name> events must be reported when a stylus or other tool is active on

BTN_{0,1,2,etc} are good generic codes for unlabeled buttons. Do not use

meaningful buttons, like BTN_FORWARD, unless the button is labeled for that

purpose on the device.

For new hardware, both INPUT_PROP_DIRECT and INPUT_PROP_POINTER should be set.

        instead of using the one provided by the hardware.

 512 - A kernel warning has occurred.

1024 - A module from drivers/staging was loaded.

2048 - The system is working around a severe firmware bug.

4096 - An out-of-tree module has been loaded.

==============================================================

F:	drivers/net/ethernet/realtek/r8169.c

8250/16?50 (AND CLONE UARTS) SERIAL DRIVER

M:	Greg Kroah-Hartman <gregkh@suse.de>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

L:	linux-serial@vger.kernel.org

W:	http://serial.sourceforge.net

S:	Maintained

F:	arch/arm/mach-imx/

F:	arch/arm/plat-mxc/

ARM/FREESCALE IMX51

M:	Amit Kucheria <amit.kucheria@canonical.com>

L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)

S:	Maintained

F:	arch/arm/mach-mx5/

ARM/FREESCALE IMX6

M:	Shawn Guo <shawn.guo@linaro.org>

L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)

CHAR and MISC DRIVERS

M:	Arnd Bergmann <arnd@arndb.de>

M:	Greg Kroah-Hartman <greg@kroah.com>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

T:	git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git

S:	Maintained

S:	Supported

F:	drivers/char/*

F:	drivers/misc/*

DOCUMENTATION

M:	Randy Dunlap <rdunlap@xenotime.net>

L:	linux-doc@vger.kernel.org

T:	quilt http://userweb.kernel.org/~rdunlap/kernel-doc-patches/current/

T:	quilt http://xenotime.net/kernel-doc-patches/current/

S:	Maintained

F:	Documentation/

F:	Documentation/blockdev/drbd/

DRIVER CORE, KOBJECTS, DEBUGFS AND SYSFS

M:	Greg Kroah-Hartman <gregkh@suse.de>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

T:	git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core-2.6.git

S:	Supported

F:	Documentation/kobject.txt

F:	net/ieee802154/

F:	drivers/ieee802154/

IIO SUBSYSTEM AND DRIVERS

M:	Jonathan Cameron <jic23@cam.ac.uk>

L:	linux-iio@vger.kernel.org

S:	Maintained

F:	drivers/staging/iio/

IKANOS/ADI EAGLE ADSL USB DRIVER

M:	Matthieu Castet <castet.matthieu@free.fr>

M:	Stanislaw Gruszka <stf_xl@wp.pl>

L:	lguest@lists.ozlabs.org

W:	http://lguest.ozlabs.org/

S:	Odd Fixes

F:	Documentation/virtual/lguest/

F:	arch/x86/include/asm/lguest*.h

F:	arch/x86/lguest/

F:	drivers/lguest/

F:	include/linux/lguest*.h

F:	arch/x86/include/asm/lguest*.h

F:	tools/lguest/

LINUX FOR IBM pSERIES (RS/6000)

M:	Paul Mackerras <paulus@au.ibm.com>

W:	http://www.linux-ntfs.org/content/view/19/37/

S:	Maintained

F:	Documentation/ldm.txt

F:	fs/partitions/ldm.*

F:	block/partitions/ldm.*

LogFS

M:	Joern Engel <joern@logfs.org>

S:	Supported

F:	arch/s390/

F:	drivers/s390/

F:	fs/partitions/ibm.c

F:	block/partitions/ibm.c

F:	Documentation/s390/

F:	Documentation/DocBook/s390*

F:	arch/alpha/kernel/srm_env.c

STABLE BRANCH

M:	Greg Kroah-Hartman <greg@kroah.com>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

L:	stable@vger.kernel.org

S:	Maintained

S:	Supported

STAGING SUBSYSTEM

M:	Greg Kroah-Hartman <gregkh@suse.de>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

T:	git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git

L:	devel@driverdev.osuosl.org

S:	Maintained

S:	Supported

F:	drivers/staging/

STAGING - AGERE HERMES II and II.5 WIRELESS DRIVERS

S:	Odd Fixes

F:	drivers/staging/tidspbridge/

STAGING - TRIDENT TVMASTER TMxxxx USB VIDEO CAPTURE DRIVERS

L:	linux-media@vger.kernel.org

S:	Odd Fixes

F:	drivers/staging/tm6000/

STAGING - USB ENE SM/MS CARD READER DRIVER

M:	Al Cho <acho@novell.com>

S:	Odd Fixes

K:	^Subject:.*(?i)trivial

TTY LAYER

M:	Greg Kroah-Hartman <gregkh@suse.de>

S:	Maintained

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

S:	Supported

T:	git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty-2.6.git

F:	drivers/tty/

F:	drivers/tty/serial/serial_core.c

F:	drivers/usb/serial/digi_acceleport.c

USB SERIAL DRIVER

M:	Greg Kroah-Hartman <gregkh@suse.de>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

L:	linux-usb@vger.kernel.org

S:	Supported

F:	Documentation/usb/usb-serial.txt

F:	drivers/usb/serial/empeg.c

USB SERIAL KEYSPAN DRIVER

M:	Greg Kroah-Hartman <greg@kroah.com>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

L:	linux-usb@vger.kernel.org

W:	http://www.kroah.com/linux/

S:	Maintained

F:	drivers/usb/serial/*keyspan*

F:	drivers/media/video/sn9c102/

USB SUBSYSTEM

M:	Greg Kroah-Hartman <gregkh@suse.de>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

L:	linux-usb@vger.kernel.org

W:	http://www.linux-usb.org

T:	git git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6.git

USERSPACE I/O (UIO)

M:	"Hans J. Koch" <hjk@hansjkoch.de>

M:	Greg Kroah-Hartman <gregkh@suse.de>

M:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>

S:	Maintained

F:	Documentation/DocBook/uio-howto.tmpl

F:	drivers/uio/