30 Dec, 2016

1 commit

  • Commit 7a777f6d6f35 ("mmc: Add generic Kconfig option") created
    a Kconfig entry for this option without any actual moves, then
    commit 44c798799f66 ("sunxi: Use Kconfig CONFIG_MMC") moved
    instances only for SUNXI.

    We generally do not like such partial moves. This kind of work
    is automated by tools/moveconfig.py, so it is pretty easy to
    complete this move.

    I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
    This shortens the configs and will ease new board porting.

    This commit was created as follows:

    [1] Edit Kconfig (remove the "depends on", add the "default",
    copy the prompt and help message from Linux)

    [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Jaehoon Chung

    Masahiro Yamada
     

24 Nov, 2016

2 commits


05 Aug, 2016

1 commit

  • We need to ensure that CONFIG_PHYS_64BIT is configured via Kconfig so
    that it is always available to the build system. Otherwise we can run
    into cases where we have inconsistent sizes of certain attributes.

    Ravi Babu reported offset mismatch of struct dwc3 across files since
    commit 95ebc253e6d4 ("types.h: move and redefine resource_size_t").
    Since the commit, resource_addr_t points to phys_addr_t, whose size
    is dependent on CONFIG_PHYS_64BIT for ARM architecture.

    I tried my best to use "select" where possible (for example, ARMv8
    architecture) because I think this kind of option is generally user-
    unconfigurable. However, I see some of PowerPC boards have 36BIT
    defconfigs as well as 32BIT ones. I moved CONFIG_PHYS_64BIT to the
    defconfigs for such boards.

    CONFIG_36BIT is no longer referenced, so all of the defines were
    removed from CONFIG_SYS_EXTRA_OPTIONS.

    Fixes: 95ebc253e6d4 ("types.h: move and redefine resource_size_t")
    Signed-off-by: Masahiro Yamada
    Reported-by: Ravi Babu
    Acked-by: Stefan Roese
    Reviewed-by: Tom Rini
    Reviewed-by: York Sun

    Masahiro Yamada
     

24 Jul, 2013

1 commit


21 Jun, 2013

1 commit

  • Currently, the macro "CONFIG_SYS_FSL_SRIO_PCIE_BOOT_MASTER" can enable
    the master module of Boot from SRIO and PCIE on a platform. But this
    is not a silicon feature, it's just a specific booting mode based on
    the SRIO and PCIE interfaces. So it's inappropriate to put the macro
    into the file arch/powerpc/include/asm/config_mpc85xx.h.

    Change the macro "CONFIG_SYS_FSL_SRIO_PCIE_BOOT_MASTER" to
    "CONFIG_SRIO_PCIE_BOOT_MASTER", remove them from
    arch/powerpc/include/asm/config_mpc85xx.h file, and add those macros
    in configuration header file of each board which can support the
    master module of Boot from SRIO and PCIE.

    Signed-off-by: Liu Gang
    Signed-off-by: Andy Fleming

    Liu Gang
     

28 Nov, 2012

1 commit

  • board configuration file is included before asm/config_mpc85xx.h.
    however, CONFIG_FSL_SATA_V2 is defined in asm/config_mpc85xx.h.
    it will never take effective in the board configuration file for
    this kind of code :

    #ifdef CONFIG_FSL_SATA_V2
    ...
    #endif

    To solve this problem, move CONFIG_FSL_SATA_V2 to board
    configuration header file.

    This patch reverts Timur's
    commit:3e0529f742e893653848494ffb9f7cd0d91304bf

    Signed-off-by: Roy Zang
    Signed-off-by: Andy Fleming

    Zang Roy-R61911
     

23 Oct, 2012

1 commit


24 Aug, 2012

1 commit


29 Nov, 2011

1 commit

  • Macro CONFIG_FSL_SATA_V2 is defined if the SOC has a V2 Freescale SATA
    controller, so it should be defined in config_mpc85xx.h instead of the various
    board header files. So now CONFIG_FSL_SATA_V2 is always defined on the P1013,
    P1022, P2041, P3041, P5010, and P5020. It was already defined for the
    P1010 and P1014.

    Signed-off-by: Timur Tabi
    Signed-off-by: Kumar Gala

    Timur Tabi
     

18 Oct, 2011

1 commit


03 Oct, 2011

2 commits


20 May, 2011

1 commit


28 Apr, 2011

1 commit

  • The P3041DS & P5020DS boards are almost identical (except for the
    processor in them). Additionally they are based on the P4080DS board
    design so we use the some board code for all 3 boards.

    Some ngPIXIS (FPGA) registers where reserved on P4080DS and now have
    meaning on P3041DS/P5020DS. We utilize some of these for SERDES clock
    configuration.

    Additionally, the P3041DS/P5020DS support NAND.

    Signed-off-by: Timur Tabi
    Signed-off-by: Shaohui Xie
    Signed-off-by: Kumar Gala

    Kumar Gala