- Nov 14, 2018
-
-
blk_next_free_devnum() can be helpful in some cases. Make it a public API. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
-
With the post_probe() changes, this API is no longer needed. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
part_init() is currently called in every DM BLK driver, either in its bind() or probe() method. However we can use the BLK uclass driver's post_probe() method to do it automatically. Update all DM BLK drivers to adopt this change. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
Currently the efi block driver uses priv_auto_alloc_size for the driver data, however that's only available after the device probe phase. In order to make it accessible in an earlier phase, switch to use platdata_auto_alloc_size instead. This patch is the prerequisite for the follow up patch of DM BLK driver changes to work with EFI loader. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
Currently the sandbox block driver uses priv_auto_alloc_size for the driver data, however that's only available after the device probe phase. In order to make it accessible in an earlier phase, switch to use platdata_auto_alloc_size instead. This patch is the prerequisite for the follow up patch of DM BLK driver changes to work with Sandbox. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
The blk_base test case creates a USB mass storage block device with the Sandbox host block device as its parent. This does not make any sense and causes potential issue, for example if the test case tries to read/write anything on the USB mass storage block device it will definitely fail as its parent is not on USB bus at all. Correct the test case by creating another Sandbox host block device instead of the USB mass storage one and adjust the case accordingly. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
This adds virtio net device driver support. Signed-off-by:
Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi> Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
VirtIO can use various different buses and virtio devices are commonly implemented as PCI devices. But virtual environments without PCI support (a common situation in embedded devices models) might use simple memory mapped device (“virtio-mmio”) instead of the PCI device. This adds a transport driver that implements UCLASS_VIRTIO for virtio over mmio. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
This adds support for managing virtual queue/ring, the channel for high performance I/O between host and guest. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
This adds a new virtio uclass driver for “virtio” [1] family of devices that are are found in virtual environments like QEMU, yet by design they look like physical devices to the guest. The uclass driver provides child_pre_probe() and child_post_probe() methods to do some common operations for virtio device drivers like device and driver supported feature negotiation, etc. [1] http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.pdf Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
This adds a call to dm_remove_devices_flags() to do_bootm_linux() so that drivers that have one of the removal flags set (e.g. DM_FLAG_ACTIVE_DMA_REMOVE) in their driver struct, may do some last-stage cleanup before the OS is started. arm and x86 already did such, and we should do the same for riscv. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
Add test case to cover uclass driver's child_post_probe() method. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
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: -
Add some overview documentation that explains the purpose and some of the features and limitations of the regmap interface. Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
Signed-off-by: Mario Six <mario.six@gdsys.cc>
-
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:
Daniel Schwierzeck <daniel.schwierzeck@gmail.com> -
Add test for regmap_{set,get} functions. Reviewed-by:Anatolij Gustschin <agust@denx.de> Reviewed-by:
-
It would be convenient if one could use the regmap API in conjunction with register maps defined as structs (i.e. structs that directly mirror the memory layout of the registers in question). A similar approach was planned with the regmap_write32/regmap_read32 macros, but was never used. Hence, implement regmap_set/regmap_range_set and regmap_get/regmap_range_get macros, which, given a register map, a struct describing the layout of the register map, and a member name automatically produce regmap_read/regmap_write calls that access the specified member in the register map. Reviewed-by:
-
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:
-
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:
-
MIPS is the only architecture currently supported by U-Boot that does not implement any of the in/out register access functions. To have a interface that is useable across architectures, add the functions to the MIPS architecture (implemented using the __raw_write and __raw_read functions). Reviewed-by:
Stefan Roese <sr@denx.de> Reviewed-by:
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
Signed-off-by: -
Add some debug output in cases where the initialization of a regmap fails. Reviewed-by:
-
Both fdtdec_get_addr_size_fixed and of_address_to_resource can fail with an error, which is not currently checked during regmap initialization. Since the indentation depth is already quite deep, extract a new 'init_range' method to do the initialization. Reviewed-by:
-
Simon Glass authored
At present 'buildman sandbox' will build all 5 boards for the sandbox architecture rather than the single board 'sandbox'. The only current way to exclude sandbox_spl, sandbox_noblk, etc. is to use -x which is a bit clumbsy. Add a --boards option to allow individual build targets to be specified. Signed-off-by: -
Simon Glass authored
Use a starting address of 256MB which should be available. This helps to make sandbox RAM buffers pointers more recognisable. Signed-off-by: -
A newly created property is currently not freed if a name could not be allocated. This patch fixes the resulting memory leak in the error patch. Reported-by: Coverity (CID: 184085) Fixes: e369e58d ("core: Add functions to set properties in live-tree") Signed-off-by:
-
Add a driver for gdsys IHS (Integrated Hardware Systems) FPGAs, which supports initialization of the FPGA, as well as information gathering. Reviewed-by:
-
This patch adds a driver for the bus associated with a IHS FPGA. Reviewed-by:
-
Makefile entries should be sorted. Reviewed-by:
-
ofnode_read_simple_addr_cells may fail and return a negative error code. Check for this when initializing regmaps. Also check if both_len is zero, since this is perfectly possible, and would lead to a division-by-zero further down the line. Reviewed-by:
-
Document the regmap_alloc() function. Reviewed-by:
-
The documentation in regmap.h is not in kernel-doc format. Correct this. Reviewed-by:
-
The upcoming changes to the regmap interface will contain a proper check for plausibility when reading/writing from/to a register map. To still have the current tests pass, increase the size of the memory region for the syscon0 device, since one of the tests reads and writes beyond this range. Reviewed-by:
-
This is currently out of order. Sort it. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
Now that we fixed the pre-relocation driver binding for driver marked with DM_FLAG_PRE_RELOC flag, add a test case to cover that scenario. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
Commit f2006808: ("dm: core: parse chosen node") added a logic to parse the chosen node during dm_scan_fdt_node(), but unfortunately it missed adding the same logic in dm_scan_fdt_live(). This mirrors the logic in the livetree version. The weird thing is that commit f2006808 did update the test case to test such logic, but even if I reset to that commit, the test case still fails, and I have no idea how it could pass. With this fix, the following 2 test cases now pass: Test: dm_test_bus_children: bus.c test/dm/bus.c:112, dm_test_bus_children(): num_devices == list_count_items(&uc->dev_head): Expected 7, got 6 Test: dm_test_fdt: test-fdt.c test/dm/test-fdt.c:184, dm_test_fdt(): num_devices == list_count_items(&uc->dev_head): Expected 7, got 6 Fixes: f2006808 ("dm: core: parse chosen node") Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
The pre_reloc_only parameter description currently only mentions drivers with the DM_FLAG_PRE_RELOC flag, but does not mention the special device tree properties. Correct them. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
Currently the comments of several APIs (eg: dm_init_and_scan()) say: @pre_reloc_only: If true, bind only drivers with the DM_FLAG_PRE_RELOC flag. If false bind all drivers. The 'Pre-Relocation Support' chapter in doc/driver-model/README.txt documents the same that both device tree properties and driver flag are supported. However the implementation only checks these special device tree properties without checking the driver flag at all. This updates lists_bind_fdt() to consider both scenarios. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
This adds a new API dm_ofnode_pre_reloc(), a livetree equivalent API of dm_fdt_pre_reloc(). Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
The description string should not contain unnecessary characters, like the ending '\n' or the leading 'CPU:'. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: -
It was observed that current output of print_cpuinfo() on QEMU x86 targets does not have an ending '\n', neither have a leading 'CPU:' any more. However it used to have these before. It turns out commit c0434407 introduced a unified DM version of print_cpuinfo() that exposed such issue on QEMU x86. Fixes: c0434407 ("board_f: Use static print_cpuinfo if CONFIG_CPU is active") Signed-off-by:
Bin Meng <bmeng.cn@gmail.com>
Reviewed-by:
-
