Eric Lee / smarc-uboot

24 Feb, 2018

1 commit

13 Dec, 2017

2 commits

18 Nov, 2017

1 commit

  • b6251db8c   Kconfig: Introduce USE_BOOTCOMMAND and migrate BOOTCOMMAND ... Browse Code »
    54

    We first introduce CONFIG_USE_BOOTCOMMAND, similar to
    CONFIG_USE_BOOTARGS. We then migrate CONFIG_BOOTCOMMAND for most
    CONFIG_DISTRO_DEFAULT users. In some cases platforms have a complex
    scheme around this usage, and these have been defered for the moment so
    that platform maintainers can work on a migration plan.

    Signed-off-by: Tom Rini
    Reviewed-by: Lukasz Majewski

    Tom Rini
     

31 Oct, 2017

1 commit

12 Oct, 2017

1 commit

  • 066d97c73   wandboard: Add support for the latest revd1 revision ... Browse Code »

    Latest wandboard hardware revision is revd1, which brings the following
    new features:

    - PFUZE100 PMIC
    - AR8035 Ethernet PHY
    - Upgrade Wifi/BT chip to BCM4339/BCM43430.

    The detection mechanism is to probe the PMIC and when it is
    found, then the revision of the board is revd1.

    As the detection is done via PMIC, we need to print the board version
    at a later stage via CONFIG_DISPLAY_BOARDINFO_LATE and also need
    to disable CONFIG_DISPLAY_BOARDINFO, which is done much earlier.

    Make the necessary adjustments for the AR8035 PHY to work on revd1.

    Based on Richard Hu's work from Technexion's U-Boot tree.

    Signed-off-by: Fabio Estevam

    Fabio Estevam
     

11 Sep, 2017

