Merge 3.13-rc4 into staging-next.

S: Stanford, California 94305

S: USA

N: Carlos Chinea

E: carlos.chinea@nokia.com

E: cch.devel@gmail.com

D: Author of HSI Subsystem

N: Randolph Chung

E: tausq@debian.org

D: Linux/PA-RISC hacker

format. For the single-planar API, applications must set <structfield> plane

</structfield> to zero.  Additional flags may be posted in the <structfield>

flags </structfield> field.  Refer to a manual for open() for details.

Currently only O_CLOEXEC is supported.  All other fields must be set to zero.

Currently only O_CLOEXEC, O_RDONLY, O_WRONLY, and O_RDWR are supported.  All

other fields must be set to zero.

In the case of multi-planar API, every plane is exported separately using

multiple <constant> VIDIOC_EXPBUF </constant> calls. </para>

	    <entry>__u32</entry>

	    <entry><structfield>flags</structfield></entry>

	    <entry>Flags for the newly created file, currently only <constant>

O_CLOEXEC </constant> is supported, refer to the manual of open() for more

details.</entry>

O_CLOEXEC </constant>, <constant>O_RDONLY</constant>, <constant>O_WRONLY

</constant>, and <constant>O_RDWR</constant> are supported, refer to the manual

of open() for more details.</entry>

	  </row>

	  <row>

	    <entry>__s32</entry>

 (4) Diff the index keys of two objects.

	int (*diff_objects)(const void *a, const void *b);

	int (*diff_objects)(const void *object, const void *index_key);

     Return the bit position at which the index keys of two objects differ or

     -1 if they are the same.

     Return the bit position at which the index key of the specified object

     differs from the given index key or -1 if they are the same.

 (5) Free an object.

Invalidation is removing an entry from the cache without writing it

back.  Cache blocks can be invalidated via the invalidate_cblocks

message, which takes an arbitrary number of cblock ranges.  Each cblock

must be expressed as a decimal value, in the future a variant message

that takes cblock ranges expressed in hexidecimal may be needed to

better support efficient invalidation of larger caches.  The cache must

be in passthrough mode when invalidate_cblocks is used.

range's end value is "one past the end", meaning 5-10 expresses a range

of values from 5 to 9.  Each cblock must be expressed as a decimal

value, in the future a variant message that takes cblock ranges

expressed in hexidecimal may be needed to better support efficient

invalidation of larger caches.  The cache must be in passthrough mode

when invalidate_cblocks is used.

   invalidate_cblocks [<cblock>|<cblock begin>-<cblock end>]*

Required properties:

- compatible : Should be "ti,omap3-mpu" for OMAP3

               Should be "ti,omap4-mpu" for OMAP4

	       Should be "ti,omap5-mpu" for OMAP5

- ti,hwmods: "mpu"

Examples:

- For an OMAP5 SMP system:

mpu {

    compatible = "ti,omap5-mpu";

    ti,hwmods = "mpu"

};

- For an OMAP4 SMP system:

mpu {