u-boot.git/drivers/core, branch v2019.01-rc1 Unnamed repository; edit this file 'description' to name the repository. core: ofnode: Fix ofnode_get_addr_index function 2018-11-29T16:30:06+00:00 Keerthy j-keerthy@ti.com 2018-11-19T06:14:47+00:00 1678754f5e2cbc14f9612e953b39cc08ada66866 Currently the else part of ofnode_get_addr_index function does not fetch addresses based on the index but rather just returns the base address. Fix that. Signed-off-by: Keerthy <j-keerthy@ti.com> 
Currently the else part of ofnode_get_addr_index function
does not fetch addresses based on the index but rather just
returns the base address. Fix that.

Signed-off-by: Keerthy <j-keerthy@ti.com>
dm: core: Add a few more specific child-finding functions 2018-11-29T16:30:05+00:00 Simon Glass sjg@chromium.org 2018-11-18T15:14:31+00:00 3abe1115355900172a8681f5e6fa01ca71a9b916 Add two functions which can find a child device by uclass or by name. The first is useful with Multi-Function-Devices (MFDs) to find one of a particular type. The second is useful when only the name is known. Signed-off-by: Simon Glass <sjg@chromium.org> 
Add two functions which can find a child device by uclass or by name.
The first is useful with Multi-Function-Devices (MFDs) to find one of a
particular type. The second is useful when only the name is known.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: core: Export uclass_find_device_by_phandle() 2018-11-29T16:30:05+00:00 Simon Glass sjg@chromium.org 2018-11-18T15:14:30+00:00 d0b4f68d199c075f5d734cf184f7eaf1a642083d This function may be useful to code outside of the code driver-model implementation. Export it and add a test. Signed-off-by: Simon Glass <sjg@chromium.org> 
This function may be useful to code outside of the code driver-model
implementation. Export it and add a test.

Signed-off-by: Simon Glass <sjg@chromium.org>
dm: core: Widen the dump tree to show more of the driver's name. 2018-11-21T02:14:22+00:00 Liviu Dudau Liviu.Dudau@foss.arm.com 2018-10-15T09:03:06+00:00 5197dafc42eb926525a12fc5aa38d2a05f22d177 With drivers that have prefix names that are quite long (like 'versatile_') it is useful to have a wider column for the driver's name when dumping the device driver tree. Also update the tests to take into account the wider output format. Signed-off-by: Liviu Dudau <liviu.dudau@foss.arm.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
With drivers that have prefix names that are quite long (like
'versatile_') it is useful to have a wider column for the driver's
name when dumping the device driver tree.

Also update the tests to take into account the wider output format.

Signed-off-by: Liviu Dudau <liviu.dudau@foss.arm.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
dm: uclass: Add uclass_next_device_err() to return a valid device 2018-11-16T21:51:55+00:00 Patrice Chotard patrice.chotard@st.com 2018-10-24T12:10:15+00:00 f6abd5389ceab5fce185126c2364a324465fafbe Similarly to uclass_first_device_err(), add uclass_next_device_err() which returns an error if there are no next devices in that uclass. Signed-off-by: Patrice Chotard <patrice.chotard@st.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Similarly to uclass_first_device_err(), add uclass_next_device_err()
which returns an error if there are no next devices in that uclass.

Signed-off-by: Patrice Chotard <patrice.chotard@st.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
uclass: Use uclass_foreach_dev() macro instead of open coding 2018-11-14T17:16:28+00:00 Liviu Dudau Liviu.Dudau@foss.arm.com 2018-09-28T13:12:55+00:00 81f351d6e7ebb371de8ea849fc21dd07dc2eff24 Use the uclass_foreach_dev() macro instead of the open coded version. Signed-off-by: Liviu Dudau <liviu.dudau@foss.arm.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Use the uclass_foreach_dev() macro instead of the open coded version.

Signed-off-by: Liviu Dudau <liviu.dudau@foss.arm.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
dm: core: Allow uclass to set up a device's child after it is probed 2018-11-14T17:16:27+00:00 Bin Meng bmeng.cn@gmail.com 2018-10-15T09:20:57+00:00 651d0c019a428ca8b14352210c1ce7804dd51fae Some buses need to set up their child devices after they are probed. Support a common child_post_probe() method for the uclass. With this change, the two APIs uclass_pre_probe_device() and uclass_post_probe_device() become symmetric. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> 
Some buses need to set up their child devices after they are probed.
Support a common child_post_probe() method for the uclass.

With this change, the two APIs uclass_pre_probe_device() and
uclass_post_probe_device() become symmetric.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
regmap: Add endianness support 2018-11-14T17:16:27+00:00 Mario Six mario.six@gdsys.cc 2018-10-15T07:24:14+00:00 9b77fe3b80b038af7114f7dae4934773bb026f8e Add support for switching the endianness of regmap accesses via the "little-endian", "big-endian", and "native-endian" boolean properties in the device tree. The default endianness is native endianness. Signed-off-by: Mario Six <mario.six@gdsys.cc> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> 
Add support for switching the endianness of regmap accesses via the
"little-endian", "big-endian", and "native-endian" boolean properties in
the device tree.

The default endianness is native endianness.

Signed-off-by: Mario Six <mario.six@gdsys.cc>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
regmap: Support reading from specific range 2018-11-14T17:16:27+00:00 Mario Six mario.six@gdsys.cc 2018-10-15T07:24:11+00:00 d5c7bd985d759b7aade2700c11890821e6187e4b It is useful to be able to treat the different ranges of a regmap separately to be able to use distinct offset for them, but this is currently not implemented in the regmap API. To preserve backwards compatibility, add regmap_read_range and regmap_write_range functions that take an additional parameter 'range_num' that identifies the range to operate on. Reviewed-by: Anatolij Gustschin <agust@denx.de> Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Mario Six <mario.six@gdsys.cc> 
It is useful to be able to treat the different ranges of a regmap
separately to be able to use distinct offset for them, but this is
currently not implemented in the regmap API.

To preserve backwards compatibility, add regmap_read_range and
regmap_write_range functions that take an additional parameter
'range_num' that identifies the range to operate on.

Reviewed-by: Anatolij Gustschin <agust@denx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Mario Six <mario.six@gdsys.cc>
regmap: Add raw read/write functions 2018-11-14T17:16:27+00:00 Mario Six mario.six@gdsys.cc 2018-10-15T07:24:10+00:00 84ff8f622d2e2aeb67c1cec1c2c814895648fca8 The regmap functions currently assume that all register map accesses have a data width of 32 bits, but there are maps that have different widths. To rectify this, implement the regmap_raw_read and regmap_raw_write functions from the Linux kernel API that specify the width of a desired read or write operation on a regmap. Implement the regmap_read and regmap_write functions using these raw functions in a backwards-compatible manner. Reviewed-by: Anatolij Gustschin <agust@denx.de> Signed-off-by: Mario Six <mario.six@gdsys.cc> Reviewed-by: Simon Glass <sjg@chromium.org> 
The regmap functions currently assume that all register map accesses
have a data width of 32 bits, but there are maps that have different
widths.

To rectify this, implement the regmap_raw_read and regmap_raw_write
functions from the Linux kernel API that specify the width of a desired
read or write operation on a regmap.

Implement the regmap_read and regmap_write functions using these raw
functions in a backwards-compatible manner.

Reviewed-by: Anatolij Gustschin <agust@denx.de>
Signed-off-by: Mario Six <mario.six@gdsys.cc>
Reviewed-by: Simon Glass <sjg@chromium.org>