u-boot.git/common/fdt_support.c, branch v2016.03

Revert "fdt_support: Add multi-serial support for stdout fixup"

2016-01-21T02:10:12+00:00

This reverts commit 3e303f748cf57fb23e8ec95ab7eac0074be50e2b.

The fix up in the /aliases node does not work under the following
scenarios:
- Not every non-DM serial driver was written to have a driver name
  that conforms the format of "serial%d" or "eserial%d".
- With driver model serial, the stdio_devices[] stores the serial
  device node name in the device tree.

Signed-off-by: Bin Meng 
Acked-by: Simon Glass

Merge git://git.denx.de/u-boot-net

2016-01-14T02:05:16+00:00

fdt: fix address cell count checking in fdt_translate_address()

2016-01-07T18:28:04+00:00

Commit: dm: core: Enable optional use of fdt_translate_address()

Enables use of this function as default, but after this it's not
possible to get dev address for the case in which: '#size-cells == 0'

This causes errors when getting address for some GPIOs, for which
the '#size-cells' is set to 0.

Example error:
'__of_translate_address: Bad cell count for gpx0'

Allowing for that case by modifying the macro 'OF_CHECK_COUNTS',
(called from )__of_translate_address(), fixes the issue.

Now, this macro doesn't check, that '#size-cells' is greater than 0.

This is possible from the specification point of view, but I'm not sure
that it doesn't introduce a regression for other configs.

Please test and share the results.

Tested-on: Odroid U3, Odroid X2, Odroid XU3, Sandbox.

Signed-off-by: Przemyslaw Marczak 
Cc: Masahiro Yamada 
Cc: Lukasz Majewski 
Cc: Jaehoon Chung 
Cc: Stefan Roese 
Cc: Simon Glass 
Cc: Bin Meng 
Cc: Marek Vasut 
Tested-by: Jaehoon Chung 
Tested-by: Lukasz Majewski

fdt: Rewrite the logic in fdt_fixup_ethernet()

2015-12-22T01:56:17+00:00

Currently in fdt_fixup_ethernet() the MAC address fix up is
handled in a loop of which the exit condition is to test the
"eth%daddr" env is not NULL. However this creates unnecessary
constrains that those "eth%daddr" env variables must be
sequential even if "ethernet%d" does not start from 0 in the
"/aliases" node. For example, with "/aliases" node below:

    aliases {
        ethernet3 = &enet3;
        ethernet4 = &enet4;
    };

"ethaddr", "eth1addr", "eth2addr" must exist in order to fix
up ethernet3's MAC address successfully.

Now we change the loop logic to iterate the properties in the
"/aliases" node. For each property, test if it is in a format
of "ethernet%d", then get its MAC address from corresponding
"eth%daddr" env and fix it up in the dtb.

Signed-off-by: Bin Meng 
Acked-by: Joe Hershberger 
Reviewed-by: Tom Rini 
On OMAP4 Panda (+v4.3 kernel)
Tested-by: Tom Rini

fdt: Deprecate "usbethaddr" usage in fdt_fixup_ethernet()

2015-12-22T01:55:27+00:00

In fdt_fixup_ethernet() only "usbethaddr" is handled to fix up the
first usb ethernet port MAC address. Other additional usb ethernet
ports are ignored as there is no logic to handle "usbeth%daddr".

It is suggested we should use "ethaddr" for all ethernet devices.
Hence deprecate "usbethaddr" usage in fdt_fixup_ethernet().

This actually reverts commit b1f49ab8c7bad60426b30c134ae065ef77d2dfc1
"ARM: fdt support: Add usbethaddr as an acceptable MAC".

Signed-off-by: Bin Meng 
Acked-by: Joe Hershberger 
Reviewed-by: Tom Rini 
On OMAP4 Panda (+ v4.3 kernel)
Tested-by: Tom Rini

fdt: Change OF_BAD_ADDR to FDT_ADDR_T_NONE

2015-12-09T09:44:36+00:00

Currently OF_BAD_ADDR is always -1ULL. When using OF_BAD_ADDR as the
return value of dev_get_addr(), it creates potential size mismatch
as dev_get_addr() uses FDT_ADDR_T_NONE as the return value which can
be either -1U or -1ULL depending on CONFIG_PHYS_64BIT. Now we change
OF_BAD_ADDR to FDT_ADDR_T_NONE to avoid such case.

Signed-off-by: Bin Meng 
Acked-by: Simon Glass 
Reviewed-by: Stefan Roese

fdt_support: Don't panic if stdout alias is missing

2015-10-26T16:09:54+00:00

Currently, using fdt_fixup_stdout() on a device tree that is missing
the relevant alias results in this:

WARNING: could not set linux,stdout-path FDT_ERR_NOTFOUND.
ERROR: /chosen node create failed
 - must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###

There is no reason for this to be a fatal error rather than a warning,
and removing this allows for a smooth transition on a platform where
the device tree currently lacks the correct aliases but will have them
in the future.

Signed-off-by: Scott Wood 
Cc: Kumar Gala 
Cc: Simon Glass 
Reviewed-by: Simon Glass 
Reviewed-by: York Sun

fdt: prevent clearing memory node if there are no banks

2015-07-20T13:21:47+00:00

Avoid clearing the reg property in the memory DT node if no memory
banks have been specified for a board (CONFIG_NR_DRAM_BANKS == 0).
This allows boards to let U-Boot skip the DT memory tinkering in case
other firmware has already setup the node properly before.
This should be safe as all callers of fdt_fixup_memory_banks that use
a computed  value put at least 1 in there.
Add some documentation comments to the header file.

Signed-off-by: Andre Przywara 
Acked-by: Simon Glass

fdt: Pass the device serial number through devicetree

2015-06-05T14:32:07+00:00

Before device-tree, the device serial number used to be passed to the kernel
using ATAGs (on ARM). This is now deprecated and all the handover to the kernel
should now be done using device-tree. Thus, this passes the serial-number
property to the kernel using the serial-number property of the root node, as
expected by the kernel.

The serial number is a string that somewhat represents the device's serial
number. It might come from some form of storage (e.g. an eeprom) and be
programmed at factory-time by the manufacturer or come from identification
bits available in e.g. the SoC.

Signed-off-by: Paul Kocialkowski 
Reviewed-by: Simon Glass

fdt: Correct warning in fdt_setup_simplefb_node()

2015-05-06T02:58:19+00:00

Adjust the printf() string to avoid a warning on sandbox.

Signed-off-by: Simon Glass