02 Sep, 2014

2 commits


06 Feb, 2014

1 commit

  • The Samsung's UDC driver is not anymore copying data from USB requests to
    aligned internal buffers. Now it works directly in data allocated in the
    upper layers like UMS, DFU, THOR.

    This change is possible since those gadgets now must take care to allocate
    buffers aligned to cache line (CONFIG_SYS_CACHELINE_SIZE).

    This can be achieved by using DEFINE_CACHE_ALIGN_BUFFER() or
    ALLOC_CACHE_ALIGN_BUFFER() macros. Those take care to allocate buffer
    aligned to cache line in both starting address and its size.
    Sometimes it is enough to just use memalign() with size being a
    multiplication of cache line size.

    Test condition
    - test HW + measurement: Trats - Exynos4210 rev.1
    - test HW Trats2 - Exynos4412 rev.1
    400 MiB compressed rootfs image download with `thor 0 mmc 0`

    Measurement:
    Transmission speed: 27.04 MiB/s

    Signed-off-by: Lukasz Majewski
    Cc: Marek Vasut

    Lukasz Majewski
     

02 Dec, 2013

1 commit


24 Jul, 2013

1 commit


20 Nov, 2012

1 commit


20 May, 2012

3 commits


30 Apr, 2012

1 commit

  • Merge our duplicate definitions with the common header.

    Also fix drivers/usb/gadget/s3c_udc_otg_xfer_dma.c to
    use min() instead of min_t() since we remove the latter
    from compat.h.

    Additionally use memalign() directly as the lin_gadget
    specific kmalloc() macro is removed from lin_gadget_compat.h
    by this patch.

    Signed-off-by: Mike Frysinger
    Signed-off-by: Anatolij Gustschin
    Cc: Lukasz Majewski

    Mike Frysinger
     

21 Dec, 2011

1 commit

  • Fix:
    In file included from s3c_udc_otg.c:216:0:
    s3c_udc_otg_xfer_dma.c: In function 'complete_tx':
    s3c_udc_otg_xfer_dma.c:280:33: warning: variable 'is_short' set but not used
    s3c_udc_otg_xfer_dma.c:280:6: warning: variable 'ep_tsr' set but not used
    s3c_udc_otg_xfer_dma.c: In function 's3c_udc_irq':
    s3c_udc_otg_xfer_dma.c:469:16: warning: variable 'flags' set but not used
    s3c_udc_otg_xfer_dma.c:468:18: warning: variable 'gintmsk' set but not used
    s3c_udc_otg_xfer_dma.c: In function 's3c_queue':
    s3c_udc_otg_xfer_dma.c:582:14: warning: variable 'gintsts' set but not used
    s3c_udc_otg_xfer_dma.c:581:16: warning: variable 'flags' set but not used
    s3c_udc_otg_xfer_dma.c: In function 's3c_ep0_read':
    s3c_udc_otg_xfer_dma.c:778:6: warning: variable 'ret' set but not used
    s3c_udc_otg_xfer_dma.c: In function 's3c_udc_set_halt':
    s3c_udc_otg_xfer_dma.c:1020:16: warning: variable 'flags' set but not used
    s3c_udc_otg_xfer_dma.c: In function 's3c_ep0_setup':
    s3c_udc_otg_xfer_dma.c:1258:13: warning: initialization from incompatible
    pointer type [enabled by default]
    s3c_udc_otg_xfer_dma.c:1239:16: warning: variable 'is_in' set but not used
    s3c_udc_otg_xfer_dma.c:1239:9: warning: variable 'bytes' set but not used
    s3c_udc_otg.c: In function 'usb_gadget_register_driver':
    s3c_udc_otg.c:292:16: warning: variable 'flags' set but not used
    s3c_udc_otg.c: In function 'usb_gadget_unregister_driver':
    s3c_udc_otg.c:338:16: warning: variable 'flags' set but not used
    s3c_udc_otg.c: In function 's3c_ep_enable':
    s3c_udc_otg.c:582:16: warning: variable 'flags' set but not used
    s3c_udc_otg.c: In function 's3c_ep_disable':
    s3c_udc_otg.c:646:16: warning: variable 'flags' set but not used
    s3c_udc_otg.c: In function 's3c_dequeue':
    s3c_udc_otg.c:704:16: warning: variable 'flags' set but not used

    Signed-off-by: Anatolij Gustschin
    Cc: Lukasz Majewski
    Cc: Remy Bohmer

    Anatolij Gustschin
     

17 Dec, 2011

1 commit

  • In 9792987721c7980453fe6447c3fa6593b44f8458 Stefan describes a usecase
    where the previous behavior of leaving wMaxPacketSize be unaligned
    caused fatal problems. The initial fix for this problem was incomplete
    however as it showed another cases of non-aligned access that previously
    worked implicitly. This switches to making sure that all access of
    wMaxPacketSize are done via (get|put)_unaligned.

    In order to maintain a level of readability to the code in some cases
    we now use a variable for the value of wMaxPacketSize and in others, a
    macro.

    Cc: Minkyu Kang
    Cc: Remy Bohmer

    OpenRISC:
    Tested-by: Stefan Kristiansson

    Beagleboard xM, Pandaboard run-tested, s5p_goni build-tested.
    Signed-off-by: Tom Rini

    Tom Rini
     

11 Dec, 2011

1 commit