1 commit

  • c7430d7d5   ipu_common: Let the MX6 IPU clock be calculated in run-time ... Browse Code »

    MX6Q/QP IPU operates at 264MHz and MX6DL IPU at 198MHz.

    When running a SPL target, which supports multiple MX6 variants we cannot
    properly setup the IPU clock frequency via CONFIG_IPUV3_CLK option as
    such decision is done in build-time currently.

    Remove the CONFIG_IPUV3_CLK option and let the IPU clock frequency be
    configured in run-time on mx6.

    Reported-by: Eric Nelson
    Signed-off-by: Fabio Estevam
    Reviewed-by: Eric Nelson
    Reviewed-by: Stefano Babic
    [agust: fixed #endif in cgtqmx6eval.h]
    Signed-off-by: Anatolij Gustschin

    Fabio Estevam
     

17 Aug, 2017

1 commit

08 Aug, 2017

1 commit

28 Jul, 2017

1 commit

26 Jul, 2017

1 commit

  • 2be296538   Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig ... Browse Code »
    20

    This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_MMC
    CONFIG_ENV_IS_IN_NAND
    CONFIG_ENV_IS_IN_UBI
    CONFIG_ENV_IS_NOWHERE

    In fact this already exists for sunxi as a 'choice' config. However not
    all the choices are available in Kconfig yet so we cannot use that. It
    would lead to more than one option being set.

    In addition, one purpose of this series is to allow the environment to be
    stored in more than one place. So the existing choice is converted to a
    normal config allowing each option to be set independently.

    There are not many opportunities for Kconfig updates to reduce the size of
    this patch. This was tested with

    ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC

    And then manual updates. This is because for CHAIN_OF_TRUST boards they
    can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
    now.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Rini

    Simon Glass
     

12 Jul, 2017

2 commits

  • 84b4690f2   wandboard: Use PARTUUID to specify the rootfs location ... Browse Code »

    Currently the rootfs location is passed via mmcblk number and the
    problem with this approach is that the mmcblk number for the eMMC
    changes depending on the kernel version.

    In order to avoid such issue, use UUID method to specify the rootfs
    location.

    This change was made based on U-Boot commit:

    - ca4f338e2efece5196eb2178e5f7d07be828da6e

    Signed-off-by: Fabio Berton
    Signed-off-by: Otavio Salvador
    Reviewed-by: Fabio Estevam

    Fabio Berton
     
  • 3bf926c0d   Convert CONFIG_CMD_SATA to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_CMD_SATA

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng

    Simon Glass
     

23 May, 2017

1 commit

  • 7a01f3c6f   Convert CONFIG_CMD_HDMIDETECT to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_CMD_HDMIDETECT

    Note that we cannot do 'default y if VIDEO' because this option is only
    enabled for a small subset of mx6 boards. Also this command is is not a
    great implementation (it doesn't use driver model).

    Signed-off-by: Simon Glass
    Reviewed-by: Tom Rini

    Simon Glass
     

16 May, 2017

2 commits

  • 80f1f3204   Kconfig: USB: Migrate existing USB_EHCI_xxx options ... Browse Code »

    The following options are migrated over fully now:
    - USB_EHCI_ATMEL
    - USB_EHCI_MARVELL
    - USB_EHCI_MX6
    - USB_EHCI_MX7
    - USB_EHCI_MSM
    - USB_EHCI_ZYNQ
    - USB_EHCI_GENERIC

    This also requires fixing the depends on USB_EHCI_MARVELL as it's used
    by Orion5X and Kirkwood as well.

    Cc: Marek Vasut
    Signed-off-by: Tom Rini
    Reviewed-by: Marek Vasut

    Tom Rini
     
  • 64d6ac5bc   Kconfig: USB: Migrate CONFIG_USB_EHCI_HCD users to Kconfig ... Browse Code »
    20

    Migrate the rest of the users of CONFIG_USB_EHCI_HCD over to Kconfig.
    For a few SoCs, imply or default y this if USB is enabled. In some
    cases we had not already migrated to CONFIG_USB so do that as well.

    Cc: Marek Vasut
    Signed-off-by: Tom Rini
    Reviewed-by: Marek Vasut

    Tom Rini
     

15 May, 2017

1 commit

30 Apr, 2017

1 commit

29 Jan, 2017

1 commit

26 Jan, 2017

1 commit

22 Jan, 2017

1 commit

29 Nov, 2016

1 commit

  • 36c0627ba   arm: imx: wandboard: fix compile error if CONFIG_VIDEO is deactivated ... Browse Code »

    When I tried to deactivate VIDEO support for the Wandboard, it still
    tried to initialize the Framebuffer and so on. That is the reason for
    the added ifdefs. CONFIG_VIDEO is enabled in the configuration as default
    and therefore nothing changes for the default user.

    The structs mx6dl_i2c2_pad_info and mx6q_i2c2_pad_info are only available
    when CONFIG_IPUV3 are set and should not be tried to access, when that
    define is not defined.

    Signed-off-by: Sven Ebenfeld

    Sven Ebenfeld
     

24 Oct, 2016

5 commits

04 Oct, 2016

1 commit

  • 5cca52a4c   wandboard: Remove videoargs script ... Browse Code »

    The videoargs script is kernel version dependent and since wandboard
    uses distro config, there is no need to handle videoargs locally.

    In case such video related settings are needed, then the proper
    location would be the distro extlinux.conf or boot.scr files.

    So remove 'videoargs' script.

    Signed-off-by: Fabio Estevam

    Fabio Estevam
     

17 Sep, 2016

2 commits

10 Sep, 2016

1 commit

20 Jul, 2016

1 commit

  • 67ff9e11f   wandboard: move environment partition farther from u-boot.img ... Browse Code »

    Recently I started to notice that u-boot.img built for Wandboard
    by some toolchains becomes so large that it basically overlaps with
    U-Boot environment area on SD-card.

    According to
    http://wiki.wandboard.org/index.php/Boot-process#sdcard_boot_data_layout
    Wandboard's SD-card layout is as follows:
    ------------------------------>8---------------------------
    Acked-by: Otavio Salvador
    Acked-by: Fabio Estevam

    ==========================================================
    1. 0x00000000 Reserved For MBR
    2. 0x00000200 512 Secondary Image Table (optional)
    3. 0x00000400 1024 uBoot Image (Starting From IVT)
    4. 0x00060000 393216 start of uboot env (size:8k)
    5. 0x00062000 end of uboot env
    6. 0x00100000 1048576 Linux kernel start
    7. 0x0076AC00 7777280 start of partition 1
    ------------------------------>8---------------------------

    So for U-Boot we have 383kB (392192 bytes).

    But in up to date U-Boot for Wandboard we build separately
    a) SPL
    b) u-boot.img

    which gives us a bit more detailed SD-card layout:
    ------------------------------>8---------------------------
    ==========================================================
    1. 0x00000000 Reserved For MBR
    2. 0x00000200 512 Secondary Image Table (optional)
    3. 0x00000400 1024 SPL
    4. 0x00011400 70656 u-boot.img
    5. 0x00060000 393216 start of uboot env (size:8k)
    6. 0x00062000 end of uboot env
    ...
    ------------------------------>8---------------------------

    >From that layout we may calculate amount of space reserved for
    u-boot.img. It's just 315kb (322560 bytes).

    Now if I build U-Boot with Sourcery CodeBench ARM 2014.05 produced
    u-boot.img is already more than we expected
    (323840 bytes instead of "< 322560"):
    ------------------------------>8---------------------------
    ls -la u-boot.img
    -rw-rw-r-- 1 user user 323840 Jul 5 07:38 u-boot.img
    ------------------------------>8---------------------------

    Funny enough if I rebuild U-Boot with ARM toolchain available in
    my Fedora 23 distro u-boot.img becomes a little bit smaller:
    ------------------------------>8---------------------------
    ls -la u-boot.img
    -rw-rw-r-- 1 user user 322216 Jul 5 07:39 u-boot.img
    ------------------------------>8---------------------------

    What's worse this problem might not affect people most of the time
    because what happens people would just copy u-boot.img on SD-card and
    live in happiness with it... well until somebody attempts to save
    environment in U-Boot with "saveenv" command which will simply
    overwrite the very end of u-boot.img.
    That will lead to unusable SD-card until user dd u-boot.img on
    SD-card again.

    I may foresee this issue in the future to become more visible once we
    add more features in U-Boot for Wandboard or just existing code base
    becomes bulkier and people will consistently get larger u-boot.img
    files produced.

    IMHO there's an obvious solution for all that - just move U-Boot's env
    to the very end of the gap between U-Boot and the first real partition
    on the SD-card. This patch will follow
    8fb9eea5653796 ("mx6sabre_common: Fix U-Boot corruption after 'saveenv'").
    So env is still not in the very end of the gap (obviously 256kb is way
    too much for U-Boot's env) but at least we have now the same
    partitioning for i.MX6 boards.

    Signed-off-by: Alexey Brodkin
    Cc: Fabio Estevam
    Cc: Otavio Salvador
    Cc: Peter Robinson
    Cc: Tom Rini
    Cc: Peter Korsgaard
    Cc: Wolfgang Denk

    Alexey Brodkin
     

12 Jul, 2016

1 commit

26 Apr, 2016

2 commits

03 Feb, 2016

1 commit

13 Nov, 2015

2 commits

02 Oct, 2015

1 commit

  • 03544c664   I2C: mxc_i2c: make I2C1 and I2C2 optional ... Browse Code »

    The driver assumed that I2C1 and I2C2 were always enabled,
    and if they were not, then an asynchronous abort was (silently)
    raised, to be caught much later on in the Linux kernel.

    Fix this by making I2C1 and I2C2 optional just like I2C3 and I2C4
    are.

    To make the change binary-invariant, declare I2C1 and I2C2 in
    every include/configs/ file which defines CONFIG_SYS_I2C_MXC.

    Also, while updating README about CONFIG_SYS_I2C_MXC_I2C1 and
    CONFIG_SYS_I2C_MXC_I2C2, add missing descriptions for I2C4 speed
    (CONFIG_SYS_MXC_I2C4_SPEED) and slave (CONFIG_SYS_MXC_I2C4_SLAVE)
    config options.

    Signed-off-by: Albert ARIBAUD (3ADEV)

    Albert ARIBAUD \\(3ADEV\\)
     

10 Jul, 2015

1 commit