[PATCH v2 1/2] rockchip: rk3399: split roc-pc-rk3399 out of evb_rk3399

From: Suniel Mahesh roc-pc-rk3399 board has one user button & three user LED's. Currently we don't have any code support for these devices. Since button and LED's are specific to roc-pc-rk3399 board, split it into its own board file and add code support here. Signed-off-by: Suniel Mahesh ---

[PATCH 1/2] rockchip: rk3399: split roc-rk3399-pc out of evb_rk3399

From: Suniel Mahesh roc-rk3399-pc board has one user button & three user LED's. Currently we don't have any code support for these devices. Since button and LED's are specific to roc-rk3399-pc board, split it into its own board file and add any code support here. Signed-off-by: Suniel Mahesh

[PATCH v2 2/2] board: roc-pc-rk3399: Add support for onboard LED's and push button to indicate power mode

From: Suniel Mahesh Added support for onboard LED's and push button. When powered board will be in low power mode(yellow LED), on button press, board enters full power mode (red LED) and boots u-boot. Signed-off-by: Suniel Mahesh --- Changes for v2: - Tested on firefly roc-pc-rk3399, an

[PATCH 2/2] board: roc-rk3399-pc: Add support for onboard LED's and push button to indicate power mode

From: Suniel Mahesh Added support for onboard LED's and push button. When powered board will be in low power mode(yellow LED), on button press, board enters full power mode (red LED) and boots u-boot. Signed-off-by: Suniel Mahesh --- arch/arm/mach-rockchip/tpl.c| 7 ++

[PATCH] Revert "board: roc-pc-rk3399: Add support for onboard LED's and push button to indicate power mode"

From: Suniel Mahesh In case of a power interruption, human intervention is required which is not desirable if the device is installed at a remote location. Keep red LED as it is to indicate board in full power mode. This reverts partially the commit 5a6d3d1fbca70d7f528c685292d64c4cd0106aa6.

[PATCH] rockchip: board: roc-pc-rk3399: Remove support for push button

From: Suniel Mahesh In case of a power interruption, human intervention is required which is not desirable if the device is installed at a remote location. Drop yellow LED as it is not much of use. Keep red LED(diy-led) as it is, to indicate board in full power mode. Signed-off-by: Suniel

[PATCH] arm: dts: rockchip: rk3399-roc-pc: Enable FE1.1 USB 2.0 HUB on roc-rk3399-pc

From: Suniel Mahesh roc-rk3399-pc has an FE1.1 USB 2.0 HUB which connects two USB ports (HOST1 and HOST2). For end devices to work we need to enable USB hub so that HOST detects there presence and enumerates them accordingly. This requires explicit pinctrl within gpio enablement. Signed-off-by:

[PATCH v2 4/4] configs: roc-rk3399-pc: Enable DM for RTC and commands

From: Suniel Mahesh Enable rtc driver DM for rk808 PMIC's, also enable date command. Signed-off-by: Suniel Mahesh --- Changes for v2: - new patch --- configs/roc-pc-rk3399_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/configs/roc-pc-rk3399_defconfig

[PATCH v2 2/4] power: pmic: rk8xx: bind rk808 RTC

From: Suniel Mahesh RK808 PMIC is a multi functional device with an RTC. In order to access RTC, bind to its parent device i.e. RK808 PMIC. Signed-off-by: Suniel Mahesh --- Changes for v2: - no changes --- drivers/power/pmic/rk8xx.c | 19 ++- 1 file changed, 18 insertions(+),

[PATCH v2 1/4] arm: dts: rockchip: rk3399-roc-pc: Add RTC child node for RK808 PMIC

From: Suniel Mahesh Rockchip RK808 PMIC is a multi function device which hosts a Real Time Clock along with other devices. Add a child RTC node so that it can be bound and probed once the master pmic node completes probe. Signed-off-by: Suniel Mahesh --- Changes for v2: - no changes ---

[PATCH v2 3/4] rtc: rk8xx: Add base support for the RK808 PMIC RTC

From: Suniel Mahesh Rockchip RK808 PMIC provides an integrated RTC module. It is commonly used with Rockchip SoCs. Add basic support to access date and time. Signed-off-by: Suniel Mahesh --- Changes for v2: - moved corresponding configs which enable rtc into a seperate patch. - changed

