[U-Boot] [PATCH RFC] possible typo in atmel_lcdfb.c

This may be a typo inside the driver, but HFP is subtracted by 2 instead of 1 like the other variables in the register. This is stated in AT91SAM9263 Summary 6249H–ATARM–27-Jul-09 p. 940 HFP: Horizontal Front Porch in LCDTIM2 So the driver should also subtract 2 to achieve the correct and

Re: [U-Boot] OT: SD/MMC-over-SPI and speed in linux

Hello Wolfgang, Am Donnerstag, 6. Mai 2010 15:13:14 schrieb Wolfgang Wegner: In U-Boot, I can get read speeds with fatload of around 400 kBytes/second, which seems reasonable as the card can handle 25 MHz SPI speed. (And, it would be sufficient for our application.) IIRC 400kBytes/second is

Re: [U-Boot] OT: SD/MMC-over-SPI and speed in linux

Am Donnerstag, 6. Mai 2010 15:59:44 schrieb Wolfgang Wegner: Hi Alexander, On Thu, May 06, 2010 at 03:33:53PM +0200, Alexander Stein wrote: [...] IIRC 400kBytes/second is the initial speed for SD cards on SPI. The card itself responds which max speed it can handle. Which could

[U-Boot] Defer net initialization

Hello, during board setup the ethernet is configured including the PHY. This takes an amount of time even if the cable is plugged in. It takes even more time of the initialization runs into a timeout if no cable is put in. Is there a possibility to defer the net initialization up to that point

Re: [U-Boot] Defer net initialization

Dear Wolfgang, Am Montag, 31. Mai 2010 18:08:30 schrieb Wolfgang Denk: during board setup the ethernet is configured including the PHY. This takes an amount of time even if the cable is plugged in. It takes even more time of the initialization runs into a timeout if no cable is put in.

Re: [U-Boot] Defer net initialization

Am Dienstag, 1. Juni 2010 08:17:41 schrieb Alexander Stein: Which version of U-Boot and which architecture / board are you talking about? Currently I'm using u-boot v2009.11 on at91sam9g20 on our own board (code yet upstream). Oh, i forgot. This code is based on the atmel at91sam9g20ek

Re: [U-Boot] Defer net initialization

Dear Wolgfang, Am Dienstag, 1. Juni 2010 10:48:25 schrieben Sie: I think this thread focus on another problem: setting the MAC address. I have a MAC in the ethaddr environment variable which gets used properly. You are wrong. The thread is exactly discussing the issue you are suffering

Re: [U-Boot] Defer net initialization

Dear Wolfgang, Am Dienstag, 1. Juni 2010 12:46:03 schrieben Sie: The problem was a defined CONFIG_RESET_PHY_R. Inside reset_phy eth_init(gd-bd); is called which actually starts the hardwre resulting in timeouts as described. According to the comment above this line (seems to be

Re: [U-Boot] Defer net initialization

Ho Ben, Am Dienstag, 1. Juni 2010 16:46:48 schrieb Ben Warren: This macb driver is fine so far. eth_initialize doesn't startup the hardware e.g. checking for link etc. The problem was a defined CONFIG_RESET_PHY_R. Inside reset_phy eth_init(gd-bd); is called which actually starts

Re: [U-Boot] [PATCH][Net] Write MAC address automatically on MACB-based boards

with in-tree support in u-boot Tested-by: Alexander Stein alexander.st...@systec-electronic.com Best regards Alexander ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH] at91: Fix AT91_PMC_MCKR_PLLADIV_ defines

Dear Wolfgang, Am Montag, 14. Juni 2010 21:01:27 schrieb Wolfgang Denk: In message 1276521853-13779-1-git-send-email-alexander.st...@systec- electronic.com you wrote: Only Bit 12 is used for Processor Clock Division. Writing a 0 means dividing by and writing a 1 means dividing by 2. See

[U-Boot] Linking some code to internal SRAM instead of SDRAM

Hello, I have an at91 based board which starts from NOR flash. I have an ugly workaround in lowlevel_init.S that switching from slowclock to PLLA is done from the internal SRAM instead directly from NOR which is not possible as the NOR flash timing are also affected. So i copied some data

Re: [U-Boot] Linking some code to internal SRAM instead of SDRAM

Dear Wolfgang, Am Mittwoch, 16. Juni 2010 14:56:31 schrieb Wolfgang Denk: A new approach would be to link lowlevel_init directly at 0x0020 (which is AT91SAM9260_SRAM0_BASE) but the code is located next to the normal .text segment. I've prepared a change to cpu/arm926ejs/u-boot.lds (I

