- 21 2月, 2021 1 次提交
-
-
由 Jesper Schmitz Mouridsen 提交于
The last block is of size media->block_size Signed-off-by: NJesper Schmitz Mouridsen <jesper@schmitz.computer> Simplify expression. Apply same change to efi_disk_write_blocks(). Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
- 20 2月, 2021 6 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-sunxi由 Tom Rini 提交于
- H616 clock fix to enable video PLL - sunxi-common.h cleanups - support for UART1 as the console on sun8i - removing wrong linux,stdout-path from DTs
-
由 Andre Przywara 提交于
OF_STDOUT_PATH was meant to hold the devicetree path to the serial console, to be put into the linux,stdout-path property of the chosen node. The only user of that was sunxi, and it was actually wrong for years there: the paths hardcoded in sunxi_common.h were not matching the DTs, evident by the leading 0's in nodenames, which have been removed years ago. On top of that, "linux,stdout-path" is now deprecated for a while (Linux commit 2a9d832cc9aae from November 2014), and also all modern DTs (including those included in U-Boot) carry a "stdout-path" property already. So remove the stanza from sunxi_common.h, and, since this was the last user, also remove the associated bits from the rest of U-Boot. Signed-off-by: NAndre Przywara <andre.przywara@arm.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Tobias Schramm 提交于
The A23, A33, H3, H5, A83T, V3 and Sochip S3 sun8i SoCs can mux uart1 on GPIOs PG6 and PG7. This patch adds support for using uart1 on those pins as boot console. Signed-off-by: NTobias Schramm <t.schramm@manjaro.org> Reviewed-by: NAndre Przywara <andre.przywara@arm.com> Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
-
由 Samuel Holland 提交于
As variables were moved to Kconfig, some of the surrounding ifdefs were left around, even though they were empty. Clean them up. Signed-off-by: NSamuel Holland <samuel@sholland.org> Reviewed-by: NAndre Przywara <andre.przywara@arm.com> Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
-
由 Jernej Skrabec 提交于
It turns out that there is a magic bit in PRCM region which seemingly makes PLLs work if it's enabled. Sadly, there is no documentation what it does exactly, so we'll just mimick BSP boot0 behaviour and enable it before any clock is set up. Fixes: b18bd53d ("sunxi: introduce support for H616 clocks") Signed-off-by: NJernej Skrabec <jernej.skrabec@siol.net> Reviewed-by: NAndre Przywara <andre.przywara@arm.com> Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-mmc由 Tom Rini 提交于
- mmc_spi improvement - added mmc-pwrseq to remove duplicated code - fix response timeout after switch command - sdhci: skip cache invalidation if DMA is not used
-
- 19 2月, 2021 14 次提交
-
-
由 Jaehoon Chung 提交于
Enable CONFIG_MMC_PWRSEQ configuration about boards that is using rockchip_dw_mmc driver. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Jaehoon Chung 提交于
Before time, PWRSEQ is selected since below commit. commit 262d3436 ("board: amlogic: select PWRSEQ for all amlogic platform") Select MMC_PWRSEQ config because of introducing CONFIG_MMC_PWRSEQ for only eMMC module. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Jaehoon Chung 提交于
Use mmc_pwrseq instead of rockchip_mmc_pwrseq. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Jaehoon Chung 提交于
Use mmc_pwrseq instead of meson_mmc_pwrseq. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com> Acked-by: NNeil Armstrong <narmstrong@baylibre.com>
-
由 Jaehoon Chung 提交于
Add mmc-pwrseq file to provide a generic interface. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Bin Meng 提交于
mmc_spi_sendcmd(), mmc_spi_readdata() and mmc_spi_writedata() are currently undocumented. Add comment blocks to explain the arguments and the return value. Signed-off-by: NBin Meng <bin.meng@windriver.com> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Bin Meng 提交于
After command is sent and before card response shows up on the line, there is a variable number of clock cycles in between called Ncr. The spec [1] says the minimum is 1 byte and the maximum is 8 bytes. Current logic in mmc_spi_sendcmd() has a flaw that it could only work with certain SD cards with their Ncr being just 1 byte. When resp_match is false, the codes try to receive only 1 byte from the SD card. On the other hand when resp_match is true, the logic happens to be no problem as it loops until timeout to receive as many bytes as possible to see a match of the expected resp_match_value. However not every call to mmc_spi_sendcmd() is made with resp_match being true hence this exposes a potential issue with SD cards that have a larger Ncr value. Given no issue was reported as of today, we can reasonably conclude that all cards being used on the supported boards happen to have a 1 byte Ncr timing requirement. But a broken case can be triggered by utilizing QEMU to emulate a larger value of Ncr (by default 1 byte Ncr is used on QEMU). This commit fixes such potential spec violation to improve the card compatibility. [1] "Physical Layer Specification Version 8.00" chapter 7.5.1: Command / Response chapter 7.5.4: Timing Values Signed-off-by: NBin Meng <bin.meng@windriver.com> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Bin Meng 提交于
The argument check should happen before any transfer on the SPI lines. Signed-off-by: NBin Meng <bin.meng@windriver.com> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Bin Meng 提交于
Add some verbose debug output when crc16 check fails. Signed-off-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Stefan Bosch 提交于
After issuing the switch command: Wait until 'current state' of the card status becomes 'tran'. This prevents from response timeout at the next command because of 'current state' = 'data'. Signed-off-by: NStefan Bosch <stefan_b@posteo.net> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Yuezhang.Mo@sony.com 提交于
If DMA(SDMA or ADMA) is not used, the cache invalidation after reading is no need, should be skipped. Otherwise U-Boot may hang at the cache invalidation. Found this issue and tested this fix on DragonBoard 410c. Fixes: commit 4155ad9a ("mmc: sdhci: fix missing cache invalidation after reading by DMA") Signed-off-by: NYuezhang.Mo <Yuezhang.Mo@sony.com> Reviewed-by: NAndy Wu <Andy.Wu@sony.com>
-
由 Jaehoon Chung 提交于
It's confusing whether arguments are optional or mandatory. Update the command's usage to clarify how to use. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Jaehoon Chung 提交于
Initialize an err variable to 0. Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com> Reported-by: Coverity (CID: 313548) Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
- Improve interactions between SPL / OP-TEE and Linux in FIT images
-
- 18 2月, 2021 19 次提交
-
-
由 Ramon Fried 提交于
in tftpboot, if ack was already sent previously for this packet, don't send again. Fixes: cc6b87ec ("net: tftp: Add client support for RFC 7440") Reported-by: NSuneel Garapati <suneelglinux@gmail.com> Signed-off-by: NRamon Fried <rfried.dev@gmail.com> Tested-by: NSuneel Garapati <suneelglinux@gmail.com> Tested-by: NOliver Graute <oliver.graute@kococonnector.com>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-raspberrypi由 Tom Rini 提交于
- add iProc RNG2000 driver for RPi4 - add support for CM4 and RPi400
-
由 Nicolas Saenz Julienne 提交于
The 'brcm,bcm2711-hdmi0' compatible string is used on RPi4 instead of 'brcm,bcm2835-hdmi' since the IP core was upgraded (now called VC6 instead of VC4). This has no functional change as far as u-boot driver is concerned. So simply add the compatible string. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
The DM_DMA option is needed in order to translate physical address into bus addresses on a per-device basis. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
This will allow us to use DM variants of phys_to_bus()/bus_to_phys() when relevant. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
So far we've been content with passing physical addresses when configuring memory addresses into XHCI controllers, but not all platforms have buses with transparent mappings. Specifically the Raspberry Pi 4 might introduce an offset to memory accesses incoming from its PCIe port. Introduce xhci_virt_to_bus() and xhci_bus_to_virt() to cater with these limitations, and make sure we don't break non DM users. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NPeter Robinson <pbrobinson@gmail.com> [mb: fix compilation for 32 bit] Signed-off-by: NMatthias Brugger <mbrugger@suse.com> fix from nicolas
-
由 Nicolas Saenz Julienne 提交于
By reusing DT nodes already available in sandbox's test DT introduce a test to validate dev_phys_to_bus()/dev_bus_to_phys(). Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
These functions, instead of relying on hard-coded platform-specific address translations, make use of the DMA constraints provided by the DM core. This allows for per-device translations. We can't yet get rid of the legacy phys_to_bus()/bus_to_phys() implementations as some of its users are not integrated into the device model. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
Add test to validate dev->dma_offset is properly set on devices. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
Calculating the DMA offset between a bus address space and CPU's every time we call phys_to_bus() and bus_to_phys() isn't ideal performance wise, as it implies traversing the device tree from the device's node up to the root. Since this information is static and available before the device's initialization, parse it before the probe call an provide the DMA offset in 'struct udevice' for the address translation code to use it. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
Introduce some new nodes in sandbox's test device-tree and dm tests in order to validate dev_get_dma_range(). Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
Add the following functions to get a specific device's DMA ranges: - dev_get_dma_range() - ofnode_get_dma_range() - of_get_dma_range() - fdt_get_dma_range() They are specially useful in oder to be able validate a physical address space range into a bus's and to convert addresses from and to address spaces. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
So far we've assumed a fixed configuration for inbound windows as we had a single user for this controller. But the controller's DMA constraints were improved starting with BCM2711's B1 revision of the SoC, notably available in CM4 and Pi400. They allow for wider inbound windows. We can now cover the whole address space, whereas before we where limited to the lower 3GB. This information is passed to us through DT's 'dma-ranges' property and it's specially important for us to honor it since some interactions with the board's co-processor assume we're doing so (specifically the XHCI firmware load operation, which is handled by the co-processor after u-boot has correctly configured the PCIe controller). Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
The Raspberry Pi Foundation released the new Compute Module 4 which we want to detect, so we can enable Ethernet on it and know the correct device tree file name. Note that this sets the Ethernet option to true since the official CM4 IO board has an Ethernet port. But that might not be the case when using custom ones. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NPeter Robinson <pbrobinson@gmail.com> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
The Raspberry Pi Foundation released the new RPi400 which we want to detect, so we can enable Ethernet on it and know the correct device tree file name. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by: NPeter Robinson <pbrobinson@gmail.com> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Marek Szyprowski 提交于
When RPi4 is booted from USB Mass Storage, the firmware reports 947MiB of the ARM memory (948 in case of the standard SD-card boot). This value is not MMU_SECTION_SIZE aligned, so the dram_bank_mmu_setup() skips mapping of the last 1MiB. This later causes u-boot in ARM 32bit mode to freeze, because it relocated itself into that unmapped memory and fails to execute. Fix this by limiting the size of the first bank to the multiple of MMU_SECTION_SIZE. Signed-off-by: NMarek Szyprowski <m.szyprowski@samsung.com> Reviewed-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Tested-by: NJaehoon Chung <jh80.chung@samsung.com> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
Make sure we handover the PCIe controller in a clean state. Some of the devices hanging from the PCIe bus might need to be properly reset through #PERST in order for Linux to be able to initialize them. This is specially important in order to properly initialize Raspberry Pi 4 B and 400's USB chip. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Nicolas Saenz Julienne 提交于
The PCIe bus the controller is connected to might need to be removed prior the handover. Make sure xhci-pci is also removed so as to avoid unexpected timeouts or hangs. Signed-off-by: NNicolas Saenz Julienne <nsaenzjulienne@suse.de> Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-
由 Matthias Brugger 提交于
We find the iProc RNG200 in the Raspberry Pi 4. Add it to all it's config so that it can be used. Signed-off-by: NMatthias Brugger <mbrugger@suse.com> Tested-by: NPeter Robinson <pbrobinson@gmail.com> [mb: drop rpi_4_32b_defconfig] Signed-off-by: NMatthias Brugger <mbrugger@suse.com>
-