[PATCH v2 0/4] Add support for Rockchip RK808 PMIC RTC device

From: Suniel Mahesh This patch series adds support for Rockchip RK808 PMIC RTC device. Patch #1, adds a child node under RK808 PMIC node. Patch #2 binds this child device with its parent RK808 PMIC. Patch #3 adds the rtc driver. Patch #4 enables DM RTC, adds date command for the target. The

[PATCH v2] rockchip: board: roc-pc-rk3399: Remove support for push button

From: Suniel Mahesh In case of a power interruption, human intervention is required which is not desirable if the device is installed at a remote location. Drop yellow LED as it is not much of use. Keep red LED(diy-led) as it is, to indicate board in full power mode. Signed-off-by: Suniel

[RESEND PATCH] arm: dts: rockchip: rk3399-roc-pc: Enable FE1.1 USB 2.0 HUB on roc-rk3399-pc

From: Suniel Mahesh roc-rk3399-pc has an FE1.1 USB 2.0 HUB which connects two USB ports (HOST1 and HOST2). For end devices to work we need to enable USB hub so that HOST detects there presence and enumerates them accordingly. This requires explicit pinctrl within gpio enablement. Signed-off-by:

[PATCH v3 3/4] rtc: rk8xx: Add base support for the RK808 PMIC RTC

From: Suniel Mahesh Rockchip RK808 PMIC provides an integrated RTC module. It is commonly used with Rockchip SoCs. Add basic support to access date and time. Signed-off-by: Suniel Mahesh --- Changes for v3: - no changes Changes for v2: - moved corresponding configs which enable rtc into a

[PATCH v3 4/4] configs: roc-rk3399-pc: Enable DM for RTC and commands

From: Suniel Mahesh Enable rtc driver DM for rk808 PMIC's, also enable date command. Signed-off-by: Suniel Mahesh --- Changes for v3: - no changes Changes for v2: - new patch --- configs/roc-pc-rk3399_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH v3 0/4] Add support for Rockchip RK808 PMIC RTC device

From: Suniel Mahesh This patch series adds support for Rockchip RK808 PMIC RTC device. Patch #1, adds a child node under RK808 PMIC node. Patch #2 binds this child device with its parent RK808 PMIC. Patch #3 adds the rtc driver. Patch #4 enables DM RTC, adds date command for the target. The

[PATCH v3 1/4] arm: dts: rockchip: rk3399-roc-pc: Add RTC child node for RK808 PMIC

From: Suniel Mahesh Rockchip RK808 PMIC is a multi function device which hosts a Real Time Clock along with other devices. Add a child RTC node so that it can be bound and probed once the master pmic node completes probe. Signed-off-by: Suniel Mahesh Reviewed-by: Kever Yang --- Changes for

[PATCH v3 2/4] power: pmic: rk8xx: bind rk808 RTC

From: Suniel Mahesh RK808 PMIC is a multi functional device with an RTC. In order to access RTC, bind to its parent device i.e. RK808 PMIC. Signed-off-by: Suniel Mahesh Reviewed-by: Kever Yang --- Changes for v3: - added reviewed by tag Changes for v2: - no changes ---

[PATCH 0/3] Add support for Rockchip RK808 PMIC RTC device

From: Suniel Mahesh This patch series adds support for Rockchip RK808 PMIC RTC device. Patch #1, adds a child node under RK808 PMIC node. Patch #2 binds this child device with its parent RK808 PMIC. Patch #3 adds the rtc driver. The RK808 PMIC RTC has a hardware bug. It counts 31 days for

[PATCH 2/3] power: pmic: rk8xx: bind rk808 RTC

From: Suniel Mahesh RK808 PMIC is a multi functional device with an RTC. In order to access RTC, bind to its parent device i.e. RK808 PMIC. Signed-off-by: Suniel Mahesh --- drivers/power/pmic/rk8xx.c | 19 ++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git

[PATCH 3/3] rtc: Add base support for the RK808 PMIC RTC