[U-Boot] [PATCH v3] at91: Add arch_preboot_os which disables PIT in a faster way

by setting the compare value to a value slightly greater than the current running counter to make the PIT stopped in short time. Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- Changes in v3: * Really fix comment arch/arm/cpu/arm926ejs/at91/cpu.c | 16 1 files

Re: [U-Boot] [PATCH] lib_arm: fix build error with gcc 4.4 and above

Hello, On Thursday 16 September 2010, 19:44:20 you wrote: This patch fixes lib_arm/board.c build errors. The combination of weak alias and inline attributes lead to a compile time error when using gcc version 4.4 and above. Signed-off-by: Stanislav O. Bezzubtsev

Re: [U-Boot] [PATCH] dlmalloc.c: Fix gcc alias warning

Hello, On Thursday 14 October 2010, 08:41:20 Joakim Tjernlund wrote: Fix these warnings: dlmalloc.c: In function 'free': dlmalloc.c:2507: warning: dereferencing pointer '({anonymous})' does break strict-aliasing rules dlmalloc.c:2507: warning: dereferencing pointer '({anonymous})' does break

Re: [U-Boot] [PATCH 2/3] include/asm-offsets.h: automatically generate assembler constants

On Tuesday 26 October 2010, 16:00:00 Wolfgang Denk wrote: @@ -453,7 +456,7 @@ $(obj)System.map: $(obj)u-boot @$(call SYSTEM_MAP,$) $(obj)System.map # -# Auto-generate the autoconf.mk file (which is included by all makefiles) +# Auto-generate the autoconi.mk file (which is

[U-Boot] current ARM development head

Hello, I noticed that there is a lot of changes in ARM part of u-boot. Especially the new relocation is a bit tricky. So I'm wondering what and where is the current ARM development head, especially the at91 part. Is it u-boot master branch or some other repository/branch? Best regards,

[U-Boot] various at91 patches to make some boards compilable again

This patch series changes some at91 boards to SoC access and adds some defines to make the boards compilable again. Please note: All changes are untested! Best regards, Alexander ___ U-Boot mailing list U-Boot@lists.denx.de

[U-Boot] [PATCH 01/11] at91sam9260: Replace PHYS_SDRAM with CONFIG_SYS_SDRAM_BASE

Same for PHYS_SDRAM_SIZE and CONFIG_SYS_SDRAM_SIZE and use SZ_* macros Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- board/atmel/at91sam9260ek/at91sam9260ek.c |6 +++--- include/configs/at91sam9260ek.h | 17 - 2 files changed, 15

[U-Boot] [PATCH 02/11] at91: Add USART DBGU base address defines

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/at91cap9.h| 12 arch/arm/include/asm/arch-at91/at91sam9260.h |7 +++ arch/arm/include/asm/arch-at91/at91sam9261.h |4 arch/arm/include/asm/arch-at91

[U-Boot] [PATCH 09/11] at91sam9261ek: make compilable again

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- board/atmel/at91sam9261ek/at91sam9261ek.c |6 +++--- include/configs/at91sam9261ek.h | 15 +++ 2 files changed, 14 insertions(+), 7 deletions(-) diff --git a/board/atmel/at91sam9261ek

[U-Boot] [PATCH 03/11] at91: Use AT91_USART0_BASE instead of AT91_USART0

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/memory-map.h |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/arm/include/asm/arch-at91/memory-map.h b/arch/arm/include/asm/arch-at91/memory-map.h index

[U-Boot] [PATCH 10/11] at91sam9263ek: make compilable again

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- board/atmel/at91sam9263ek/at91sam9263ek.c |6 +++--- include/configs/at91sam9263ek.h | 15 +++ 2 files changed, 14 insertions(+), 7 deletions(-) diff --git a/board/atmel/at91sam9263ek

[U-Boot] [PATCH 05/11] at91: Fix pdc register names and add some defines

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/at91_pdc.h |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/arch/arm/include/asm/arch-at91/at91_pdc.h b/arch/arm/include/asm/arch-at91/at91_pdc.h index 42f87ca

[U-Boot] [PATCH 08/11] atmel_dataflash: Update to SoC access

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/hardware.h | 10 ++-- drivers/spi/atmel_dataflash_spi.c | 109 +++-- 2 files changed, 60 insertions(+), 59 deletions(-) diff --git a/arch/arm/include/asm

[U-Boot] [PATCH 06/11] at91: Add defines for spi SoC access

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/at91_spi.h | 14 ++ 1 files changed, 14 insertions(+), 0 deletions(-) diff --git a/arch/arm/include/asm/arch-at91/at91_spi.h b/arch/arm/include/asm/arch-at91/at91_spi.h index

