21 Jun, 2017

2 commits


20 Jun, 2017

5 commits


12 Jun, 2017

2 commits

  • 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: Ye Li
    Tested-by: Fancy Fang
    (cherry picked from commit 91be2789a93288cc087cd9e8db522c8308ef007c)
    (cherry picked from commit 40fd4ea8d86142a7182d13a99db4f2b4d1b55d35)

    Ye Li
     
  • The OTG ID pin mux setting is missed in DTS, so the OTG can't work
    as host mode.

    Signed-off-by: Ye Li
    Reviewed-by: Peng Fan
    (cherry picked from commit b23324508acf2fcda3531bce17055548758c49f8)

    Ye Li
     

24 May, 2017

2 commits

  • The reset_sata should reset the sata device info and free the probe_ent
    memory. Otherwise, it will cause memory leak if we init the sata again.

    Signed-off-by: Ye Li
    (cherry picked from commit 39c9261fd057b0fa98f9dfdee7d368aa029ff736)

    Ye Li
     
  • When sata stop is executed, the sata_curr_device is not reset to -1, so
    any following sata commands will not initialize the sata again and cause
    problem.

    Additional, in sata init implementation, the sata_curr_device should be updated,
    otherwise sata will be initialized again when doing other sata commands like
    read/write/info/part/device.

    Signed-off-by: Ye Li
    (cherry picked from commit e2a66807f3573e8344dcd285dcb7d53f0e5fcf8e)

    Ye Li
     

22 May, 2017

2 commits

  • Current setup_spi is in board_early_init_f which is too early, so gpio_request
    can't reserve the gpio successfully. Move it to board_init.

    Signed-off-by: Ye Li
    (cherry picked from commit 7c1b220f77313d9df84dbaf0da6ac820e85cba9a)

    Ye Li
     
  • To avoid security leak, check the IVT DCD pointer before authenticating
    the kernel image. If the pointer is not 0, set back it to 0 and give a warning
    like the log below.

    Authenticate image from DDR location 0x80800000...
    Warning, DCD pointer must be 0

    Signed-off-by: Ye Li
    (cherry picked from commit 083daef8d9206d53fb4fa9807f37b8ff5dc319c7)

    Ye Li
     

16 May, 2017

1 commit

  • 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: Ye Li

    Ye Li
     

15 May, 2017

2 commits

  • 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: Ye Li

    Ye Li
     
  • 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: Ye Li

    Ye Li
     

12 May, 2017

2 commits


11 May, 2017

5 commits

  • Using u-boot-2017.05 on i.MX6UL we ran into following problem:
    Initially U-Boot could be started normally.
    If we added one random command in configuration, the newly generated
    image hung at startup (last output was DRAM: 256 MiB).

    We tracked this down to a data abort within relocation (relocated_code).

    relocated_code in arch/arm/lib/relocate.S copies 8 bytes per loop
    iteration until the source pointer is equal to __image_copy_end.
    In a good case __image_copy_end was aligned to 8 bytes, so the loop
    stopped as suggested, but in an errornous case __image_copy_end was
    not aligned to 8 bytes, so the loop ran out of bounds and caused a
    data abort exception.

    This patches solves the issue by aligning __image_copy_end to 8 byte
    using the linker script related to arm.

    From Community: http://patchwork.ozlabs.org/patch/760592/

    Signed-off-by: Peng Fan

    Manfred Schlaegl
     
  • Fix coverity:392391 392382 392385 Unsigned compared against 0

    Signed-off-by: Peng Fan

    Peng Fan
     
  • Add return value check

    Coverity 392391

    Signed-off-by: Peng Fan

    Peng Fan
     
  • The device managed API actually not free the memory, so need
    to use devm_kfree to free the memory to avoid leakage.

    Coverity: 392384 resource leak

    Signed-off-by: Peng Fan

    Peng Fan
     
  • There are two problems in enabling DDR mode in this new driver:
    1. The TDH bits in FLSHCR register should be set to 1. Otherwise, the TX DDR delay logic
    won't be enabled. Since u-boot driver does not have DDR commands in LUT. So this won't
    cause explicit problem.
    2. When doing read/write/readid/erase operations, the MCR register is overwritten, the bits
    like DDR_EN are cleared during these operations. When we using DDR mode QSPI boot, the TDH bit
    is set to 1 by ROM. if the DDR_EN is cleared, there is no clk2x output for TX data shift.
    So these operations will fail.
    The explicit problem is users may get "SF: unrecognized JEDEC id bytes: ff, ff, ff" error
    after using DDR mode QSPI boot on 6UL/ULL EVK boards.

    Signed-off-by: Ye Li

    Ye Li
     

10 May, 2017

2 commits


09 May, 2017

4 commits


08 May, 2017

4 commits


04 May, 2017

1 commit


03 May, 2017

1 commit


29 Apr, 2017

5 commits