18 Jan, 2020

2 commits


03 Dec, 2019

4 commits


12 Aug, 2019

1 commit


26 Nov, 2018

1 commit


11 Oct, 2018

2 commits

  • The interruption support had be removed for ARM architecture and
    the function get_timer_masked() is no more used except in some
    the timer.c files.

    This patch clean each timer.c which implement this function and
    remove the associated prototype in u-boot-arm.h

    For timer.c, I don't verify if the weak version of get_timer
    (in lib/time.c) can be used

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     
  • The interruption support had be removed for ARM architecture and
    the function udelay_masked() is no more used except in some timer.c
    files and have the same content than udelay() or __udelay().

    This patch update each timer.c implementing this function and
    remove the associated prototype in u-boot-arm.h.

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     

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
     

16 Aug, 2017

1 commit


05 Jun, 2017

1 commit


01 Jun, 2017

1 commit


13 Aug, 2015

1 commit


23 Apr, 2015

2 commits


24 Mar, 2015

1 commit

  • Various files are needlessly rebuilt every time due to the version and
    build time changing. As version.h is not actually needed, remove the
    include.

    Signed-off-by: Rob Herring
    Cc: Albert Aribaud
    Cc: Stefano Babic
    Cc: Minkyu Kang
    Cc: Marek Vasut
    Cc: Tom Warren
    Cc: Michal Simek
    Cc: Macpaul Lin
    Cc: Wolfgang Denk
    Cc: York Sun
    Cc: Stefan Roese
    Cc: Nobuhiro Iwamatsu
    Cc: Simon Glass
    Cc: Philippe Reynes
    Cc: Eric Jarrige
    Cc: "David Müller"
    Cc: Phil Edworthy
    Cc: Robert Baldyga
    Cc: Torsten Koschorrek
    Cc: Anatolij Gustschin
    Reviewed-by: Linus Walleij
    Reviewed-by: Łukasz Majewski

    Rob Herring
     

29 Oct, 2014

1 commit

  • This commit introduces a Kconfig symbol for each ARM CPU:
    CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,
    CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.
    Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selected
    for CPU_ARM1176 and CPU_V7.

    For each target, the corresponding CPU is selected and the definition of
    SYS_CPU in the corresponding Kconfig file is removed.

    Also, it removes redundant "string" type in some Kconfig files.

    Signed-off-by: Georges Savoundararadj
    Acked-by: Albert ARIBAUD
    Cc: Masahiro Yamada

    Georges Savoundararadj
     

14 Sep, 2014

1 commit

  • Now the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}
    are specified in arch/Kconfig.

    We can delete the ones in arch and board Kconfig files.

    This commit can be easily reproduced by the following command:

    find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '
    /config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ {
    N
    s/\n[[:space:]]*string//
    }
    '

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

30 Jul, 2014

2 commits

  • We have switched to Kconfig and the boards.cfg file is going to
    be removed. We have to retrieve the board status and maintainers
    information from it.

    The MAINTAINERS format as in Linux Kernel would be nice
    because we can crib the scripts/get_maintainer.pl script.

    After some discussion, we chose to put a MAINTAINERS file under each
    board directory, not the top-level one because we want to collect
    relevant information for a board into a single place.

    TODO:
    Modify get_maintainer.pl to scan multiple MAINTAINERS files.

    Signed-off-by: Masahiro Yamada
    Suggested-by: Tom Rini
    Acked-by: Simon Glass

    Masahiro Yamada
     
  • This commit adds:
    - arch/${ARCH}/Kconfig
    provide a menu to select target boards
    - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
    - configs/${TARGET_BOARD}_defconfig
    default setting of each board

    (This commit was automatically generated by a conversion script
    based on boards.cfg)

    In Linux Kernel, defconfig files are located under
    arch/${ARCH}/configs/ directory.
    It works in Linux Kernel since ARCH is always given from the
    command line for cross compile.

    But in U-Boot, ARCH is not given from the command line.
    Which means we cannot know ARCH until the board configuration is done.
    That is why all the "*_defconfig" files should be gathered into a
    single directory ./configs/.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada
     