[U-Boot] [PATCH 07/11] at91: Add spi base addresses

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/at91cap9.h|2 ++ arch/arm/include/asm/arch-at91/at91sam9260.h |2 ++ arch/arm/include/asm/arch-at91/at91sam9261.h |2 ++ arch/arm/include/asm/arch-at91/at91sam9263.h |2

Re: [U-Boot] various at91 patches to make some boards compilable again

Dear Reinhard Meyer, On Monday 01 November 2010, 09:40:52 Reinhard Meyer wrote: This patch series changes some at91 boards to SoC access and adds some defines to make the boards compilable again. Please note: All changes are untested! Ok, I will look over them, and apply them in a test

Re: [U-Boot] [PATCH 06/11] at91: Add defines for spi SoC access

On Monday 01 November 2010, 09:43:57 Reinhard Meyer wrote: Dear Alexander Stein, Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/at91_spi.h | 14 ++ 1 files changed, 14 insertions(+), 0 deletions(-) diff

Re: [U-Boot] [PATCH 02/11] at91: Add USART DBGU base address defines

Dear Andreas, On Monday 01 November 2010, 11:57:14 Andreas Bießmann wrote: Am 01.11.2010 um 09:29 schrieb Alexander Stein: Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/at91cap9.h| 12 arch/arm/include/asm/arch

Re: [U-Boot] [PATCH 06/11] at91: Add defines for spi SoC access

Dear Reinhard, On Monday 01 November 2010, 13:31:38 Reinhard Meyer wrote: In this particular case the driver is not yet using the (existing) struct at91_spi at all WAIT!!! There is the COMMON driver atmel_spi.c with atmel_spi.h in drivers/spi. There need not be and should not

Re: [U-Boot] [RFC] AT91 cleanup, was: Re: [PATCH 02/11] at91: Add USART DBGU base addres s defines

Hello, On Tuesday 02 November 2010, 15:11:00 Reinhard Meyer wrote: I leaped a bit ahead there, and did some cleanups already. Note that they are not complete and are up for discussion. In order to avoid flooding the list with patches, you can have a look at u-boot-atmel, at91cleanup branch.

Re: [U-Boot] Booting with kernel and root fs in JFFS2 flash?

Hello Adam, Am Donnerstag, 1. Juli 2010, 04:37:31 schrieb Adam Moskowitz: To make better use of the 32MB of flash on the board, we're considering putting the kernel, the root filesystem, and some state data in a JFFS2 partition on the flash. I thought sure I read somewhere in the docs that

Re: [U-Boot] U-boot and AT91SAM9263-EK

Hello, Am Mittwoch, 14. Juli 2010, 17:05:47 schrieb Radovan Vápeník: i have compiled new u-boot (2010-06) for at91sam9263-ek and I have problem with access and save environment variables to NAND Flash. When I set any environment variable and save it to Nand (saveenv), uBoot shows me Saving

[U-Boot] Does u-boot support CFI for NOR flash interleaving?

Hello, I checked the linux mtd drivers and found handling of interleaving. But I couldn't figure out any related or similar code in u-boot. So does u-boot support NOR flash interleaving when using CFI? Best regards, Alexander ___ U-Boot mailing list

[U-Boot] [PATCH] atmel_lcd: Allow contrast polarity to be either positive or negative

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- drivers/video/atmel_lcdfb.c |3 ++- include/lcd.h |1 + 2 files changed, 3 insertions(+), 1 deletions(-) diff --git a/drivers/video/atmel_lcdfb.c b/drivers/video/atmel_lcdfb.c index db86763..c02ffd8

[U-Boot] [PATCH] memmove_wd: Allow overlapping memory area

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- common/image.c | 11 --- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/common/image.c b/common/image.c index 6d8833e..da0fdd5 100644 --- a/common/image.c +++ b/common/image.c @@ -456,9 +456,14

[U-Boot] [PATCH] at91: Don't initialize watchdog if CONFIG_SYS_WDTC_WDMR_VAL is undefined

This allows Linux to initialize and use the watchdog with the included driver. CONFIG_AT91SAM9_WATCHDOG and CONFIG_HW_WATCHDOG should be defined to make u-boot trigger the watchdog Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/cpu/arm926ejs/at91

Re: [U-Boot] [PATCH] at91: Don't initialize watchdog if CONFIG_SYS_WDTC_WDMR_VAL is undefined

and CONFIG_HW_WATCHDOG. Best regards, Alexander Stein ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH] at91: Don't initialize watchdog if CONFIG_SYS_WDTC_WDMR_VAL is undefined

