Release v2019.04.0 ...

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

of: Fix reproducible names for #address-cells != 1 ...

For the new "fixed-partitions" binding we ignore the partitions
subnode for creating reproducible names and set node to its parent.
To get the number of address cells we must call of_n_addr_cells()
before setting node to its parent though, not afterwards. With the
current behaviour we always get OF_ROOT_NODE_ADDR_CELLS_DEFAULT (=1).
This happens to work then the partitioned device is less than 4GiB
in size. On bigger devices #address-cells = <2> is chosen by the
mtd partition fixup code.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Reported-by: Bastian Krause <bst@pengutronix.de>

Revert "fix zbarebox linking with new ld" ...

--no-dynamic-linker is already added just a few lines below, do not add
the option twice. This option also needs to be embedded in a test if
the linker supports this option which we already have in the other place
adding this option.

This reverts commit 25de306.

ARM: Makefile: restore kindle3 imxcfg-y setting ...

Commit 45f38c1a846f ("ARM: Makefile: Drop unnecessary imxcfg-y settings")
dropped the imximg generation for the kindle3. This device is not covered
within multiimage support and can be configured with kindle3_defconfig.

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

mci: imx-esdhc: resolve conflicting flags ...

With commit 3354adee3920 ("mci: imx-esdhc: Add bigendian register access
support") and commit 15b64fd520c2 ("mci: imx-esdhc: Add layerscape support")
two ESDHC_FLAGs got assigned to already existing values. This conflict made
the imx6sl usdhc appear to be big endian.
Resolve this conflict by assign the new flags to the next vacant values.

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

mci: imx-esdhc-pbl: initialize is_be ...

Initialize is_be, otherwise the value of is_be is undefined.
So it is possible that the i.MX8 will not boot because the bigendian
functions are used.

Signed-off-by: Christian Hemp <c.hemp@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

dtc: disable noisy warnings ...

Disable the following warnings from dtc:

-Wno-alias_paths
-Wno-graph_child_address
-Wno-simple_bus_reg
-Wno-unique_unit_address

This syncs the warning flags with the Kernel.

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

Merge branch 'for-next/spd'

Merge branch 'for-next/rpi'

Merge branch 'for-next/nvme'

Merge branch 'for-next/misc'

Merge branch 'for-next/imx8-usb'

Merge branch 'for-next/imx-i2c'

Merge branch 'for-next/imx'

Merge branch 'for-next/fs'

Merge branch 'for-next/efi'

Merge branch 'for-next/dts'

Merge branch 'for-next/dtc'

ARM: rpi: Clarify debug uart names ...

Now that we support the miniuart as lowlevel debug UART clarify that
the other UARTs are PL011.

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

common: Kconfig: improve help text for DEBUG_LL ...

This adopts the help text used in Linux for the same setting. It
clarifies that a build with DEBUG_LL enabled will only work on the
system you chose the debug UART for.

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

fixup! ARM: rpi: Add mini UART debug_ll support

fixup! ARM: rpi: move debug UART Kconfig settings

dts: update to v5.0 ...

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

dts: update to v5.0-rc8 ...

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

dts: update to v5.0-rc7 ...

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

Release v2019.03.0 ...

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

images: pbl: verify CONFIG_BAREBOX_MAX_IMAGE_SIZE is not exceeded ...

For platforms such as the at91, the boot ROM imposes an upper limit
on barebox file size.  Prior to 5a1a5ed253 ("ARM: images: use piggydata"),
BAREBOX_MAX_PBLX_SIZE seems to have been the way to go for limiting
the size of the final barebox binary when using the PBL.
With pblx removed, this variable is of no use, so have the existing
BAREBOX_MAX_IMAGE_SIZE replace its functionality.

Currently BAREBOX_MAX_IMAGE_SIZE is only checked against in the non-PBL
case, so add a check in the PBL case as well.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: dts: imx6*phytec*: switch to new partitioning scheme ...

Both Linux and barebox support this new scheme and it's the actually
the recommended one.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: i.MX6UL: liteSOM: depend on DDR controller settings ...

Initially we depended on DDR controller settings for liteSOM and liteboard. With
33fdc89d4cbd ("dts: update to v5.0-rc1") a `device_type = "memory";` property
was added to imx6ul-litesom.dtsi file, which causes "ram0" to be added with
512MB size (value in dtsi) instead of the real 256MB size that is configured in
barebox-grinn-liteboard-256mb.img. As a result Linux kernel fails to boot.

Lets depend on DDR controller settings, by removing whole `/memory` node from
device tree. This makes barebox-grinn-liteboard-256mb.img able to boot Linux
kernel once again.

Reported-by: Bartosz Bilas <b.bilas@grinn-global.com>
Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

fix zbarebox linking with new ld ...

Signed-off-by: 张忠山 <zzs213@126.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>