27 Feb, 2014

1 commit


01 Nov, 2013

1 commit


15 Oct, 2013

1 commit


24 Jul, 2013

1 commit


29 Jul, 2012

1 commit


05 Mar, 2012

1 commit

  • The reference implementation of the PCI initialization code almost
    everywhere contain this fragile loop of "a few usecs", and its
    use of volatile variables to delay a number of bus cycles is indeed
    uncertain.

    Reading the manual "Integrator/AP Users Guide", page 5-15 it is
    clearly stated:

    "Wait until 230ms after the end of the reset period before
    accessing V360EPC internal registers. The V360EPC supports the
    use of a serial configuration PROM and the software must wait for
    the device to detect the absence of this PROM before accessing any
    registers. The required delay is a function of the PCI Clock, but
    at the lower frequency (25MHz) is 230ms".

    So let's simply wait 230ms per the spec.

    This solves the compilation error that looked like this:
    pci.c: In function ‘pci_init_board’:
    pci.c:286:18: warning: variable ‘j’ set but not used

    Reported-by: Wolfgang Denk
    Signed-off-by: Linus Walleij

    Linus Walleij
     

28 Feb, 2012

2 commits

  • The PCI support for the Integrator AP has apparently never
    been finished and I strongly suspect that it has never worked,
    so let's fix it. This is a list of the more or less
    un-splittable changes done in this driver rewrite:

    - Replace the register definitions stashed into the config
    file (!) with a copy if the register file from the Linux
    kernels arch/arm/include/asm/hardware/pci_v3.h

    - Delete the unreadable gigantic macros that perform the
    config accesses and replace them with copyedited code from
    Linux arch/arm/mach-integrator/pci_v3.c

    - Rewrite the rest of the setup code to use the
    v3_[read|write][lwb]() accessors.

    - Enable PCI by default in the AP board configuration.

    - Fix checkpatch warnings and make code more conformant.

    Tested-by: Will Deacon
    Signed-off-by: Linus Walleij

    Linus Walleij
     
  • The U-Boot startup infrastructure already makes sure pci_init() is
    called at a proper time, calling it again from within the board
    setup code will not make things better.

    Signed-off-by: Linus Walleij

    Linus Walleij
     

10 Nov, 2011

5 commits


09 Nov, 2011

1 commit

  • When booting from Flash, the Integrator remaps its flash memory
    from 0x24000000 to 0x00000000, and starts executing it at
    0x00000000. This ROM thus hides the RAM underneath and first
    0x40000 bytes of the memory cannot be tested by get_ram_size().
    So let's test from 0x40000 to the end of detected memory
    instead.

    Signed-off-by: Linus Walleij

    Linus Walleij
     

16 Oct, 2011

1 commit

  • The top level Makefile does not do any recursion into subdirs when
    cleaning, so these clean/distclean targets in random arch/board dirs
    never get used. Punt them all.

    MAKEALL didn't report any errors related to this that I could see.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

04 Sep, 2011

3 commits

  • This deletes the integrator split_by_variant.sh script and
    defines a number of unique board types for the core modules
    that are meaningful to support for the Integrator AP/CP, i.e.
    the ones that did not just say "unsupported core module" in
    split_by_variant.sh. If more core modules need to be supported
    they are easy to add.

    We delete all the old cruft in Makefile and MAKEALL that was
    working around the old way of building boards. We create a
    unique config file per board to satisfy the build system, but
    they are just oneliners that include the existing
    integratorap.h and integratorcp.h configs.

    Signed-off-by: Linus Walleij

    Linus Walleij
     
  • The integrator board was apparently never converted over to support
    relocation until now. After this the integrator u-boot both compiles
    and boots on the Integrator AP.

    This also fixes the SDRAM memory size detection.

    Signed-off-by: Linus Walleij

    Linus Walleij
     
  • The integratorap/cp config for u-boot was outdated and would not
    even compile, so fix the obvious missing bits for it to start
    building. After this "make ap920t_config/make all" starts working
    again.

    Signed-off-by: Linus Walleij

    Linus Walleij