- Feb 01, 2019
-
-
The chosen node was added in the kernel. This may come in handy in the future, so resync with 5.0-rc3 Signed-off-by:Adam Ford <aford173@gmail.com>
-
Resync with Kernel 5.0-rc3 Signed-off-by: -
To comply with pending requirements, this sets the flags to enable DM_SPI and DM_USB. Signed-off-by: -
CONFIG_SPL_FS_EXT4 can be used to include/exclude the FS EXT4 from SPL build. Excluding the FS EXT4 from SPL build can help to save 20KiB memory. Signed-off-by:
Tien Fong Chee <tien.fong.chee@intel.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Replace CONFIG_SPL_EXT_SUPPORT to CONFIG_SPLY_FS_EXT4 so both obj-$(CONFIG_$(SPL_)FS_EXT4) and CONFIG_IS_ENABLED(FS_EXT4) can be used to control the build in both SPL and U-Boot. Signed-off-by:
-
Most of the time SPL only needs very simple FAT reading, so having CONFIG_IS_ENABLED(FAT_WRITE) to exclude it from SPL build would help to save 64KiB default max clustersize from memory. Signed-off-by:
Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com> Reviewed-by:
-
Replace CONFIG_SPL_FAT_SUPPORT with CONFIG_SPL_FS_FAT so obj-$(CONFIG_$(SPL_)FS_FAT) can be used to control the build in both SPL and U-Boot. Signed-off-by:
-
This feature is now supported by the main config for am335x_evm: am335x_evm_defconfig Signed-off-by:
Jean-Jacques Hiblot <jjhiblot@ti.com> Reviewed-by:
-
The AM335x ROM boot is able to download the SPL from a RNDIS connection on USB0. To enable a full RNDIS boot flow (romboot -> SPL -> u-boot -> ..), we can use USB_ETHER in SPL and u-boot. However this increase the size of the SPL past its limit. So removing the unused SPL_EXT_SUPPORT. Signed-off-by:
-
This USB port is mainly used for RNDIS and DFU. To be able to use it with DM_USB and DM_USB_GADGET, we need to provide a dr_mode value in the DTS. Signed-off-by:
-
If the host does not respond in time, the initialization fails. However the usb ether driver will still be registered. This will make usb_gadget_probe_driver() fail the next time the initialization is attempted because it cannot find an available UDC. Fixing this by calling _usb_eth_halt() when the init fails. Signed-off-by:
Lukasz Majewski <lukma@denx.de>
-
port the am335x based shc board to DM, to get rid of DW warnings when compiling U-Boot. - remove uneccessary board code - adapt defconfigs - remove unneeded defconfigs configs/am335x_shc_prompt_defconfig configs/am335x_shc_sdboot_prompt_defconfig Signed-off-by:
Heiko Schocher <hs@denx.de> Reviewed-by:
-
add u-boot specific am335x-shc-u-boot.dtsi file, in which we add u-boot specific adaptions. Signed-off-by:
-
add DTS from linux tree commit "47bfa6d9dc8c060bf56554a465c9031e286d2f80" change for U-Boot: switch to SPDX-license identifier. Signed-off-by:
-
- Jan 31, 2019
-
-
git://git.denx.de/u-boot-videoTom Rini authored
- ihs and imx driver fixes - relax EDID validation checks for 0 hsync/vsync pulse width (support some quirky displays)
-
git://git.denx.de/u-boot-amlogicTom Rini authored
- Add features and fixups to support video on Amlogic GX SoCs - Add video support for Amlogic GX SoC - Add DT fixups - Enable Video and USB Console for libretech-cc board
-
Maxime Jourdan authored
libretech-cc being the main device tested with CONFIG_VIDEO_MESON, let's enable it by default. Also enable: - CONFIG_SYS_WHITE_ON_BLACK for prettiness - CONFIG_VIDEO_DT_SIMPLEFB for framebuffer sharing with kernel Signed-off-by:
Maxime Jourdan <mjourdan@baylibre.com> Signed-off-by:
Neil Armstrong <narmstrong@baylibre.com> Reviewed-by:
Anatolij Gustschin <agust@denx.de>
-
Maxime Jourdan authored
With the recent addition of the meson VPU driver, enable the following config entries by default for meson-64 targets: CONFIG_CONSOLE_MUX, CONFIG_SYS_CONSOLE_IS_IN_ENV. This allows outputting the console via video if CONFIG_VIDEO_MESON is selected. Signed-off-by:
-
Neil Armstrong authored
Allows displaying the console via video and using a USB keyboard. Also enables CONFIG_SPLASH_SCREEN if using video. Signed-off-by:
-
Maxime Jourdan authored
If VIDEO_MESON is enabled, we need to setup the fdt for the framebuffer. Call meson_vpu_rsv_fb() which reserves the framebuffer memory region for EFI, and sets up simple-framebuffer nodes if simplefb support is enabled. Signed-off-by:
-
Maxime Jourdan authored
There's no reliable way to reuse the hhi entry from the vpu as is done in the linux kernel, so we duplicate it here. We will be able to sync against kernel DTS in the future when the VPU gets based on the clock framework rather than the HHI reg. Signed-off-by:
-
Neil Armstrong authored
The hdmi_5v regulator must be enabled to provide power to the physical HDMI PHY and enables the HDMI 5V presence loopback for the monitor. Fixes: b409f625a6d5 ("ARM64: dts: meson-gx: Add HDMI_5V regulator on selected boards") Signed-off-by:Kevin Hilman <khilman@baylibre.com> [backport of linux commit e1f2163deac059ad39f07aba9e314ebe605d5a7a]
-
Maxime Jourdan authored
Flag the appropriate nodes with u-boot,dm-pre-reloc Signed-off-by:
-
Neil Armstrong authored
This adds video output support for Amlogic GXBB/GXL/GXM chips. The supported ports are CVBS and HDMI (based on DW_HDMI). When using HDMI, only DMT modes are supported. There is support for simple-framebuffer (CONFIG_VIDEO_DT_SIMPLEFB) Signed-off-by:
Jorge Ramire-Ortiz <jramirez@baylibre.com> Signed-off-by:
-
Jorge Ramirez-Ortiz authored
Some IPs like the meson VPU can only feed a particular pixel format to dw_hdmi. As of now, the driver is hardcoded to use RGB888 as input. This commit enables different pixel format inputs, with the appropriate CSC configuration. Signed-off-by:
-
Jorge Ramirez-Ortiz authored
Some IPs like the meson VPU have a specific way to write to dw_hdmi registers. Make it configurable. Signed-off-by:
-
Maxime Jourdan authored
MESON_GX_VPU_POWER_DOMAIN should depend on POWER_DOMAIN. Signed-off-by:
-
Add entry for Amlogic SoC maintained files and the freshly created mailing-list. Signed-off-by: -
If `make mrproper` does not delete the generated drivers/video/fonts/*.S files a following `make tests` fails. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
This unbreaks dfu mmc_file_op which is currently broken since using the load cmd on a buffer from heap is not allowed - added with commit aa3c609e ("fs: prevent overwriting reserved memory") Fixes: commit aa3c609e ("fs: prevent overwriting reserved memory") Reported-by:
Stephen Warren <swarren@wwwdotorg.org> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Acked-by:
-
- Jan 30, 2019
-
-
-
Jagan Teki authored
Enable DM_MMC for all Allwinner SoCs, this will eventually enable BLK. Also removed DM_MMC enablement in few parts of sunxi configurations. Signed-off-by:
Jagan Teki <jagan@amarulasolutions.com> Reviewed-by:
Andre Przywara <andre.przywara@arm.com> Signed-off-by:
-
Jagan Teki authored
Like other Allwinner A64 boards, pinebook also need altering auto-numbering of mmc2 to mmc1 which is available in common sunxi dsti file, sunxi-u-boot.dtsi Pinebook has a separate sun50i-a64-pinebook-u-boot.dtsi which takes more precedence for u-boot.dtsi inclusion and it eventually failed to include the sunxi-u-boot.dtsi. So, this patch add support to include the sunxi-u-boot.dtsi in the sun50i-a64-pinebook-u-boot.dtsi Signed-off-by: -
Jagan Teki authored
Environment and fastboot mmc devices are configured based on the number of mmc slots defined on particular board configs, MMC_SUNXI_SLOT_EXTRA. If MMC_SUNXI_SLOT_EXTRA is more than 1, the default env and fastboot mmc devices is mmc1 by assuming mmc0 is SD and mmc1 is emmc device. But with DM_MMC the mmc devices are numbered as per the dts node enablement. If there is a chance of having enabling all mmc nodes in dts say mmc0, mmc1, mmc2 then the default env and fastboot devices will failed to assign proper emmc device since mmc2 is emmc in most of the Allwinner platforms. So, we need to alter the auto-numbering by aliasing mmc2 to mmc1 since aliases take precedence over auto-numbering. If the dts enables mmc0, mmc1, mmc2, then all the nodes will probe sequentially and auto-numbered as it is. but when aliases mmc1 with mmc2 the resulting number should be that mmc0 is till mmc0, mmc2 become mmc1 and mmc2 become mmc1 Without aliases of mmc1 = &mmc2; ------------------------------- MMC: mmc@1c0f000: 0, mmc@1c10000: 1, mmc@1c11000: 2 With aliases of mmc1 = &mmc2; ---------------------------- MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000' mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... OK Some platforms like A20 has mmc0...mmc3, but there is no usecases now for enabling all mmc controllers in any of A20 board dts files. Signed-off-by: -
Some Allwinner clock devices have parent clocks and reset gates itself, which need to be activated for them to work. Add some code to just assert all resets and enable all clocks given. This should enable the A80 MMC config clock, which requires both to be activated. The full CCU devices typically don't require resets, and have just fixed clocks as their parents. Since we treat both as optional and enabling fixed clocks is a NOP, this works for all cases, without the need to differentiate between those clock types. Signed-off-by:
Jagan Teki <jagan@openedev.com>
-
-
- Jan 29, 2019
-
-
If a board DT describes a cd-gpios property, but also marks the storage as non-removable, we must ignore the GPIO (as Linux does). Teach the DM_MMC part of the Allwinner MMC driver about the non-removable DT property, to fix DM_MMC access on the SoPine and Pine64-LTS board. Signed-off-by:
-
Enabling DM_MMC skips the call to mmc_pinmux_setup() in board.c, as this is supposed to be handled by the MMC driver, using DT information. However we don't have a pinctrl driver yet, but would still like to keep the working pinmux setup for our MMC devices. So bring this particular call back to the DM_MMC code flow. When booting from either SD card or eMMC, the SPL does the setup for us, but when booting from SPI or USB we must not skip this part. Fixes, boot via FEL or SPI flash, where the SPL won't setup the pinmux Signed-off-by:
-
Now that we have the gate clocks and the reset gates in our new Allwinner clock driver, let's make use of them in the MMC driver, when DM_MMC is defined. We treat the reset device as optional now, as the older SoCs don't implement it. Signed-off-by:
-
Jagan Teki authored
A80 gates clock already be part of CLK framework, so just add mod_clk offset with A80 compatible string. Cc: Rask Ingemann Lambertsen <rask@formelder.dk> Cc: Jaehoon Chung <jh80.chung@samsung.com> Signed-off-by:
-
