u-boot.git/drivers/core, branch v2020.01

regmap: Fix potential memory leaks

2019-12-03T13:44:14+00:00

Free allocated memory in case of an error in regmap_init_mem() and
regmap_init_mem_index().

Signed-off-by: Faiz Abbas

common: Move ARM cache operations out of common.h

2019-12-02T23:24:58+00:00

These functions are CPU-related and do not use driver model. Move them to
cpu_func.h

Signed-off-by: Simon Glass 
Reviewed-by: Daniel Schwierzeck 
Reviewed-by: Tom Rini

Merge tag 'dm-pull-29oct19' of git://git.denx.de/u-boot-dm

2019-11-01T13:34:35+00:00

- Fix for patman with email addresses containing commas
- Bootstage improvements for TPL, SPL
- Various sandbox and dm improvements and fixes

fdt: Fix alignment issue when reading 64-bits properties from fdt

2019-10-27T19:01:53+00:00

The FDT specification [0] gives a requirement of aligning properties on
32-bits. Make sure that the compiler is aware of this constraint when
accessing 64-bits properties.

[0]: https://github.com/devicetree-org/devicetree-specification/blob/master/source/flattened-format.rst

Signed-off-by: Jean-Jacques Hiblot 
Reviewed-by: Simon Glass

dm: core: Update log method for uclass_find_device_by_seq

2019-10-27T19:01:43+00:00

Use log() insted of debug() for uclass_find_device_by_seq function,
since this print is very much and we can filter it out with log()
interface.

Signed-off-by: Kever Yang 
Reviewed-by: Simon Glass 
Move #define to top of file as per docs:
Signed-off-by: Simon Glass

dm: regmap: Fix mask in regmap_update_bits()

2019-10-27T16:56:41+00:00

This function assumes that the 'val' parameter has no masked bits set.
This is not defined by the function prototype though. Fix the function to
mask the value and update the documentation.

Signed-off-by: Simon Glass 
Reviewed-by: Bin Meng 
Reviewed-by: Jean-Jacques Hiblot

drivers: clk: Fix using assigned-clocks in the node of the clock it sets up

2019-10-22T14:14:05+00:00

This fixes the case where assigned-clocks is used to define a clock
defaults inside this same clock's node. This is used sometimes to setup a
default parents and/or rate for a clock.

example:
muxed_clock: muxed_clock {
	clocks = <&clk_provider 0>, <&clk_provider 1>;
	#clock-cells = <0>;
	assigned-clocks = <&muxed_clock>;
	assigned-clock-parents = <&clk_provider 1>;
};

It doesn't work in u-boot because the assigned-clocks are setup *before*
the clock is probed. (clk_set_parent() will likely crash or fail if called
before the device probe function)
Making it work by handling "assigned-clocks" in 2 steps: first before the
clk device is probed, and then after the clk device is probed.

Signed-off-by: Jean-Jacques Hiblot

dm: Tidy up dump output when there are many devices

2019-10-15T14:40:03+00:00

At present the 'Index' column of 'dm tree' assumes there is
two digits, this patch increase it to 3 digits.

It also aligns output of 'dm uclass', assuming the same 3 digits index.

The boards with CONFIG_PINCTRL_FULL activated have one pinconfig
by pin configuration, so they can have more than 100 devices
pinconfig (for example with stm32mp157c-ev1 board we have
106 pinconfig node).

Signed-off-by: Patrick Delaunay 
Reviewed-by: Simon Glass

dm: core: device: switch off power domain after device removal

2019-10-15T14:40:03+00:00

The power domain associated with a device is enabled when probing,
but currently the domain remains enabled when the device is removed.
Some boards started to disable power domains for selected devices
via custom board_quiesce_devices(), but it doesn't work in many
cases, i. e. because devices still can be accessed later in
.remove() callback on behalf of dm_remove_devices_flags().

Utilize the DM core to power off the device power domain, but add a
device flag to be able to selectively let the power domain enabled
after device removal. This might be required for devices that must
remain enabled when booting OS, i. e. serial console for debug
output, etc.

Signed-off-by: Anatolij Gustschin 
Signed-off-by: Lokesh Vutla 
Reviewed-by: Simon Glass

dm: core: Allow for not controlling the power-domain by DM framework

2019-10-15T14:40:03+00:00

In some remoteproc cases, enabling the power domain of the core will
start running the core. In such cases image should be loaded before
enabling the power domain. But the current DM framework enables the
power-domain by default during probe. This is causing the remotecore
to start and crash as there is no valid image loaded.

In order to avoid this introduce a DM flag that doesn't allow for
enabling/disabling the power-domain by DM framework.

Signed-off-by: Lokesh Vutla 
Reviewed-by: Simon Glass