param: fix stub prototype of dev_add_param ...

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

ARM: socfpga: fix QSPI platform data init ...

The struct member has been renamed, fix it.

Fixes: fddf254b8b9a (mtd: spi-nor: cadence: change devicetree bindings to upstream)
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: i.MX50: Kindle-MX50 DT fixes ...

* fix IOMUX for MAX14656 IRQ, it requires a pull-up to work
* enable UART console for Model EY21
* set up IOMUX for EY21 GPIO lid-close hall sensor
* remove IOMUX for non-existing EY21 GPIO keys
* replace space indention with tabs

Signed-off-by: Alexander Kurz <akurz@blala.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: i.MX50: Amazon Kindle: Model EY21 compatibility check ...

Extend the compatibility check for i.MX50 based kindles also on model EY21.

Signed-off-by: Alexander Kurz <akurz@blala.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

of: of_find_node_by_devpath: Fix offset in mtd devices ...

When a cdev is a mtd device the partition offset must be used from
there, not from the cdev.

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

PPC: request a consistent memory layout ...

Using the memory test command will crash barebox, because it tests the
area where the stack is located for the PPC architecture.

On PPC the stack is below the barebox binary. Below the stack the malloc
area is located. Until this change some routines used the macros
from 'memory_layout.h', some other calculated their values by their
own - which resulted into an unrequested and unprotected stack area.

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

ARM: i.MX50: Amazon Kindle: Add missing compatibility checks ...

Add the checks to prevent Kindle specific code on other machines.
This also adds compatible strings for the Kindle machines as they
currently lack them.

Reported-by: Stefan Riedmüller <S.Riedmueller@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

state: Fix example in documentation ...

The backend property must contain a phandle, so use a phandle
in the example.

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

globalvar: Fix value of new globalvar when nvvar exists ...

When a new globalvar with a value is created and the corresponding
nvvar exists, then the globalvar gets the value of the nvvar, not
from the newly assigned value as expected.

nv quux=foo; global quux=bar; echo ${global.quux}

Should give "bar", not "foo". Fix this.

Reported-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

nv: Fix setting of nv.dev.<devname>.<param> variables ...

nv variables with the form nv.dev.<devname>.<param> shall be mirrored to
the device parameter <param> of the device named <devname>. This is
broken since:

| commit 35d8e85
| Author: Sascha Hauer <s.hauer@pengutronix.de>
| Date:   Thu Apr 6 15:23:56 2017 +0200
|
|     nv: Do not create globalvars from nvvars

Fix this by attaching the setting of the mirror device parameter
directly to the nv device rather than to the global device.

Reported-by: Ian Abbott <abbotti@mev.co.uk>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

clock: initialize dummy clocksource statically ...

Assigning the dummy clocksource in a initcall has the problem that
get_time_ns() crashes before that initcall is executed. This happens
when dmesg support is enabled in conjunction with CONFIG_DEBUG_INITCALLS.
In this case the dmesg code wants to have the timestamp of a log
message.
Solve this by setting the current clocksource to the dummy clock
statically and not at runtime. This way we always have a dummy
clock available.

Fixes:
commit 8972eb7
Author: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Date:   Fri Mar 3 13:34:02 2017 +0100

    clocksource: move dummy clock source to init_clock

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

Merge branch 'for-next/state'

Merge branch 'for-next/socfpga'

Merge branch 'for-next/parameter-types'

Merge branch 'for-next/omap'

Merge branch 'for-next/mvebu'

Merge branch 'for-next/misc'

Merge branch 'for-next/libgen'

Merge branch 'for-next/imx'

Merge branch 'for-next/dts'

Merge branch 'for-next/arm'

imx-bbu-nand-fcb: add support for imx6ul ...

imx6ul secure the fcb with bch 40. The imx-kobs tool use a own modified
bch lib. They reverse the bit order of the data and the ecc.
To use the bch lib in barebox the bytes in the data buffers must be
reversed.
The data layout on nand is bit aligned. But with 40 bits this is not an
issue for imx6ul now.

Signed-off-by: Jan Remmet <J.Remmet@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

dts: update to v4.11-rc8 ...

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

Release v2017.05.0 ...

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

arm: boards: Add MLO handler for EMMC devices ...

This patch enables the barebox handler to flash MLOs on EMMC devices
with 'barebox_update'.

Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

arm: mach-omap: Change file flags in emmc handler ...

This handler tries to read from a file descriptor with 'write only'
flags and fails. Add read permissions for the file, so the handler can
read the partition layout.

Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

state: Create alias in of_state_fixup() ...

When the kernel device tree is fixed up we assume that it doesn't
have a state node, so we must also assume that it doesn't have
a alias. Create it.

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

state: Make an alias mandatory ...

The userspace barebox-state utility gets confused when no alias exists.
Make the alias mandatory, so that people make it right^tm without having
to ask.

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

state: warn when a state node will be overwritten ...

People do not seem to know that a state node in the kernel
device tree will be overwritten by barebox. Print a warning
when this happens so that people can get an idea why changes
in the kernel device tree state node do not have any effect.

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

state: Binding: remove @0 from node name ...

The '@0' suffix is for nodes which have a reg property, so
do not use this suffix in the state example node which does
not have a reg property.

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