[PATCH 2/2] arm: dts: k3-j721e: Fix interconnect node names

The various CBASS interconnect nodes on K3 J721E SoCs are defined using the node name "interconnect". This is not a valid node name as per the dt-schema. Fix these node names to use the standard name used for SoC interconnects, "bus". Signed-off-by: Suman Anna --- arch/arm/dts/k3-j721e.dtsi | 4

[PATCH 1/2] arm: dts: k3-am65: Fix interconnect node names

The various CBASS interconnect nodes on K3 AM65x SoCs are defined using the node name "interconnect". This is not a valid node name as per the dt-schema. Fix these node names to use the standard name used for SoC interconnects, "bus". Signed-off-by: Suman Anna --- arch/arm/dts/k3-am65.dtsi | 6

[PATCH 0/2] Update TI K3 cbass interconnect node names

Hi Lokesh, The following 2 patches are minor cleanups that fix the various CBASS interconnect node names from "interconnect" to "bus" on K3 AM65x and J721E SoCs. "bus" is the correct dt-schema acceptible node name. regards Suman Suman Anna (2): arm: dts: k3-am65: Fix interconnect node names

[PATCH 8/9] bcmgenet: fix DMA buffer management

This commit fixes a serious issue occurring when several network commands are run on a raspberry pi 4 board: for instance a "dhcp" command and then one or several "tftp" commands. In this case, packet recv callbacks were called several times on the same packets, and send function was failing most

[PATCH 1/9] fs/fat/fat.c: Do not perform zero block reads if there are no blocks left

While using u-boot with qemu's virtio driver I stumbled across a problem reading files less than sector size. On the real hardware the block reader seems ok with reading zero blocks, and while we could fix the virtio host side of qemu to deal with a zero block read instead of crashing, the u-boot

[PULL][PATCH 0/9] Raspberry pi improvements qemu/usb/ethernet

I would like to get these patches merged for the next release, but there has been no movement on some of them in over a month. I would fix any problems with the patches, but I am not aware of any. The patch set has been tested on all the generations of the raspberry pi hardware and qemu and

[PATCH 7/9] usb.c: Add a retry in the usb_prepare_device()

I have found through testing some USB 2 composite mouse/keyboard devices do not response to the usb_set_address call immediately following the port reset. It can take anywhere from 2ms to 20ms. This patch adds a retry and delay for usb_prepare_device() and allows all the USB keyboards I tried to

[PATCH 2/9] xhci: Add polling support for USB keyboards

The xhci driver was causing intermittent 5 second delays from the USB keyboard polling hook. Executing something like a "sleep 1" for example would sleep for 5 seconds, unless an event occurred on the USB bus to shorten the delay. Modeled after the code in the DWC2 driver, a nonblock state was

[PATCH 5/9] xhci-ring.c: Add the poll_pend state to properly abort transactions

xhci_trl_tx and xhchi_bulk_tx can be called synchronously by other drivers such as the usb storage or network, while the keyboard driver exclusively uses the polling mode. And pending polling transactions must be aborted before switching modes to avoid corrupting the state of the controller.

[PATCH 6/9] xhci-ring: Fix crash when issuing "usb reset"

If a "usb reset" is issued when the poll_pend state is set the abort_td() function will hit one of the BUG() statements in abort_td() or the BUG() statement at the end of xhci_wait_for_event(). The controller has been reset, so the rest of the cleanup should be skipped and poll_pend flag should

[PATCH 9/9] bcmgenet: Add support for rgmii-rxid

The commit 57805f2270c4 ("net: bcmgenet: Don't set ID_MODE_DIS when not using RGMII") needed to be extended for the case of using the rgmii-rxid. The latest version of the Rasbperry Pi4 dtb files for the 5.4 now specify the rgmii-rxid. Signed-off-by: Jason Wessel --- drivers/net/bcmgenet.c | 3

[PATCH 3/9] usb_kbd: succeed even if no interrupt is pending

After the initial configuration some USB keyboard+mouse devices never return any kind of event on the interrupt line. In particular, the device identified by "Cypress Cypress USB Keyboard / PS2 Mouse as 3f98.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:04B4:0101.0001/input/input0" never returns a data

[PATCH 4/9] common/usb.c: Work around keyboard reporting "USB device not accepting new address"

When resetting the rpi3 board sometimes it will display: USB device not accepting new address (error=0) After the message appears, the usb keyboard will not work. It seems that the configuration actually did succeed however. Checking the device status for a return code of zero and

[PATCH] Convert CONFIG_SYS_MMC_ENV_DEV et al to Kconfig

This converts the following to Kconfig: CONFIG_SYS_MMC_ENV_DEV CONFIG_SYS_MMC_ENV_PART Cc: Priyanka Jain Cc: Madalin Bucur Signed-off-by: Tom Rini --- Due to some non-environment usage of the variables, cc'ing a few folks. --- configs/am335x_boneblack_vboot_defconfig | 1 +

