1. 23 Jun, 2019 1 commit
  2. 03 Apr, 2019 2 commits
  3. 23 Nov, 2018 1 commit
  4. 23 Jul, 2018 1 commit
  5. 05 Jul, 2018 1 commit
  6. 28 Jun, 2018 1 commit
  7. 19 Jun, 2018 1 commit
  8. 12 Jun, 2018 1 commit
  9. 24 May, 2018 1 commit
  10. 15 Feb, 2018 1 commit
  11. 07 Feb, 2018 1 commit
  12. 05 Feb, 2018 1 commit
  13. 26 Jan, 2018 1 commit
  14. 23 Jan, 2018 2 commits
  15. 15 Jan, 2018 1 commit
  16. 12 Jan, 2018 1 commit
  17. 25 Jul, 2017 1 commit
    • MLK-16069 imx6slevk: Workaround to limit the u-boot in low 512MB memory · 92216844
      Ye Li authored
      On i.MX6SLEVK board, the LPDDR2 chip(CS1) is not reset before accessing.
      And due to MMDC limitation, the script we get from IC team is only doing
      CS0 reset but skipping CS1 reset, the reason is that doing CS1 reset might
      cause CS0 can NOT be accessed any longer.
      Because of this HW issue, we found the high 512MB memory needs more time to
      be stable. Since the u-boot relocates itself to highest address after booting,
      so this will cause issue.
      To work around it, we just limit the u-boot running at low 512MB memory.
      Signed-off-by: 's avatarYe Li <ye.li@nxp.com>
      (cherry picked from commit 5fc93379)
  18. 12 Jul, 2017 1 commit
    • MLK-15341 mx6qpsabresd: add PHY AR8031 hw reset · 721193c1
      Fugang Duan authored
      Currently mx6qpsabresd board file only add PHY AR8031 gpio reset
      in non-DM driver, then net DM driver PHY cannot work after stress
      reboot test. So also add gpio reset for DM driver.
      RGMII and PHY work at VDDIO 1.8V has better timing and to align
      the IO voltage with kernel, also set the IO voltage to 1.8V.
      Since i.MX6QP tx_clk can loop from SOC internal, no need to set
      PHY output 125Mhz clock that can save power.
      Signed-off-by: 's avatarFugang Duan <fugang.duan@nxp.com>
      Reviewed-by: 's avatarYe Li <ye.li@nxp.com>
  19. 10 Jul, 2017 2 commits
    • MA-9409-3 Add base board support for android and android things. · 2c119607
      zhang sanshan authored
      * add board support for android and android things.
        mx6ul_nxpu_iopb, pico-6ul, pico-imx7d, aquila-6ul
        reorganize the Kconfig, and fix the redefine issue.
      * add android configure into configure-while
      * add a common file mx_android_common.h
        it will be included by android and android things.
        defconfig only include ANDROID_THINGS_SUPPORT or ANDROID_SUPPORT
      * move partition_table_valid into f_fastboot.c.
        it's a common code.
      * add invalidate_dcache_range in fixed order.
        It will have salt invalid issue if we do not add it in order
      * add display for pico-7d.
      Change-Id: I6f8a4876c2f8bbd098034d1e3f53033109300bca
      Signed-off-by: 's avatarzhang sanshan <sanshan.zhang@nxp.com>
    • MA-9409-2 fix some issue for android and android things · ff92794f
      zhang sanshan authored
      * Add CONFIG_SYSTEM_RAMDISK_SUPPORT to support system's ramdisk
      * Normal boot: cmdline to bypass ramdisk in boot.img,
        but use Recovery boot: Use the ramdisk in boot.img
      * commandline is larger than 512, system can't bootup sometime for commandline issue.
      * support fastboot getvar.
      * Support "fastboot erase" command for emmc device.
        TODO: uboot community have api to operate flash, we can unify this part
      * support "fastboot flash" even on damaged gpt
      Change-Id: I080c25d6569d6cab56ff025601cd3b8df21cf3dd
  20. 21 Jun, 2017 3 commits
  21. 20 Jun, 2017 2 commits
  22. 12 Jun, 2017 1 commit
    • MLK-14533 mx7ulp_evk: Change APLL and its PFD0 frequencies · db3ece42
      Ye Li authored
      To support HDMI display on EVK board, the LCDIF pix clock must be 25.2Mhz. Since
      the its PCC divider range is from 1-8, the max rate of LCDIF PCC source clock is
      201.6Mhz. This limits the source clock must from NIC1 bus clock or NIC1 clock, other sources
      from APLL PFDs are higher than this max rate.
      The NIC1 bus clock and NIC1 clock are from DDRCLK whose parent source is APLL PFD0, so we must
      change the APLL PFD0 and have impact to DDRCLK, NIC1 and NIC1 bus.
      Eventually, this requests to set the APLL PFD0 frequency to 302.4Mhz (25.2 * 12),
      with settings:
      PFD0 FRAC:  32
      APLL MULT:  22
      APLL NUM:   2
      APLL DENOM: 5
      Signed-off-by: 's avatarYe Li <ye.li@nxp.com>
      Tested-by: 's avatarFancy Fang <chen.fang@nxp.com>
      (cherry picked from commit 91be2789)
      (cherry picked from commit 40fd4ea8)
  23. 22 May, 2017 1 commit
  24. 16 May, 2017 1 commit
    • MLK-14915 mx6ul_arm2/mx6ull_arm2: Fix ENET PHY reset issue · 950b322f
      Ye Li authored
      There are two pins used for ENET PHY reset, need to assert them before init the PHY.
      Current DM driver does not have such operation, need board level codes to handle.
      This patch moves the PHY reset operation into setup_fec, which is common for DM driver
      and non-DM driver.
      Signed-off-by: 's avatarYe Li <ye.li@nxp.com>
  25. 15 May, 2017 2 commits
    • MLK-14890 i2c: Enable I2C force idle bus · 25515dfb
      Ye Li authored
      This patch enables the I2C force idle bus for all i.MX6 and i.MX7 boards to avoid
      i2c bus problem during reboot. To use it, we must add some i2c properties in DTB file
      and the GPIO pinctrl for i2c.
      For mx6qsabreauto, mx6slevk, mx6sxsabresd and mx6sxscm, these boards call the
      setup_i2c. To remove conflict, change to use "setup_i2c" only for non-DM i2c driver.
      Signed-off-by: 's avatarYe Li <ye.li@nxp.com>
    • MLK-14891 mx6slevk/mx6sll_arm2: Fix SPINOR CS GPIO using · 09f2bc9e
      Ye Li authored
      Needs to request the GPIO pin before assigning to GPIO to SPI driver
      which will directly setting it to output without request it.
      Signed-off-by: 's avatarYe Li <ye.li@nxp.com>
  26. 10 May, 2017 1 commit
  27. 09 May, 2017 1 commit
    • MLK-14845 mx6/mx7: Not call usb setup functions used by non-DM driver · 32d4060f
      Ye Li authored
      Use CONFIG_DM_USB to comment out USB setup functions used by non-DM driver. So
      they won't be executed when using DM driver.
      These USB setup functions may setup power control pins to USB_PWR function not GPIO,
      which is different as the GPIO function used by USB vbus-supply. And cause the power control
      not work.
      Signed-off-by: 's avatarYe Li <ye.li@nxp.com>
  28. 08 May, 2017 1 commit
  29. 04 May, 2017 1 commit
  30. 03 May, 2017 1 commit
  31. 28 Apr, 2017 3 commits