- 20 5月, 2021 10 次提交
-
-
由 Marcin Wojtas 提交于
Until now the mvpp2 driver used an extra 'phy-speed' DT property in order to differentiate between the SGMII and SGMII @2.5GHz. As there is a dedicated PHY_INTERFACE_MODE_SGMII_2500 flag to mark the latter start using it and drop the custom flag. Signed-off-by: NMarcin Wojtas <mw@semihalf.com> Reviewed-by: NStefan Chulski <stefanc@marvell.com> Reviewed-by: NNadav Haklai <nadavh@marvell.com> Tested-by: NNadav Haklai <nadavh@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de> Reviewed-by: NRamon Fried <rfried.dev@gmail.com>
-
由 Stefan Chulski 提交于
Currently, there are 2 valid cases for interface, PHY and mdio relation: - If an interface has PHY handler, it'll call mdio_mii_bus_get_from_phy(), which will register MDIO bus. - If we want to use fixed-link for an interface, PHY handle is not defined in the DTS, and no MDIO is registered. There is a third case, for some boards (with switch), the MDIO is used for switch configuration, but the interface itself uses fixed link. This patch allows this option by checking if fixed-link subnode is defined, in this case, MDIO bus is registers, but the PHY address is set to PHY_MAX_ADDR for this interface, so this interface will not try to access the PHY later on. Signed-off-by: NStefan Chulski <stefanc@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Ben Peled 提交于
Signed-off-by: NBen Peled <bpeled@marvell.com> Reviewed-by: NStefan Chulski <stefanc@marvell.com> Reviewed-by: NKostya Porotchkin <kostap@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de> Reviewed-by: NRamon Fried <rfried.dev@gmail.com>
-
由 Ben Peled 提交于
Signed-off-by: NBen Peled <bpeled@marvell.com> Reviewed-by: NStefan Chulski <stefanc@marvell.com> Reviewed-by: NKostya Porotchkin <kostap@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de> Reviewed-by: NRamon Fried <rfried.dev@gmail.com>
-
由 Ben Peled 提交于
Signed-off-by: NBen Peled <bpeled@marvell.com> Reviewed-by: NStefan Chulski <stefanc@marvell.com> Reviewed-by: NKostya Porotchkin <kostap@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Stefan Chulski 提交于
GMII_SPEED should be enabled for 2.5G speed Signed-off-by: NStefan Chulski <stefanc@marvell.com> Reviewed-by: NYan Markman <ymarkman@marvell.com> Reviewed-by: NKostya Porotchkin <kostap@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Marcin Wojtas 提交于
Because the mvpp2 driver now relies on the PHYLIB and the external MDIO driver, configuring low level SMI bus settings is redundant. Signed-off-by: NMarcin Wojtas <mw@semihalf.com> Reviewed-by: NKostya Porotchkin <kostap@marvell.com> Reviewed-by: NStefan Chulski <stefanc@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de> Reviewed-by: NRamon Fried <rfried.dev@gmail.com>
-
由 Stefan Chulski 提交于
Signed-off-by: NStefan Chulski <stefanc@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de> Reviewed-by: NRamon Fried <rfried.dev@gmail.com>
-
由 Stefan Chulski 提交于
1. Differ between Port1 RGMII and SFI modes in Netcomplex config. 2. Remove XPCS config from SFI mode. Port1 doesn't XPCS domain, XPCS config should be removed. Access to Port1 XPCS can cause stall. 3. Add Port1 MPCS configurations. Signed-off-by: NStefan Chulski <stefanc@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Stefan Chulski 提交于
Signed-off-by: NStefan Chulski <stefanc@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
- 19 5月, 2021 14 次提交
-
-
https://source.denx.de/u-boot/custodians/u-boot-microblaze由 Tom Rini 提交于
Xilinx changes for v2021.07-rc3 ZynqMP: - Syncup DT with Linux kernel - Fix mmc mini configurations via DT - Add pinctrl/psgtr description to DTs - Add DTs for Kria boards - Enable RTC and Time commands Versal: - Fix early BSS section location
-
由 Michal Simek 提交于
Right now U-Boot is not aware about date/time that's why enable it by default also with EFI runtime service for setting time. Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 T Karthik Reddy 提交于
U-Boot expects to be linked to a specific hard-coded address and to be loaded to and run from that address. CONFIG_POSITION_INDEPENDENT config lifts that restriction & allowing the code to be loaded to and executed from almost any address. As we enabled CONFIG_POSITION_INDEPENDENT, CONFIG_INIT_SP_RELATIVE is enabled by default, where it will set the early stack pointer at runtime by adding an offset value to &_bss_start. The offset value is taken from SYS_INIT_SP_BSS_OFFSET. SYS_INIT_SP_BSS_OFFSET offset should be large enough so that the early malloc region, global data (gd), and early stack should fit. With commit d8fabcc424bd ("arm64: versal: Increase SYS_MALLOC_F_LEN") SYS_MALLOC_F_LEN is increased from 32KB to 1MB, so we need to accommodate this space with SYS_INIT_SP_BSS_OFFSET. Hence increasing SYS_INIT_SP_BSS_OFFSET to 1.5MB. Signed-off-by: NT Karthik Reddy <t.karthik.reddy@xilinx.com> Acked-by: NAshok Reddy Soma <ashok.reddy.soma@xilinx.com> Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Michal Simek 提交于
The patch contains several DT files for SOM platform. Carrier card is sck-kv (KV260) revA/B. SMK-K26 is description for starter kit which doesn't have EMMC populated. And SM-K26 is full som with EMMC. Files are divided in this way to make sure that SOM can be plugged to different carrier card and all peripherals on SOM (or defined by a spec) can be used by U-Boot. Full DT for SOM+CC can be merged together as overlays. Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Michal Simek 提交于
Mainline kernel has psgtr driver that's why it is good to add description to DT files. Some boards are just missing description for USB3 and sata. zc1751-dc1 and p-a2197 are also missing clock descriptions for input clocks. Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Michal Simek 提交于
ZynqMP pinctrl Linux driver has been merged to 5.13-rc1 kernel. Based on it DT files can be extended by pinctrl configurations. Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 T Karthik Reddy 提交于
Probe zynqmp firmware driver by adding zynqmp firmware, power & ipi mailbox device tree nodes for mini emmc. Signed-off-by: NT Karthik Reddy <t.karthik.reddy@xilinx.com>
-
由 Michal Simek 提交于
Add missing xlnx,mio-bank property to sdhci node. Also add properties with 0 value to have it listed in case that files are copied to different projects where default case doesn't need to be handled in the same way. That's why explicitly list them too. Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Michal Simek 提交于
These comments weren't push to mainline that's why remove them. Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Raviteja Narayanam 提交于
I2C muxes that have the slave devices with same address are falling into the below problem. VCK190 system controller (SC) - zynqmp-e-a2197-00-revA.dts I2C1 (0xff030000) -> Mux1 (@0x74) -> Channel 3 -> 0x50 I2C1 (0xff030000) -> Mux2 (@0x75) -> Channel 0 -> 0x50 1. SC accesses I2C1 - Mux1 (0x74) - Channel 3 and then 2. SC accesses I2C1 - Mux2 (0x75) - Channel 0. Now it results in 2 slave devices with same address (0x50) on the I2C bus, making the communication un-reliable. When ' i2c-mux-idle-disconnect' is in DT, after '1', the Mux channel output is disconnected, making none of the channels available to the I2C1. So, there is no question of having the same addressed slave (0x50) present on the bus when we are doing '2'. Same pattern is seen in below two boards also. ZCU208 - zynqmp-zcu208-revA.dts ZCU216 - zynqmp-zcu216-revA.dts Signed-off-by: NRaviteja Narayanam <raviteja.narayanam@xilinx.com>
-
由 Saeed Nowshadi 提交于
Add label to GPIO lines so the user-level applications can find any line without knowing its physical path on System Controller on VCK190/VMK180. These labels are describing EMIO gpio connection which depends on PL which we normally don't describe but that's only way to go for now. Lately this should be done out of this source code. Signed-off-by: NSaeed Nowshadi <saeed.nowshadi@xilinx.com> Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Saeed Nowshadi 提交于
The 'silabs,skip-recall' property prevents interruption in operation of the clock while the driver is being probed. Without this property, the DDR DIMM clk can cause a failure during Versal's boot. Signed-off-by: NSaeed Nowshadi <saeed.nowshadi@xilinx.com>
-
由 Michal Simek 提交于
All si570 which are used for ps reference clock generation should contain silabs,skip-recall property not to cause break on ps clock. On Versal boards this will cause hang on Versal cpu when it is booted at the same time with SC. Signed-off-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Tom Rini 提交于
-
- 18 5月, 2021 16 次提交
-
-
https://source.denx.de/u-boot/custodians/u-boot-efi由 Tom Rini 提交于
Pull request for efi-2021-07-rc3 Documentation: * add a man-page for the size command * add man-page for extension command to index Bug fixes: * avoid build failure due to missing SHA512 hardware acceleration * correct error handling in TCG2 protocol * don't let user disable capsule authentication * correct reading directories via UEFI API
-
-
由 Masahisa Kojima 提交于
Build error occurs when CONFIG_EFI_SECURE_BOOT or CONFIG_EFI_CAPSULE_AUTHENTICATE is enabled, because hash-checksum.c is not compiled. Since hash_calculate() implemented in hash-checksum.c can be commonly used aside from FIT image signature verification, this commit itroduces HASH_CALCULATE option to decide if hash-checksum.c shall be compiled. Signed-off-by: NMasahisa Kojima <masahisa.kojima@linaro.org> Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Ilias Apalodimas 提交于
EFI_TCG2 depends not only on TPMv2 but also on the underlying algorithms. So select the missing SHA1, SHA256, SHA384 and SHA512 we currently support Reported-by: NMichal Simek <michal.simek@xilinx.com> Signed-off-by: NIlias Apalodimas <ilias.apalodimas@linaro.org> Add 'default y'. Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Ilias Apalodimas 提交于
Up to now we are stopping the EFI subsystem if a TPMv2 exists but the protocol fails to install. Now that we've switched the config to 'default y' the sandbox TPM fails, since it doesn't support all the required capabilities of the protocol. Not installing the protocol is not catastrophic. If the protocol fails to install the PCRs will never be extended to the expected values, so some other entity later in the boot flow will eventually figure it out and take the necessary actions. While at it fix a corner case were the user can see an invalid error message when the protocol failed to install. We do have a tcg2_uninit() which we call when the protocol installation fails. There are cases though that this might be called before the configuration table is installed (e.g probing the TPM for capabilities failed). In that case the user will see "Failed to delete final events config table". So stop printing it since it's not an actual failure , simply because the config table was never installed in the first place. In order to stop printing it make efi_init_event_log() and create_final_event() cleanup themselves and only call tcg2_uninit() when the protocol installation fails. Signed-off-by: NIlias Apalodimas <ilias.apalodimas@linaro.org> Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Ilias Apalodimas 提交于
Instead of just failing, clean up the installed config table and EventLog memory if logging an s-crtm event fails during the protocol installation Signed-off-by: NIlias Apalodimas <ilias.apalodimas@linaro.org> Eliminate label 'out:' by using return. Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Ilias Apalodimas 提交于
efi_init_event_log() calls tcg2_uninit() in case of failure. We can skip that since the function is called on efi_tcg2_register() which also cleans up if an error occurs Signed-off-by: NIlias Apalodimas <ilias.apalodimas@linaro.org> Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Peng Fan 提交于
This is same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1733817, but that fix was wrongly partial reverted. When reading a directory, EFI_BUFFER_TOO_SMALL should be returned when the supplied buffer is too small, so a use-case is to call EFI_FILE_PROTOCOL.Read() with *buffer_size=0 and buffer=NULL to obtain the needed size before doing the actual read. So remove the check only for directory reading, file reading already do the check by itself. Fixes: db12f518("efi_loader: implement non-blocking file services") Signed-off-by: NPeng Fan <peng.fan@nxp.com> Cc: Stefan Sørensen <stefan.sorensen@spectralink.com> Tested-by: NPeter Robinson <pbrobinson@gmail.com> Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Sughosh Ganu 提交于
The current capsule authentication code checks if the environment variable capsule_authentication_enabled is set, for authenticating the capsule. This is in addition to the check for the config symbol CONFIG_EFI_CAPSULE_AUTHENTICATE. Remove the check for the environment variable. The capsule will now be authenticated if the config symbol is set. Signed-off-by: NSughosh Ganu <sughosh.ganu@linaro.org> Reviwed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Commit a479f103 ("hash: Allow for SHA512 hardware implementations") defined function definitions for hardware accelerated SHA384 and SHA512. If CONFIG_SHA_HW_ACCEL=y, these functions are used. We already have boards using CONFIG_SHA_HW_ACCEL=y but none implements the new functions hw_sha384() and hw_sha512(). For implementing the EFI TCG2 protocol we need SHA384 and SHA512. The missing hardware acceleration functions lead to build errors on boards like peach-pi_defconfig. Introduce a new Kconfig symbol CONFIG_SHA512_HW_ACCEL to control if the functions hw_sha384() and hw_sha512() shall be used to implement the SHA384 and SHA512 algorithms. Fixes: a479f103 ("hash: Allow for SHA512 hardware implementations") Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Heinrich Schuchardt 提交于
Building 32bit boards with the TCG2 protocol enabled leads to a build warning due to a missing conversion. lib/efi_loader/efi_tcg2.c:774:27: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast] 774 | ret = tcg2_create_digest((u8 *)data_to_hash, data_to_hash_len, | ^ Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: NIlias Apalodimas <ilias.apalodimas@linaro.org>
-
由 Heinrich Schuchardt 提交于
'make htmldocs' results in a build warning checking consistency... doc/usage/extension.rst: WARNING: document isn't included in any toctree Add the document to the index. Fixes: 2f84e9cf ("cmd: add support for a new "extension" command") Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Heinrich Schuchardt 提交于
Provide a man-page for the size command. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Ley Foon Tan 提交于
My mail address doesn't work any longer, change to gmail. Signed-off-by: NLey Foon Tan <ley.foon.tan@intel.com>
-
由 Simon Glass 提交于
Versions of U-Boot before 2014.01 created a symlink from include/asm to the architecture-specific header directory. If an ARM board is build with that old version, then sandbox is built on a more recent version (both with in-tree builds), the include/asm symlink confuses the build system. It picks up the ARM headers when it should be using the sandbox ones. Since 2014 U-Boot has only created a symlink inside the include/asm/ directory and only for out-of-tree builds. So for in-tree builds it does not expect to see an include/asm symlink. It is not removed by 'make mrproper'. It does show up with 'git status' but is easy enough to miss. Add include/asm to the files to remove with 'make mkproper'. For recent U-Boot builds this has no effect, since include/asm is a directory, not a file. If the include/asm symlink is there, it will be removed. Reported-by: NMarek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Igor Opaniuk 提交于
s/psci_features/request_psci_features/g for the case when both ARCH_SUPPORT_PSCI=y and ARM_PSCI_FW=y, that leads to these compilation issues: drivers/firmware/psci.c:69:12: error: conflicting types for 'psci_features' 69 | static int psci_features(u32 psci_func_id) | ^~~~~~~~~~~~~ In file included from drivers/firmware/psci.c:23: ./arch/arm/include/asm/system.h:548:5: note: previous declaration of 'psci_features' was here 548 | s32 psci_features(u32 function_id, u32 psci_fid); | ^~~~~~~~~~~~~ Tested-by: NAlexandru Gagniuc <mr.nuke.me@gmail.com> Reported-by: NAlexandru Gagniuc <mr.nuke.me@gmail.com> Fixes: b7135b03 ("psci: add features/reset2 support") Signed-off-by: NIgor Opaniuk <igor.opaniuk@foundries.io>
-