Merge branch 'for-next/usb'

Merge branch 'for-next/socfpga'

Merge branch 'for-next/restart'

Merge branch 'for-next/param'

Merge branch 'for-next/of_path'

Merge branch 'for-next/mtd'

Merge branch 'for-next/misc'

Merge branch 'for-next/login'

Merge branch 'for-next/imx'

Merge branch 'for-next/gpio'

Merge branch 'for-next/fb-imx-ipu-v3'

Merge branch 'for-next/fb'

Merge branch 'for-next/arm-l2x0'

Release v2015.09.0 ...

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: do not ignore data aborts initially ...

arm_ignore_data_abort can be set to nonzero to ignore data aborts. The
default should be not to ignore data aborts. Fix this.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: dts: directly point to partitions in the barebox,environment binding ...

We can now directly point to the partitions in the barebox,environment
binding. Convert some boards over to it.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

of_path: Allow pointing directly to the partition ...

We could only point to partitions in the device tree by using
&norflash, "partname:barebox-environment". Allow to point to the
partition directly without having to parse the partition labels.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

cdev: Add function to find cdev by device_node ...

This adds a device_node member to struct cdev and a function
to find a cdev by device_node.
This also removes the setting of cdev->dev->device_node in
the of partition parser. We must not set the device since it
may not refer to a partition but to a whole device with partitions.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

spi: i.MX: optimize transfers for ECSPI v2.3 ...

Instead of writing one word to the txfifo and then wait until
one is received in the rxfifo we can write until the txfifos
are not full and read as long the rxfifos contain data. This
makes transfers for the m25p80 driver around 7 times faster
here.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

spi: i.MX: create SoC specific transfer functions ...

There are SoC specific ways to optimize transfers. Make the way free
to implement these by creating SoC specific transfer functions.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

spi: i.MX: use start mode control bit ...

The i.MX SPI controller in version 2.3 can immediately start a transfer
when the txfifo is written to. In this mode we no longer have to trigger
the transfer with the xch bit which makes the code a bit simpler.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

commands: ubiformat: Document -y option ...

This was missing in the help text.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

boot command: Allow to enable watchdog ...

Enabling the watchdog before booting the kernel is a common usecase.
Add an option to the boot command and also add a global variable for
it to make it configurable easily.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

watchdog: Fix static inline ops ...

...by actually making them static inline.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

mtd: spi-nor: mostly drop lock/unlock code ...

The lock/unlock code is broken beyond repair.

First of all the algorithm doesn't work properly. SPI NOR flashes
can only protect a certain amount of blocks from the end of the device
which is incompatible to the protect(start,len) API we have. The
algorithm tries to be clever by doing protection only when it does
not protect unrelated blocks and unprotection only when it does not
unprotect unrelated blocks. This breaks for example when some code
protects the last blocks (which may contain the bootloader), then
protects the blocks before the last ones (which may contain the
environment). Then if we try to overwrite the bootloader this won't
work since it would unprotect the environment aswell, so the driver
will not unprotect anything resulting in a failed erase/write later.

Then the protection behaviour is different between different flashes.
Some have three protection bits, some have four. For some the smallest
protection are is 1/16 of the device, others have 1/256 or 1/64. Some
have a bit which selects the lower area instead of upper area for
protection. The position of this bit differs on different flashes.

This patch removes the lock code completely and always unprotects
the whole device. This way we can unprotect a device for writing to
it and never protect it again.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: imx53: vincell: guard board initcall ...

Make sure that the initcall only executes on the expected board.

Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

reset-source: Add some debugging aids ...

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

mfd: da9053: add da9053 watchdog and system restart driver ...

Signed-off-by: Jan Luebbe <jlu@pengutronix.de>
Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

mfd: da9063: add da9063 watchdog and system restart driver ...

Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>

login: explain PASSWORD_DEFAULT option ...

This option looks like it takes the default password, but instead
it takes a filename of a file which contains the password encoded
with the selected password digest.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>