from u- boot itself does still work, wrt. the default watchdog settings. Best regards, Alexander Stein ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] [PATCH v3] at91: Don't initialize watchdog if CONFIG_SKIP_WATCHDOG_INIT is undefined

-boot is still able to trigger the watchdog. Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- Changes in v2: * Add a new specific option CONFIG_SKIP_WATCHDOG_INIT * Add some documentation Changes in v3: * Be more verbose in describing the problem in the commit message

Re: [U-Boot] How can i add intterrupt for AT91SAM9260EK board

Hello, Am Donnerstag, 29. Juli 2010, 08:25:53 schrieb Reinhard Meyer: You have add interrupt handling (write source) to AT91 in general and provide a patch for that. But first you have to define why you need interrupts (in the u-boot phase) in the first place. One reason would be to

[U-Boot] [PATCH] at91_pit: Fix AT91_PIT_MR_PIV_MASK macro

Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/include/asm/arch-at91/at91_pit.h |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/arm/include/asm/arch-at91/at91_pit.h b/arch/arm/include/asm/arch-at91/at91_pit.h index 5615a02

[U-Boot] [PATCH] at91: Add arch_preboot_os which disables PIT in a faster way

by setting the compare value to a value slightly greater than the current running counter to make the PIT stopped in short time. Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/cpu/arm926ejs/at91/cpu.c | 15 +++ 1 files changed, 15 insertions(+), 0 deletions

Re: [U-Boot] [PATCH V3] AT91 Fix: return value of get_tbclk

Hello, Am Samstag, 7. August 2010, 19:49:42 schrieb Jens Scharsig: * Fix: return value of get_tbclk * this fixes issue with prematurely restart/retry, if BOOT_RETRY_TIMEOUT is used This issue also arises, if you use CONFIG_AUTOBOOT_KEYED friends Signed-off-by: Jens Scharsig

[U-Boot] [PATCH v4] at91: Don't initialize watchdog if CONFIG_SKIP_WATCHDOG_INIT is defined

-boot is still able to trigger the watchdog. Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- Changes in v2: * Add a new specific option CONFIG_SKIP_WATCHDOG_INIT * Add some documentation Changes in v3: * Be more verbose in describing the problem in the commit message

Re: [U-Boot] [PATCH] memmove_wd: Allow overlapping memory area

Dear Wolfgang, Am Montag, 9. August 2010, 00:18:19 schrieb Wolfgang Denk: In message 1279701826-20083-1-git-send-email-alexander.st...@systec- electronic.com you wrote: Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- common/image.c | 11 --- 1 files

Re: [U-Boot] [PATCH] memmove_wd: Allow overlapping memory area

Dear Wolfgang, Am Montag, 9. August 2010, 11:26:56 schrieb Wolfgang Denk: IIRC the problem arose when i downloaded my image to 0x2000 (SD-RAM) using TFTP and my Linux kernel entry point was at 0x20008000. So when Don;t do this, then. Such kind of overlap has never been supported. Even

Re: [U-Boot] [PATCH v4] at91: Don't initialize watchdog if CONFIG_SKIP_WATCHDOG_INIT is defined

Hello Mike, Am Montag, 9. August 2010, 09:13:45 schrieb Mike Frysinger: On AT91 the watchdog mode register can only be written once after reset. If this register is written by u-boot e.g. a Linux driver can't reconfigure the watchdog later. If the watchdog is left untouched this is

Re: [U-Boot] [PATCH] memmove_wd: Allow overlapping memory area

Dear Wolfgang, August 2010, 13:43:32 schrieb Wolfgang Denk: Well, that's at least one possibility but it is very annoying that something like memmove that works fine so far suddenly stops working when watchdog support is enabled. Yes, I understand this. It's also annoying when you've

[U-Boot] [PATCH] CONFIG_CMD_JFFS2 is not necessary to use mtdparts on erase protect on/off

The include jffs2/jffs2.h is still necessary though. Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- common/cmd_flash.c | 12 ++-- 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/common/cmd_flash.c b/common/cmd_flash.c index ff43965..3e6bab2

Re: [U-Boot] [RFD] store env size in env area (+ cookie + len)

On Thursday 12 August 2010, 09:27:31 you wrote: Why not store the size of the environment sector as env variable? The size should be only needed for storing the environment and not for loading (as it is terminated by a '\0'). So we could load the environment, check for env_size and if its not

Re: [U-Boot] [PATCH V3] AT91 Fix: return value of get_tbclk

Hello Eric, On Wednesday 18 August 2010, 09:17:26 you wrote: Hello, Am Samstag, 7. August 2010, 19:49:42 schrieb Jens Scharsig: * Fix: return value of get_tbclk * this fixes issue with prematurely restart/retry, if BOOT_RETRY_TIMEOUT is used This issue also arises, if

