04 Mar, 2016

3 commits


29 Apr, 2015

1 commit


07 Nov, 2014

1 commit


23 Oct, 2014

3 commits

  • The EDMA3 controller’s primary purpose is to service data transfers
    that you program between two memory-mapped slave endpoints on the device.

    Typical usage includes, but is not limited to the following:
    - Servicing software-driven paging transfers (e.g., transfers from external
    memory, such as SDRAM to internal device memory, such as DSP L2 SRAM)
    - Servicing event-driven peripherals, such as a serial port
    - Performing sorting or sub-frame extraction of various data structures
    - Offloading data transfers from the main device DSP(s)
    - See the device-specific data manual for specific peripherals that are
    accessible via the EDMA3 controller

    Signed-off-by: Ivan Khoronzhuk

    Khoronzhuk, Ivan
     
  • The keystone_nav driver is general driver intended to be used for
    working with queue manager and pktdma for different IPs like NETCP,
    AIF, FFTC, etc. So the it's API shouldn't be named like it works only
    with one of them, it should be general names. The names with prefix
    like netcp_* rather do for drivers/net/keystone_net.c driver. So it's
    good to generalize this driver to be used for different IP's and
    delete confusion with real NETCP driver.

    The current netcp_* functions of keystone navigator can be used for
    other settings of pktdma, not only for NETCP. The API of this driver
    is used by the keystone_net driver to work with NETCP, so net driver
    also should be corrected. For convenience collect pkdma
    configurations in drivers/dma/keystone_nav_cfg.c.

    Acked-by: Vitaly Andrianov
    Signed-off-by: Ivan Khoronzhuk

    Khoronzhuk, Ivan
     
  • The keystone_nav is used by drivers/net/keystone_net.c driver to
    send and receive packets, but currently it's placed at keystone
    arch sources. So it should be in the drivers directory also.
    It's separate driver that can be used for sending and receiving
    pktdma packets by others drivers also.

    This patch just move this driver to appropriate directory and
    doesn't add any functional changes.

    Acked-by: Murali Karicheri
    Signed-off-by: Ivan Khoronzhuk

    Khoronzhuk, Ivan
     

25 Sep, 2014

2 commits


09 Aug, 2014

1 commit

  • The following configs are not defined at all.

    - CONFIG_OMAP1510
    - CONFIG_OMAP_1510P1
    - CONFIG_OMAP_SX1
    - CONFIG_OMAP3_DMA
    - CONFIG_OMAP3_ZOOM2
    - CONFIG_OMAP_INNOVATOR

    Signed-off-by: Masahiro Yamada
    Cc: Tom Rini

    Masahiro Yamada
     

01 Nov, 2013

1 commit


10 Aug, 2013

1 commit

  • Add special function that executes a specially crafted circular
    DMA descriptor. The function doesn't wait for the descriptor to
    finish the transfer, since the descritor never finishes. This is
    useful when operating a SmartLCD through the LCDIF interface, as
    the LCDIF does not give us any means to have continuous refresh
    of the SmartLCD. Instead, the RUN bit in the LCDIF CTRL register
    must be triggered manually. This can be worked around by starting
    an DMA transfer which continuously sets the RUN bit. This function
    allows starting exactly such transfer.

    Signed-off-by: Marek Vasut
    Cc: Anatolij Gustschin
    Cc: Fabio Estevam
    Cc: Otavio Salvador
    Cc: Stefano Babic

    Marek Vasut
     

24 Jul, 2013

1 commit


22 Apr, 2013

2 commits


28 Jan, 2013

1 commit

  • The MX23 has less channels for the APBH DMA, sligtly different register
    layout and some bits in those registers are placed differently. Reflect
    this in the driver. This patch fixes MMC/DMA issue on MX23.

    Signed-off-by: Marek Vasut
    Cc: Otavio Salvador
    Cc: Fabio Estevam
    Cc: Stefano Babic

    Marek Vasut
     

01 Sep, 2012

3 commits


16 Apr, 2012

1 commit

  • This fixes the issue where mxs_dma_init() was called either twice or never,
    without introducing any new init hooks.

    The idea is to allow each and every device using the APBH DMA block to
    configure and request only the channels it uses, instead of making it call init
    for all the channels as is now.

    The common DMA block init part, which only configures the block, is then called
    from CPUs arch_cpu_init() call.

    NOTE: This patch depends on:

    http://patchwork.ozlabs.org/patch/150957/

    Signed-off-by: Marek Vasut
    Cc: Stefano Babic
    Cc: Wolfgang Denk
    Cc: Detlev Zundel
    Cc: Fabio Estevam
    Tested-by: Fabio Estevam

    Marek Vasut
     

29 Mar, 2012

1 commit


07 Dec, 2011

2 commits


11 Nov, 2011

1 commit


28 Oct, 2011

1 commit


07 Jul, 2011

1 commit

  • Commit 359ec4931944adb885882deb9b781e4095eabc94 broke support for the
    Freescale DMA engine on the 83xx parts. This is due to using registers
    which do not exist on 83xx. Remove the attribute register accesses from
    the 83xx build.

    Signed-off-by: Ira W. Snyder
    Cc: York Sun
    Cc: Peter Tyser
    Cc: Kumar Gala
    Signed-off-by: Kim Phillips

    Ira W. Snyder
     

18 Nov, 2010

1 commit

  • Before this commit, weak symbols were not overridden by non-weak symbols
    found in archive libraries when linking with recent versions of
    binutils. As stated in the System V ABI, "the link editor does not
    extract archive members to resolve undefined weak symbols".

    This commit changes all Makefiles to use partial linking (ld -r) instead
    of creating library archives, which forces all symbols to participate in
    linking, allowing non-weak symbols to override weak symbols as intended.
    This approach is also used by Linux, from which the gmake function
    cmd_link_o_target (defined in config.mk and used in all Makefiles) is
    inspired.

    The name of each former library archive is preserved except for
    extensions which change from ".a" to ".o". This commit updates
    references accordingly where needed, in particular in some linker
    scripts.

    This commit reveals board configurations that exclude some features but
    include source files that depend these disabled features in the build,
    resulting in undefined symbols. Known such cases include:
    - disabling CMD_NET but not CMD_NFS;
    - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.

    Signed-off-by: Sebastien Carlier

    Sebastien Carlier
     

01 Sep, 2010

1 commit


26 Aug, 2009

1 commit


03 Jul, 2009

1 commit


02 Jul, 2009

8 commits


13 Aug, 2008

1 commit