From: Suniel Mahesh Rockchip RK808 PMIC provides an integrated RTC module. It is commonly used with Rockchip SoCs. Add basic support to access date and time. Signed-off-by: Suniel Mahesh --- Note: 1. The RK808 PMIC RTC has a hardware bug. It counts 31 days for november month and the weeks

[PATCH 1/3] arm: dts: rockchip: rk3399-roc-pc: Add RTC child node for RK808 PMIC

From: Suniel Mahesh Rockchip RK808 PMIC is a multi function device which hosts a Real Time Clock along with other devices. Add a child RTC node so that it can be bound and probed once the master pmic node completes probe. Signed-off-by: Suniel Mahesh --- arch/arm/dts/rk3399-roc-pc-u-boot.dtsi

[2/5] roc-rk3399-pc: Configure the leds only during POR

As far as linux reboot is concerned, once reboot is done, there is no led status indication when in u-boot. Since its a reboot and board has entered full power mode, enabling RED led would be fine I guess. Suniel

[PATCH 5/5] roc-pc-rk3399: Enable PCIe/M.2, NVMe

From: Suniel Mahesh ROC-RK3399-PC Mezzanine is an add-on board for roc-pc-rk3399 target and it hosts a PCIe/M.2 interface. As we have added runtime detection support for this add-on board, this patch enables PCIe/M.2, NVMe so that SSD's which have a PCIe/M.2 interface can be detected. => nvme

[PATCH 3/5] roc-pc-rk3399: Add support for add-on board run-time detection

From: Suniel Mahesh roc-pc-rk3399 target has an add-on board, this add-on board hosts a CW2015 chip which is connected as slave to I2C2. In order to dynamically detect this add-on board at runtime, I2C2 is probed in SPL. If probe is successfull then a corresponding dtb is loaded, else regular

[PATCH 0/5] Enable I2C in SPL, support runtime detection of add-on board

From: Suniel Mahesh This patch series adds runtime detection of add-on board(ROC-RK3399-PC Mezzanine) by enabling I2C in SPL. This add on board hosts a CW2015 chip which is connected as slave to I2C2. In order to dynamically detect this add-on board at runtime, I2C2 is probed in SPL. If probe

[PATCH 1/5] rockchip: spl: Move board_early_init_f after cpu timer

From: Jagan Teki Custom board_early_init_f not only deal with simple gpio configuration but also have a possibility to access clocks to process any clock related operations like checking reset cause state and etc. So, call it once the rockchip timer initialization done instead of calling first

[PATCH 2/5] roc-pc-rk3399: Enable I2C in SPL for add-on board detection

From: Suniel Mahesh This patch enables I2C in SPL for any add-on board detection at run time. Signed-off-by: Suniel Mahesh Signed-off-by: Jagan Teki --- arch/arm/dts/rk3399-roc-pc-u-boot.dtsi | 13 + configs/roc-pc-rk3399_defconfig| 5 - 2 files changed, 17

[PATCH 4/5] rk3399: drop ROC-RK3399-PC Mezzanine board

From: Suniel Mahesh As we have added runtime detection support for ROC-RK3399-PC Mezzanine board, which is an add-on board and as indicated in earlier commit, we are dropping separate defconfig file and support. see commit f417d71ea78b ("rk3399: Add ROC-RK3399-PC Mezzanine board")

[PATCH] rockchip: Fix spl mmc boot device ofpath