[U-Boot] [PATCH v2] at91: Add arch_preboot_os which disables PIT in a faster way

by setting the compare value to a value slightly greater than the current running counter to make the PIT stopped in short time. Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- Changes in v2: * Fix comment arch/arm/cpu/arm926ejs/at91/cpu.c | 15 +++ 1 files changed

Re: [U-Boot] boot-up time optimization. Where to start?

Hi, Am Mittwoch, 27. April 2011, 15:39:18 schrieb Simon Schwarz: I just started to work on my bachelor thesis. It is about Linux boot-up time optimization. The past days I spend analyzing what consumes the most time in the boot process. I found that u-boot takes pretty much as long as the

Re: [U-Boot] boot-up time optimization. Where to start?

Dear Wolfgang, Am Mittwoch, 27. April 2011, 21:08:50 schrieb Wolfgang Denk: In message 201104271759.11818.alexander.st...@systec-electronic.com you wrote: Setting stdin, stdout and stderr takes a lot of time (IIRC ~500ms). Which IMO is useless on a bootloader without LCD support.

Re: [U-Boot] boot-up time optimization. Where to start?

Hi Detlev, Am Montag, 2. Mai 2011, 17:31:15 schrieb Detlev Zundel: Hi Alexander, Dear Wolfgang, Am Mittwoch, 27. April 2011, 21:08:50 schrieb Wolfgang Denk: In message 201104271759.11818.alexander.st...@systec-electronic.com you wrote: Setting stdin, stdout and stderr takes

Re: [U-Boot] boot-up time optimization. Where to start?

Dear Wolfgang, Am Montag, 2. Mai 2011, 19:00:47 schrieb Wolfgang Denk: In message 201105021640.27241.alexander.st...@systec-electronic.com you wrote: Ok, let me be more precise on this. We used U-Boot v2010.09 on a custom board running on an I.MX35 (ARM1136). Let's summarize known facts:

Re: [U-Boot] boot-up time optimization. Where to start?

Dear Wolfgang, Am Donnerstag, 5. Mai 2011, 07:32:20 schrieb Wolfgang Denk: In message 201105030848.17576.alexander.st...@systec-electronic.com you wrote: This specific version was selected due to relocation problems on ARM. But I expect the dcache doesn't have that big influence on the

[U-Boot] [PATCH] arm relocation: Fix calculation of board_init_r

Signed-off-by: Alexander Stein alexander.st...@informatik.tu-chemnitz.de --- Hello, I just played a bit with my at91sam9g20ek and tried using a new u-boot. So I compiled 656b990daa84bfdd512407ee2e3d2610e305a455 (atmel/wip110202) load it into memory using jtag to 0x2200 while it was linked

Re: [U-Boot] Can't erase or read NOR using mtd part-id

Hello, On Wednesday 09 February 2011, 16:52:35 Alexandre Gambier wrote: I'm using u-boot to boot a Linux-based device. Which version og u-boot are you running? I created some MTD partitions for my NOR and NAND flashes. Here is the configuration: device nor0 NOR, # parts = 4 #: name

Re: [U-Boot] Can't erase or read NOR using mtd part-id

Hello, On Wednesday 09 February 2011, 17:16:37 Alexandre Gambier wrote: thanks for your reply. I'm running u-boot 1.3.1. I got it from STLinux. ouch, that's pretty old. I will try to set CONFIG_JFFS2. But does it mean it will erase the partition using JFFS2 ? No, the feature depended on

[U-Boot] u-boot does not build when lensfun is installed on host system

: control reaches end of non-void function [-Wreturn-type] make[1]: *** [tools/aisimage.o] Error 1 make: *** [tools] Error 2 -- Dipl.-Inf. Alexander Stein SYS TEC electronic GmbH Am Windrad 2 08468 Heinsdorfergrund Tel.: 03765 38600-1156 Fax: 03765 38600-4100 Email: alexander.st...@systec

Re: [U-Boot] [PATCH 1/1] mmc: bcm2835_sdhci: Use calloc to allocate bcm2835_sdhci_host

Any feedback on this? Best regards, Alexander On Friday 17 April 2015, 17:33:17 wrote Alexander Stein: We need to clear the allocated memory explicitly as the included struct sdhci_host has function pointers. Those are compared to NULL to test if this (optional) feature is supported. Leaving

[U-Boot] [PATCH 1/1] mmc: bcm2835_sdhci: Use calloc to allocate bcm2835_sdhci_host

