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
     

19 Jan, 2016

1 commit

  • In a number of places we had wordings of the GPL (or LGPL in a few
    cases) license text that were split in such a way that it wasn't caught
    previously. Convert all of these to the correct SPDX-License-Identifier
    tag.

    Signed-off-by: Tom Rini

    Tom Rini
     

26 Nov, 2013

2 commits


28 Nov, 2012

1 commit

  • There were a number of shared files that were using
    CONFIG_SYS_MPC85xx_DDR_ADDR, or CONFIG_SYS_MPC86xx_DDR_ADDR, and
    several variants (DDR2, DDR3). A recent patchset added
    85xx-specific ones to code which was used by 86xx systems.
    After reviewing places where these constants were used, and
    noting that the type definitions of the pointers assigned to
    point to those addresses were the same, the cleanest approach
    to fixing this problem was to unify the namespace for the
    85xx, 83xx, and 86xx DDR address definitions.

    This patch does:

    s/CONFIG_SYS_MPC8.xx_DDR/CONFIG_SYS_MPC8xxx_DDR/g

    All 85xx, 86xx, and 83xx have been built with this change.

    Signed-off-by: Andy Fleming
    Tested-by: Andy Fleming
    Acked-by: Kim Phillips

    Andy Fleming
     

12 Jan, 2012

2 commits

  • Existing boards by default have an issue where the LBC SDRAM
    SPD EEPROM and the DDR2 SDRAM SPD EEPROM both land at 0x51.

    After the hardware modification listed in the README is made,
    then the DDR2 SPD EEPROM appears at 0x53. So this implements
    a board specific get_spd() by taking advantage of the existing
    weak linkage, that 1st tries reading at 0x53 and then if that
    fails, it falls back to the old 0x51.

    Since the old dependency issue of "SPD implies no LBC SDRAM"
    gets removed with the hardware errata fix, remove that restriction
    in the code, so both LBC SDRAM and SPD can be selected.

    Signed-off-by: Paul Gortmaker
    Signed-off-by: Kumar Gala

    Paul Gortmaker
     
  • Nothing to see here, just a relocation of the fixed ddr init
    sequence to live in the actual ddr.c file itself.

    Signed-off-by: Paul Gortmaker
    Signed-off-by: Kumar Gala

    Paul Gortmaker
     

04 Apr, 2011

2 commits

  • Move fsl_ddr_get_spd into common mpc8xxx/ddr/main.c as most boards
    pretty much do the same thing. The only variations are in how many
    controllers or DIMMs per controller exist. To make this work we
    standardize on the names of the SPD_EEPROM_ADDRESS defines based on the
    use case of the board.

    We allow boards to override get_spd to either do board specific fixups
    to the SPD data or deal with any unique behavior of how the SPD eeproms
    are wired up.

    Signed-off-by: Kumar Gala

    Kumar Gala
     
  • Every 85xx board implements fsl_ddr_get_mem_data_rate via get_ddr_freq()
    and every 86xx board uses get_bus_freq(). If implement get_ddr_freq()
    as a static inline to call get_bus_freq() we can remove
    fsl_ddr_get_mem_data_rate altogether and just call get_ddr_freq()
    directly.

    Signed-off-by: Kumar Gala

    Kumar Gala
     

19 Oct, 2008

1 commit

  • Because some dimm parameters like n_ranks needs to be used with the board
    frequency to choose the board parameters like clk_adjust etc. in the
    board_specific_paramesters table of the board ddr file, we need to pass
    the dimm parameters to the board file.

    * move ddr dimm parameters header file from /cpu to /include directory.
    * add ddr dimm parameters to populate board specific options.
    * Fix fsl_ddr_board_options() for all the 8xxx boards which call this function.

    Signed-off-by: Haiying Wang

    Haiying Wang
     

28 Aug, 2008

1 commit