27 Jul, 2011

1 commit

  • This allows us to move duplicated code in
    (atomic_inc_not_zero() for now) to

    Signed-off-by: Arun Sharma
    Reviewed-by: Eric Dumazet
    Cc: Ingo Molnar
    Cc: David Miller
    Cc: Eric Dumazet
    Acked-by: Mike Frysinger
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Arun Sharma
     

10 Jan, 2011

2 commits


07 Aug, 2010

1 commit

  • The dma_memcpy() function takes care of flushing different caches for us.
    Normally this is what we want, but when resuming from mem, we don't yet
    have caches enabled. If these functions happen to be placed into L1 mem
    (which is what we're trying to relocate), then things aren't going to
    work. So define a non-cache dma_memcpy() variant to utilize in situations
    like this.

    Signed-off-by: Michael Hennerich
    Signed-off-by: Mike Frysinger

    Michael Hennerich
     

09 Mar, 2010

1 commit


15 Dec, 2009

3 commits


12 Jun, 2009

2 commits

  • Make sure the internal core buffers are flushed before telling the DMA
    engine to fetch the descriptor structure so that it gets the right values.

    Signed-off-by: Sonic Zhang
    Signed-off-by: Mike Frysinger

    Sonic Zhang
     
  • Our early L1 relocate code may implicitly call code which lives in L1
    memory. This is due to the dma_memcpy() rewrite that made the DMA code
    lockless and safe to be used by multiple processes. If we start the
    early DMA memcpy to relocate things into L1 instruction but then our
    DMA memcpy code calls a function that lives in L1, things fall apart.
    As such, create a small dedicated DMA memcpy routine that we can assume
    sanity at boot time.

    Reported-by: Filip Van Rillaer
    Signed-off-by: Robin Getz
    Signed-off-by: Mike Frysinger

    Robin Getz
     

07 Jan, 2009

13 commits


28 Oct, 2008

1 commit


27 Aug, 2008

1 commit