01 Nov, 2015

3 commits


26 Oct, 2015

2 commits


13 Aug, 2015

2 commits


06 Aug, 2015

1 commit


05 Aug, 2015

1 commit


04 Aug, 2015

1 commit


29 Apr, 2015

1 commit

  • For android without shell environment, do suspend/resume test, uart port has
    no output message.

    In common code, cons->cflag is cleared to zero in .uart_port_startup(), but
    after resume back, use the cons->cflag to set termios.
    ......................
    uart_resume_port()->
    termios.c_cflga = uport->cons->cflag;
    ...
    uport->ops->set_termios(uport, &termios, NULL);

    uart_port_startup->
    uport->cons->cflag = 0;
    ......................

    So the patch save the console cflag.

    Signed-off-by: Fugang Duan

    guoyin.chen
     

27 Apr, 2015

1 commit


23 Apr, 2015

1 commit

  • SB: gadget: mtp: Fix hang in ioctl(MTP_RECEIVE_FILE) for
    WritePartialObject

    In receive_file_work, we now queue reads with length rounded up to
    max packet size rather than mtp_rx_req_len.
    Otherwise the read request will never complete.

    Bug: 12195339

    Cherry-picked from 0373636d110d37aedfc5d71ea56af61f6bb3b65e
    Mike Lockwood

    Signed-off-by: Haoran Wang

    Haoran Wang
     

17 Apr, 2015

2 commits

  • In megafix power off, the driver save necessary registers in suspend, and resotre the
    registers in resume, but access registers need ipg clock gate on, so the patch make sure
    ipg clock gate is on before save/restore the uart registers.

    Signed-off-by: Fugang Duan
    (cherry picked and merge from commit 1c3f8b2e199b8aadedf87b55c585c697bae3033f)

    Fugang Duan
     
  • When uart port (non-console port) in dma mode and use uart as remote wakeup
    source, after resume back, the AWAKE bit is not cleared most of interrupts
    are disabled. And then let system suspend state, system resume back immediately
    without any wake up action. So we need to clear the AWAKE bit after resume
    back in DMA mode.

    Signed-off-by: Fugang Duan
    (cherry picked from commit 940e204f8dc4f620a1b6b90f3ccd2d22da1e4beb)

    Fugang Duan
     

06 Apr, 2015

1 commit


05 Apr, 2015

1 commit


04 Apr, 2015

1 commit

  • Apply errata based on PL310 version instead of compile
    time. Also set Prefetch offset to 15, since it improves
    memcpy performance by 35%. Don't enable Incr double
    Linefill enable since it adversely affects memcpy
    performance by about 32MB/s and reads by 90MB/s. Tested
    with 4K to 16MB sized src and dst aligned buffer.

    Signed-off-by: Nitin Garg

    Nitin Garg
     

03 Apr, 2015

3 commits


18 Mar, 2015

1 commit

  • The class android.permission.cts.FileSystemPermissionTest in cts will check whether
    /sys/class/xt_idletimer exits. This patch enable xt_idletimer.
    Idletimer Xtables target is used to identify when interfaces have been idle for a certain period of time.
    It main be used in netfilter.

    Signed-off-by: Zhang Sanshan

    Zhang Sanshan
     

17 Mar, 2015

1 commit


16 Mar, 2015

1 commit


07 Mar, 2015

1 commit


04 Mar, 2015

1 commit


02 Mar, 2015

1 commit


27 Feb, 2015

6 commits


26 Feb, 2015

1 commit


24 Feb, 2015

1 commit


19 Feb, 2015

2 commits


11 Feb, 2015

1 commit


06 Feb, 2015

2 commits

  • Conflicts:
    arch/arm/boot/dts/imx6sx-sdb.dts
    arch/arm/mach-imx/clk-imx6sx.c

    guoyin.chen
     
  • We've got a race condition bewteen the interrupt handler mxsfb_irq_handler()
    and the function mxsfb_wait_for_vsync() on the flag host->wait4vsync.
    If a CUR_FRAME_DONE interrupt comes and we just finish setting host->wait4vsync
    to be 1 in mxsfb_wait_for_vsync() before we go to the interrupt handler, we are
    likely to see the VSYNC_EDGE interrupt status bit asserted in the interrupt
    handler for the CUR_FRAME_DONE interrupt, disable the not yet enabled VSYNC_EDGE
    interrupt and finally clear host->wait4vsync.
    Then, we go back to mxsfb_wait_for_vsync() and enable the VSYNC_EDGE interrupt
    with host->wait4vsync=0. This may leave the VSYNC_EDGE interrupt enabled all
    the time and never get a chance to be disabled in the interrupt handler.
    So, we are deemed to hang up because the uncleared VSYNC_EDGE interrupt status
    bit will cause the CPU to be trapped forever, according to SoC designer's words.
    This patch corrects the interrupt handling to handle only the interrupts which
    are acknowledged by checking both the interrupt enablement bits and the status
    bits but not the status bits only. This may avoid any bogus interrupt from
    being handled.

    Signed-off-by: Liu Ying
    (cherry picked from commit 24e1e55076b624f9dc93c1f23e14dd024bdff1c7)

    Liu Ying