- 11 7月, 2020 10 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-dm由 Tom Rini 提交于
of-platdata: better phandle and compatible-string support patman support for Python3 on Ubuntu 14.04 new checkpatch check to avoid #ifdefs
-
由 Heinrich Schuchardt 提交于
Call pytest3 with argument -ra to display the reason why Python tests are skipped. The -r flag displays a test summary info for each test. -ra eliminates this info for passed tests. Pros an cons were discussed in: https://lists.denx.de/pipermail/u-boot/2020-June/417090.htmlSigned-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-raspberrypi由 Tom Rini 提交于
- add support for PCI and XHCI for RPi4 (64 bit only) - optionally reset XHCI device on registration - enable USB_KEYBOARD for rpi_4_defconfig
-
由 Tom Rini 提交于
- Bring in Marek Szyprowski's series to allow for arbitrary virtual-physical address mappings.
-
由 Marek Szyprowski 提交于
This requires enabling BRCMSTB PCIe and XHCI_PCI drivers as well as PCI and USB commands. To get it working one has to call the following commands: "pci enum; usb start;", thus such commands have been added to the default "preboot" environment variable. One has to update their environment if it is already configured to get this feature working out of the box. Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com>
-
由 Marek Szyprowski 提交于
Create a non-cacheable mapping for the 0x600000000 physical memory region, where MMIO registers for the PCIe XHCI controller are instantiated by the PCIe bridge. Due to 32bit limit in the CPU virtual address space in ARM 32bit mode, this region is mapped at 0xff800000 CPU virtual address. Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com>
-
由 Seung-Woo Kim 提交于
On build with 32 bit, there is a warning for int-to-pointer-cast. Fix the int to pointer cast by using uintptr_t. Signed-off-by: NSeung-Woo Kim <sw0312.kim@samsung.com> Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com>
-
由 Marek Szyprowski 提交于
Provide function for setting arbitrary virtual-physical MMU mapping and cache settings for the given region. Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Marek Szyprowski 提交于
Update the comments in include/asm/system.h to the common style. Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Marek Szyprowski 提交于
Move ADDR_MAP related config options from include/configs/*.h to the proper place in lib/Kconfig. This has been done using ./tools/moveconfig.py and manual inspection of the generated changes. This is a preparation to use ADDR_MAP helper on ARM 32bit Raspberry Pi4 board for mapping the PCIe XHCI MMIO, which is above the 4GiB identity mapping limit. Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
- 10 7月, 2020 30 次提交
-
-
由 Nicolas Saenz Julienne 提交于
Supporting USB keyboards out of the box is both handy for development and production. Notably if u-boot is used to boot into GRUB. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSylwester Nawrocki <s.nawrocki@samsung.com> Reviewed-by: NBin Meng <bmeng.cn@gmail.com> [mb: drop rpi_4_32b_defconfig hunk] Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
Some atypical users of xhci might need to manually reset their xHCI controller before starting the HCD setup. Check if a reset controller device is available to the PCI bus and trigger a reset. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> [mb: squash fix to only build xhci_reset_hw() if CONFIG_DM_BUS] Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
This is required in order to access the reset controller used to initialize the board's xHCI chip. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
Raspberry Pi 4's co-processor controls some of the board's HW initialization process, but it's up to Linux to trigger it when relevant. Introduce a reset controller capable of interfacing with RPi4's co-processor that models these firmware initialization routines as reset lines. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
On the Raspberry Pi 4, after a PCI reset, VL805's (a xHCI chip) firmware may either be loaded directly from an EEPROM or, if not present, by the SoC's VideCore (the SoC's co-processor). Introduce the function that informs VideCore that VL805 may need its firmware loaded. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Marek Szyprowski 提交于
This requires enabling BRCMSTB PCIe and XHCI_PCI drivers as well as PCI and USB commands. To get it working one has to call the following commands: "pci enum; usb start;", thus such commands have been added to the default "preboot" environment variable. One has to update their environment if it is already configured to get this feature working out of the box. Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: NSylwester Nawrocki <s.nawrocki@samsung.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Sylwester Nawrocki 提交于
This patch adds basic driver PCI Express controller found on Broadcom set-top-box SoCs, e.g. BCM2711. The code is based on Linux upstream driver (pcie-brcmstb.c) with MSI handling removed. The inbound access memory region is not currently parsed from dma-ranges DT property and a fixed 3GB region is used. The patch has been tested on RPI4 board, i.e. on BCM2711 SoC with VL805 USB Host Controller. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: NSylwester Nawrocki <s.nawrocki@samsung.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Sylwester Nawrocki 提交于
Add PCI Express capability definitions required by the Broadcom STB PCIe controller driver. Signed-off-by: NSylwester Nawrocki <s.nawrocki@samsung.com> Reviewed-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
Imports Al Viro's original Linux commit 00b0c9b82663a, which contains an in depth explanation and two fixes from Johannes Berg: e7d4a95da86e0 "bitfield: fix *_encode_bits()", 37a3862e12382 "bitfield: add u8 helpers". Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> [s.nawrocki: added empty lines between functions and macros] Signed-off-by: NSylwester Nawrocki <s.nawrocki@samsung.com> [mb: squash fix including byteorder.h] Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Walter Lozano 提交于
Add a test for dtoc taking into account the cd-gpios property. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
Currently dtoc does not support the property cd-gpios used to declare the gpios for card detect in mmc. This patch adds support to cd-gpios property. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
Several MMC drivers use GPIO for card detection with cd-gpios property in the MMC node pointing to a GPIO node. However, as U-Boot tries to save space by keeping only required nodes using u-boot* properties, several devices tree result in having only in the MMC node but not the GPIO node associated to cd-gpios. This patch, fixes several ocurrence of this issue. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: Adam Ford <aford173@gmail.com> #da850-evm
-
由 Walter Lozano 提交于
Update documentation to reflect the new phandle support when OF_PLATDATA is used. Now phandles are implemented as pointers to U_BOOT_DEVICE, which makes it possible to get a pointer to the actual device. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
In the current implementation, when dtoc parses a dtb to generate a struct platdata it converts the information related to linked nodes as pointers to struct platdata of destination nodes. By doing this, it makes difficult to get pointer to udevices created based on these information. This patch extends dtoc to use struct driver_info when populating information about linked nodes, which makes it easier to later get the devices created. In this context, reimplement functions like clk_get_by_index_platdata() which made use of the previous approach. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
In order to be able to update data in u_boot_list, move this section to make it RW. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
Currently when creating an U_BOOT_DEVICE entry a struct driver_info is declared, which contains the data needed to instantiate the device. However, the actual device is created at runtime and there is no proper way to get the device based on its struct driver_info. This patch extends struct driver_info adding a pointer to udevice which is populated during the bind process, allowing to generate a set of functions to get the device based on its struct driver_info. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
In order to prepare for a new support of phandle when OF_PLATDATA is used drop the const for struct driver_info as this struct will need to be updated on runtime. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
Update the documentation with the support for driver aliases using U_BOOT_DRIVER_ALIAS. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
As dtoc now performs checks for valid driver names, when running dtoc tests several warnings arise as these tests don't use valid driver names. This patch adds an option to disable those warning, which is only intended for running tests. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
Currently dtoc scans dtbs to convert them to struct platdata and to generate U_BOOT_DEVICE entries. These entries need to be filled with the driver name, but at this moment the information used is the compatible name present in the dtb. This causes that only nodes with a compatible name that matches a driver name generate a working entry. In order to improve this behaviour, this patch adds to dtoc the capability of scan drivers source code to generate a list of valid driver names and aliases. This allows to generate U_BOOT_DEVICE entries using valid driver names and rise a warning in the case a name is not valid. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Open files in utf-8 mode: Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
Currently when using OF_PLATDATA the binding between devices and drivers is done trying to match the compatible string in the node with a driver name. However, usually a single driver supports multiple compatible strings which causes that only devices which its compatible string matches a driver name get bound. To overcome this issue, this patch adds the U_BOOT_DRIVER_ALIAS macro, which generates no code at all, but allows an easy way to declare driver name aliases. Thanks to this, dtoc could be improve to look for the driver name based on its alias when it populates the U_BOOT_DEVICE entry. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
Add missing information about internal class members in order to make the code easier to follow. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Walter Lozano 提交于
When using OF_PLATDATA, the bind process between devices and drivers is performed trying to match compatible string with driver names. However driver names are not strictly defined, and also there are different names used when declaring a driver with U_BOOT_DRIVER, the name of the symbol used in the linker list and the used in the struct driver_info. In order to make things a bit more clear, rename the drivers names. This will also help for further OF_PLATDATA improvements, such as checking for valid driver names. Signed-off-by: NWalter Lozano <walter.lozano@collabora.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Add a fix for sandbox of-platdata to avoid using an invalid ANSI colour: Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
This adds a test case to test the functionality of the fdtdec API fdtdec_add_reserved_memory(). Signed-off-by: NBin Meng <bin.meng@windriver.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
It should be "writable". Signed-off-by: NBin Meng <bin.meng@windriver.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Bin Meng 提交于
Add DECLARE_GLOBAL_DATA_PTR since it is referenced in the test codes. Signed-off-by: NBin Meng <bin.meng@windriver.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Heinrich Schuchardt 提交于
When printing the device tree we want to get an output that can be used as input for the device tree compiler. This requires that we do not write bogus lines like pcie@10000000 { interrupt-map = * 0x4000127c [0x00000280]; For instance the QEMU virt device has a property interrupt-map with 640 bytes which exceeds CMD_FDT_MAX_DUMP=64. So lets do away with the artificial limitation to 64 bytes. As indicated in commit f0a29d43 ("fdt: Limit printed hex in fdt print and list commands") if a device tree contains binary blobs, it may still be desirable to limit the output length. Provide environment variable fdt_max_dump for this purpose. Fixes: 5d927b42 ("Kconfig: Drop CONFIG_CMD_FDT_MAX_DUMP") Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Heinrich Schuchardt 提交于
Use the BIT() macro when creating a bitmask for the logging fields. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Heinrich Schuchardt 提交于
The name of the function emitting a log message may be of interest for a developer but is distracting for normal users. See the example below: try_load_entry() Booting: Debian Make the default format for log messages customizable. By default show only the message text. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This warning should only be displayed for C files. Fix it and update the test. Signed-off-by: NSimon Glass <sjg@chromium.org>
-