[PATCH] mvebu: bubt: Drop dead code

The code around CONFIG_SYS_MMC_ENV_PART has been untested since merge. This can be seen by it referencing 'mmc->part_num' which was migrated elsewhere prior to this code being merged. Cc: Joel Johnson Cc: Stefan Roese Signed-off-by: Tom Rini --- cmd/mvebu/bubt.c | 15 --- 1 file

Re: [PATCH] CONFIG_NR_DRAM_BANKS: Remove unreferenced code as its always defined

> Since commit 86cf1c82850f ("configs: Migrate CONFIG_NR_DRAM_BANKS") & > commit 999a772d9f24 ("Kconfig: Migrate CONFIG_NR_DRAM_BANKS"), > CONFIG_NR_DRAM_BANKS is always defined with a value (4 is default). > It makes no sense to still carry code that is guarded with > "#ifndef

[PATCH 1/1] test: do not rely on => being the prompt

In our tests we should use the customized prompt for testing. Reported-by: Tom Rini Signed-off-by: Heinrich Schuchardt --- test/py/tests/test_efi_loader.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/py/tests/test_efi_loader.py b/test/py/tests/test_efi_loader.py

Re: [PATCH] CONFIG_NR_DRAM_BANKS: Remove unreferenced code as its always defined

On Fri, Jul 24, 2020 at 5:54 PM Stefan Roese wrote: > > Since commit 86cf1c82850f ("configs: Migrate CONFIG_NR_DRAM_BANKS") & > commit 999a772d9f24 ("Kconfig: Migrate CONFIG_NR_DRAM_BANKS"), > CONFIG_NR_DRAM_BANKS is always defined with a value (4 is default). > It makes no sense to still carry

[PATCH 1/1] dm: remove superfluous comment for union ofnode_union

"future live tree" does not make sense anymore as we have CONFIG_OF_LIVE. Signed-off-by: Heinrich Schuchardt --- include/dm/ofnode.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/dm/ofnode.h b/include/dm/ofnode.h index a0d3df7786..8df2facf99 100644 ---

[PATCH v2 1/1] mtd: cfi_flash: read device tree correctly

The size of #address-cells and #size-cells is not correctly determined if CONFIG_OF_LIVE=n. dev_read_size_cells() and dev_read_addr_cells() do not walk up the device tree to find the number of cells. On error they return 1 and 2 respectively. On qemu_arm64_defconfig this leads to the incorrect

Re: [PATCH 1/1] mtd: cfi_flash: read device tree correctly

On 24.07.20 11:14, Rick Chen wrote: > Hi Heinrich > >> From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Heinrich >> Schuchardt >> Sent: Tuesday, July 21, 2020 10:51 AM >> To: Stefan Roese >> Cc: Simon Glass; u-boot@lists.denx.de; Heinrich Schuchardt >> Subject: [PATCH 1/1] mtd:

Re: [PATCH v2 8/8] test: dm: add a test for class button

Hi Simon, > Hi Philippe, > > On Mon, 20 Jul 2020 at 08:30, Philippe REYNES > wrote: >> >> Hi Simon, >> >> > Hi Philippe, >> > >> > On Fri, 17 Jul 2020 at 06:22, Philippe Reynes >> > wrote: >> >> >> >> Add a test to confirm that we can read button state >> >> using the button-gpio driver.

[PATCH v3 3/8] cmd: button: add a new 'button' command

Adds a command 'button' that provides the list of buttons supported by the board, and the state of a button. Reviewed-by: Simon Glass Signed-off-by: Philippe Reynes --- Changelog: v3: - no change v2 - no change cmd/Kconfig | 11 cmd/Makefile | 1 + cmd/button.c | 86

[PATCH v3 8/8] test: dm: add a test for class button

Add a test to confirm that we can read button state using the button-gpio driver. Signed-off-by: Philippe Reynes --- Changelog: v3: - no change v2: - new commit in the serie test/dm/Makefile | 1 + test/dm/button.c | 74 2 files

[PATCH v3 6/8] sandbox: enable button

Enable the support of button (driver and command) on sandbox. Reviewed-by: Simon Glass Signed-off-by: Philippe Reynes --- Changelog: v3: - no change v2: - no change configs/sandbox_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/configs/sandbox_defconfig

[PATCH v3 4/8] sandbox: dtsi: add buttons

Adds two buttons on sandbox so button framework may be tested. Reviewed-by: Simon Glass Signed-off-by: Philippe Reynes --- Changelog: v3: - update comptatible to "gpio-keys" v2: - no change arch/sandbox/dts/sandbox.dtsi | 14 ++ 1 file changed, 14 insertions(+) diff --git

[PATCH v3 2/8] dm: button: add a driver for button driven by gpio