From: Suniel Mahesh Linux v5.7-rc1 dts(i) sync has changed the sdmmc node from dwmmc@fe32 to mmc@fe32 and this ofpath is being used in rockchip spl bootdevice code. So, update the ofpath with a new node name. Fixes: 167efc2c7a46 ("arm64: dts: rk3399: Sync v5.7-rc1 from Linux"

[U-Boot] [U-Boot-Users] mpc8641hpcn linker script and the bootpg section

the pheripherals on our board we just interested in four ethernet ports and thts it.it would be a great help if u tell me what changes are to be made in uboot source and in which folder/file. thnx and regards sunil khatri rtts india. ___ U-Boot mailing list U-Boot

[U-Boot] [PATCH v2] arm: dts: am33xx: sync DTS with Linux 4.13-rc4

From: Suniel Mahesh This re-syncs AM33xx DTS file with current file from Linux v4.13-rc4 to ensure a consistent configuration. Upstream Linux removed the redundant Interrupt-parent property from mmc, mac, lcdc and tscadc sub nodes. Signed-off-by: Suniel Mahesh

[U-Boot] [RESEND PATCH] arm: dts: am33xx: Remove redundant interrupt-parent property

From: Suniel Mahesh Upstream Linux has the Interrupt-parent property being removed from mmc, mac, lcdc and tscadc sub nodes in the dtsi file. Interrupt-parent property is already defined in the root node. Therefore, update the dtsi to mimic this change and remove

[U-Boot] [PATCH] arm: dts: am33xx: Remove redundant interrupt-parent property

From: Suniel Mahesh Upstream Linux has the Interrupt-parent property being removed from mmc, mac, lcdc and tscadc sub nodes in the dtsi file. Interrupt-parent property is already defined in the root node. Therefore, update the dtsi to mimic this change and remove

[U-Boot] [PATCH] drivers: mmc: Change buffer type in ALLOC_CACHE_ALIGN_BUFFER macro

From: Suniel Mahesh __be32_to_cpu() accepts argument of type __be32. This patch changes type of the buffer in ALLOC_CACHE_ALIGN_BUFFER macro to __be32, which is then passed to __be32_to_cpu(). This prevents sparse build warnings. drivers/mmc/mmc.c: warning: cast to

[U-Boot] [PATCH] arm: dts: am33xx: Remove redundant interrupt-parent property

From: Suniel Mahesh Interrupt-parent property is defined in the root node as "interrupt-parent = <>". This interrupt-parent value becomes the default for the system, so removed redundant "interrupt-parent" property from mmc, mac, lcdc and tscadc nodes. Signed-off-by:

[U-Boot] [PATCH v2] drivers: mmc: Avoid memory leak in case of failure

From: Suniel Mahesh priv pointer should be freed before returning with an error value from exynos_dwmci_get_config(). Signed-off-by: Suniel Mahesh Signed-off-by: Raghu Bharadwaj --- Changes for v2: - rebased on latest u-boot tree

[U-Boot] [PATCH v2] drivers: mmc: Change buffer type in ALLOC_CACHE_ALIGN_BUFFER macro

From: Suniel Mahesh __be32_to_cpu() accepts argument of type __be32. This patch changes type of the buffer in ALLOC_CACHE_ALIGN_BUFFER macro to __be32, which is then passed to __be32_to_cpu(). This prevents sparse build warnings. drivers/mmc/mmc.c: warning: cast to

[U-Boot] [PATCH 2/2] watchdog: omap_wdt: Disable DM watchdog support in SPL

From: Suniel Mahesh This patch disables DM watchdog support for SPL builds and uses the legacy omap watchdog on TI AM335x chipsets. The following build error is reported if DM watchdog support was enabled in SPL: CC spl/drivers/usb/gadget/rndis.o LD

[U-Boot] [PATCH 1/2] watchdog: omap_wdt: Convert watchdog driver to use DT and DM

From: Suniel Mahesh This patch adds device tree and driver model watchdog support, converts the legacy omap watchdog driver to driver model for TI AM335x chipsets. The following compile warning is removed: = WARNING == This board does not use CONFIG_WDT

[U-Boot] [PATCH v2 2/2] watchdog: omap_wdt: Disable DM watchdog support in SPL

From: Suniel Mahesh This patch disables DM watchdog support for SPL builds and uses the legacy omap watchdog driver on TI AM335x chipsets. The following build error is reported if DM watchdog support was enabled in SPL: CC spl/drivers/usb/gadget/rndis.o LD

[U-Boot] [PATCH v2 1/2] watchdog: omap_wdt: Convert watchdog driver to use DT and DM

From: Suniel Mahesh This patch adds device tree and driver model watchdog support, converts the legacy omap watchdog driver to driver model for TI AM335x chipsets. The following compile warning is removed: = WARNING == This board does not use CONFIG_WDT

[U-Boot] [PATCH] arm: omap2: am43xx: Enable CONFIG_BLK

From: Suniel Mahesh With DM_MMC enabled, enable CONFIG_BLK to remove this compile warning for am43xx based targets: = WARNING == This board does not use CONFIG_DM_MMC. Please update the board to use CONFIG_DM_MMC before the v2019.04 release. Failure to

[U-Boot] [PATCH] Makefile: clean *dtb_HS

From: Suniel Mahesh All TI HS platforms generate HS images/binaries along with the normal images. These *dtb_HS are generated in dts dir and there is no rule for cleanup. Added entry for cleanup in clean and distclean targets. Signed-off-by: Suniel Mahesh --- Makefile | 4 ++-- 1 file

[U-Boot] [PATCH v2] arm: dts: Makefile: clean *dtb_HS

From: Suniel Mahesh TI HS platforms generate *dtb_HS binary blobs and there is no rule for cleanup. Added entry for cleanup in clean-files target. Signed-off-by: Suniel Mahesh --- Changes for v2: - changed description to fit the change done. - As suggested by Lokesh Vutla, moved cleaning

[U-Boot] [PATCH] Makefile: clean build generated SPL binary for TI AM65x

From: Suniel Mahesh TI AM65x platforms (evm and HS) generate an SPL image 'tispl.bin*' and there is no rule for cleanup. Added entry for cleanup in clean target. Signed-off-by: Suniel Mahesh --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile

[U-Boot] [PATCH 1/2] arm: am437x: cm-t43: Add device tree, enable OF_CONTROL

From: Suniel Mahesh Add device tree from Linux for driver model conversion and enable OF_CONTROL. This will remove the following compile warning: == Device Tree Source is not correctly specified. Please define 'CONFIG_DEFAULT_DEVICE_TREE' or build

[U-Boot] [PATCH 2/2] arm: am437x: cm-t43: Enable DM for MMC, USB, SPI, SPI_FLASH, enable BLK

From: Suniel Mahesh Enable driver model for USB, MMC, SPI and SPI_FLASH. Also enable BLK. This will remove the following compile warnings: = WARNING == This board does not use CONFIG_DM_MMC. Please update the board to use CONFIG_DM_MMC before the v2019.04

[U-Boot] [PATCH] arm: omap2: am43xx: Enable CONFIG_DM_USB

From: Suniel Mahesh Enable CONFIG_DM_USB to remove compile warning for am43xx based targets: = WARNING == This board does not use CONFIG_DM_USB. Please update the board to use CONFIG_DM_USB before the v2019.07 release. Failure to update by the deadline

[U-Boot] [PATCH] arm: imx6: cm_fx6: Enable DM SPI and SPI_FLASH, fix SPL build errors

From: Suniel Mahesh Enable driver model for SPI and SPI_FLASH to remove the following compile warning on CM-FX6 SOM: = WARNING == This board does not use CONFIG_DM_SPI_FLASH. Please update the board to use CONFIG_SPI_FLASH before the v2019.07 release.

[U-Boot] [PATCH] board: ti: am43xx_evm_usbboot: Enable DM for USB, fix SPL build errors

From: Suniel Mahesh To address the following warning message: = WARNING == This board does not use CONFIG_DM_USB. Please update the board to use CONFIG_DM_USB before the v2019.07 release. Failure to update by the deadline may result in board removal. See

[U-Boot] [PATCH] watchdog: omap_wdt: Fix WDT target reset when booted from emmc

From: Suniel Mahesh AM335X based beaglebone black target gets reset by DM converted watchdog if booted from emmc around 60sec. Fixed this by moving driver's private struct variable initialization at different places in the driver to driver's probe. Tested on Beaglebone Black. Cc: Grygorii

[U-Boot] [PATCH 1/2] configs: am335x_boneblack_vboot_defconfig: Fix regression by enabling BLK and DM support, disable in SPL

From: Suniel Mahesh This patch adds BLK and DM support for verified boot on TI AM335x chipsets. The following compile warnings are removed: = WARNING == This board does not use CONFIG_DM_MMC. Please update the board to use CONFIG_DM_MMC before the

[U-Boot] [PATCH 2/2] configs: am335x_boneblack_vboot_defconfig: Add DM for SPI and Flash devices

From: Suniel Mahesh This patch adds SPI and SPI_FLASH DM support for verified boot on TI AM335 chipsets. The following compile warning is removed: = WARNING == This board does not use CONFIG_DM_SPI_FLASH. Please update the board to use CONFIG_SPI_FLASH

[U-Boot] [PATCH 2/2] board: cm_fx6: Enable CONFIG_DM_ETH

From: Suniel Mahesh Enable CONFIG_DM_ETH to remove compile warning on CM-FX6 SOM based target: = WARNING == This board does not use CONFIG_DM_ETH (Driver Model for Ethernet drivers). Please update the board to use CONFIG_DM_ETH before the v2020.07

[U-Boot] [PATCH 1/2] board: cm_fx6: Enable DM support for video, fix build error

From: Suniel Mahesh Enable driver model for Video to remove the following compile warning on CM-FX6 SOM based target: = WARNING == This board does not use CONFIG_DM_VIDEO Please update the board to use CONFIG_DM_VIDEO before the v2019.07 release.

[U-Boot] [RESEND PATCH] arm: imx6: cm_fx6: Enable DM SPI and SPI_FLASH, fix SPL build errors

From: Suniel Mahesh Enable driver model for SPI and SPI_FLASH to remove the following compile warning on CM-FX6 SOM: = WARNING == This board does not use CONFIG_DM_SPI_FLASH. Please update the board to use CONFIG_SPI_FLASH before the v2019.07 release.

[U-Boot] TFTP Issue

BOOTP broadcast 5 = Thanks in advance! Best Regards, Sunil ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] TFTP Issue