We need to clear the allocated memory explicitly as the included struct sdhci_host has function pointers. Those are compared to NULL to test if this (optional) feature is supported. Leaving them undefined let u-boot jump to arbitrary memory. Signed-off-by: Alexander Stein alexander...@web.de

[U-Boot] [PATCH 1/5] arm1176/cpu: Match cache_flush to arm1136

This is effectively the same code but it also does a clean cache before invalidating and doing a memory barrier. Signed-off-by: Alexander Stein alexander...@web.de --- arch/arm/cpu/arm1176/cpu.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/arch/arm/cpu/arm1176

[U-Boot] [PATCH 4/5] arm/mach-bcm283x/mbox: Flush and invalidate dcache when using fw mailbox

When using dcache the setup data for the mailbox must be actually written into memory before calling into firmware. Thus flush and invalidate the memory. Signed-off-by: Alexander Stein alexander...@web.de --- arch/arm/mach-bcm283x/mbox.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[U-Boot] [PATCH 0/5] dcache support for Raspberry Pi 1

to have any affect on RPI 2 though. I just get error messages about non-cacheline aligned address upon invalidation. The performance stucks at 1.2 MiB/s. This was tested by the following command: fatload mmc 0:1 ${kernel_addr_r} zImage Alexander Stein (5): arm1176/cpu: Match cache_flush

[U-Boot] [PATCH 2/5] arm1176/cpu: Add icache and dcache support

The code is copied 1:1 from arm1136 which uses the same cp15 registers. Signed-off-by: Alexander Stein alexander...@web.de --- arch/arm/cpu/arm1176/cpu.c | 97 ++ 1 file changed, 97 insertions(+) diff --git a/arch/arm/cpu/arm1176/cpu.c b/arch/arm/cpu

[U-Boot] [PATCH 3/5] arm1176/cpu: Align cache flushing addresses to cacheline size

cache flushing addresses must be cacheline size aligned, so mask the start and stop address appropriately. Signed-off-by: Alexander Stein alexander...@web.de --- arch/arm/cpu/arm1176/cpu.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/cpu/arm1176/cpu.c b/arch/arm/cpu

[U-Boot] [PATCH 5/5] arm/rpi: Enable dcache

Now that mailbox driver supports cache flush and invalidation, we can enable dcache. Signed-off-by: Alexander Stein alexander...@web.de --- include/configs/rpi-common.h | 1 - 1 file changed, 1 deletion(-) diff --git a/include/configs/rpi-common.h b/include/configs/rpi-common.h index 1012cdd

Re: [U-Boot] [PATCH 0/5] dcache support for Raspberry Pi 1

Hello Albert, On Monday 06 July 2015, 09:39:40 wrote Albert ARIBAUD: On Sat, 4 Jul 2015 11:48:39 +0200, Alexander Stein alexander...@web.de wrote: dcache supprt increases the MMC read performance on RPI 1 from 5,4 MiB/s to 12.3 MiB/s. It doesn't seem to have any affect on RPI 2 though. I

Re: [U-Boot] arm: ls1021a: Ensure LS1021 ARM Generic Timer CompareValue Set 64-bit

this problem which _only_ differ in those 2 register usages. Best regards, Alexander -- Dipl.-Inf. Alexander Stein SYS TEC electronic GmbH alexander.st...@systec-electronic.com Legal and Commercial Address: Am Windrad 2 08468 Heinsdorfergrund Germany Office: +49 (0) 3765 38600-0 Fax:+49 (0) 3765

Re: [U-Boot] arm: ls1021a: Ensure Generic Timer disabled before jumping into the OS

in timer_init is fixed to pass an 64-bit variable to mcrr. Maybe someone will take that code snippet as an example and such problems occur again. Opinions? Best regards, Alexander -- Dipl.-Inf. Alexander Stein SYS TEC electronic GmbH alexander.st...@systec-electronic.com Legal and Commercial

[U-Boot] [PATCH 1/1] arm: ls102xa: timer: Fix undefined behavior

variable. Signed-off-by: Alexander Stein alexander.st...@systec-electronic.com --- arch/arm/cpu/armv7/ls102xa/timer.c| 3 ++- arch/arm/include/asm/arch-ls102xa/immap_ls102xa.h | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/arch/arm/cpu/armv7/ls102xa/timer.c

[U-Boot] [PATCH v3 0/7] dcache support for Raspberry Pi 1

to roundup Changes in v2: * Merge arm1136/1176 cache code * Use cacheline size as mailbox buffer alignment * Flush/invalidate mailbox buffer up to cacheline size Alexander Stein (7): arm1136: Remove dead code arm1136/arm1176: Merge cache handling code ARM: bcm283x: Define

