public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] net: fec: Avoid MX28 bus sync issue
Date: Mon, 15 Jul 2013 22:20:36 +0200	[thread overview]
Message-ID: <20130715222036.5b8fda19@lilith> (raw)
In-Reply-To: <51E454BC.9090604@boundarydevices.com>

Hi Troy,

On Mon, 15 Jul 2013 12:59:56 -0700, Troy Kisky
<troy.kisky@boundarydevices.com> wrote:

> On 7/15/2013 10:39 AM, Troy Kisky wrote:
> > On 7/15/2013 6:41 AM, Albert ARIBAUD wrote:
> >> Hi Troy,
> >>
> >> On Fri, 12 Jul 2013 19:43:07 -0700, Troy Kisky
> >> <troy.kisky@boundarydevices.com> wrote:
> >>
> >>> On 7/11/2013 4:18 PM, Fabio Estevam wrote:
> >>>> On Thu, Jul 11, 2013 at 8:03 PM, Marek Vasut <marex@denx.de> wrote:
> >>>>> The MX28 multi-layer AHB bus can be too slow and trigger the
> >>>>> FEC DMA too early, before all the data hit the DRAM. This patch
> >>>>> ensures the data are written in the RAM before the DMA starts.
> >>>>> Please see the comment in the patch for full details.
> >>>>>
> >>>>> This patch was produced with an amazing help from Albert Aribaud,
> >>>>> who pointed out it can possibly be such a bus synchronisation
> >>>>> issue.
> >>>>>
> >>>>> Signed-off-by: Marek Vasut <marex@denx.de>
> >>>>> Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
> >>>>> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> >>>>> Cc: Stefano Babic <sbabic@denx.de>
> >>>> Excellent, managed to transfer 90MB via TFTP on mx28evk without a
> >>>> single timeout.
> >>>>
> >>>> Tested-by: Fabio Estevam <fabio.estevam@freescale.com>
> >>>> _______________________________________________
> >>>> U-Boot mailing list
> >>>> U-Boot at lists.denx.de
> >>>> http://lists.denx.de/mailman/listinfo/u-boot
> >>>>
> >>> Perhaps this because our memory barriers are lacking.
> >>>
> >>> Linux has this code
> >>> asm/io.h:#define writel(v,c)            ({ __iowmb();
> >>> writel_relaxed(v,c); })
> >>>
> >>> asm/io.h-#ifdef CONFIG_ARM_DMA_MEM_BUFFERABLE
> >>> asm/io.h-#include <asm/barrier.h>
> >>> asm/io.h-#define __iormb()              rmb()
> >>> asm/io.h:#define __iowmb()              wmb()
> >>> asm/io.h-#else
> >>> asm/io.h-#define __iormb()              do { } while (0)
> >>> asm/io.h:#define __iowmb()              do { } while (0)
> >>> asm/io.h-#endif
> >>>
> >>> asm/io.h-#ifdef CONFIG_ARM_DMA_MEM_BUFFERABLE
> >>> asm/io.h-#include <asm/barrier.h>
> >>> asm/io.h-#define __iormb()              rmb()
> >>> asm/io.h:#define __iowmb()              wmb()
> >>> asm/io.h-#else
> >>> asm/io.h-#define __iormb()              do { } while (0)
> >>> asm/io.h:#define __iowmb()              do { } while (0)
> >>> asm/io.h-#endif
> >>>
> >>> asm/barrier.h-#elif defined(CONFIG_ARM_DMA_MEM_BUFFERABLE) ||
> >>> defined(CONFIG_SMP)
> >>> asm/barrier.h-#define mb()              do { dsb(); outer_sync(); }
> >>> while (0)
> >>> asm/barrier.h-#define rmb()             dsb()
> >>> asm/barrier.h:#define wmb()             mb()
> >>> asm/barrier.h-#else
> >>> asm/barrier.h-#define mb()              barrier()
> >>> asm/barrier.h-#define rmb()             barrier()
> >>> asm/barrier.h:#define wmb()             barrier()
> >>> asm/barrier.h-#endif
> >>>
> >>> asm/barrier.h-#if __LINUX_ARM_ARCH__ >= 7
> >>> asm/barrier.h-#define isb() __asm__ __volatile__ ("isb" : : : "memory")
> >>> asm/barrier.h:#define dsb() __asm__ __volatile__ ("dsb" : : : "memory")
> >>> asm/barrier.h-#define dmb() __asm__ __volatile__ ("dmb" : : : "memory")
> >>> asm/barrier.h-#elif defined(CONFIG_CPU_XSC3) || __LINUX_ARM_ARCH__ == 6
> >>> asm/barrier.h-#define isb() __asm__ __volatile__ ("mcr p15, 0, %0, c7,
> >>> c5, 4" \
> >>> asm/barrier.h-                              : : "r" (0) : "memory")
> >>> asm/barrier.h:#define dsb() __asm__ __volatile__ ("mcr p15, 0, %0, c7,
> >>> c10, 4" \
> >>> asm/barrier.h-                              : : "r" (0) : "memory")
> >>> asm/barrier.h-#define dmb() __asm__ __volatile__ ("mcr p15, 0, %0, c7,
> >>> c10, 5" \
> >>>
> >>> _____________________________________
> >>> Can you try just adding a dsb() instead of the dummy read?
> >>>
> >>> If this also fixes your problem, it seems better to fix our writel 
> >>> macro
> >> Not sure I understand who you are answering to exactly, as Fabio
> >> indicates his problem is solved.
> >>
> >> Besides, Marek and I had in fact investigated barriers, adding some as
> >> I did in times past in mvgbe.c, and fiddling with the one already in
> >> dcache_flush_range(). None of this had any effect.
> >
> > You tried adding a  dsb()  to dcache_flush_range()?
> > That should have fixed the problem as well.
> >
> >>
> >> However, if our barriers are lacking, then they may fail us somehow on
> >> other occasions, so best is if we analyze the failings. Can you clarify
> >> in what respect exactly they are lacking? For instance, are all our
> >> barriers lacking, or only some, and which ones?
> >>
> >> Amicalement,
> >
> > Linux has
> >
> > Kconfig:config ARM_DMA_MEM_BUFFERABLE
> > Kconfig-        bool "Use non-cacheable memory for DMA" if (CPU_V6 || 
> > CPU_V6K) && !CPU_V7
> > Kconfig-        depends on !(MACH_REALVIEW_PB1176 || 
> > REALVIEW_EB_ARM11MP || \
> > Kconfig-                     MACH_REALVIEW_PB11MP)
> > Kconfig-        default y if CPU_V6 || CPU_V6K || CPU_V7
> > Kconfig-        help
> >
> >
> > So, if this symbol is y then all writel/readl will be preceded by a 
> > dsb() as shown above.
> >
> > However, u-boot probably uses cacheable memory for dma, so maybe 
> > u-boot is also correct with
> >
> > asm/io.h-#define dmb()          __asm__ __volatile__ ("" : : : "memory")
> > asm/io.h-#define __iormb()    dmb()
> > asm/io.h:#define __iowmb()    dmb()
> >
> >
> > and no dsb(), but perhaps flush_dcache still needs one at the end.
> >
> >
> > Troy
> >
> 
> for armv7, flush dcache does have a dsb.
> 
> //u-boot
> #define CP15DSB asm volatile ("mcr     p15, 0, %0, c7, c10, 4" : : "r" (0))
> 
> //linux
> asm/barrier.h:#define dsb() __asm__ __volatile__ ("mcr p15, 0, %0, c7, 
> c10, 4"  : : "r" (0) : "memory")
> 
> 
> 
> Don't know why I didn't see that before.
> So, I don't know why that wasn't good enough.
> 
> Maybe  CONFIG_SYS_DCACHE_OFF was set and
> 
> void flush_dcache_range(unsigned long start, unsigned long stop)
> {
> }
> 
> Needs a dsb too???

