- 28 7月, 2018 10 次提交
-
-
由 Adam Ford 提交于
With the pending requirement for CONFIG_BLK, this patch removes the USB_STORAGE option which assumes that DM_USB is enabled, but isn't yet available for the omap2340 musb glue among other issues. Once the USB issues are resolved, a future patch can enable them again. Signed-off-by: NAdam Ford <aford173@gmail.com>
-
由 Heinrich Schuchardt 提交于
The driver sets the weekday incorrectly when called by the 'date set' command. Sunday is 1, Saturday is 7 unlike in U-Boot (see data sheet https://www.nxp.com/docs/en/data-sheet/MC146818.pdf, table 3). Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Miquel Raynal 提交于
Now that TPMv1 and TPMv2 can be compiled at the same time, let's compile them both with Sandbox as well as both drivers (and, it is already implied in Kconfig: both commands). Signed-off-by: NMiquel Raynal <miquel.raynal@bootlin.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Miquel Raynal 提交于
TPM_V1 was already compiled by default. Now that both can be compiled at the same time, compiled them both by default. Signed-off-by: NMiquel Raynal <miquel.raynal@bootlin.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Miquel Raynal 提交于
While using the 'tpm' command should work on most cases, this test suite only works with TPMv2 and since the work to make both versions build at the same time, we might end up having both 'tpm' (TPMv1) and 'tpm2' (TPMv2) commands available at the same time. Ensure this test suite always use the right one. Signed-off-by: NMiquel Raynal <miquel.raynal@bootlin.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Miquel Raynal 提交于
While there is probably no reason to do so in a real life situation, it will allow to compile test both stacks with the same sandbox defconfig. As we cannot define two 'tpm' commands at the same time, the command for TPM v1 is still called 'tpm' and the one for TPM v2 'tpm2'. While this is the exact command name that must be written into eg. test files, any user already using the TPM v2 stack can continue to do so by just writing 'tpm' because as long as TPM v1 support is not compiled, U-Boot prompt will search for the closest command named after 'tpm'. The command set can also be changed at runtime (not supported yet, but ready to be), but as one can compile only either one stack or the other, there is still one spot in the code where conditionals are used: to retrieve the v1 or v2 command set. Signed-off-by: NMiquel Raynal <miquel.raynal@bootlin.com> Reviewed-by: NSimon Glass <sjg@chromium.org> [trini: In sandbox_tpm2_fill_buf() use NULL not \0 to ensure NULL terminated string due to LLVM warning] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Miquel Raynal 提交于
The TPM_DRIVER_SELECTED symbol was used in one of the initial series about TPMv2 but its use has been dropped, making these selects useless, remove them. Signed-off-by: NMiquel Raynal <miquel.raynal@bootlin.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Miquel Raynal 提交于
When Sandbox and the TPM stack are both selected, compile Sandbox TPM driver by default. Signed-off-by: NMiquel Raynal <miquel.raynal@bootlin.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Miquel Raynal 提交于
The udevice given to the open() function of course must be opened, not closed. Signed-off-by: NMiquel Raynal <miquel.raynal@bootlin.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
-
- 27 7月, 2018 30 次提交
-
-
由 Tom Rini 提交于
With some recent changes to relevant drivers here the openrd board (openrd_client in this case) does not fit within its size constraint. We can however drop the slightly extended baudrate table and then the duplication of mtdparts/mtdids in the default environment. These defaults are set in the environment by the 'mtdparts' command and otherwise referenced throughout the code. Signed-off-by: NTom Rini <trini@konsulko.com>
-
-
-
由 Masahiro Yamada 提交于
fdt_fixup_mtdparts() calls mtdparts_init() and device_find(), which are defined in cmd/mtdparts.c The combination of FDT_FIXUP_PARTITIONS=y and CMD_MTDPARTS=n emits the following link error: common/fdt_support.c:903: undefined reference to `mtdparts_init' common/fdt_support.c:914: undefined reference to `device_find' Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Jens Wiklander 提交于
Prior to this patch is fdtdec_setup_memory_banksize() incorrectly ignoring the "status" field. This patch fixes that by testing the status with fdtdec_get_is_enabled() before using a memory node. Signed-off-by: NJens Wiklander <jens.wiklander@linaro.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Chris Packham 提交于
Signed-off-by: NChris Packham <judge.packham@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Adam Sampson 提交于
Previously the first three words in a git-mailrc alias entry could only be separated by spaces. git-send-email and Mutt both allow arbitrary whitespace here. Signed-off-by: NAdam Sampson <ats@offog.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Adam Sampson 提交于
patman's _ReadAliasFile only splits on spaces, not tabs, so the entries for dinh and maxime weren't being recognised as valid. I'll fix patman in a separate patch, but this makes all the entries consistent. Signed-off-by: NAdam Sampson <ats@offog.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Tom Warren 提交于
Fix warning when compiling tegra30-beaver/-apalis.dts with latest DTC: "Warning (avoid_unnecessary_addr_size): /pci/pch@1f,0: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property" Signed-off-by: NTom Warren <twarren@nvidia.com>
-
由 Stephen Warren 提交于
If a secure carveout exists, U-Boot cannot use that memory. Fix carveout_size() to reflect this, and hence transitively fix usable_ram_size_below_4g() and board_get_usable_ram_top(). This change ensures that when U-Boot copies the secure monitor code to install it, the copy target is not in-use for U-Boot code/data. Signed-off-by: NStephen Warren <swarren@nvidia.com> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
由 Stephen Warren 提交于
When fixing up the DT to report PSCI support, explicitly enable the node. DTs may ship with the node disabled in case a PSCI implementation is not present, and expect any PSCI implementation to enable the node if they are actually present. Signed-off-by: NStephen Warren <swarren@nvidia.com> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
由 Stephen Warren 提交于
Enhance the PSCI DT editing code to allow setting a PSCI v0.2 compatible value in the DT. The CONFIG_ option is added to the whitelist to match the existing PSCI_1_0 option. While not adding new options to Kconfig isn't ideal, I figure it's better to keep related options together. Signed-off-by: NStephen Warren <swarren@nvidia.com> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
由 Stephen Warren 提交于
Add a MON_MODE define for ARM's monitor mode. This can be used later by a secure monitor to avoid hard-coding mode IDs. Signed-off-by: NStephen Warren <swarren@nvidia.com> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
由 Bibek Basu 提交于
RAM repair has a few pre-requisites: 1) PMIC power supply (rail) enabled. 2) PMC CRAIL power partition powered. 3) Fuse clock active (it's the default). 4) PLLP reshift branch enabled (it's the default, when PLLP is active). RAM repair also only need run whenever specific partitions are powered (main SoC and CCPLEX respectively); RAM repair does not need to be triggered when any other partition changes state. start_cpu() needs to be re-ordered slightly to match these requirements. Note that C0NC and CE0 aren't required for RAM repair to operate, but they also do no harm, so the entire of powerup_cpus() is moved rather than splitting it up. The call to remove_cpu_resets() is moved last to ensure that all other actions complete before releasing reset; since the PMC power partitions are now enabled early, releasing reset is what causes the CPUs to start executing code, and RAM repair must complete before the CPU boots. Note that this commit is the result of squashing a numbmer of commits in NVIDIA's downstream L4T branch, hence the multiple signoffs below. Signed-off-by: NBibek Basu <bbasu@nvidia.com> Signed-off-by: NSandipan Patra <spatra@nvidia.com> Signed-off-by: NStephen Warren <swarren@nvidia.com> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
由 Stephen Warren 提交于
This reverts commit 701b7b1d. It will be immediately replaced by a different implementation that is more complete and runs are more targetted times. Signed-off-by: NStephen Warren <swarren@nvidia.com> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
-
由 Simon Glass 提交于
Use GNU make pattern rules to indicate that a single run of binman produces all three Tegra output files. The avoids make running binman three times (perhaps in parallel) and those instances inteferring with each other. See http://patchwork.ozlabs.org/patch/944611/ for the bug report. Signed-off-by: NSimon Glass <sjg@chromium.org> Tested-by: NStephen Warren <swarren@nvidia.com>
-
由 Tom Rini 提交于
Scott is no longer maintaining the NAND subsystem, mark as orphaned for now. Acked-by: NScott Wood <oss@buserror.net> Signed-off-by: NTom Rini <trini@konsulko.com>
-
This patch updates the zynq gem driver to support livetree. Signed-off-by: NSiva Durga Prasad Paladugu <siva.durga.paladugu@xilinx.com> Signed-off-by: NVipul Kumar <vipul.kumar@xilinx.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Grygorii Strashko 提交于
Now zynq_gem driver will overwrite UCLASS_ETH node when PHY is connected and configured which is not correct. Use struct phydev->node instead. Signed-off-by: NGrygorii Strashko <grygorii.strashko@ti.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Tested-by: NSiva Durga Prasad Paladugu <siva.durga.paladugu@xilinx.com>
-
由 Grygorii Strashko 提交于
Now CPSW driver will overwrite UCLASS_ETH node when PHY is connected and configured which is not correct. Use struct phydev->node instead. Signed-off-by: NGrygorii Strashko <grygorii.strashko@ti.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Grygorii Strashko 提交于
Use PHY API phy_get_ofnode() helper to get PHY DT node. Signed-off-by: NGrygorii Strashko <grygorii.strashko@ti.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Grygorii Strashko 提交于
Use PHY API phy_get_ofnode() helper to get PHY DT node. Signed-off-by: NGrygorii Strashko <grygorii.strashko@ti.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Tested-by: NSiva Durga Prasad Paladugu <siva.durga.paladugu@xilinx.com>
-
由 Grygorii Strashko 提交于
Now the UCLASS_ETH device "node" field is owerwritten by some network drivers in case of Ethernet PHYs which are linked to UCLASS_ETH device using "phy-handle" DT property and when Ethernet PHY driver needs to read some additional information from DT. In such cases following happens (in general): - network drivers priv->phydev = phy_connect(priv->bus, priv->phyaddr, dev, priv->interface); <-- phydev is connected to dev which is UCLASS_ETH device if (priv->phy_of_handle > 0) dev_set_of_offset(priv->phydev->dev, priv->phy_of_handle); <-- phydev->dev->node is overwritten by phy-handle DT node - PHY driver in .config() callback int node = dev_of_offset(dev); <-- PHY driver uses overwritten dev->node const void *fdt = gd->fdt_blob; if (fdtdec_get_bool(fdt, node, "property")) ... As result, UCLASS_ETH device can't be used any more for DT accessing. This patch adds additional ofnode node field to struct phy_device which can be set explicitly by network drivers and used by PHY drivers, so overwriting can be avoided. Also add helper function phy_get_ofnode() which will check and return phy_device->node or dev_ofnode(phydev->dev) for backward compatibility with existing drivers. Signed-off-by: NGrygorii Strashko <grygorii.strashko@ti.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Joe Hershberger 提交于
We want to be able to include some other system headers in phy.h but that requires us to have included common.h in the top-level first. Also, common.h includes config.h as the first thing it does, so don't include it directly. Series-to: u-boot Series-cc: Grygorii Strashko <grygorii.strashko@ti.com> Seried-cc: ti Series-process-log: sort, uniq Cover-letter: Prepare for net: phy: prevent uclass_eth device "node" field overwriting Prepare for [1] so that it doesn't break the build for a bunch of boards. There are a number of reasons this series broke the build but none of them depend on changes in the series, so fix up those situations ahead of applying that series. [1] https://patchwork.ozlabs.org/cover/940104/ END Signed-off-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Joe Hershberger 提交于
Because some phy wants to export some functions [1], export.h was including the whole phy subsystem which pulls in lots of stuff that causes some ordering and redefinition issues. Split out the only part that is actually needed in export.h and include it there and in phy.h. [1] commit 95279315 ("board/ls2085rdb: Export functions for standalone AQ FW load apps") Signed-off-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Joe Hershberger 提交于
The include/phy.h will start including dm.h, which pulls in linux/compat.h after the attempted redefinition in arch/arm/include/asm/armv8/mmu.h, so move this include to allow redefinition. Signed-off-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Grygorii Strashko 提交于
Switch to use more generic ofnode API instead of FDT API. Signed-off-by: NGrygorii Strashko <grygorii.strashko@ti.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Tested-by: NSiva Durga Prasad Paladugu <siva.durga.paladugu@xilinx.com>
-
由 Murali Karicheri 提交于
The data manual for DP83867IR/CR, SNLS484E[1], revised march 2017, advises that strapping RX_DV/RX_CTRL pin in mode 1 and 2 is not supported (see note below Table 5 (4-Level Strap Pins)). It further advises that if a board has this pin strapped in mode 1 and mode 2, then bit[7] of Configuration Register 4 (address 0x0031) must be cleared to 0. This is to ensure proper operation of PHY. Since it is not possible to detect in software if RX_DV/RX_CTRL pin is incorrectly strapped, add a device-tree property to advertise this and allow corrective action in software. [1] http://www.ti.com/lit/ds/snls484e/snls484e.pdfSigned-off-by: NMurali Karicheri <m-karicheri2@ti.com> Reviewed-by: NHannes Schmelzer <oe5hpm@oevsv.at> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Tested-by: NSiva Durga Prasad Paladugu <siva.durga.paladugu@xilinx.com>
-
由 Chris Packham 提交于
Add driver model support to the mvgbe driver. As a temporary measure both DM and non-DM uses are supported. Once all the users have been converted the non-DM support can be dropped. Signed-off-by: NChris Packham <judge.packham@gmail.com> Tested-by: NMichael Walle <michael@walle.cc> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-