I use tftpboot load_address image Can you please let me know what are the other options and their syntax for loading a image? -Original Message- From: sywang [mailto:syw...@dongniannetworks.com] Sent: Friday, December 17, 2010 11:51 AM To: T K, Sunil Kumar; u-boot@lists.denx.de

Re: [U-Boot] TFTP Issue

address: 0x9400 Loading: * ARP Retry count exceeded; starting again == Regards, Sunil ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] TFTP Issue

.) But earlier it was gatewayip=0.0.0.0 and was working fine also. Can't we go ahead without gatewayip? Regards, Sunil -Original Message- From: Wolfgang Denk [mailto:w...@denx.de] Sent: Friday

[U-Boot] [PATCH v2 2/2] configs: sun50i: Add support for Olimex A64-Olinuxino-eMMC

=sunxi/dt-for-5.4=02bb66b347ff8115f53948f86b884e008ba385b9 Based on a64-olinuxino_defconfig. This patch has been tested on A64-OLinuXino-1Ge16GW. Signed-off-by: Sunil Mohan Adapa --- board/sunxi/MAINTAINERS | 5 + configs/a64-olinuxino-emmc_defconfig | 17 + 2

[U-Boot] [PATCH v2 1/2] arm64: dts: sun50i: Add support for A64 OLinuXino (with eMMC)