Add a simple driver which allows use of buttons attached to GPIOs. Reviewed-by: Simon Glass Signed-off-by: Philippe Reynes --- Changelog: v3: - change compatible to gpio-keys and gpio-keys-polled (feedback from Neil Armstrong) v2: - remove useless default in Kconfig - re-order include - fix

[PATCH v3 1/8] dm: button: add an uclass for button

Add a new uclass for button that implements two functions: - button_get_by_label - button_get_status Reviewed-by: Simon Glass Signed-off-by: Philippe Reynes --- Changelog: v3: - no change v2: - re-order include - use uclass_id_foreach_dev - add comments to enum button_state_t drivers/Kconfig

[PATCH v3 7/8] test/py: add tests for the button commands

Adds tests for the button commands. Reviewed-by: Simon Glass Signed-off-by: Philippe Reynes --- Changelog: v3: - update compatible to "gpio-keys" v2: - no change (button uclass test is added in another commit arch/sandbox/dts/test.dts| 14 ++ test/py/tests/test_button.py | 19

[PATCH v3 5/8] sandbox64: enable button

Enable the support of button (driver and command) on sandbox64. Reviewed-by: Simon Glass Signed-off-by: Philippe Reynes --- Changelog: v3: - no change v2: - no change configs/sandbox64_defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/configs/sandbox64_defconfig

Re: [PATCH V2 7/7] env: Add support for explicit write access list

On Tue, Jul 07, 2020 at 08:51:39PM +0200, Marek Vasut wrote: > This option marks any U-Boot variable which does not have explicit 'w' > writeable flag set as read-only. This way the environment can be locked > down and only variables explicitly configured to be writeable can ever > be changed by

Re: [PATCH V2 6/7] env: Add option to only ever append environment

On Tue, Jul 07, 2020 at 08:51:38PM +0200, Marek Vasut wrote: > Add configuration option which prevents the environment hash table to be > ever cleared and reloaded with different content. This is useful in case > the first environment loaded into the hash table contains e.g. sensitive > content

Re: [PATCH V2 4/7] env: Fix invalid env handling in env_init()

On Tue, Jul 07, 2020 at 08:51:36PM +0200, Marek Vasut wrote: > This fixes the case where there are multiple environment drivers, one of > them is the default environment one, and it is followed by an environment > driver which does not implement .init() callback. The default environment > driver

Re: [PATCH V2 5/7] env: nowhere: Implement .load callback

On Tue, Jul 07, 2020 at 08:51:37PM +0200, Marek Vasut wrote: > Add .load callback for the 'nowhere' environment driver. This is useful > for when the 'nowhere' driver is used in combination with other drivers > and should be used to load the default environment. > > Signed-off-by: Marek Vasut

Re: [PATCH V2 2/7] env: Add H_DEFAULT flag

On Tue, Jul 07, 2020 at 08:51:34PM +0200, Marek Vasut wrote: > Add another internal environment flag which indicates that the operation > is resetting the environment to the default one. This allows the env code > to discern between import of external environment and reset to default. > >

Re: [PATCH V2 1/7] env: Warn on force access if ENV_ACCESS_IGNORE_FORCE set

On Tue, Jul 07, 2020 at 08:51:33PM +0200, Marek Vasut wrote: > If the ENV_ACCESS_IGNORE_FORCE is set, inform user that the variable > cannot be force-set if such attempt happens. > > Signed-off-by: Marek Vasut Reviewed-by: Tom Rini -- Tom signature.asc Description: PGP signature

Re: [PATCH V2 3/7] env: Discern environment coming from external storage

On Tue, Jul 07, 2020 at 08:51:35PM +0200, Marek Vasut wrote: > Add another custom environment flag which discerns environment coming > from external storage from environment set by U-Boot itself. > > Signed-off-by: Marek Vasut Reviewed-by: Tom Rini -- Tom signature.asc Description: PGP

[PATCH] CONFIG_NR_DRAM_BANKS: Remove unreferenced code as its always defined

Since commit 86cf1c82850f ("configs: Migrate CONFIG_NR_DRAM_BANKS") & commit 999a772d9f24 ("Kconfig: Migrate CONFIG_NR_DRAM_BANKS"), CONFIG_NR_DRAM_BANKS is always defined with a value (4 is default). It makes no sense to still carry code that is guarded with "#ifndef CONFIG_NR_DRAM_BANKS" (and

Re: [PATCH v4 00/27] rockchip: x86: Support building ROM files automatically with binman

Hi Kever (and other Rockchip people), Are there any more comments on this series? I can pick it up via -dm but I would like to get more comments if possible. I'd also like to see if someone can take on removing the other ad-hoc Rockchip script. Regards, Simon On Sun, 19 Jul 2020 at 21:07,

[PATCH] arm: imx6q: pcm058: Rework SPI NOR configuration

Enable CONFIG_SPL_DM_SPI_FLASH to be able to boot from SPI NOR, modify the offset of U-boot proper in the SPI NOR, so the difference in offset matches between SPL and U-boot matches that of the SD Card, allowing u-boot-with-spl.imx to also be copied to SPI NOR at an offset of 0x400. Update the

Re: [U-Boot] Pull request: u-boot-riscv/master 20200724

On Fri, Jul 24, 2020 at 03:18:45PM +0800, ub...@andestech.com wrote: > Hi Tom, > > Please pull some riscv updates: > > - Fix SiFive HiFive Unleashed board booting failure problem. > - Enable SiFive fu540 PWM driver. > - Support SiFive fu540: SPI boot. > - Update OpenSBI used for RISC-V CI

Re: [PATCH v2 06/10] drivers: spi: Add SPI controller driver for Octeon

On 24.07.20 15:56, Daniel Schwierzeck wrote: Am Donnerstag, den 23.07.2020, 12:17 +0200 schrieb Stefan Roese: From: Suneel Garapati Adds support for SPI controllers found on Octeon II/III and Octeon TX TX2 SoC platforms. Signed-off-by: Aaron Williams Signed-off-by: Suneel Garapati

Re: [PATCH v2 06/10] drivers: spi: Add SPI controller driver for Octeon

Am Donnerstag, den 23.07.2020, 12:17 +0200 schrieb Stefan Roese: > From: Suneel Garapati > > Adds support for SPI controllers found on Octeon II/III and Octeon TX > TX2 SoC platforms. > > Signed-off-by: Aaron Williams > Signed-off-by: Suneel Garapati > Signed-off-by: Stefan Roese > Cc:

[PATCH] sandbox, test: change hog gpio

Since commit 9ba84329dc45 ("sandbox, test: add test for GPIO_HOG function"), the gpio_a 0,1,2 and 3 are used by hog in test.dts. But 2 leds 'sandbox:red' and 'sandbox:green' are using gpio_a 0 and 1. As hog always request his gpios, the led command on both led is broken: => led sandbox:red LED

Re: Using gerrit or github for review?

Hi, I'm a bit late to this discussion, but I'll drop my $0.02 anyway. On 13/07/20 02:06PM, Simon Glass wrote: > Hi Heinrich, > > On Mon, 13 Jul 2020 at 13:36, Heinrich Schuchardt wrote: > > > > On 13.07.20 20:25, Simon Glass wrote: > > > Hi, > > > > > > At present U-Boot uses the mailing list

Re: [PATCH 07/18] arm: mach-k3: j721e: Add detection for j721e

On 24/07/20 5:55 pm, Grygorii Strashko wrote: > > > On 23/07/2020 11:47, Lokesh Vutla wrote: >> Add an api soc_is_j721e(), and use it to enable certain functionality >> that is available only on j721e. >> >> Signed-off-by: Lokesh Vutla >> Signed-off-by: Suman Anna >> --- >>  

Re: Please pull u-boot-dm

On Thu, Jul 23, 2020 at 09:09:33PM -0400, Tom Rini wrote: > On Mon, Jul 20, 2020 at 02:19:02PM -0600, Simon Glass wrote: > > > Hi Tom, > > > > https://gitlab.denx.de/u-boot/custodians/u-boot-dm/pipelines/4139 > > > > The following changes since commit 7303ba10a4a39852b9ba356fae5656b43122eec6: >

[PATCH] clk: versal: Move pm_query_id out of clock driver

There is no reason to have firmware specific structure in clock driver. Move it to generic location and also initialize enum values which is based on https://lore.kernel.org/linux-arm-kernel/20200318125003.ga2727...@kroah.com/ recommended way to go to make sure that values guaranteed by compiler.

Re: [PATCH 07/18] arm: mach-k3: j721e: Add detection for j721e

On 23/07/2020 11:47, Lokesh Vutla wrote: Add an api soc_is_j721e(), and use it to enable certain functionality that is available only on j721e. Signed-off-by: Lokesh Vutla Signed-off-by: Suman Anna --- arch/arm/mach-k3/common.c | 10 ++

Re: [PATCH 2/2] xilinx: zynqmp: Enable DFU tftp support

st 15. 7. 2020 v 15:51 odesílatel Michal Simek napsal: > > Enable DFU tftp support for firmware update. Fill dfu_ram_tftp variable to > have command present for showing how to use it. > > boot FIT image has been created from below fragment. Key part is that type > of image has to be firmware.

Re: [PATCH 1/2] xilinx: Align dfu ram with booti command

st 15. 7. 2020 v 15:51 odesílatel Michal Simek napsal: > > Image should be loaded to 0x8 address and not to $kernel_addr_r. > Also kernel_addr, fdt_addr and fdt_size in zynqmp case are not defined > that's why define it to be aligned with Versal. > > Signed-off-by: Michal Simek > --- > >

Re: [PATCH] arm64: zynqmp: Reduce malloc memory for mini QSPI configuration

čt 16. 7. 2020 v 12:03 odesílatel Michal Simek napsal: > > From: Ashok Reddy Soma > > Mini U-boot runs on lower foot print of 256KB OCM. Hence 8K memory > for malloc may not be required. Reduce it by 1.5K. > > Signed-off-by: Ashok Reddy Soma > Signed-off-by: Michal Simek > --- > >

Re: [PATCH v2 0/3] xilinx: Enable Versal allocation from low memory

pá 10. 7. 2020 v 14:40 odesílatel Michal Simek napsal: > > Hi, > > Generated DTS files don't need to have memory nodes sorted out that's why > it can happen that the first memory node is not pointing to lowest DDR > which is normally used for system boot. That's why new function was > introduced

Re: [PATCH] versal: fix versal PM ret payload size

st 8. 7. 2020 v 14:54 odesílatel Michal Simek napsal: > > From: Ibai Erkiaga > > The PM return payload size is defined as 4 bytes for Versal arquitecture > while the PM calls implemented both in the Versal clock driver and > ZynqMP firmware driver expects 5 bytes length. > > Signed-off-by: Ibai

Re: [PATCH v2] xilinx: versal: Add new versal loadpdi command

st 24. 6. 2020 v 14:49 odesílatel Michal Simek napsal: > > From: T Karthik Reddy > > Versal loadpdi command is used for loading secure & non-secure > pdi images. > > Signed-off-by: T Karthik Reddy > Signed-off-by: Michal Simek > --- > > Changes in v2: > - Fix failures for versal mini

Re: [PATCH] arm64: zynqmp: Fix set_fdtfile() not to break u-boots DTB

st 24. 6. 2020 v 14:44 odesílatel Michal Simek napsal: > > Origin function was calling strsep which replaced delimiter ',' by a null > byte ('\0'). Operation was done directly on FDT which ends up with the > following behavior: > > ZynqMP> printenv fdtfile > fdtfile=xilinx/zynqmp.dtb > ZynqMP>

Re: [PATCH v4 08/17] board_f: Factor out bdinfo bi_mem{start, size} to setup_bdinfo

Hi Ovidiu, > Move all assignments to gd->bd->bi_mem{start,size} to generic code in > setup_bdinfo. > > Xtensa architecture is special in this regard as it defines its own > handling of gd->bd->bi_mem{start,size} fields. In order to avoid defining > a weak SDRAM function, let arch_setup_bdinfo

Re: [PATCH] xilinx: Setup bootm variables

pá 10. 7. 2020 v 13:20 odesílatel Michal Simek napsal: > > On system with PL DDR which is placed before PS DDR in DT > env_get_bootm_size() and env_get_bootm_low() without specifying bootm_low > and bootm_size variables are taking by default gd->bd->bi_dram[0].start and > gd->bd->bi_dram[0].size.

[PATCH v4 13/17] dm: blk: Use IS_ENABLED() instead of #ifdefs in blk_post_probe

Use IS_ENABLED() instead of #ifdef in blk_post_probe function. No functional change intended. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- drivers/block/blk-uclass.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/block/blk-uclass.c

[PATCH v4 17/17] common/board_r: Move blkcache_init call earlier in the boot sequence

blkcache_init manually relocates blkcache list pointers when CONFIG_NEEDS_MANUAL_RELOC is enabled. However, it is called very late in the boot sequence, which could be a problem if previous boot calls execute blkcache operations with the non-relocated pointers. For example, mmc is initialized

[PATCH v4 14/17] drivers: serial: Make serial_initialize return int

serial_initialize is called only during the common init sequence, after relocation (in common/board_r.c). Because it has a void return value, it has to wrapped in initr_serial. In order to be able to get rid of this indirection, make serial_initialize return int. Remove extern from prototype in

[PATCH v4 16/17] blkcache: Extend blkcache_init to cover CONFIG_NEEDS_MANUAL_RELOC

Extend manual relocation of block_cache list pointers to all platforms that enable CONFIG_NEEDS_MANUAL_RELOC. Remove m68k-specific checks and provide a single implementation that adds gd->reloc_off to the pre-relocation pointers. Acked-by: Angelo Dureghello Tested-by: Angelo Dureghello

[PATCH v4 03/17] Kconfig: Convert CONFIG_SYS_SRAM_SIZE to Kconfig

This converts ad-hoc CONFIG_SYS_SRAM_SIZE to Kconfig. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- Kconfig | 7 +++ include/configs/devkit8000.h | 1 - include/configs/pic32mzdask.h | 2 -- include/configs/tricorder.h | 1 -

[PATCH v4 15/17] common/board_r: Remove initr_serial wrapper

Remove the initr_serial->serial_initialize indirection and call serial_initialize directly. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- common/board_r.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/common/board_r.c b/common/board_r.c index

[PATCH v4 10/17] board_f: m68k: Factor out m68k-specific bdinfo setup

Factor out m68k-specific bdinfo setup to arch_setup_bdinfo in arch/m68k/lib/bdinfo.c. Also, use if(IS_ENABLED()) instead of #ifdef where possible. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- arch/m68k/lib/bdinfo.c | 21 + common/board_f.c | 19

[PATCH v4 11/17] board_f: ppc: Factor out ppc-specific bdinfo setup

Factor out ppc-specific bdinfo setup from generic init sequence to arch_setup_bdinfo in arch/powerpc/lib/bdinfo.c. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- arch/powerpc/lib/bdinfo.c | 25 + common/board_f.c | 36

[PATCH v4 12/17] board_f: Remove setup_board_part1

Now that all arch specific code was converted to setup_bdinfo, we can remove setup_board_part1. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- common/board_f.c | 12 +--- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/common/board_f.c b/common/board_f.c index

[PATCH v4 06/17] board_f: Introduce setup_bdinfo initcall

Introduce setup_bdinfo initcall as a generic routine to populate bdinfo fields. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- common/board_f.c | 6 ++ include/init.h | 10 ++ 2 files changed, 16 insertions(+) diff --git a/common/board_f.c b/common/board_f.c index

[PATCH v4 05/17] cmd: bdinfo: Move sram info prints to generic code

bi_sramstart and bi_sramsize are generic members of the bd_info structure, so move the m68k/powerpc-specific prints to generic code. Also, print them only if SRAM support is enabled via CONFIG_SYS_HAS_SRAM. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- arch/m68k/lib/bdinfo.c|

[PATCH v4 09/17] board_f: Move sram bdinfo assignments to generic code

Move sram related bdinfo from arch-specific setup_board_part1 to generic code in setup_bdinfo. Also use "if (IS_ENABLED(CONFIG_SYS_HAS_SRAM))" instead of "#ifdef CONFIG_SYS_SRAM_BASE". Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- common/board_f.c | 10 +- 1 file changed,

[PATCH v4 04/17] Kconfig: Remove CONFIG_SYS_SRAM_START

Remove ad-hoc CONFIG_SYS_SRAM_START and use CONFIG_SYS_SRAM_BASE instead. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- Kconfig | 2 ++ include/configs/devkit8000.h | 3 --- include/configs/tricorder.h | 3 --- scripts/config_whitelist.txt | 1 - 4 files

[PATCH v4 08/17] board_f: Factor out bdinfo bi_mem{start, size} to setup_bdinfo

Move all assignments to gd->bd->bi_mem{start,size} to generic code in setup_bdinfo. Xtensa architecture is special in this regard as it defines its own handling of gd->bd->bi_mem{start,size} fields. In order to avoid defining a weak SDRAM function, let arch_setup_bdinfo overwrite the generic

[PATCH v4 02/17] Kconfig: Convert CONFIG_SYS_SRAM_BASE to Kconfig

This converts ad-hoc CONFIG_SYS_SRAM_BASE to Kconfig. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- Kconfig | 5 + include/configs/pic32mzdask.h | 1 - scripts/config_whitelist.txt | 1 - 3 files changed, 5 insertions(+), 2 deletions(-) diff --git

[PATCH v2 1/3] armv8: gpio: add gpio feature

From: "hui.song" add one struct mpc8xxx_gpio_plat to enable gpio feature. Signed-off-by: hui.song --- .../include/asm/arch-fsl-layerscape/gpio.h| 22 +++ 1 file changed, 22 insertions(+) create mode 100644 arch/arm/include/asm/arch-fsl-layerscape/gpio.h diff --git

[PATCH v4 07/17] board_f: Introduce arch_setup_bdinfo initcall

Certain architectures (ppc, mips, sh, m68k) use setup board_part1 and setup_board_part2 calls during pre-relocation init to populate gd->bd boardinfo fields. This makes the generic init sequence cluttered with arch-specific ifdefs. In order to clean these arch-specific sequences from generic

[PATCH v2 3/3] gpio: mpc8xxx: support fsl-layerscape platform.

From: "hui.song" Make the MPC8XXX gpio driver to support the fsl-layerscape. Signed-off-by: hui.song --- drivers/gpio/mpc8xxx_gpio.c | 108 +--- 1 file changed, 87 insertions(+), 21 deletions(-) diff --git a/drivers/gpio/mpc8xxx_gpio.c

[PATCH v1 21/24] net: Add NIC controller driver for OcteonTX2

From: Suneel Garapati Adds support for Network Interface controllers found on OcteonTX2 SoC platforms. Signed-off-by: Suneel Garapati Cc: Joe Hershberger Signed-off-by: Stefan Roese --- Changes in v1: - Change patch subject - Rebased on latest TOT - Removed inclusion of common.h

[PATCH v2 2/3] dm: armv8: gpio: include for fsl-layerscape

From: "hui.song" Enable the gpio feature on fsl-layerscape platform. Signed-off-by: hui.song --- arch/arm/include/asm/gpio.h | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/arch/arm/include/asm/gpio.h b/arch/arm/include/asm/gpio.h index 333e407b66..7715a01706

[PATCH v1 18/24] mmc: Add MMC controller driver for OcteonTX / TX2

From: Suneel Garapati Adds support for MMC controllers found on OcteonTX or OcteonTX2 SoC platforms. Signed-off-by: Aaron Williams Signed-off-by: Suneel Garapati Cc: Peng Fan Signed-off-by: Stefan Roese --- Changes in v1: - Change patch subject - Rebased on latest TOT - Removed inclusion

[PATCH] Fix data abort caused by mis-aligning fit data in

Attempting to place device tree immediately after an image in memory can lead to mis-aligned data accesses if that image size is not divisible by the alignment requirements of the architecture. Data aborts caused by this were observed on a custom Marvel A388 based system, where the image was a

[PATCH v4 01/17] Kconfig: Introduce CONFIG_SYS_HAS_SRAM

In order to be able to replace "#ifdef CONFIG_SYS_SRAM_BASE" sequences with the IS_ENABLED() equivalent, introduce a new boolean Kconfig option that signals whether the platform has SRAM support. Reviewed-by: Simon Glass Signed-off-by: Ovidiu Panait --- Kconfig | 11 +++ 1 file

[PATCH 4/7] rockchip: Add Engicam PX30.Core EDIMM2.2 Starter Kit

PX30.Core is an EDIMM SOM based on Rockchip PX30 from Engicam. EDIMM2.2 Starter Kit is an EDIMM 2.2 Form Factor Capacitive Evaluation Board from Engicam. PX30.Core needs to mount on top of this Evaluation board for creating complete PX30.Core EDIMM2.2 Starter Kit. Add support for it.

[PATCH 7/7] doc: rockchip: Document Rockchip miniloader flashing

This would be useful and recommended boot flow for new boards which has doesn't have the DDR support yet in mainline. Sometimes it is very useful for debugging mainline DDR support. Documen it for px30 boot flow. Signed-off-by: Jagan Teki --- doc/board/rockchip/rockchip.rst | 40

[PATCH 5/7] arm: dts: rockchip: px30: Add Engicam C.TOUCH 2.0 10.1" OF

Engicam C.TOUCH 2.0 10.1" Open Frame is a Carrier board with Capacitive touch 10.1" open frame. Genaral features: - TFT 10.1" industrial, 1280x800 LVDS display - Ethernet 10/100 - Wifi/BT - USB Type A/OTG - Audio Out - CAN SOM's like PX30.Core needs to mount on top of this Carrier board for

[PATCH 6/7] rockchip: Add Engicam PX30.Core C.TOUCH 2.0 10.1" OF

PX30.Core is an EDIMM SOM based on Rockchip PX30 from Engicam. C.TOUCH 2.0 10.1" Open Frame is a Carrier board with Capacitive touch 10.1" open frame from Engicam. PX30.Core needs to mount on top of this Carrier board for creating complete PX30.Core C.TOUCH 2.0 10.1" Open Frame. Add support for

[PATCH 3/7] rockchip: px30: Add EVB_PX30 Kconfig help

TARGET_EVB_PX30 can be possible to use other px30 boards. Add the help text for existing EVB, so-that the new boards which are resuing this config option can mention their board help text. This would help to track which boards are using EVB_PX30 config. Signed-off-by: Jagan Teki ---

[PATCH 2/7] arm: dts: rockchip: Add Engicam PX30.Core SOM

PX30.Core is an EDIMM SOM based on Rockchip PX30 from Engicam. General features: - Rockchip PX30 - Up to 2GB DDR4 - eMMC 4 GB expandible - rest of PX30 features PX30.Core needs to mount on top of Engicam baseboards for creating complete platform boards. Possible baseboards are, - EDIMM2.2 -

[PATCH 1/7] arm: dts: rockchip: px30: Add Engicam EDIMM2.2 Starter Kit

Engicam EDIMM2.2 Starter Kit is an EDIMM 2.2 Form Factor Capacitive Evaluation Board. Genaral features: - LCD 7" C.Touch - microSD slot - Ethernet 1Gb - Wifi/BT - 2x LVDS Full HD interfaces - 3x USB 2.0 - 1x USB 3.0 - HDMI Out - Mini PCIe - MIPI CSI - 2x CAN - Audio Out SOM's like PX30.Core

[PATCH 0/7] rockchip: Add Engicam PX30.Core support

PX30.Core is an EDIMM SOM based on Rockchip PX30 from Engicam. PX30.Core needs to mount on top of Engicam baseboards for creating complete platform boards. Possible baseboards are, - EDIMM2.2 Starter Kit - C.TOUCH 2.0 10.1" Open Frame Right now boot support is working via Rockchip miniloader,

RE: [PATCH v4 2/6] drivers: net: add a DSA sandbox driver

>-Original Message- >From: Priyanka Jain (OSS) [...] > >Kindly fix build error for target >BUILDMAN="sandbox x86" TOOLCHAIN="i386" > >https://travis-ci.org/github/p-priyanka-jain/u-boot/jobs/711090082 > > Hi Priyanka, I will look into rebasing the patches and addressing these new

Re: [PATCH 15/18] arm: dts: k3-j7200: Add dts support

On 23/07/20 3:20 pm, Faiz Abbas wrote: > Hi Lokesh, > > Hi Lokesh, > > On 23/07/20 2:17 pm, Lokesh Vutla wrote: >> Add the basic r5 and a72 basic dts for j7200. Following nodes were >> supported: >> - UART >> - MMC SD >> - I2C >> - TISCI communication >> >> Signed-off-by: Lokesh Vutla >>

[PATCH v1 24/24] arm: octeontx2: Add support for OcteonTX2 SoC platforms

From: Suneel Garapati This patch adds support for all OcteonTX2 96xx/95xx boards from Marvell. For 96xx boards, use octeontx_96xx_defconfig and for 95xx boards, use octeontx_95xx_defconfig. Signed-off-by: Suneel Garapati Signed-off-by: Stefan Roese --- Changes in v1: - Changed patch subject

[PATCH v1 13/24] arm: octeontx: Add headers for OcteonTX

From: Suneel Garapati Signed-off-by: Suneel Garapati Signed-off-by: Stefan Roese --- Changes in v1: - Change patch subject arch/arm/include/asm/arch-octeontx/board.h| 123 ++ arch/arm/include/asm/arch-octeontx/clock.h| 25 + .../asm/arch-octeontx/csrs/csrs-mio_emm.h | 1193

[PATCH v1 19/24] mtd: nand: Add NAND controller driver for OcteonTX

From: Suneel Garapati Adds support for NAND controllers found on OcteonTX or OcteonTX2 SoC platforms. Also includes driver to support Hardware ECC using BCH HW engine found on these platforms. Signed-off-by: Aaron Williams Signed-off-by: Suneel Garapati Signed-off-by: Stefan Roese ---

[PATCH v1 22/24] watchdog: Add reset support for OcteonTX / TX2

From: Suneel Garapati Adds support for Core 0 watchdog poke on OcteonTX and OcteonTX2 platforms. Signed-off-by: Suneel Garapati Signed-off-by: Stefan Roese --- Changes in v1: - Change patch subject - Remove inclusion of common.h - Remove global wdt_dev as its unused - Remove #ifdef's -

[PATCH v1 16/24] pci: Add PCI controller driver for OcteonTX / TX2

From: Suneel Garapati Adds support for PCI ECAM/PEM controllers found on OcteonTX or OcteonTX2 SoC platforms. Signed-off-by: Suneel Garapati Cc: Simon Glass Cc: Bin Meng Signed-off-by: Stefan Roese --- Changes in v1: - Change patch subject - Remove inclusion of common.h - Remove #ifdef's

[PATCH v1 23/24] arm: octeontx: Add support for OcteonTX SoC platforms

From: Suneel Garapati This patch adds support for all OcteonTX 81xx/83xx boards from Marvell. For 81xx boards, use octeontx_81xx_defconfig and for 83xx boards, use octeontx_83xx_defconfig. Signed-off-by: Suneel Garapati Signed-off-by: Stefan Roese --- Changes in v1: - Changed patch subject

[PATCH v1 17/24] mmc: Remove static qualifier on mmc_power_init

From: Suneel Garapati For platforms with multiple slot support like OcteonTX, this is invoked per slot. Signed-off-by: Suneel Garapati Cc: Peng Fan Signed-off-by: Stefan Roese --- Changes in v1: - Change patch subject drivers/mmc/mmc.c | 2 +- include/mmc.h | 1 + 2 files changed, 2

[PATCH v1 12/24] arm: include/asm/io.h: Add 64bit clrbits and setbits helpers

From: Suneel Garapati Add 64bit API for clrbits and setbits. Signed-off-by: Suneel Garapati Reviewed-by: Simon Glass Signed-off-by: Stefan Roese --- Changes in v1: - Change patch subject - Add small commit text - Also add clr/setbits_64 (without endianess extension), which is needed for

[PATCH v1 15/24] ata: ahci: Add BAR index quirk for Cavium PCI SATA device

From: Suneel Garapati For SATA controller found on OcteonTX SoC's, use non-standard PCI BAR0 instead of BAR5. Signed-off-by: Suneel Garapati Cc: Simon Glass Signed-off-by: Stefan Roese --- Changes in v1: - Change patch subject - Use constants from pci_ids.h instead of hardcoded values

  1   2   >