[U-Boot] [PATCH v3 6/7] dwc2: Add dcache support

This adds dcache support for dwc2. The DMA buffers must be DMA aligned and is flushed for outgoing transactions before starting transfer. For ingoing transactions it is invalidated after the transfer has finished. Signed-off-by: Alexander Stein alexander...@web.de --- drivers/usb/host/dwc2.c

[U-Boot] [PATCH v3 4/7] ARM: bcm283x: Allocate all mailbox buffers cacheline aligned

The mailbox buffer is required to be at least 16 bytes aligned, but for cache invalidation and/or flush it needs to be cacheline aligned. Use ALLOC_CACHE_ALIGN_BUFFER for all mailbox buffer allocations. Signed-off-by: Alexander Stein alexander...@web.de --- Changes in v3: * Use

[U-Boot] [PATCH v3 5/7] arm/mach-bcm283x/mbox: Flush and invalidate dcache when using fw mailbox

When using dcache the setup data for the mailbox must be actually written into memory before calling into firmware. Thus flush and invalidate the memory. Signed-off-by: Alexander Stein alexander...@web.de --- Changes in v3: * Use ARCH_DMA_MINALIGN instead of fixed 32 * Adjust comment in header

[U-Boot] [PATCH v3 7/7] arm/rpi: Enable dcache

Now that mailbox driver supports cache flush and invalidation, we can enable dcache. Signed-off-by: Alexander Stein alexander...@web.de --- include/configs/rpi-common.h | 1 - include/configs/rpi_2.h | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/include/configs/rpi

[U-Boot] [PATCH v3 2/7] arm1136/arm1176: Merge cache handling code

As both cores are similar merge the cache handling code for both CPUs to arm11 directory. Signed-off-by: Alexander Stein alexander...@web.de --- arch/arm/cpu/arm11/Makefile | 8 +++ arch/arm/cpu/arm11/cpu.c | 150 ++ arch/arm/cpu/arm1136/Makefile

[U-Boot] [PATCH v3 1/7] arm1136: Remove dead code

Apparently lcd_panel_disable is not defined anywhere, so no config for an arm1136 board would have set CONFIG_LCD. Remove the unused code. Signed-off-by: Alexander Stein alexander...@web.de --- arch/arm/cpu/arm1136/cpu.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/arch/arm/cpu

[U-Boot] [PATCH v3 3/7] ARM: bcm283x: Define CONFIG_SYS_CACHELINE_SIZE

The cacheline is always 32 bytes for arm1176 CPUs, so define it at board config level for cache handling code. Signed-off-by: Alexander Stein alexander...@web.de --- include/configs/rpi-common.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/configs/rpi-common.h b/include/configs

[U-Boot] [PATCH v4 2/7] arm1136/arm1176: Merge cache handling code

As both cores are similar merge the cache handling code for both CPUs to arm11 directory. Signed-off-by: Alexander Stein alexander...@web.de Acked-by: Stephen Warren swar...@wwwdotorg.org Tested-by: Stephen Warren swar...@wwwdotorg.org --- Changes in v4: * Used git format-patch -M to generate

[U-Boot] [PATCH v4 1/7] arm1136: Remove dead code

Apparently lcd_panel_disable is not defined anywhere, so no config for an arm1136 board would have set CONFIG_LCD. Remove the unused code. Signed-off-by: Alexander Stein alexander...@web.de Acked-by: Stephen Warren swar...@wwwdotorg.org Tested-by: Stephen Warren swar...@wwwdotorg.org --- arch

[U-Boot] [PATCH v4 7/7] arm/rpi: Enable dcache

Now that mailbox driver supports cache flush and invalidation, we can enable dcache. Signed-off-by: Alexander Stein alexander...@web.de Acked-by: Stephen Warren swar...@wwwdotorg.org Tested-by: Stephen Warren swar...@wwwdotorg.org --- include/configs/rpi-common.h | 1 - include/configs/rpi_2.h

[U-Boot] [PATCH v4 6/7] dwc2: Add dcache support

This adds dcache support for dwc2. The DMA buffers must be DMA aligned and is flushed for outgoing transactions before starting transfer. For ingoing transactions it is invalidated after the transfer has finished. Signed-off-by: Alexander Stein alexander...@web.de Acked-by: Stephen Warren swar

[U-Boot] [PATCH v4 0/7] dcache support for Raspberry Pi 1

size as mailbox buffer alignment * Flush/invalidate mailbox buffer up to cacheline size Alexander Stein (7): arm1136: Remove dead code arm1136/arm1176: Merge cache handling code ARM: bcm283x: Define CONFIG_SYS_CACHELINE_SIZE ARM: bcm283x: Allocate all mailbox buffers cacheline aligned arm

