ARM: at91rm9200 timer: remove unused include ...

at91rm9200_time.c doesn't need anything from at91_pmc.h, remove the
inclusion.

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

ARM: at91: remove unused header file ...

nothing from mach/at91_tc.h is used, remove it.

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

ARM: at91rm9200: Add SoC namespace to memory controller defines ...

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

ARM: at91: Use SoC specific base addresses where appropriate ...

Replace AT91_ base addresses with their SoC specific variants where
possible.

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

ARM: at91: Add SoC namespace to matrix defines ...

Add SoC namespace to matrix define so we have one source less of
conflicting defines.

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

ARM: at91: remove common matrix header file ...

The common matrix header file can be removed when the users include the
SoC specific one. Fix the only user and remove the file.

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

ARM: at91: consolidate phy reset functions ...

Many boards have the same ethernet phy reset function, so share the code
in a common function.
While at it remove the AT91_RSTC offset from the rstc register defines.
AT91_RSTC was the offset between the AT91_SYSTEM_BASE and the reset
controller.

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

ARM: at91: remove AT91_SDRAM_BASE ...

AT91_SDRAM_BASE is only used in board code which known the SDRAM base
address, so we do not need a common define.

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

ARM: at91: drop AT91_NB_USART ...

AT91_NB_USART only used to return an error from at91_register_uart() if
an invalid UART number is passed. This will never happen as the linker
fails earlier in that case, so the runtime check can be removed and with
it the now unused AT91_NB_USART define.

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

ARM: at91: remove unused defines ...

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

ARM: at91sam926x: Add header for at91sam926x common base addresses ...

There are some base addresses common to at91sam926x. Add a separate
header for these.

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

ARM: at91rm9200ek: Use SoC specific defines ...

Use AT91RM9200_BASE_PIOC rather than AT91_BASE_PIOC so we can get rid of
the latter later.

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

ARM: at91: remove unused CONSISTENT_DMA_SIZE defines ...

CONSISTENT_DMA_SIZE is unused, remove it.

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

ARM: at91: remove unused AT_DMA_ID_ defines ...

The defines are unused and not properly namespaced, so remove them.

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

ARM: at91: Add initial support for the EVB-KSZ9477 eval board ...

The EVB-KSZ9477 is an evaluation board for the KSZ9477 ethernet switch.
This board is equipped with a atsama5d3 SoC with 256MiB of SDRAM, 256MiB
of NAND flash and a SD card slot.

For now only second stage booting is supported with AT91bootstrap as
first stage loader.

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

arm: at91: fix sdram controller init ...

e739663535 confused parameters to __raw_writel. The value and the base
address was mixed up.

Fixes: e739663535 (arm: at91: code cleanup in at91sam926x_board_init)

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

kconfig: Avoid format overflow warning from GCC 8.1 ...

Linux commit 2ae89c7 adapted for
barebox:

In file included from scripts/kconfig/zconf.tab.c:2485:
scripts/kconfig/confdata.c: In function ‘conf_write’:
scripts/kconfig/confdata.c:773:22: warning: ‘%s’ directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
  sprintf(newname, "%s%s", dirname, basename);
                      ^~
scripts/kconfig/confdata.c:773:19: note: assuming directive output of 7 bytes
  sprintf(newname, "%s%s", dirname, basename);
                   ^~~~~~
scripts/kconfig/confdata.c:773:2: note: ‘sprintf’ output 1 or more bytes (assuming 4104) into a destination of size 4097
  sprintf(newname, "%s%s", dirname, basename);
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
scripts/kconfig/confdata.c:776:23: warning: ‘.tmpconfig.’ directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]
   sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());
                       ^~~~~~~~~~~
scripts/kconfig/confdata.c:776:3: note: ‘sprintf’ output between 13 and 4119 bytes into a destination of size 4097
   sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Increase the size of tmpname and newname to make GCC happy.

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

usb: gadget: fastboot: remove unused variable ...

ep is unused, remove it.

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

of: unflatten: access property properly ...

Properties have to be accessed with of_property_get_value() rather than
accessing them directly from the devicenode. The accessor does the
right thing when of_new_property_const() is used.

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

fs: devfs: implement d_revalidate hook ...

The files in devfs can change withouut the fs layer noticing, so we
have to revalidate dentries before using them.

A failure could be triggered with:

ls /dev/nand0.root.ubi; ubiattach /dev/nand0.root; ls /dev/nand0.root.ubi

The first 'ls' would create a dentry for nand0.root.ubi with no inode
associated since it does not yet exist. 'ubiattach' then creates that
file, but the second 'ls' does not show it since the dentry is not
revalidated and thus no inode is added to that dentry. This patch
fixes this and also the opposite case when a file is removed (for
example with ubidetach).

Reported-by: Ladislav Michl <ladis@linux-mips.org>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

fs: implement d_revalidate ...

d_revalidate is useful when filesystems change under the hood of the
fs layer. This can happen with network filesystems or with devfs.

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

scripts: imx-usb-loader: list_imx_device_types(): move variable declaration out of for() loop ...

On older compilers this causes the following error:
| scripts/imx/imx-usb-loader.c: In function 'list_imx_device_types':
| scripts/imx/imx-usb-loader.c:252:2: error: 'for' loop initial declarations are only allowed in C99 mode
|   for (int i = 0; i < ARRAY_SIZE(imx_ids); i++) {
|   ^
| scripts/imx/imx-usb-loader.c:252:2: note: use option -std=c99 or -std=gnu99 to compile your code

Fixes: bcc2df673cdb ("scripts: imx-usb-loader: allow use of unknown USB IDs")
Reported-by: Niklas Reisser <Niklas.Reisser@de.bosch.com>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

net: make routing work after dhcp command ...

At the moment only ifup stuff turns netif up.
After the commit f0624a701513 ('net: Do not route traffic
to interfaces that are not up') the dhcp command
keeps netif->ifup == false and network subsystem
can't route packets.

How to repropduce the problem on qemu-malta_defconfig:

    qemu-system-mips -nodefaults -M malta -m 256 \
                     -nographic -serial stdio -monitor null \
                     -bios barebox-flash-image \
                     -net user -net nic,model=rtl8139

    ...

    barebox:/ dhcp
    eth0: 100Mbps full duplex link detected
    eth0: DHCP client bound to address 10.0.2.15
    barebox:/ ping 10.0.2.2
    ping failed: No route to host

However if ifup command is used for network interface
configuration then there is no network problem, e.g.

    barebox:/ ifup eth0
    eth0: 100Mbps full duplex link detected
    eth0: DHCP client bound to address 10.0.2.15
    barebox:/ ping 10.0.2.2
    host 10.0.2.2 is alive

Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
CC: Andrey Smirnov <andrew.smirnov@gmail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

environment: bypass overlap check for mtd devices ...

For mtd devices the overlap check does not work as expected for two
reasons. First is that cdev->offset is 0 for mtd partitions, instead
cdev->mtd->master_offset has to be used. That could be fixed easily.
Second on NAND devices the environment is on the bb devices and not
on the raw nand devices which means we would need something to get
the mtd device from the bb device before doing the check.

Both issues are fixable, but the check was mainly done to catch cases
when an environment partition is created in the free space before the
first MBR/GPT partition on SD/MMC devices, so leave out the mtd case
for now.

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

environment: Fix overlapping partitions error message ...

Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
Fixes: b234a6da331f ("environment: Do not use environment when
                      overlapping with other partitions")
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/ubifs'

Merge branch 'for-next/socfpga'

Merge branch 'for-next/ratp'

Merge branch 'for-next/net-imx-fec'

Merge branch 'for-next/mtd'