=sunxi/dt-for-5.4=02bb66b347ff8115f53948f86b884e008ba385b9 This patch has been tested on A64-OLinuXino-1Ge16GW and is based on Linux device-tree. Signed-off-by: Sunil Mohan Adapa --- arch/arm/dts/Makefile | 1 + arch/arm/dts/sun50i-a64-olinuxino-emmc.dts | 23

[U-Boot] [PATCH v2 0/2] arm64: dts: sun50i: Add support for A64 OLinuXino (with eMMC)

tree for emmc models. Sunil Mohan Adapa (2): arm64: dts: sun50i: Add support for A64 OLinuXino (with eMMC) configs: sun50i: Add support for Olimex A64-Olinuxino-eMMC arch/arm/dts/Makefile | 1 + arch/arm/dts/sun50i-a64-olinuxino-emmc.dts | 23

Re: [U-Boot] [PATCH v2 0/2] arm64: dts: sun50i: Add support for A64 OLinuXino (with eMMC)

On 06/09/19 9:05 pm, Jagan Teki wrote: > On Fri, Aug 23, 2019 at 1:56 AM Sunil Mohan Adapa wrote: >> >> This is a follow up a patch that didn't create a separate dts: >> https://lists.denx.de/pipermail/u-boot/2019-July/379109.html >> >> A64 OLinuXino boa

