- 11 5月, 2017 8 次提交
-
-
由 Kever Yang 提交于
RK3399 device memory region is 0xf8000000~0xffffffff. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Xu Ziyuan 提交于
The genunie bus clock is sclk_x for eMMC/SDMMC, add support for it. Signed-off-by: NZiyuan Xu <xzy.xu@rock-chips.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Xu Ziyuan 提交于
The genunie bus clock is sclk_x for eMMC/SDMMC/SDIO, add support for it. Signed-off-by: NZiyuan Xu <xzy.xu@rock-chips.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Xu Ziyuan 提交于
The genunie bus clock is sclk_x for eMMC/SDMMC/SDIO, add support for it. Signed-off-by: NZiyuan Xu <xzy.xu@rock-chips.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Xu Ziyuan 提交于
The genunie bus clock is sclk_x for eMMC/SDIO, add support for it. Signed-off-by: NZiyuan Xu <xzy.xu@rock-chips.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Xu Ziyuan 提交于
As you know, biu_clk is used for AMBA AHB/APB interface, ciu_clk is used for communication between host and card devices. The real bus clock is ciu, so let's rectify it. Signed-off-by: NZiyuan Xu <xzy.xu@rock-chips.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Kever Yang 提交于
Add support for rk3328 package header in mkimage tool. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Kever Yang 提交于
Use regulators_enable_boot_on() instead of init regulators one by one, the interface can init all the regulators with regulator-boot-on property. Signed-off-by: NKever Yang <kever.yang@rock-chips.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
- 10 5月, 2017 32 次提交
-
-
由 Adam Ford 提交于
With the addition of Kconfig now having CONFIG_TWL4030_POWER and with that being the default when OMAP34XX is selected, this is no longer needed in include/configs and can be removed from the whitelist. This has only been tested on logic PD DM3730 using ti_omap3_common.h Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Adam Ford 提交于
As requested, I added the CONFIG_TWL4030_POWER to Kconfig and made it the implied default when selecting OMAP34XX as a platform. Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Adam Ford 提交于
With the addition of twl4030_power_off(), let's allow the 'poweroff' command to run this function when CONFIG_CMD_POWEROFF is enabled. Tested on a DM3730 with twl4030 PMIC. Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com>
-
由 Adam Ford 提交于
This patch also removes all the excessive code for NS16550 intiailization as the device tree can do that now. This also adds DM_I2C and DM_MMC since the overlying drivers have the built-in support already. The corresponding include/config/omap3_logic.h also reduced in size due to the new device tree support. Signed-off-by: NAdam Ford <aford173@gmail.com> Changes in V2: Retain Auto-detect ability between SOM-LV and Torpedo Split this off from the device sub submissions
-
由 Adam Ford 提交于
Previous commit has this combined with SOM-LV. This commit has only the Torpedo Device Tree. The device trees were sync'd with 4.9.y stable with two changes: disable mmc2 and stdout-path = &uart1. Both of those two changes will be submitted to the linux-omap list Signed-off-by: NAdam Ford <aford173@gmail.com> Changes in V2: Split device tree from other board
-
由 Adam Ford 提交于
This adds the device tree. Previous commit added both boards at the same time. Signed-off-by: NAdam Ford <aford173@gmail.com> Changes in V2: Split the SOM-LV from Torpedo
-
由 Adam Ford 提交于
Some OMAP3 devices support an SMSC ethernet PHY connected to the GPMC bus. This copies this device tree from Linux 4.9.y stable Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Adam Ford 提交于
Many OMAP3 boards use a TWL4030 PMIC. This brings in the related device tree information for common TWL4030 and TWL4030 with OMAP3. Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Adam Ford 提交于
New i2c_read, i2c_write and i2c_probe functions, tested on OMAP4 (4430/60/70), OMAP5 (5430) and AM335X (3359) were added in 960187ff( "ARM: OMAP: I2C: New read, write and probe functions") but not tested on OMAP3. This patch will allow the updated drivers using device tree and DM_I2C to operate on OMAP3. Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Adam Ford 提交于
Add device tree support to allow for CONFIG_OF_CONTROL in OMAP3630 boards. DM3730 can use this same device tree. Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Adam Ford 提交于
Add device tree support to allow for CONFIG_OF_CONTROL in OMAP3 boards. Signed-off-by: NAdam Ford <aford173@gmail.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Adam Ford 提交于
This patch changes the way DM_MMC calculates offset to the base register of MMC. Previously this was through an #ifdef but that wasn't necessary for OMAP3. This patch will now add in the offset to the base address based on the .compatible flags. Signed-off-by: NAdam Ford <aford173@gmail.com> V2: Remove ifdef completely and reference offset from the omap_hsmmc_ids table. V1: Change ifdef to ignore OMAP3 Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Alex Deymo 提交于
In some boards like the Raspberry Pi the initial bootloader will pass a DT to the kernel. When using U-Boot as such kernel, the board code in U-Boot should be able to provide U-Boot with this, already assembled device tree blob. This patch introduces a new config option CONFIG_OF_BOARD to use instead of CONFIG_OF_EMBED or CONFIG_OF_SEPARATE which will initialize the DT from a board-specific funtion instead of bundling one with U-Boot or as a separated file. This allows boards like the Raspberry Pi to reuse the device tree passed from the bootcode.bin and start.elf firmware files, including the run-time selected device tree overlays. Signed-off-by: NAlex Deymo <deymo@google.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Paolo Pisati 提交于
Signed-off-by: NPaolo Pisati <p.pisati@gmail.com>
-
由 Simon Glass 提交于
The board code should all move into msg.c for consistency. Add a TODO for this. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Adjust the video driver to work with driver model and move over existing baords. There is no need to keep the old code. We can also drop setting of CONFIG_FB_ADDR since driver model doesn't have this problem. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NAnatolij Gustschin <agust@denx.de>
-
由 Simon Glass 提交于
Allow this to work with CONFIG_DM_VIDEO enabled. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NAnatolij Gustschin <agust@denx.de>
-
由 Simon Glass 提交于
Adjust this function so that we can convert it to support CONFIG_DM_VIDEO without a lot of code duplication. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NAnatolij Gustschin <agust@denx.de>
-
由 Simon Glass 提交于
Add a function to set the video parameters to the msg handler and remove it from the video driver. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NAnatolij Gustschin <agust@denx.de>
-
由 Simon Glass 提交于
Add a function to get the video size to the msg handler and remove it from the video driver. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NAnatolij Gustschin <agust@denx.de>
-
由 Simon Glass 提交于
We should not use an embedded device tree on a production board. There does not seem to be any reason for it in commit 76709096. So drop this. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Convert the bcm2835 SDHCI driver over to support CONFIG_DM_MMC and move all boards over. There is no need to keep the old code since there are no other users. Reviewed-by: NJaehoon Chung <jh80.chung@samsung.com> Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Move this code into the new message handler file. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
The bcm283x chips provide a way for the ARM core to communicate with the graphics processor, which is in charge of many things. This is handled by way of a message prototcol. At present the code for sending message (and receiving a reply) is spread around U-Boot, primarily in the board file. This means that sending a message from a driver requires duplicating the code. Create a new message implementation with a function to support powering on a subsystem as a starting point. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Enable CONFIG_DM_ETH so that driver model is used for the USB Ethernet device. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Start using driver model for USB on the Raspberry Pi. The dwc2 supports this now so this is just a config change. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This is not needed now that serial uses driver model. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
We can rely on the device tree to provide this information. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
A common use of memmove() can be handled by memcpy(). Also memcpy() includes an optimisation for large sizes: it copies a word at a time. So we can get a speed-up by calling memcpy() to handle our move in this case. Update memmove() to call memcpy() if the destination is before the source. Signed-off-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Simon Glass 提交于
On further review this returns the wrong packet length from the driver. It may not be noticed since protocols will take care of it. Fix it by subtracting the header length from the packet length returned. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
-
-