1. 13 Nov, 2013 7 commits
    • Lauren Post's avatar
      imx6solosabresd.conf: Add ldo device tree · 362c55a3
      Lauren Post authored
      ENGR00277895: dts: ARM: imx6: add ldo-enable dts files
      
        Currently, we use different dts files to support ldo-bypass or ldo-enable, then
      we need add both dts files for the boards which can support ldo-bypass mode(all
      boards support ldo-enable at least). So for below boards we need add ldo-enable
      dts file so that we can use this to easily support ldo-enable mode:
        1)mx6q-sabresd board:  ldo-bypass dts->mx6q-sabresd.dtb,
                               ldo-enable dts->mx6q-sabresd-ldo.dtb
        2)mx6q-sabresd board:  ldo-bypass dts->mx6dl-sabresd.dtb,
                       ldo-enable dts->mx6dl-sabresd-ldo.dtb
        3)mx6sl-evk board:     ldo-bypass dts->mx6sl-evk.dtb,
                       ldo-enable dts->mx6sl-evk-ldo.dtb
      
      Change-Id: I261c516495e3921fb1c2d8937d96fb6e3a23e87b
      Signed-off-by: default avatarLauren Post <lauren.post@freescale.com>
      362c55a3
    • Lauren Post's avatar
      imx6slevk.conf: Add ldo device tree · b9596cd3
      Lauren Post authored
      ENGR00277895: dts: ARM: imx6: add ldo-enable dts files
      
        Currently, we use different dts files to support ldo-bypass or ldo-enable, then
      we need add both dts files for the boards which can support ldo-bypass mode(all
      boards support ldo-enable at least). So for below boards we need add ldo-enable
      dts file so that we can use this to easily support ldo-enable mode:
        1)mx6q-sabresd board:  ldo-bypass dts->mx6q-sabresd.dtb,
                               ldo-enable dts->mx6q-sabresd-ldo.dtb
        2)mx6q-sabresd board:  ldo-bypass dts->mx6dl-sabresd.dtb,
                       ldo-enable dts->mx6dl-sabresd-ldo.dtb
        3)mx6sl-evk board:     ldo-bypass dts->mx6sl-evk.dtb,
                       ldo-enable dts->mx6sl-evk-ldo.dtb
      
      Change-Id: I997bf896a3d3fde482fe9c120a92c16d49817adb
      Signed-off-by: default avatarLauren Post <lauren.post@freescale.com>
      b9596cd3
    • Lauren Post's avatar
      imx6qsabresd.conf: Add ldo and hdcp DTS · c4940e8b
      Lauren Post authored
      ENGR00274059-02 ARM: Add new dts for imx6q/imx6dl SabreSD hdcp
      
      hdcp ddc pins conflict with i2c2,
      add new dts file for imx6q and imx6dl SabreSD board,
      enable hdcp and disable i2c2 in these dts files.
      Remove hdmi pins property from mx6qdl-sabresd.dtsi.
      
      ENGR00279402-1 ARM: dts: imx6: add wdog reset source seclect in dts
      
      Some boards use another WDOG reset source to reboot system in ldo-bypass mode.
      We need add the property in board dts file so that we can easily know the
      WDOG reset source currently.
      
      For Sabresd, WDOG1 for ldo-enable mode(WDOG event), WDOG2 for ldo-bypass mode
      (reset external pmic to trigger POR event).
      For sl-evk board, there is no WDOG pin connected with external pmic as Sabresd
      , because mx6sl boot at 400Mhz. Then both ldo-enable and ldo-bypass mode use
      the common WDOG1 as reset source.
      
      ENGR00277895: dts: ARM: imx6: add ldo-enable dts files
      
        Currently, we use different dts files to support ldo-bypass or ldo-enable, then
      we need add both dts files for the boards which can support ldo-bypass mode(all
      boards support ldo-enable at least). So for below boards we need add ldo-enable
      dts file so that we can use this to easily support ldo-enable mode:
        1)mx6q-sabresd board:  ldo-bypass dts->mx6q-sabresd.dtb,
                               ldo-enable dts->mx6q-sabresd-ldo.dtb
        2)mx6q-sabresd board:  ldo-bypass dts->mx6dl-sabresd.dtb,
                       ldo-enable dts->mx6dl-sabresd-ldo.dtb
        3)mx6sl-evk board:     ldo-bypass dts->mx6sl-evk.dtb,
                       ldo-enable dts->mx6sl-evk-ldo.dtb
      
      Change-Id: I38fb55249a002888c9da2c5e298acca089759876
      Signed-off-by: default avatarLauren Post <lauren.post@freescale.com>
      c4940e8b
    • Lauren Post's avatar
      imx6qsabreauto.conf: Add gpmi-weim DTS · 61130550
      Lauren Post authored
      ENGR00269945: ARM: imx6: add the secondary sabreauto dts for pin conflict
      
      The patch is to solve the pin conflicts between devices that are
      currently added in imx6qdl-sabreauto dts file.  It has ecspi1, i2c3, and
      uart3 enabled while gpmi and weim disabled in the primary
      imx6qdl-sabreauto.dtsi, and creates the secondary
      imx6q/dl-sabreauto dts to have gpmi and weim enabled while others
      disabled.  Since usbh1 and usbotg depend on GPIO from max7310 on i2c3,
      they have to be disabled as well in the secondary sabreauto dts files.
      
      Change-Id: I6338e60fa8c1622b2a73e99aa1e3def0a2555bc2
      Signed-off-by: default avatarLauren Post <lauren.post@freescale.com>
      61130550
    • Lauren Post's avatar
      imx6dlsabresd.conf: Add in ldo and hdcp DTS · e6286b97
      Lauren Post authored
      ENGR00274059-02 ARM: Add new dts for imx6q/imx6dl SabreSD hdcp
      
      hdcp ddc pins conflict with i2c2,
      add new dts file for imx6q and imx6dl SabreSD board,
      enable hdcp and disable i2c2 in these dts files.
      Remove hdmi pins property from mx6qdl-sabresd.dtsi.
      
      ENGR00279402-1 ARM: dts: imx6: add wdog reset source seclect in dts
      
      Some boards use another WDOG reset source to reboot system in ldo-bypass mode.
      We need add the property in board dts file so that we can easily know the
      WDOG reset source currently.
      
      For Sabresd, WDOG1 for ldo-enable mode(WDOG event), WDOG2 for ldo-bypass mode
      (reset external pmic to trigger POR event).
      For sl-evk board, there is no WDOG pin connected with external pmic as Sabresd
      , because mx6sl boot at 400Mhz. Then both ldo-enable and ldo-bypass mode use
      the common WDOG1 as reset source.
      
      ENGR00277895: dts: ARM: imx6: add ldo-enable dts files
      
      Currently, we use different dts files to support ldo-bypass or ldo-enable, then
      we need add both dts files for the boards which can support ldo-bypass mode(all
      boards support ldo-enable at least). So for below boards we need add ldo-enable
      dts file so that we can use this to easily support ldo-enable mode:
        1)mx6q-sabresd board:  ldo-bypass dts->mx6q-sabresd.dtb,
                               ldo-enable dts->mx6q-sabresd-ldo.dtb
        2)mx6q-sabresd board:  ldo-bypass dts->mx6dl-sabresd.dtb,
                       ldo-enable dts->mx6dl-sabresd-ldo.dtb
        3)mx6sl-evk board:     ldo-bypass dts->mx6sl-evk.dtb,
                       ldo-enable dts->mx6sl-evk-ldo.dtb
      
      Change-Id: I8a5863d135e5c72419c1eb8f4f34483c2397e567
      Signed-off-by: default avatarLauren Post <lauren.post@freescale.com>
      e6286b97
    • Lauren Post's avatar
      imxdlsabreauto.conf: Add gpmi-weim DTS · 6097d786
      Lauren Post authored
      ENGR00269945: ARM: imx6: add the secondary sabreauto dts for pin conflict
      
      The patch is to solve the pin conflicts between devices that are
      currently added in imx6qdl-sabreauto dts file.  It has ecspi1, i2c3, and
      uart3 enabled while gpmi and weim disabled in the primary
      imx6qdl-sabreauto.dtsi, and creates the secondary
      imx6q/dl-sabreauto dts to have gpmi and weim enabled while others
      disabled.  Since usbh1 and usbotg depend on GPIO from max7310 on i2c3,
      they have to be disabled as well in the secondary sabreauto dts files.
      
      Change-Id: I1f51cda59468140a2552a73fca5d710ecde1967e
      Signed-off-by: default avatarLauren Post <lauren.post@freescale.com>
      6097d786
    • Otavio Salvador's avatar
      fsl-default-providers.inc: Make virtual/kernel assigment delayed · 3f2f08fe
      Otavio Salvador authored
      In 01851da (machine/*: Allow kernel provider override) the assigment
      of preferred provider for virtual/kernel has been changed to a weak
      assignment. This works for most of cases but has caused a regression
      in some machines.
      
      When a machine includes the imx-base.inc file, the assignment is done
      and the intended setting of the machine does not take effect.
      
      For example, in the below code fragment:
      
      ,----[ Wandboard board configuration fragment  ]
      | include conf/machine/include/imx-base.inc
      | ...
      | PREFERRED_PROVIDER_virtual/kernel ?= "linux-wandboard"
      `----
      
      the virtual/kernel provider would be 'linux-imx' as, at the time of
      imx-base.inc inclusion, it was undefined. The expected behaviour would
      be to use 'linux-imx' /only/ when no setting has been done.
      
      The ??= operator solves this as it is used /only/ if no assignment is
      done to the virtual/kernel provider in the end of the parsing. So it
      gives the expected behaviour.
      
      Change-Id: Iab73dcff8bef7f2df1064a0d5d04fd506a4c3144
      Reported-by: default avatarAlfonso Tamés <alfonso@mantic.mx>
      Signed-off-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      3f2f08fe
  2. 04 Nov, 2013 1 commit
  3. 18 Oct, 2013 1 commit
  4. 14 Oct, 2013 1 commit
  5. 08 Oct, 2013 1 commit
  6. 05 Oct, 2013 1 commit
    • Eric BENARD's avatar
      imx-base: provide right package for amd-gpu-bin if x11 is disabled · 00f0cf37
      Eric BENARD authored
      so that users don't have to customize it outside,
      else we get very stranges errors like :
      ERROR: Multiple versions of mesa are due to be built
      (/scratch/openembedded-core/meta/recipes-graphics/mesa/mesa_git.bb
      /scratch/openembedded-core/meta/recipes-graphics/mesa/mesa_9.1.6.bb).
      Only one version of a given PN should be built in any given build.
      You likely need to set PREFERRED_VERSION_mesa to select the correct
      version or don't depend on multiple versions.
      Signed-off-by: default avatarEric Bénard <eric@eukrea.com>
      00f0cf37
  7. 28 Sep, 2013 2 commits
  8. 25 Sep, 2013 10 commits
  9. 29 Aug, 2013 2 commits
  10. 20 Aug, 2013 1 commit
    • Otavio Salvador's avatar
      Rework machines to use dtb file in KERNEL_DEVICETREE variable · 7c869ff2
      Otavio Salvador authored
      The linux-dtb.inc has been reworked to use the Linux kernel build
      system to generate the DeviceTree binaries so now KERNEL_DEVICETREE
      variable should has the /target/ name, not the file path. This patch
      reworks following machines:
      
       - imx23evk
       - imx28evk
       - imx51evk
       - imx53ard
       - imx53qsb
       - imx6dlsabreauto
       - imx6dlsabresd
       - imx6qsabreauto
       - imx6qsabresd
       - imx6solosabreauto
       - imx6solosabresd
      
      Change-Id: I37e9c3737552299677e315b6279a6e0a8e217836
      Signed-off-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      7c869ff2
  11. 15 Aug, 2013 1 commit
  12. 07 Aug, 2013 7 commits
  13. 05 Aug, 2013 1 commit
  14. 31 Jul, 2013 1 commit
    • Otavio Salvador's avatar
      imx-base.inc: Add fsl-alsa-plugins to i.MX6 recommended packages · ab88f0e2
      Otavio Salvador authored
      This ensures the fsl-alsa-plugins is installed per default by images
      but allow it to be manually skipped, using BAD_RECOMMENDATIONS, if need.
      
      This change has been based on a change done in meta-fsl-bsp-release,
      3.5.7 dylan branch, which originally add this in the packagegroup-fsl
      by Jun Zhu <R01007@freescale.com>.
      
      The inclusion of this, inside imx-base.inc, is preferred as it is
      common for all i.MX6 machines and not something specific for demos
      thus should be installed by default.
      
      Change-Id: I209d389b4e0a62b89b4fdede56627e0ec528df87
      Signed-off-by: default avatarOtavio Salvador <otavio@ossystems.com.br>
      ab88f0e2
  15. 29 Jul, 2013 2 commits
  16. 10 Jul, 2013 1 commit