1. 23 Mar, 2018 1 commit
    • Breno Lima's avatar
      MLK-17898: mx6sl: Select MX6SL option via Kconfig · a2860393
      Breno Lima authored
      Currently it's not possible to build i.MX6SL EVK with CONFIG_SECURE_BOOT
      In file included from drivers/crypto/fsl/jobdesc.c:12:0:
      drivers/crypto/fsl/jobdesc.c: In function ‘inline_cnstr_jobdesc_blob_dek’:
      include/fsl_sec.h:268:25: error: ‘CAAM_ARB_BASE_ADDR’ undeclared (first
      use in this function)
       #define SEC_MEM_PAGE1  (CAAM_ARB_BASE_ADDR + 0x1000)
      drivers/crypto/fsl/jobdesc.c:140:21: note: in expansion of macro
        memcpy((uint32_t *)SEC_MEM_PAGE1, (uint32_t *)plain_txt, in_sz);
      include/fsl_sec.h:268:25: note: each undeclared identifier is reported only
      once for each function it appears in
       #define SEC_MEM_PAGE1  (CAAM_ARB_BASE_ADDR + 0x1000)
      drivers/crypto/fsl/jobdesc.c:140:21: note: in expansion of macro
        memcpy((uint32_t *)SEC_MEM_PAGE1, (uint32_t *)plain_txt, in_sz);
      scripts/Makefile.build:280: recipe for target 'drivers/crypto/fsl/jobdesc.o'
      Currently the MX6SL option is selected via CONFIG_SYS_EXTRA_OPTIONS, so
      CONFIG_FSL_CAAM is being wrongly selected by the imx-common Kconfig.
      Select CONFIG_MX6SL via Kconfig to address this issue.
      Signed-off-by: default avatarBreno Lima <breno.lima@nxp.com>
      Reviewed-by: default avatarYe Li <ye.li@nxp.com>
  2. 05 Apr, 2017 2 commits
  3. 25 Jan, 2017 1 commit
  4. 09 Sep, 2016 1 commit
  5. 17 Jun, 2016 1 commit
  6. 25 Apr, 2016 3 commits
  7. 14 Mar, 2016 1 commit
  8. 25 Nov, 2015 1 commit
  9. 18 Nov, 2015 1 commit
  10. 02 Sep, 2015 1 commit
    • Peng Fan's avatar
      imx: mx6 move TARGET_xx Kconfig option to mx6 specific Kconfig file · 21782828
      Peng Fan authored
      Move TARGET_xx Kconfig option based on mx6 to arch/arm/cpu/armv7/mx6/Kconfig.
      Add enable "CONFIG_ARCH_MX6" for boards based on mx6.
      Then we can choose target boards using "make ARCH=arm menuconfig"
      with ARCH_MX6 defined.
      If using original way, we have no chance to enable ARCH_MX6 when
      "make menuconfig". Even define CONFIG_ARCH_MX6=y in xx_defconfig,
      kconfig will complains "arch/../configs/platinum_titanium_defconfig:3:
      warning: override: TARGET_PLATINUM_TITANIUM changes choice state"
      Signed-off-by: default avatarPeng Fan <Peng.Fan@freescale.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Tim Harvey <tharvey@gateworks.com>
      Cc: Eric Bénard <eric@eukrea.com>
      Cc: Fabio Estevam <fabio.estevam@freescale.com>
      Cc: Eric Nelson <eric.nelson@boundarydevices.com>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Christian Gmeiner <christian.gmeiner@gmail.com>
      Cc: Stefan Roese <sr@denx.de>
      Cc: Soeren Moch <smoch@web.de>
      Cc: Otavio Salvador <otavio@ossystems.com.br>
      Acked-by: default avatarStefano Babic <sbabic@denx.de>
      Acked-by: default avatarSoeren Moch <smoch@web.de>
      Acked-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      Acked-by: default avatarChristian Gmeiner <christian.gmeiner@gmail.com>
  11. 26 Jun, 2015 2 commits
  12. 01 Jun, 2015 1 commit
  13. 12 May, 2015 1 commit
  14. 23 Mar, 2015 1 commit
  15. 30 Jul, 2014 1 commit
    • Masahiro Yamada's avatar
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada authored
      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: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>