- 01 9月, 2020 21 次提交
-
-
由 Peng Fan 提交于
Add support to f_sdp to search and load iMX8 container image or iMX8M FIT image by new UUU command SDPV. When using the SDPV, the uuu will continue to send out data after first level boot loader used by ROM. This means uuu won't skip to the offset of the second boot loader, and the padding data before second boot loader will be sent out. So we have to search the FIT header or container header in the buffer that SDP received. Also change to more common method to exit f_sdp handler not depending on SPL_FIT_FOUND flag because container loader won't set this. Signed-off-by: NPeng Fan <peng.fan@nxp.com>
-
由 Ye Li 提交于
Because the buffer length of sdp usb request is 65, we have to allocate 65 bytes not 64 bytes. Otherwise there is potential buffer overflow. Signed-off-by: NYe Li <ye.li@nxp.com> Signed-off-by: NPeng Fan <peng.fan@nxp.com> Reviewed-by: NLukasz Majewski <lukma@denx.de>
-
由 Ye Li 提交于
Add HS endpoint descriptor for SDP. So that we can use high speed endpoint, and the SDP device can send packet with 512 byte size. Signed-off-by: NYe Li <ye.li@nxp.com> Signed-off-by: NPeng Fan <peng.fan@nxp.com> Reviewed-by: NLukasz Majewski <lukma@denx.de>
-
由 Frank Li 提交于
Need initialize UDC before run sdp download Signed-off-by: NFrank Li <Frank.Li@nxp.com> Signed-off-by: NPeng Fan <peng.fan@nxp.com>
-
由 Jassi Brar 提交于
MAX3420 implements FullSpeed USB Device over SPI. Another version MAX3421, also implements USB Host mode. This driver should be good for the device mode of max3421 as well. Signed-off-by: NJassi Brar <jaswinder.singh@linaro.org>
-
由 Roman Kovalivskyi 提交于
Default implementation of fastboot_set_reboot_flag function that depends on "bcb" commands could be used in general case if there are no need to make any platform-specific implementation, otherwise it could be disabled via Kconfig option FASTBOOT_USE_BCB_SET_REBOOT_FLAG. Please note that FASTBOOT_USE_BCB_SET_REBOOT_FLAG is mutually exclusive with some platforms which already have their own implementation of this function. Signed-off-by: NRoman Kovalivskyi <roman.kovalivskyi@globallogic.com>
-
由 Roman Kovalivskyi 提交于
Android 10 adds support for dynamic partitions and in order to support this userspace fastboot must be used[1]. New tool fastbootd is included into recovery. Userspace fastboot works from recovery and is launched if: 1) - Dynamic partitioning is enabled 2) - Boot control block has 'boot-fastboot' value into command field The bootloader is expected to load and boot into the recovery image upon seeing boot-fastboot in the BCB command. Recovery then parses the BCB message and switches to fastbootd mode[2]. Please note that boot script is expected to handle 'boot-fastboot' command in BCB and load into recovery mode. Bootloader must support 'reboot fastboot' command which should reboot device into userspace fastboot to accomodate those changes[3]. Another command that bootloader must support[3] is 'reboot recovery'. This command should simply reboot device into recovery mode. [1] - https://source.android.com/devices/bootloader/fastbootd [2] - https://source.android.com/devices/bootloader/fastbootd#unified_fastboot_and_recovery [3] - https://source.android.com/devices/bootloader/fastbootd#modifications_to_the_bootloaderSigned-off-by: NRoman Kovalivskyi <roman.kovalivskyi@globallogic.com> Signed-off-by: NRoman Stratiienko <r.stratiienko@gmail.com> Change-Id: I9d2bdc9a6f6f31ea98572fe155e1cc8341e9af76
-
由 Roman Kovalivskyi 提交于
Extend fastboot_set_reboot_flag arguments with reboot reason so that it could handle different reboot cases in future. Signed-off-by: NRoman Kovalivskyi <roman.kovalivskyi@globallogic.com>
-
由 Heinrich Schuchardt 提交于
The environment variable loadaddr is in the virtual address space of the sandbox. To get the actual memory address where the FIT image has been loaded we have to convert this address according to the memory mapping of the sandbox. Equally the addresses in the *.its file have to be converted when used in the dfu_ram driver. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
For testing automated updates via dfu and mtd we need the dfu and mtd commands as well as preboot support. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Function mtdparts_init() is needed for the DFU MTD driver. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
%s/parameteres/parameters/g Even if a line exceeds 80 characters we should not split output strings to make debugging easier. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Filip Brozovic 提交于
Add support for defining raw fastboot partitions in eMMC by specifying the offset and size in an environment variable. Optionally, the eMMC hardware partition number may also be specified. This makes it possible to e.g. update only part of the eMMC boot partition, instead of having to write the entire partition. Signed-off-by: NFilip Brozovic <fbrozovic@gmail.com>
-
由 Ye Li 提交于
When unregister gadget driver in ci_udc, the usb device is not removed or stop. This causes next "usb start" fails to work. Add a new interface "usb_remove_ehci_gadget" in usb-uclass to remove the usb device for DM driver. Using "usb_lowlevel_stop" for non-DM driver. Signed-off-by: NYe Li <ye.li@nxp.com> Signed-off-by: NPeng Fan <peng.fan@nxp.com>
-
由 Ye Li 提交于
The usb mass storage (f_mass_storage.c) uses fixed usb index 0, this causes problem while CDNS3 USB controller index is 1. Modify the API of fsg to pass the controller index. Reviewed-by: NJun Li <jun.li@nxp.com> Signed-off-by: NYe Li <ye.li@nxp.com> Signed-off-by: NPeng Fan <peng.fan@nxp.com>
-
由 Hayes Wang 提交于
This is used to support RTL8153B and RTL8154B. Signed-off-by: NHayes Wang <hayeswang@realtek.com>
-
由 Hayes Wang 提交于
The original rtl_clear_bp() is used to clear the firmware of both PLA and USB MCU. The new one could clear the firmware of PLA or USB independently. It is unnecessary to clear firmware, if there is no one to be updated. Besides, clear the firmware by writing the relative registers in bulk. Signed-off-by: NHayes Wang <hayeswang@realtek.com>
-
由 Hayes Wang 提交于
Some settings of PHY have to work after resetting PHY. Signed-off-by: NHayes Wang <hayeswang@realtek.com>
-
由 Hayes Wang 提交于
Reset bmu after disabling Tx/Rx. This is used to clear the FIFO of Tx/Rx. The remained data may be transferred after Tx/Rx is re-enabled. And it results in garbage data. Signed-off-by: NHayes Wang <hayeswang@realtek.com>
-
由 Masahiro Yamada 提交于
I am leaving Socionext. Orphan the UniPhier platform until somebody takes the role. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-ti由 Tom Rini 提交于
- Update to ABI 3.0 - Fix i2c write in eeprom driver
-
- 31 8月, 2020 19 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-marvell由 Tom Rini 提交于
- MVEBU Espressobin fixes and enhancements (fix switch security issue, enable MVNETA, enable SD-card, fix COMPHY nodes, default env variables, etc) - MMC Xenon: Set signal voltage and max base clock - a37xx PCI driver: Depend on DM_GPIO and remove #ifdef's
-
由 Pali Rohár 提交于
Include information about permanent ethernet MAC address and add link how to build ATF as U-Boot on Espressobin cannot be flashed without ATF. Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NStefan Roese <sr@denx.de>
-
由 Pali Rohár 提交于
Boot scripts for existing Espressobin Linux distributions, like OpenWRT, expect that U-Boot set fdt_addr and kernel_addr envs. So add env aliases from fdt_addr_r and kernel_addr_r values. Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Pali Rohár 提交于
Current loadaddr is not writable on Espressobin and 'loadb' command cause rebooting board. Marvell's U-Boot already set default loadaddr to value 0x06000000 [1] and after this change 'loadb' is working fine. [1] - https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/commit/0a5b159806baa0746b6449920e450498bc269ba7Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Pali Rohár 提交于
According to Marvell's U-Boot description [1] current env load addresses overlaps with ATF RT services region and TEE. Because the ATF RT service and TEE region is going to be marked as secure and can't be overwritten, use different different addresses for envs. [1] - https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/commit/0a5b159806baa0746b6449920e450498bc269ba7Signed-off-by: NPali Rohár <pali@kernel.org> Tested-by: NAndre Heider <a.heider@gmail.com> Reviewed-by: NStefan Roese <sr@denx.de>
-
由 Pali Rohár 提交于
For proper initialization of aardvark pci driver it is required to de-assert reset GPIO. So depeneds on DM_GPIO option. Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Pali Rohár 提交于
Due to different partition layouts in different U-Boot versions, DTS for Espressobin in Linux does not contain any definition of MTD partitions. See commit https://git.kernel.org/stable/c/00954566464a4 for more details. This patch via ft_board_setup() hook fills current partition layout used by U-Boot, so booted kernel would see correct MTD partitions layout. U-Boot env partition is calculated from CONFIG_ENV_OFFSET option. First partition contains secure firmware, ARM trusted firmware and U-Boot with checksums. So it is not possible to replace just one image (e.g. U-Boot) without updating other parts where is stored checksum of U-Boot. Therefore there is no extra partition defined for U-Boot and first partition is called just 'firmware'. Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Pali Rohár 提交于
Espressobin board comes with Marvell's U-Boot version where U-Boot env is stored in SPI at offset 0x3F0000. This patch changes env offset in Espressobin defconfig file to match Marvell's U-Boot version. Users who want to use previous or different env offset can still change it in .config file when compiling U-Boot. Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Wilson Ding 提交于
Enabled SDIO slot 0 (south bridge) for SD card on Espressobin board. Change-Id: I51a2debf9fba276b9c4a2bc6da91328d47f443e3 Signed-off-by: NWilson Ding <dingwei@marvell.com> Signed-off-by: NKonstantin Porotchkin <kostap@marvell.com> Reviewed-on: http://vgitil04.il.marvell.com:8080/60945Tested-by: NiSoC Platform CI <ykjenk@marvell.com> Reviewed-by: NIgal Liberman <igall@marvell.com> [pali: Define cd-gpios and enable CONFIG_DM_REGULATOR_GPIO] Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Evan Wang 提交于
- The SDIO signal voltage and max base clock frequency setting are missing in driver, which causes SDIO not working. - The patch adds SDIO signal voltage switch support, which is based on regulator-gpio of vqmmc-supply, and sets the max base clock frequency. - Fix the zero clock value in call to sdhci_setup_cfg() function. Change-Id: I79c8860c65b8db166f4f70db56ede4097f71f1fa Signed-off-by: NEvan Wang <xswang@marvell.com> Reviewed-on: http://vgitil04.il.marvell.com:8080/53589Reviewed-by: NHua Jing <jinghua@marvell.com> Tested-by: NHua Jing <jinghua@marvell.com> [pali: Amended fixup patch] Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Pali Rohár 提交于
This change ensures that PCIe card is put into reset state when U-Boot stops using it. DM_FLAG_OS_PREPARE ensures that U-Boot executes driver's remove callback prior booting Linux kernel. Linux kernel pci-aardvark driver needs to reset PCIe card via PERST# signal prior initializing it. If it does not issue reset then some PCIe cards (specially Compex WiFi cards) are not detected at all. Putting PCIe card into reset state prior booting Linux kernel would ensure that card would be properly reset at time when Linux kernel starts initializing pci-aardvark driver. Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Pali Rohár 提交于
Change active-high to active-low and change DT property name from reset-gpio to reset-gpios. This format of gpio reset is used by pci-aardvark driver in Linux kernel. Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NStefan Roese <sr@denx.de> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Marek Behún 提交于
This commit fixes initialization of COMPHY on EspressoBin. Commit 22f41893 ("phy: marvell: a3700: Use comphy_mux on Armada 37xx.") introduced usage of comphy_mux on Armada 37xx comphy driver. The lanes are defined in comphy_a3700.c as described in functional specification, that is: lane 0 is SGMII1 or USB3 lane 1 is PCIe or SGMII0 lane 2 is SATA or USB3 But the DTS for EspressoBin configures PCIe on lane 0 and USB3 on lane 1, which is wrong in the sense of the specification and doesn't work with the comphy_mux code, which is 2 years now (the aardvark driver causes synchronous abort in U-Boot). It worked till the above mentioned commit, because the code for powering up PCIe PHY doesn't work with lane number at all, and the code for powering up USB3 PHY works differently only if USB3 is on lane 2, ie. the check goes like: if (lane == 2) something else something else so it does not differentiate between lanes 0 and 1. In the future I shall post patches that remove the comphy_a3700 driver and add comphy driver which uses calls to ATF, like Linux' driver does. This will have the advantage of same DTS bindings as Linux', but till this is done, we need this patch. Signed-off-by: NMarek Behún <marek.behun@nic.cz> Tested-by: NPali Rohár <pali@kernel.org> Cc: Stefan Roese <sr@denx.de> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Pali Rohár 提交于
Espressobin uses mvneta ethernet driver. Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Pali Rohár 提交于
By default Topaz switch on Espressobin board forwards packets between all ethernet ports, including CPU (port 0), wan (port 1) and lan (ports 2,3). This default U-Boot setup is unsuitable for using Espressobin as router as it opens security hole in forwarding all packets between wan and lan ports. E.g. dhcp packets from wan network leaks to lan network during small time window until U-Boot boots Linux kernel which loads network drivers which disallows forwarding between wan and lan. This patch fixes above problem. For Espressobin board prior putting Topaz switch into forwarding mode, Topaz switch is reconfigured to allow forwarding packets from wan and lan ports only to CPU port. This ensures that packets from wan port are not forwarded to lan ports and vice-versa. Packets from CPU port are still forwarded to all other ports, so U-Boot network boot works with any ethernet port as before. This problem was already discussed on Espressobin forum [1] and on Marvell's github issue tracker [2]. As a workaround people on Espressobin forum patched U-Boot to completely disable lan ports on Topaz switch which prevented forwarding packets. That workaround had an issue that U-Boot was unable to netboot via lan ports anymore. Change in this patch does not have such issue. This security issue has been dicussed here as well: [3]. [1] - https://web.archive.org/web/20191231164238/http://espressobin.net/forums/topic/boot-behavior-of-the-switch-and-security/ [2] - https://github.com/MarvellEmbeddedProcessors/u-boot-marvell/issues/18 [3] - https://forum.armbian.com/topic/12635-espressobin-uboot-security-concerns-switch-init-portmask/Signed-off-by: NPali Rohár <pali@kernel.org> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NAndre Heider <a.heider@gmail.com>
-
由 Michal Simek 提交于
There shouldn't be a need to call additional i2c read if above failed already. Based on comment it should be enough to try to detect legacy boards which are mentioned in the comment. Fixes: 2463f672 ("ti: common: board_detect: Allow DM I2C without CONFIG_DM_I2C_COMPAT") Fixes: 0bea813d ("ARM: omap-common: Add standard access for board description EEPROM") Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Lokesh Vutla 提交于
Update the ringacc and udma dt nodes to use the latest RM resource types similar to the ones used in k3-j721e dt nodes. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
struct ti_sci_rm_type_map is no longer used. Drop its definition and its declarations. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Lokesh Vutla 提交于
With ABI 3.0, sysfw deprecated special resource types used for AM65x SoC. Instead started using device id as resource type similar to the convention used in J721E SOC. Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-