- 22 6月, 2020 5 次提交
-
-
由 Fabio Estevam 提交于
As per kernel commit 0672d22a1924 ("ARM: dts: imx: Fix the AR803X phy-mode) the correct phy-mode should be "rgmii-id", so fix it accordingly to fix the Ethernet regression. This problem has been exposed by commit: commit 13114f38 Author: Vladimir Oltean <vladimir.oltean@nxp.com> Date: Thu May 7 00:11:51 2020 +0200 phy: atheros: Explicitly disable RGMII delays To eliminate any doubts about the out-of-reset value of the PHY, that the driver previously relied on. If bisecting shows that this commit breaks your board you probably have a wrong PHY interface mode. You probably want the PHY_INTERFACE_MODE_RGMII_RXID or PHY_INTERFACE_MODE_RGMII_ID mode. Signed-off-by: NVladimir Oltean <vladimir.oltean@nxp.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Fix the phy-mode accordingly to fix the regression. Signed-off-by: NFabio Estevam <festevam@gmail.com>
-
由 Fabio Estevam 提交于
Migration to DM_ETH is mandatory, so convert mx6cuboxi to Ethernet Driver Model. This also brings the benefit of restoring Ethernet functionality. Reported-by: NTom Rini <trini@konsulko.com> Signed-off-by: NFabio Estevam <festevam@gmail.com> Tested-by: NTom Rini <trini@konsulko.com>
-
由 Fabio Estevam 提交于
Sync the device tree with 5.8-rc1. It basically contains the following extra kernel commit: commit 86b08bd5b99480b79a25343f24c1b8c4ddcb5c09 Author: Russell King <rmk+kernel@armlinux.org.uk> Date: Wed Apr 15 16:44:17 2020 +0100 ARM: dts: imx6-sr-som: add ethernet PHY configuration Add ethernet PHY configuration ahead of removing the quirk that configures the clocking mode for the PHY. The RGMII delay is already set correctly. Signed-off-by: NRussell King <rmk+kernel@armlinux.org.uk> Reviewed-by: NFabio Estevam <festevam@gmail.com> Signed-off-by: NShawn Guo <shawnguo@kernel.org> , which passes the 'qca,clk-out-frequency' property and it is important to specify the correct frequency generated by the AR8035. Signed-off-by: NFabio Estevam <festevam@gmail.com> Tested-by: NTom Rini <trini@konsulko.com>
-
由 Fabio Estevam 提交于
As we move towards driver model, it is required to let the FEC driver know how to properly deal with an Ethernet PHY subnode in the device tree. For example: &fec { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_microsom_enet_ar8035>; phy-handle = <&phy>; phy-mode = "rgmii-id"; phy-reset-duration = <2>; phy-reset-gpios = <&gpio4 15 GPIO_ACTIVE_LOW>; status = "okay"; mdio { #address-cells = <1>; #size-cells = <0>; phy: ethernet-phy@0 { reg = <0>; qca,clk-out-frequency = <125000000>; }; }; }; Currently the PHY node pointer is incorrectly associated with the Ethernel controller instead of the PHY node itself. This causes the PHY properties, such as "qca,clk-out-frequency" in the example above to not get parsed. Fix this problem by populating the phy_of_node node. Suggested-by: NVladimir Oltean <vladimir.oltean@nxp.com> Signed-off-by: NFabio Estevam <festevam@gmail.com> Tested-by: NTom Rini <trini@konsulko.com>
-
由 Fabio Estevam 提交于
The clock ouput frequency is calculated incorrectly for AR8035 due to wrong masking of priv->clk_25m_reg and priv->clk_25m_mask. This same issue has been already fixed in the kernel by: commit b1f4c209d84057b6d40b939b6e4404854271d797 Author: Oleksij Rempel <o.rempel@pengutronix.de> Date: Wed Apr 1 11:57:32 2020 +0200 net: phy: at803x: fix clock sink configuration on ATH8030 and ATH8035 The masks in priv->clk_25m_reg and priv->clk_25m_mask are one-bits-set for the values that comprise the fields, not zero-bits-set. This patch fixes the clock frequency configuration for ATH8030 and ATH8035 Atheros PHYs by removing the erroneous "~". To reproduce this bug, configure the PHY with the device tree binding "qca,clk-out-frequency" and remove the machine specific PHY fixups. Fixes: 2f664823a47021 ("net: phy: at803x: add device tree binding") Signed-off-by: NOleksij Rempel <o.rempel@pengutronix.de> Reported-by: NRussell King <rmk+kernel@armlinux.org.uk> Reviewed-by: NRussell King <rmk+kernel@armlinux.org.uk> Tested-by: NRussell King <rmk+kernel@armlinux.org.uk> Signed-off-by: NDavid S. Miller <davem@davemloft.net> Apply the same fix in the U-Boot driver. Tested on a i.MX6 Hummingboard. Signed-off-by: NFabio Estevam <festevam@gmail.com> Reviewed-by: NMichael Walle <michael@walle.cc> Tested-by: NTom Rini <trini@konsulko.com>
-
- 21 6月, 2020 1 次提交
-
-
- 20 6月, 2020 3 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-efi由 Tom Rini 提交于
Pull request for UEFI sub-system for efi-2020-07-rc5 (2) Fix memory reservations: do not use random bytes from the stack.
-
https://gitlab.denx.de/u-boot/custodians/u-boot-stm由 Tom Rini 提交于
- fix SD card cart detect on DHCOM and ST boards
-
-
- 19 6月, 2020 13 次提交
-
-
由 Patrick Delaunay 提交于
The cd-gpios with (GPIO_ACTIVE_LOW | GPIO_PULL_UP) gpio is thus far unsupported, reinstate the old cd-gpios behavior until this handling is fully implemented. This avoid potential issue for SDCard boot: the card detect fails with floating gpio. Signed-off-by: NPatrick Delaunay <patrick.delaunay@st.com> Reviewed-by: NPatrice Chotard <patrice.chotard@st.com>
-
由 Marek Vasut 提交于
The cd-gpios with (GPIO_ACTIVE_LOW | GPIO_PULL_UP) gpio is thus far unsupported, reinstate the old cd-gpios behavior until this handling is fully implemented. This permits the DHSOM to boot from SD again, without this patch the card detect fails. Signed-off-by: NMarek Vasut <marex@denx.de> Cc: Patrick Delaunay <patrick.delaunay@st.com> Cc: Patrice Chotard <patrice.chotard@st.com> Reviewed-by: NPatrick Delaunay <patrick.delaunay@st.com>
-
由 Atish Patra 提交于
fdtdec_get_addr_size reads the uses a fixed value for address & size cell properties which may not be correct always. Use the auto variant of the function which automatically reads #address-cells & #size-cells from parent and uses to read the "reg" property. Signed-off-by: NAtish Patra <atish.patra@wdc.com> On 32 bit systems fdt_addr_t may be 4 bytes long but size is defined as u64. Avoid filling the upper 4 bytes of the sizep parameter of fdtdec_get_addr_size_auto_parent() with random bytes from the stack by defining a separate variable fdt_size. Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Tom Warren 提交于
This allows Nano to use the key M.2 on the CVB to connect and use a M.2 NVMe SSD stick. Works on my Nano B00, WD SN750 NVMe SSD shows up w/'nvme' commands. Will add booting from NVMe via distro cmds in a future patch. Signed-off-by: NTom Warren <twarren@nvidia.com>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-video由 Tom Rini 提交于
- fix stdout in default environment for apalis_imx6, colibri_imx6 and cm_fx6 boards
-
由 Igor Opaniuk 提交于
Take over maintainership for Colibri T20 module. Signed-off-by: NIgor Opaniuk <igor.opaniuk@toradex.com> Acked-by: NLucas Stach <dev@lynxeye.de>
-
由 Jon Hunter 提交于
The PSCI nodes are currently not populated for the Tegra210 and Tegra186 devices. This prevents the PSCI driver from being able to identify the PSCI method used by these devices and causes the probe of the PSCI driver to fail. Since commit 81ea0083 ("efi_loader: PSCI reset and shutdown") was added, which moves the PSCI EFI system reset handler into the PSCI driver, this has prevented the EFI system reset from working for Tegra210 and Tegra186. Therefore, populating these nodes is necessary to fix the EFI system reset for Tegra210 and Tegra186. Signed-off-by: NJon Hunter <jonathanh@nvidia.com> Tested-by: NPeter Robinson <pbrobinson@gmail.com>
-
由 Jon Hunter 提交于
When CONFIG_OF_LIVE is enabled, dev_of_offset() cannot be used and if used returns an invalid offset. This causes the call to fdt_stringlist_get() in the psci_probe() to fail to read the 'method' property from the PSCI node for the device and hence prevents PSCI from working. Fix this by using the ofnode_read_string() API instead of the fdt_stringlist_get() because this will handle reading the property both when CONFIG_OF_LIVE is enabled or disabled. Due to the above problem and since commit 81ea0083 ("efi_loader: PSCI reset and shutdown") was added, the EFI system reset has been broken for Tegra210 and Tegra196 platforms. This also fixes the EFI system reset for these Tegra platforms. Signed-off-by: NJon Hunter <jonathanh@nvidia.com> Tested-by: NPeter Robinson <pbrobinson@gmail.com>
-
由 Tom Rini 提交于
- Add guestfstools, efitools - Latest Ubuntu/bionic snapshot Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Marek Vasut 提交于
The ethernet PHY on all known Gen3 boards takes a while to come out of reset, increase the auto-negotiation timeout to prevent it from timing out in case the ethernet is used right after the board was reset. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
由 Anatolij Gustschin 提交于
After migration to DM 'vga' name is not longer supported, change it to 'vidconsole' in the default environment. Signed-off-by: NAnatolij Gustschin <agust@denx.de> Acked-by: NIgor Opaniuk <igor.opaniuk@toradex.com>
-
由 Anatolij Gustschin 提交于
After migration to DM 'vga' name is not longer supported, change it to 'vidconsole' in the default environment. Signed-off-by: NAnatolij Gustschin <agust@denx.de> Acked-by: NIgor Opaniuk <igor.opaniuk@toradex.com>
-
由 Anatolij Gustschin 提交于
After migration to DM 'vga' name is not longer supported, change it to 'vidconsole' in the default environment. Signed-off-by: NAnatolij Gustschin <agust@denx.de> Cc: Nikita Kiryanov <nikita@compulab.co.il>
-
- 18 6月, 2020 3 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-amlogic由 Tom Rini 提交于
- move amlogic board documentation into doc/board in RsT format
-
由 Neil Armstrong 提交于
Add the recently added reStructuredText board documentation in the appropriate MAINTAINERS files. Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>
-
由 Neil Armstrong 提交于
Move the natural text Amlogic board README files to doc/board/amlogic into reStructuredText and : - add reStructuredText markup for bash code - fix secondary titles markup - move board support into global support matrix Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>
-
- 16 6月, 2020 5 次提交
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-stm由 Tom Rini 提交于
- fix boot with OP-TEE for stm32mp15 boards
-
由 Etienne Carriere 提交于
Add OP-TEE firmware node in stm32mp15 U-Boot DTSI. This node is needed since commit [1] that changed U-Boot/stm32mp15 to detect OP-TEE availability by probing the resource instead of relying on U-Boot configuration. The software sequence implemented by [1] is fine but U-Boot DTS/DTSI files were not updated accordingly since, hence OP-TEE presence is never detected by U-Boot, preventing Linux kernel from using OP-TEE resources. For consistency and to synchronize stm32mp15 DTSI files (excluding U-Boot specific DTSI files) with the Linux kernel ones, this change also moves the OP-TEE reserved memory nodes from board generic DTSI files to U-Boot specific board DTSI files. Link: [1] commit 43df0a15 ("stm32mp1: dynamically detect op-tee presence") Signed-off-by: NEtienne Carriere <etienne.carriere@linaro.org> Signed-off-by: NPatrick Delaunay <patrick.delaunay@st.com> Reviewed-by: NPatrice Chotard <patrice.chotard@st.com>
-
由 Etienne Carriere 提交于
Fix the sequence in stm32mp1 fdt.c that disables OP-TEE resources defined in FDT when U-boot detects OP-TEE firmware is not present. Before this change, helper function stm32_fdt_disable_optee() set property status to "disabled" for the OP-TEE reserved memory nodes but this has no impact since Linux kernel does not consider the status property for reserved-memory subnodes. This change make U-Boot to attempt to delete the node instead. Fixes: 4a1b975d ("board: stm32mp1: reserve memory for OP-TEE in device tree") Signed-off-by: NEtienne Carriere <etienne.carriere@linaro.org> Signed-off-by: NPatrick Delaunay <patrick.delaunay@st.com> Reviewed-by: NPatrice Chotard <patrice.chotard@st.com>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-efi由 Tom Rini 提交于
Pull request for UEFI sub-system for efi-2020-07-rc5 Use correct printf code in efi_image_parse(). Add random number generation to HTML documentation.
-
由 Mark Kettenis 提交于
The fix in commit b7adcdd0 has the side-effect that the regulator will be disabled when requesting the relevant gpio in regulator_common_ofdata_to_platdata() and enabled in regulator_pre_probe() when the regulator was already enabled. This leads to a short interruption in the 3.3V power to the PCIe slot on the firefly-rk3399 which makes an ADATA SX8000NP NVMe SSD unhappy. Fix this by setting the GPIOD_IS_OUT_ACTIVE flag again when the 'regulator-boot-on' property is set, but check for this property explicitly instead of relying on the "boot_on" member of the uclass platdata. Signed-off-by: NMark Kettenis <kettenis@openbsd.org> Tested-by: NPatrice Chotard <patrice.chotard@st.com>
-
- 15 6月, 2020 10 次提交
-
-
由 Tom Rini 提交于
- Assorted bug fixes
-
由 Patrick Delaunay 提交于
Update the comment for SYS_RELOC_GD_ENV_ADDR as gd->env_addr is updated in board_r.c::initr_reloc_global_data() under the compilation flags CONFIG_SYS_RELOC_GD_ENV_ADDR Signed-off-by: NPatrick Delaunay <patrick.delaunay@st.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Heinrich Schuchardt 提交于
Several configutation options require additional memory before relocation: * CONSOLE_RECORD * LOG * RSA The current default of 0x400 is too small to encompass them all. Increase the value of SYS_MALLOC_F_LEN to 0x2000 for ARCH_QEMU. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Sean Anderson 提交于
This reverts commit 0486497e. The strtoul has well-defined semantics. It is defined by the C standard and POSIX. To quote the relevant section of the man pages, > If base is zero or 16, the string may then include a "0x" prefix, and the > number will be read in base 16; otherwise, a zero base is taken as 10 > (decimal) unless the next character is '0', in which case it is taken as > 8 (octal). Keeping these semantics is important for several reasons. First, it is very surprising for standard library functions to behave differently than usual. Every other implementation of strtoul has different semantics than the implementation in U-Boot at the moment. Second, it can result in very surprising results from small changes. For example, changing the string "1f" to "20" causes the parsed value to *decrease*. Forcing use of the "0x" prefix to specify hexidecimal numbers is a feature, not a bug. Lastly, this is slightly less performant, since the entire number is parsed twice. This fixes the str_simple_strtoul test failing with test/str_ut.c:29, run_strtoul(): expect_val == val: Expected 0x44b (1099), got 0x1099ab (1087915) test/str_ut.c:46, str_simple_strtoul(): 0 == run_strtoul(uts, str2, 0, 1099, 4): Expected 0x0 (0), got 0x1 (1) Signed-off-by: NSean Anderson <seanga2@gmail.com> CC: Michal Simek <michal.simek@xilinx.com> CC: Shiril Tichkule <shirilt@xilinx.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Michal Simek 提交于
s/booot/boot/g The first ase is booot instead of boot and second u-booot instead of u-boot. Signed-off-by: NMichal Simek <michal.simek@xilinx.com> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Etienne Carriere 提交于
Fix the loop that parses FDT for a reserved memory node named "optee". Before this change, if at least one subnode was found in the reserved-memory node, the function endlessly looped since instruction continue returned back in the loop without updating variable subnode. This change fixes the issue by using a for loop. Fixes: 6ccb05ea ("image: fdt: copy possible optee nodes to a loaded devicetree") Signed-off-by: NEtienne Carriere <etienne.carriere@linaro.org> Signed-off-by: NPatrick Delaunay <patrick.delaunay@st.com>
-
https://gitlab.denx.de/u-boot/custodians/u-boot-mmc由 Tom Rini 提交于
- fsl_esdhc sdr104 and hs200 fix and error path fix - fsl_esdhc workaround 3.3v io issue - ca_dw_mmc cleanup - presidio-asic emmc DT update.
-
由 Marek Vasut 提交于
Unsupported voltage on voltage switch is not an error, do not print error message in such a case. This happens e.g. if the eMMC is already in 1V8 mode or when testing 1V2 mode operation on systems which only do 3V3/1V8 switching. Signed-off-by: NMarek Vasut <marex@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: Peng Fan <peng.fan@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Marek Vasut 提交于
The 3V3/1V8 switching could never have worked on any of the iMXes ever since 51313b49 ("mmc: fsl_esdhc: support SDR104 and HS200"), because that commit uses priv->vqmmc_dev when switching voltages on mode switch, while local vqmmc_dev in probe to store the regulator pointer. Those are two different variables with the same name. So the priv->vqmmc_dev was always NULL and thus voltage switch between modes never really suceeded. Fix this by assigning priv->vqmmc_dev with value of the vqmmc_dev in probe. Fixes: 51313b49 ("mmc: fsl_esdhc: support SDR104 and HS200") Signed-off-by: NMarek Vasut <marex@denx.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Jaehoon Chung <jh80.chung@samsung.com> Cc: Peng Fan <peng.fan@nxp.com> Cc: Stefano Babic <sbabic@denx.de> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Alex Nemirovsky 提交于
Change DT compatibility name to match change in driver's name. Remove unused io_ds and fifo_mode fields from DT. Signed-off-by: NAlex Nemirovsky <alex.nemirovsky@cortina-access.com> CC: Peng Fan <peng.fan@nxp.com> CC: Jaehoon Chung <jh80.chung@samsung.com> CC: Tom Rini <trini@konsulko.com>
-