27 Nov, 2018

1 commit


10 Oct, 2018

1 commit


07 May, 2018

1 commit

  • When U-Boot started using SPDX tags we were among the early adopters and
    there weren't a lot of other examples to borrow from. So we picked the
    area of the file that usually had a full license text and replaced it
    with an appropriate SPDX-License-Identifier: entry. Since then, the
    Linux Kernel has adopted SPDX tags and they place it as the very first
    line in a file (except where shebangs are used, then it's second line)
    and with slightly different comment styles than us.

    In part due to community overlap, in part due to better tag visibility
    and in part for other minor reasons, switch over to that style.

    This commit changes all instances where we have a single declared
    license in the tag as both the before and after are identical in tag
    contents. There's also a few places where I found we did not have a tag
    and have introduced one.

    Signed-off-by: Tom Rini

    Tom Rini
     

29 Sep, 2017

1 commit


01 Jun, 2017

1 commit

  • These support the flat device tree. We want to use the dev_read_..()
    prefix for functions that support both flat tree and live tree. So rename
    the existing functions to avoid confusion.

    In the end we will have:

    1. dev_read_addr...() - works on devices, supports flat/live tree
    2. devfdt_get_addr...() - current functions, flat tree only
    3. of_get_address() etc. - new functions, live tree only

    All drivers will be written to use 1. That function will in turn call
    either 2 or 3 depending on whether the flat or live tree is in use.

    Note this involves changing some dead code - the imx_lpi2c.c file.

    Signed-off-by: Simon Glass

    Simon Glass
     

08 Feb, 2017

1 commit

  • At present devices use a simple integer offset to record the device tree
    node associated with the device. In preparation for supporting a live
    device tree, which uses a node pointer instead, refactor existing code to
    access this field through an inline function.

    Signed-off-by: Simon Glass

    Simon Glass
     

09 Jul, 2016

1 commit


12 Sep, 2015

1 commit


01 Jul, 2015

2 commits


30 Mar, 2015

1 commit


20 Jun, 2014

1 commit


18 Apr, 2014

1 commit

  • Currently davinci spi driver supports only bus 0 cs 0.
    This patch allows driver to support bus 1 and bus 2 with
    configurable number of chip selects. Also defaults are
    selected in a way to avoid regression on other platforms
    that uses davinci spi driver and has only one spi bus.

    Signed-off-by: Rex Chang
    Signed-off-by: Murali Karicheri
    Reviewed-by: Jagannadha Sutradharudu Teki

    Karicheri, Muralidharan
     

24 Jul, 2013

1 commit


19 Mar, 2013

1 commit


06 Jul, 2010

1 commit


22 Jun, 2010

1 commit

  • The following restructuring and optimisations increase the SPI
    read performance from 1.3MiB/s (on da850) to 2.87MiB/s (on da830):

    Remove continual revaluation of driver state from the core of the
    copy loop. State can not change during the copy loop, so it is
    possible to move these evaluations to before the copy loop.

    Cost is more code space as loop variants are required for each set
    of possible configurations. The loops are simpler however, so the
    extra is only 128bytes on da830 with CONFIG_SPI_HALF_DUPLEX
    defined.

    Unrolling the first copy loop iteration allows the TX buffer to be
    pre-loaded reducing SPI clock starvation.

    Unrolling the last copy loop iteration removes testing for the
    final loop iteration every time round the loop.

    Using the RX buffer empty flag as a transfer throttle allows the
    assumption that it is always safe to write to the TX buffer, so
    polling of TX buffer full flag can be removed.

    Signed-off-by: Nick Thompson
    Signed-off-by: Sandeep Paulraj

    Nick Thompson
     

08 Jun, 2010

1 commit

  • I have updated this patch based on the comments [1] by Wolfgang Denk and
    removed unused variables.
    [1][http://lists.denx.de/pipermail/u-boot/2010-May/071728.html]

    Reduce the number of reads per byte transferred on the BUF register from 2 to 1 and
    take advantage of the TX buffer in the SPI module. On LogicPD OMAP-L138 EVM,
    SPI read throughput goes up from ~0.8Mbyte/s to ~1.3Mbyte/s. Tested with a 2Mbyte image file.
    Remove unused variables in the spi_xfer() function.

    Signed-off-by: Delio Brignoli
    Tested-by: Ben Gardiner
    Signed-off-by: Sandeep Paulraj

    Delio Brignoli
     

13 Mar, 2010

1 commit


13 Feb, 2010

1 commit