21 Nov, 2014

1 commit


16 Nov, 2014

2 commits


12 Nov, 2014

1 commit


11 Nov, 2014

2 commits


06 Nov, 2014

1 commit

  • MX6SX sabreauto board has analog video input from VADC. Add the GIS
    support for this board that video input can display on LVDS at booting.

    The environment variable "gis" must be set to "vadc" to enable the function.

    Signed-off-by: Ye.Li
    (cherry picked from commit 5f2008a6dc08f07d462a063a0642f5e54fedbd21)

    Ye.Li
     

24 Oct, 2014

3 commits


23 Oct, 2014

1 commit


22 Oct, 2014

1 commit


20 Oct, 2014

3 commits


11 Oct, 2014

1 commit


09 Oct, 2014

4 commits


08 Oct, 2014

1 commit


30 Sep, 2014

1 commit


29 Sep, 2014

1 commit


26 Sep, 2014

2 commits


25 Sep, 2014

1 commit

  • Currently, flash quad bit is set in "spi_flash_validate_params" and later
    at the end in the same api, we write 0 to status register for few flashes,
    thereby overriding the quad bit set. This fix moves the quad bit setting
    outside this api in "spi_flash_probe_slave"

    Signed-off-by: Sourav Poddar
    Reviewed-by: Jagannadha Sutradharudu Teki

    Poddar, Sourav
     

23 Sep, 2014

1 commit


18 Sep, 2014

6 commits


11 Sep, 2014

1 commit


10 Sep, 2014

1 commit


05 Sep, 2014

2 commits

  • This problem is found when debugging QuadSPI. When "A" bit is enabled,
    unaligned access will cause data abort exception. Actually, we do not
    want this exception. So clear the align bit for MX6 SOCs.

    Tested this code with android team colleague and did not find problem.

    Signed-off-by: Peng Fan

    Peng Fan
     
  • To fsl_qspi_write_data and fsl_qspi_ip_read, pointer txbuf and
    rxbuf are not guaranteed that they are 4 Bytes aligned. Also,
    it it not a good idea to cast type 'u8 *' to 'u32 *', except
    we are sure that pointer type 'u8 *' is 4 Bytes aligned and
    cast it to 'u32 *' will not pass memory boundary.

    The problem is found when using fsl_qspi_write_data to write
    registers in flash devices. The err msg:

    data abort
    pc : [] lr : []
    sp : bf5512c8 ip : 0000001c fp : bf856608
    r10: 87868904 r9 : bf551efc r8 : 200f048c
    r7 : 00000002 r6 : bf551336 r5 : bf552a70 r4 : 00000001
    r3 : 00000000 r2 : 00000060 r1 : 8783b520 r0 : 8783b520
    Flags: nZCv IRQs on FIQs off Mode SVC_32
    Resetting CPU ...

    The asm code which cause data abort is:
    87822f30: e5964000 ldr r4, [r6]
    From the dump msg, r6 is not 4 Bytes aligned, and data abort exception.

    So, Use mempcy but not unsafe type casting.

    In this patch, max_write_size is assigned using txfifo to avoid possible
    errors in future.

    Signed-off-by: Peng Fan

    Peng Fan
     

04 Sep, 2014

1 commit


02 Sep, 2014

1 commit


30 Aug, 2014

1 commit

  • The QSPI clock rate was set without disabling the clock gate, the
    randomly glitch may mess up the clock and there will be no clock output,
    when kernel boot up the QSPI access will fail.

    To debug this issueon i.MX6SX SDB, changed the u-boot bootscript to 'sf probe; reset'
    to keep rebooting, the issue can be reproduced in 20 mins, set clock out
    register in CCM and measured TP86, found there is no clock ouput.

    To fix this bug, disable clock gate before changing clock rate.
    NOTICE: QSPI2 and GPMI_BCH_INPUT_GPMI_IO share the same clock gate, need
    to disable both of them.

    Signed-off-by: Allen Xu

    Allen Xu