[U-Boot] [PATCH v4 3/7] ARM: bcm283x: Define CONFIG_SYS_CACHELINE_SIZE

The cacheline is always 32 bytes for arm1176 CPUs, so define it at board config level for cache handling code. The ARM Cortex-A7 has a dcache line size of 64 bytes. Signed-off-by: Alexander Stein alexander...@web.de Acked-by: Stephen Warren swar...@wwwdotorg.org Tested-by: Stephen Warren swar

[U-Boot] [PATCH v4 4/7] ARM: bcm283x: Allocate all mailbox buffers cacheline aligned

The mailbox buffer is required to be at least 16 bytes aligned, but for cache invalidation and/or flush it needs to be cacheline aligned. Use ALLOC_CACHE_ALIGN_BUFFER for all mailbox buffer allocations. Signed-off-by: Alexander Stein alexander...@web.de Acked-by: Stephen Warren swar

[U-Boot] [PATCH v4 5/7] arm/mach-bcm283x/mbox: Flush and invalidate dcache when using fw mailbox

When using dcache the setup data for the mailbox must be actually written into memory before calling into firmware. Thus flush and invalidate the memory. Signed-off-by: Alexander Stein alexander...@web.de Acked-by: Stephen Warren swar...@wwwdotorg.org Tested-by: Stephen Warren swar

[U-Boot] Raspberry Pi2 performance

Hi, after getting dcache support for Raspberry Pi 1 (see other thread) to work: I wanted to do that for rpi2 too. But even without dcaches rpi2 is slower than rpi1 for both MMC and USB ethernet. I have no idea why, but trying the new dhry command from current origin/master confirms my

Re: [U-Boot] [PATCH v2 6/6] arm/rpi: Enable dcache

On Monday 20 July 2015, 23:00:04 wrote Alexander Stein: Now that mailbox driver supports cache flush and invalidation, we can enable dcache. Signed-off-by: Alexander Stein alexander...@web.de Well, I just noticed that the dwc2 driver does not support dache yet. I'm on the way to add

Re: [U-Boot] [PATCH 5/5] arm/rpi: Enable dcache

On Friday 10 July 2015, 23:24:58 wrote Stephen Warren: On 07/04/2015 03:48 AM, Alexander Stein wrote: Now that mailbox driver supports cache flush and invalidation, we can enable dcache. Did you also test that HDMI output doesn't show any issues after this change? I think there's already

[U-Boot] [PATCH v2 0/6] dcache support for Raspberry Pi 1

: fatload mmc 0:1 ${kernel_addr_r} zImage Changes in v2: * Merge arm1136/1176 cache code * Use cacheline size as mailbox buffer alignment * Flush/invalidate mailbox buffer up to cacheline size Alexander Stein (6): arm1136: Remove dead code arm1136/arm1176: Merge cache handling code ARM

[U-Boot] [PATCH v2 4/6] ARM: bcm283x: Allocate all mailbox buffers cacheline aligned

The mailbox buffer is required to be at least 16 bytes aligned, but for cache invalidation and/or flush it needs to be cacheline aligned. Use CONFIG_SYS_CACHELINE_SIZE alignment for all mailbox buffer allocations. Signed-off-by: Alexander Stein alexander...@web.de --- board/raspberrypi/rpi/rpi.c

[U-Boot] [PATCH v2 6/6] arm/rpi: Enable dcache

Now that mailbox driver supports cache flush and invalidation, we can enable dcache. Signed-off-by: Alexander Stein alexander...@web.de --- Changes in v2: * Only enable dcache on rpi1, but not on rpi2 include/configs/rpi-common.h | 1 - include/configs/rpi_2.h | 1 + 2 files changed, 1

[U-Boot] [PATCH v2 5/6] arm/mach-bcm283x/mbox: Flush and invalidate dcache when using fw mailbox

When using dcache the setup data for the mailbox must be actually written into memory before calling into firmware. Thus flush and invalidate the memory. Signed-off-by: Alexander Stein alexander...@web.de --- Changes in v2: * Add hint in header about alignment requirements * Invalidate cache

[U-Boot] [PATCH v2 2/6] arm1136/arm1176: Merge cache handling code

As both cores are similar merge the cache handling code for both CPUs to arm11 directory. Signed-off-by: Alexander Stein alexander...@web.de --- arch/arm/cpu/arm11/Makefile | 8 +++ arch/arm/cpu/arm11/cpu.c | 150 ++ arch/arm/cpu/arm1136/Makefile

  1   2   >