[U-Boot] [PATCH v3] arm64: dts: sun50i: Add support for A64 OLinuXino (with eMMC)

=sunxi/dt-for-5.4=02bb66b347ff8115f53948f86b884e008ba385b9 This patch has been tested on A64-OLinuXino-1Ge16GW and is based on Linux device-tree and a64-olinuxino_defconfig. changes: v3: Squash two separate patches into a single one. v2: Separate device tree for emmc models. Signed-off-by: Sunil

[U-Boot] [PATCH] sunxi: dts: a64-olinuxino: Fix regression to eMMC support

Description for eMMC is missing the DTS causing eMMC to regress after DM_MMC was enabled for sunxi in a7cca5793774ee139b75a704d6efaa4d29f09f93. Signed-off-by: Sunil Mohan Adapa Tested-by: Sunil Mohan Adapa Cc: linux-su...@googlegroups.com --- arch/arm/dts/sun50i-a64-olinuxino.dts | 11

Re: [RFC PATCH 1/1] efi_loader: Enable RISCV_EFI_BOOT_PROTOCOL support

Hi Heinrich, On Thu, Jan 27, 2022 at 09:44:57AM +0100, Heinrich Schuchardt wrote: > On 1/26/22 12:06, Sunil V L wrote: > > This adds support for new RISCV_EFI_BOOT_PROTOCOL to > > communicate the boot hart ID to bootloader/kernel on RISC-V > > UEFI platforms. > > &

[RFC PATCH V2 1/2] efi_loader: Enable RISCV_EFI_BOOT_PROTOCOL support

This adds support for new RISCV_EFI_BOOT_PROTOCOL to communicate the boot hart ID to bootloader/kernel on RISC-V UEFI platforms. The specification of the protocol is hosted at: https://github.com/riscv-non-isa/riscv-uefi Signed-off-by: Sunil V L --- include/efi_api.h | 4 +++ include

[RFC PATCH V2 2/2] efi_selftest: unit test for RISCV_EFI_BOOT_PROTOCOL

Add a test for the RISCV_EFI_BOOT_PROTOCOL. Signed-off-by: Sunil V L --- lib/efi_selftest/Makefile | 1 + lib/efi_selftest/efi_selftest_riscv.c | 119 ++ 2 files changed, 120 insertions(+) create mode 100644 lib/efi_selftest/efi_selftest_riscv.c diff

[RFC PATCH V2 0/2] RISCV_EFI_BOOT_PROTOCOL support in U-boot

which consume this protocol. The linux patch can be found in: riscv_boot_protocol_rfc_v2 branch at https://github.com/vlsunil/linux.git Changes since RFC V1: - Used EFI_ENTRY/EXIT and removed need for static variable - Addressed other comments from Heinrich - Added unit test patch Sunil V

[RFC PATCH 1/1] efi_loader: Enable RISCV_EFI_BOOT_PROTOCOL support

This adds support for new RISCV_EFI_BOOT_PROTOCOL to communicate the boot hart ID to bootloader/kernel on RISC-V UEFI platforms. Signed-off-by: Sunil V L --- include/efi_api.h | 4 +++ include/efi_loader.h | 2 ++ include/efi_riscv.h| 16 + lib/efi_loader

[RFC PATCH 0/1] RISCV_EFI_BOOT_PROTOCOL support in U-boot

this protocol. The linux patch can be found in: riscv_boot_protocol_rfc_v1 branch at https://github.com/vlsunil/linux.git Sunil V L (1): efi_loader: Enable RISCV_EFI_BOOT_PROTOCOL support include/efi_api.h | 4 +++ include/efi_loader.h | 2 ++ include/efi_riscv.h| 16

Re: [PATCH 1/1] efi_loader: use EFI_EXIT in efi_riscv_get_boot_hartid

return EFI_INVALID_PARAMETER; > + return EFI_EXIT(EFI_INVALID_PARAMETER); > > *boot_hartid = gd->arch.boot_hart; > Reviewed-by: Sunil V L > -- > 2.37.2 >