I think everything is explained in Marek's commit message.

> Troy

Amicalement,
-- 
Albert.

  reply	other threads:[~2013-07-15 20:20 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 23:03 [U-Boot] [PATCH] net: fec: Avoid MX28 bus sync issue Marek Vasut
2013-07-11 23:18 ` Fabio Estevam
2013-07-12  3:41   ` Alexandre Pereira da Silva
2013-07-12  3:51     ` Marek Vasut
2013-07-12 11:37       ` Hector Palacios
2013-07-12 11:39         ` Fabio Estevam
2013-07-12 12:01         ` Marek Vasut
2013-07-12 15:08           ` Hector Palacios
2013-07-12 15:50             ` Albert ARIBAUD
2013-07-12 16:48             ` Marek Vasut
2013-07-15  8:58               ` Hector Palacios
2013-07-15 12:30                 ` Marek Vasut
2013-07-15 15:09                   ` Hector Palacios
2013-07-15 15:12                     ` Marek Vasut
2013-07-15 15:24                       ` Hector Palacios
2013-07-16  3:51                     ` Fabio Estevam
2013-07-16  4:18                       ` Fabio Estevam
2013-07-16  4:44                         ` Marek Vasut
2013-07-17 15:55                           ` Hector Palacios
2013-07-18  4:12                             ` Marek Vasut
2013-09-12 10:22                             ` Hector Palacios
2013-09-12 10:50                               ` Marek Vasut
     [not found]                                 ` <52319DE8.5080607@digi.com>
2013-09-12 11:00                                   ` Marek Vasut
2013-09-12 11:02                                 ` Robert Hodaszi
2013-09-12 14:05                                   ` Marek Vasut
2013-09-12 14:15                                     ` Robert Hodaszi
2013-09-12 14:31                                       ` Marek Vasut
2013-09-12 14:32                                         ` Robert Hodaszi
2013-09-12 15:06                                           ` Marek Vasut
2013-09-12 18:17                                     ` Wolfgang Denk
2013-09-12 18:39                                       ` Fabio Estevam
2013-09-12 18:53                                         ` Wolfgang Denk
2013-09-12 19:37                                           ` Fabio Estevam
2013-09-13 11:11                                             ` Robert Hodaszi
2013-09-13 11:13                                               ` Robert Hodaszi
2013-09-13 14:01                                                 ` Marek Vasut
2013-09-13 14:24                                                   ` Robert Hodaszi
2013-09-13 16:06                                               ` Wolfgang Denk
2013-09-13 16:24                                                 ` Marek Vasut
2013-09-13 17:46                                                   ` Wolfgang Denk
2013-09-14 22:05                                                     ` Fabio Estevam
2013-09-12 11:08                                 ` Robert Hodaszi
2013-09-12 18:12                                   ` Wolfgang Denk
2013-09-12 17:50                               ` Wolfgang Denk
2013-07-13  2:43   ` Troy Kisky
2013-07-15 13:41     ` Albert ARIBAUD
2013-07-15 17:39       ` Troy Kisky
2013-07-15 19:59         ` Troy Kisky
2013-07-15 20:20           ` Albert ARIBAUD [this message]
2013-07-15 20:20         ` Albert ARIBAUD
2013-07-15 21:18           ` Troy Kisky
2013-07-12  5:57 ` Albert ARIBAUD
2013-07-12  6:39   ` Albert ARIBAUD
2013-07-12 11:51     ` Marek Vasut
2013-07-12  6:56   ` Stefano Babic
2013-07-12  7:30 ` Stefano Babic
  -- strict thread matches above, loose matches on Subject: below --
2013-09-15 18:12 Oliver Metz
2013-09-15 18:16 ` Fabio Estevam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130715222036.5b8fda19@lilith \
    --to=albert.u.boot@aribaud.net \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox