- 12 7月, 2016 27 次提交
-
-
由 Simon Glass 提交于
The list is shrinking and we should avoid adding new things. Instead, a proper driver should be created with driver model. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NBin Meng <bmeng.cn@gmail.com>
-
由 Simon Glass 提交于
A few drivers have moved to driver model, so we can drop these strings. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Simon Glass 提交于
We have drivers for several more devices now, so drop the strings which are no-longer used. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NBin Meng <bmeng.cn@gmail.com>
-
由 Xu Ziyuan 提交于
This fixes the following compiler error: common/fb_mmc.c: In function ‘fb_mmc_erase’: common/fb_mmc.c:209:17: error: ‘struct blk_desc’ has no member named ‘block_erase’ Signed-off-by: NZiyuan Xu <xzy.xu@rock-chips.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Hamish Martin 提交于
Define a platform data structure for the MPC85XX GPIO driver to allow use of the driver without device tree. Users should define the GPIO blocks for their platform like this: struct mpc85xx_gpio_plat gpio_blocks[] = { { .addr = 0x130000, .ngpios = 32, }, { .addr = 0x131000, .ngpios = 32, }, }; U_BOOT_DEVICES(my_platform_gpios) = { { "gpio_mpc85xx", &gpio_blocks[0] }, { "gpio_mpc85xx", &gpio_blocks[1] }, }; This is intended to build upon the recent submission of the base MPC85XX driver from Mario Six. We need to use that new driver without dts support and this patch gives us that flexibility. This has been tested on a Freescale T2080 CPU, although only the first GPIO block. Signed-off-by: NHamish Martin <hamish.martin@alliedtelesis.co.nz> Reviewed-by: NMario Six <mario.six@gdsys.cc> Tested-by: NMario Six <mario.six@gdsys.cc> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Update the method of accessing the block device so that it works with CONFIG_BLK enabled. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Update the method of accessing the block device so that it works with CONFIG_BLK enabled. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Now that we have fully moved to driver model, drop the old code. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Update this board to use driver model for block devices and MMC operations. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Add support for using driver model for block devices and MMC operations in this driver. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Add support for using driver model for block devices and MMC operations in this driver. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Move the configuration setting into a separate function which can be used by the driver-model code. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Update the sandbox MMC emulation to use driver model for MMC operations. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
These boards should have maintainer entries. Add them. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Enable this option to move rockchip over to use driver model for MMC operations. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Add support to dwmmc for using driver model for MMC operations. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
The driver model conversion for MMC has moved in small steps. The first step was to have an MMC device (CONFIG_DM_MMC). The second was to use a child block device (CONFIG_BLK). The final one is to use driver model for MMC operations (CONFIG_DM_MMC_OP). Add support for this. The immediate priority is to make all boards that use DM_MMC also use those other two options. This will allow them to be removed. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This option is not actually needed for rockchip boards. Drop it, since it will not support driver-model MMC operation support. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Move this code into separate functions so that it can be used from the uclass also. Add static inline versions for when the option is disabled. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Since all Rockchip boards use CONFIG_BLK, we can remove this old code. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Rather than having an #ifdef in the main mmc.c file, control this feature from the Makefile by moving the code into its own file. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Rather than having #ifdef in mmc.c, move this code into the legacy file. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Rather than having #ifdef in mmc.c, move this code into the uclass file. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
These private functions are used both in the driver-model implementation and in the legacy code. Add them to the header. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Rockchip uses driver model for all subsystems. Specify this in the arm Kconfig rather than as defaults in the Rockchip Kconfig. This means that boards cannot turn these options off, which seems correct. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
These comments were missed when the original code was written. Add them to help people port their drivers over. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 11 7月, 2016 3 次提交
-
-
由 Andre Przywara 提交于
Since we lack information about the DRAM initialization for the Allwinner A64 SoC, booting any A64 based board like the Pine64 is a bit involved at the moment. Add a README file to explain the process. Signed-off-by: NAndre Przywara <andre.przywara@arm.com> Reviewed-by: NTom Rini <trini@konsulko.com> [trini: Move to board/sunxi/ from doc/] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Stefano Babic 提交于
Because a gpimage cannot be detected, a false GP header is printed instead of checking for further image types. Move gpimage as last to be linked, letting check all other image types and printing a GP header just in case no image is detected. Signed-off-by: NStefano Babic <sbabic@denx.de>
-
由 jk.kernel@gmail.com 提交于
It's easier to Cc rockchip maintainers on rockchip-releated patches. Signed-off-by: Njk <jk.kernel@gmail.com>
-
- 09 7月, 2016 6 次提交
-
-
由 Mingkai Hu 提交于
For A53, data coherency is enabled only when the CPUECTLR.SMPEN bit is set. The SMPEN bit should be set before enabling the data cache. If not enabled, the cache is not coherent with other cores and data corruption could occur. For A57/A72, SMPEN bit enables the processor to receive instruction cache and TLB maintenance operations broadcast from other processors in the cluster. This bit should be set before enabling the caches and MMU, or performing any cache and TLB maintenance operations. Signed-off-by: NMingkai Hu <mingkai.hu@nxp.com> Signed-off-by: NGong Qianyu <Qianyu.Gong@nxp.com> Reviewed-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Daniel Schwierzeck 提交于
Some archs like MIPS or PPC have a different 'bdinfo' output than ARM regarding the memory configuration. Also support 'memstart = 0x*' in u_boot_utils.find_ram_base() to make all tests requiring the RAM base working on those archs. Signed-off-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com> Acked-by: NStephen Warren <swarren@nvidia.com>
-
由 Stephen Warren 提交于
Prior to this patch, any VT100 codes emitted by U-Boot are considered part of a command's output, which often causes tests to fail. For example, test_env_echo_exists executes printenv, and then considers any text on a line before an = sign as a valid U-Boot environment variable name. This includes any VT100 codes emitted. When the test later attempts to use that variable, the name would be invalid since it includes the VT100 codes. Solve this by stripping VT100 codes from the match buffer, so they are never seen by higher level test code. The codes are still logged unmodified, so that users can expect U-Boot's exact output without interference. This does clutter the log file a bit. However, it allows users to see exactly what U-Boot emitted rather than a modified version, which hopefully is better for debugging. It's also much simpler to implement, since logging happens as soon as text is received, and so stripping the VT100 codes from the log would require handling reception and stripping of partial VT100 codes. Signed-off-by: NStephen Warren <swarren@nvidia.com>
-
由 Alexander Graf 提交于
Commit e6777248 (arm: Fix setjmp) added code to fix compilation of the setjmp code path with thumv1. Unfortunately it missed a constraint that the adr instruction can only refer to 4 byte aligned offsets. So this patch adds the required alignment hooks to make compilation work again even when setjmp doesn't happen to be 4 byte aligned. Signed-off-by: NAlexander Graf <agraf@suse.de> Tested-by: NTom Rini <trini@konsulko.com>
-
由 Andre Przywara 提交于
As printf calls may be executed quite early, we should avoid using any BSS stored variables, since some boards put BSS in DRAM, which may not have been initialised yet. Explicitly mark those "static global" variables as belonging to the .data section, to keep tiny-printf clear of any BSS usage. Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
-
由 Stephen Warren 提交于
Some CONFIG_ variables were recently renamed, but test/py wasn't updated to match. This causes some tests to be skipped. Fix test/py so the tests are run. Fixes: 11636258 ("Rename reset to sysreset") Fixes: f1f9d4fa ("hush: complete renaming CONFIG_SYS_HUSH_PARSER to CONFIG_HUSH_PARSER") Cc: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: NStephen Warren <swarren@nvidia.com>
-
- 08 7月, 2016 1 次提交
-
-
由 Mateusz Kulikowski 提交于
MMC core expects (now) valid mmc->dev pointer. During conversion in commit cffe5d86 not every driver was updated. This patch fixes crash while accessing MMC on boards using Qualcomm SDHCI controller. Signed-off-by: NMateusz Kulikowski <mateusz.kulikowski@gmail.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
- 07 7月, 2016 3 次提交
-
-
-
由 York Sun 提交于
Commit 92623672 moves USB errata workaround into a C file. This causes compiling error for kmcoge4 and kmlion1. To enable the errata workaround, define CONFIG_USB_EHCI_FSL in common header. Signed-off-by: NYork Sun <york.sun@nxp.com> Cc: Marek Vasut <marex@denx.de> Cc: Ed Swarthout <Ed.Swarthout@nxp.com> Cc: Sriram Dash <sriram.dash@nxp.com> Fixes: 92623672 ("fsl: usb: make errata function common for PPC and ARM")
-
-