- Jun 17, 2021
-
-
The EXPU1 design is a new 40G capable ethernet service unit card for Hitachi-Powergrids wired-com product lines. The base SoC is same as for already added SELI8 card, consequently the already added u-boot support for SELI8 is reused. Signed-off-by:
Rainer Boschung <rainer.boschung@hitachi-powergrids.com> Signed-off-by:
Aleksandar Gerasimovski <aleksandar.gerasimovski@hitachi-powergrids.com> [Fixed new line error at EOF] Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Add "Priyanka Jain <priyanka.jain@nxp.com>" as MAINTAINER for t102xrdb board. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Add "Priyanka Jain <priyanka.jain@nxp.com>" as MAINTAINER for p2041rdb board. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Add "Priyanka Jain <priyanka.jain@nxp.com>" as MAINTAINER for p1_p2_rdb_pc board. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Priyanka Jain authored
Add "Priyanka Jain <priyanka.jain@nxp.com>" as MAINTAINER for t4rdb board. Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Address and size cells on SOC are set to 1. But gpio nodes are specified with 2 cells. This fixes the gpio nodes to correct cells. Signed-off-by:
Lasse Klok Mikkelsen <lkmi@prevas.dk> Reviewed-by:
Rasmus Villemoes <rasmus.villemoes@prevas.dk> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Current tsec adapter sets adapter gigabit capabilities by default, and in reality this must not always be the case. It is possible that tsec adapter is used for 100Mbps connection, and in this case setting 1000Mbps capabilities can lead to some side effects such longer autoneg process. In our ls102x designs this problem leads to long autoneg times (> 4 sec) in case board rgmii link is 100Mbps capable only. Limiting the rgmii link capabilities provides faster and smoother link establishment. Signed-off-by:
Aleksandar Gerasimovski <aleksandar.gerasimovski@hitachi-powergrids.com> Reviewed-by:
Vladimir Oltean <vladimir.oltean@nxp.com> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Commit df86d324 breaks linux kernel and product application boot. Linux kernel and our product application scripts are expecting 0x prefix for hexadecimal values, while env_set_hex writes them without a prefix. This patch partially revert env_set_hex usage for affected env variables. Signed-off-by:
Aleksandar Gerasimovski <aleksandar.gerasimovski@hitachi-powergrids.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
During the mainlining of the board this was by mistake set to sector size. Our user space env scripts are expecting envsize of 0x4000, and setting this differently will break our cross-platform compatibility. Signed-off-by:
Aleksandar Gerasimovski <aleksandar.gerasimovski@hitachi-powergrids.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Drop CONFIG_SYS_FSL_MMC_HAS_CAPBLT_VS33. CONFIG_FSL_ESDHC_VS33_NOT_SUPPORT is used instead. Signed-off-by:
Yangbo Lu <yangbo.lu@nxp.com> Acked-by: Michael Walle <michael@walle.cc> [for kontron-sl28] Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
There is no i.MX board using such option. Drop it. Signed-off-by:
Yangbo Lu <yangbo.lu@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
For eSDHC, power supply is through peripheral circuit. Some eSDHC versions have value 0 of the bit but that does not reflect the truth. 3.3V is common for SD/MMC, and is supported for all boards with eSDHC in current u-boot. So, make 3.3V is supported in default in code. CONFIG_FSL_ESDHC_VS33_NOT_SUPPORT can be enabled if future board does not support 3.3V. This is also a fix-up for one previous patch, which converted to use IS_ENABLED() for CONFIG_SYS_FSL_MMC_HAS_CAPBLT_VS33 that is not a Kconfig option. Fixes: 52faec31 ("mmc: fsl_esdhc: replace most #ifdefs by IS_ENABLED()") Signed-off-by:
Yangbo Lu <yangbo.lu@nxp.com> Reviewed-by:
Jaehoon Chung <jh80.chung@samsung.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
These boards, according to the schematic and per the board I own, use an M24256-BWDW6TP I2C EEPROM which requires two address bytes. This fixes the 'mac' command which is used to program, among other things, the MAC addresses for the ethernet interfaces on the board. Signed-off-by:
Matt Merhar <mattmerhar@protonmail.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
IFC NOR flash base address of ls2088a is 0x580000000, and offset of env crc is 0x500000, so fix the macro CONFIG_ENV_ADDR to fix synchronous exception(access illegal address) Fixes: 59071804 ("configs: ls2080a: Correct ENV_ADDR value") Signed-off-by:
Biwen Li <biwen.li@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Signed-off-by:
Kuldeep Singh <kuldeep.singh@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Add properties related to eMMC HS400 mode for esdhc1. Signed-off-by:
Yangbo Lu <yangbo.lu@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Stop to initialize the PCIe controller if it's disabled by RCW. Fixes: 118e58e2 ("pci: layerscape: Split the EP and RC driver") Signed-off-by:
Hou Zhiqiang <Zhiqiang.Hou@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Read Linux PPFE firmware from flash partition and pass it to Linux through FDT entry. So that we can avoid placing PPFE firmware in Linux rootfs. (FDT may increase at max by 64KB) Signed-off-by:
Chaitanya Sakinam <chaitanya.sakinam@nxp.com> Signed-off-by:
Anji J <anji.jagarlmudi@nxp.com> Signed-off-by:
Biwen Li <biwen.li@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Enable eMMC HS400 workarounds for LX2160A/LX2162A. Signed-off-by:
Yangbo Lu <yangbo.lu@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
For cpu release command, check whether PSCI is supported firstly, if supported, use PSCI to kick off secondary cores, otherwise still use spin table. Signed-off-by:
Jiafei Pan <Jiafei.Pan@nxp.com> [Fixed checkpatch alignment CHECKs] Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Add check for return value of adjust_vdd() Signed-off-by:
Biwen Li <biwen.li@nxp.com> Signed-off-by:
Priyanka Singh <priyanka.singh@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
- Jun 16, 2021
-
-
When using bootefi to boot a EFI binary, u-boot is supposed to provide networking service for EFI application. Currently, 'pfe stop' command is called from bootcmd before running bootefi. As a result network stops working for EFI applications and console is flooded with "Rx pkt not on expected port" messages. Implement board_quiesce_devices() for ls1012a boards and call pfe_command_stop() from it instead of calling 'pfe stop' from *_bootcmd and bootcmd. Tested-by:
Anji Jagarlmudi <anji.jagarlmudi@nxp.com> Signed-off-by:
Mian Yousaf Kaukab <ykaukab@suse.de> Reviewed-by:
Ramon Fried <rfried.dev@gmail.com> [Fixed checkpatch space error] Signed-off-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
It was noticed that the clock isn't continuously enabled when there is no link. This is because the 125MHz clock is derived from the internal PLL which seems to go into some kind of power-down mode every once in a while. The LS1028A expects a contiuous clock. Thus enable the PLL all the time. Also, the RGMII pad voltage is wrong, it was configured to 2.5V (that is the VDDH regulator). The correct voltage is 1.8V, i.e. the VDDIO regulator. Signed-off-by:
Michael Walle <michael@walle.cc> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
Add required CONFIG_NXP_ESBC for ls1046afrwy to enable ESBC Chain of Trust. Signed-off-by:
Manish Tomar <manish.tomar@nxp.com> Reviewed-by:
Priyanka Jain <priyanka.jain@nxp.com>
-
- Jun 15, 2021
-
-
https://source.denx.de/u-boot/custodians/u-boot-marvellTom Rini authored
- Turris: Fix bootcmd_rescue (Pali)
-
One of the points of putting the rescue boot command into default environment is that user can invoke it without physical access to the board (without having to press the factory reset button), by running run bootcmd_rescue in U-Boot's console. Therefore we have to ensure that bootcmd_rescue is always set to default value, regardless of whether the factory reset button was pressed. Otherwise the variable will be empty for example after upgrade from previous U-Boot. Fixes: ec3784d6 ("arm: mvebu: turris_mox: add support for board rescue mode") Fixes: 176c3e77 ("arm: mvebu: turris_omnia: support invoking rescue boot from console") Signed-off-by:
Pali Rohár <pali@kernel.org> Signed-off-by:
Marek Behún <marek.behun@nic.cz> Reviewed-by:
Stefan Roese <sr@denx.de>
-
- Jun 11, 2021
-
-
https://source.denx.de/u-boot/custodians/u-boot-microblazeTom Rini authored
Xilinx changes for v2021.07-rc5 zynqmp: - Fix ANALOG_BUS value after powerup - Disable EFI_CAPSULE_ON_DISK_EARLY zynqmp-gqspi: - Fix write issue
-
Michal Simek authored
Sata/scsi and usb based devices are not started at this stage that's why disks are not found and early update can't happen. It is because of deficiency in the UEFI implementation which is not able to deal with block devices which are added or removed after initialization. EFI capsule on disk early feature needs to be fixed first to be able to enable this feature properly. Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
Ashok Reddy Soma authored
Enable manual start in zynqmp_qspi_fill_gen_fifo(). Also enable GQSPI_IXR_GFNFULL_MASK and check for it instead of GQSPI_IXR_GFEMTY_MASK. Add dummy write to genfifo register in chipselect. Signed-off-by:
Ashok Reddy Soma <ashok.reddy.soma@xilinx.com>
-
Adrian Fiergolski authored
The default register configuration after powerup for PSSYSMON_ANALOG_BUS register is incorrect. Hence, fix this in SPL by writing correct fixed value. It follows UG1085 chapter 'PS SYSMON Analog_Bus' and reflects commit sw_apps:zynq ("056ca65d44549ce27f716d423e8dfdefeee7440c") in Xilinx:embeddedsw[1]. [1] https://github.com/Xilinx/embeddedsw Signed-off-by:
Adrian Fiergolski <adrian.fiergolski@fastree3d.com> Signed-off-by:
Michal Simek <michal.simek@xilinx.com>
-
- Jun 10, 2021
-
-
https://source.denx.de/u-boot/custodians/u-boot-marvellTom Rini authored
- mvebu: Turris MOX misc updates (cmds, rescue mode, LED's etc) (Marek) - mvebu: correct Armada 8K addresses (Heinrich)
-
0x04000000- 0x06000000 is reserved memory. We cannot load to anything here. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by:
Stefan Roese <sr@denx.de>
-
Enable configuration options to support Turris network boot. This includes FIT support and some crypto commands. Signed-off-by:
Marek Behún <marek.behun@nic.cz> Reviewed-by:
Pali Rohár <pali@kernel.org> Reviewed-by:
Stefan Roese <sr@denx.de>
-
Add nodes for SPI NOR partitions to the device tree of Turris MOX, as are in Linux' device tree. Signed-off-by:
Marek Behún <marek.behun@nic.cz> Reviewed-by:
Stefan Roese <sr@denx.de>
-
Add default fdtfile environment variable with value marvell/armada-3720-turris-mox.dtb. This can be useful for some boot scenarios. Signed-off-by:
Marek Behún <marek.behun@nic.cz> Reviewed-by:
Pali Rohár <pali@kernel.org> Reviewed-by:
Stefan Roese <sr@denx.de>
-
Configure blinking on ethernet PHY LEDs on the MOX A board when entering rescue mode via reset button. Signed-off-by:
Marek Behún <marek.behun@nic.cz> Reviewed-by:
Pali Rohár <pali@kernel.org> Reviewed-by:
Stefan Roese <sr@denx.de>
-
Add necessary config options and board code to support board factory reset / rescue mode on Turris MOX. In order to also support invoking rescue mode from U-Boot console, without having to press the factory reset button, put the rescue command into `bootcmd_rescue` default environment variable. When factory reset button is pressed, invoke rescue mode via distroboot by setting `boot_targets` to `rescue`. Rescue boot from console can be invoked by running run bootcmd_rescue Signed-off-by:
Marek Behún <marek.behun@nic.cz> Reviewed-by:
Pali Rohár <pali@kernel.org> Reviewed-by:
Stefan Roese <sr@denx.de>
-
Add nodes for indicator LED and reset button so that board code can implement board factory reset mechanism. Signed-off-by:
Marek Behún <marek.behun@nic.cz> Reviewed-by:
Pali Rohár <pali@kernel.org> Reviewed-by:
Stefan Roese <sr@denx.de>
-
The fragmented files were not correctly read because of two issues: - The squashfs_file_info struct has a field named 'comp', which tells if the file's fragment is compressed or not. This field was always set to 'true' in sqfs_get_regfile_info and sqfs_get_lregfile_info. It should actually take sqfs_frag_lookup's return value. This patch addresses these two assignments. - In sqfs_read, the fragments (compressed or not) were copied to the output buffer through a for loop which was reading data at the wrong offset. Replace these loops by equivalent calls to memcpy, with the right parameters. I tested this patch by comparing the MD5 checksum of a few fragmented files with the respective md5sum output in sandbox, considering both compressed and uncompressed fragments. Signed-off-by:
Joao Marcos Costa <jmcosta944@gmail.com> Tested-by:
Richard Genoud <richard.genoud@posteo.net> Reviewed-by:
Miquel Raynal <miquel.raynal@bootlin.com>
-
- Jun 09, 2021
-
-