25 Mar, 2014

1 commit


18 Mar, 2014

22 commits


14 Mar, 2014

2 commits


13 Mar, 2014

4 commits


12 Mar, 2014

3 commits


11 Mar, 2014

8 commits

  • Tom Rini
     
  • Tom Rini
     
  • Many USB host controller drivers contain almost identical copies of the
    same virtual root hub descriptors. Put these into a common file to avoid
    duplication.

    Note that there were some very minor differences between the descriptors
    in the various files, such as:

    - USB 1.0 vs. USB 1.1
    - Manufacturer/Device ID
    - Max packet size
    - String content

    I assume these aren't relevant.

    Cc: Thomas Lange
    Cc: Shinya Kuribayashi
    Cc: Gary Jennejohn
    Cc: Wolfgang Denk
    Cc: Eric Millbrandt
    Cc: Pierre Aubert
    Cc: Stefan Roese
    Cc: Daniel Hellstrom
    Cc: Denis Peter
    Cc: Rodolfo Giometti
    Cc: Zhang Wei
    Cc: Mateusz Zalega
    Cc: Remy Bohmer
    Cc: Markus Klotzbuecher
    Cc: Minkyu Kang
    Cc: Gary Jennejohn
    Cc: C Nauman
    Cc: David Müller
    Cc: Yoshihiro Shimoda
    Cc: Nobuhiro Iwamatsu
    Cc: Thomas Abraham
    Cc: Tom Rini
    Cc: Andrew Murray
    Cc: Matej Frančeškin
    Cc: Cliff Cai
    Cc: Bryan Wu
    Signed-off-by: Stephen Warren

    Stephen Warren
     
  • These data structures are passed to cache-flushing routines, and hence
    must be conform to both the USB the cache-flusing alignment requirements.
    That means aligning to USB_DMA_MINALIGN. This is important on systems
    where cache lines are >32 bytes.

    Signed-off-by: Stephen Warren

    Stephen Warren
     
  • Section 4.10.2 "Advance Queue" of ehci-specification-for-usb.pdf
    specifies how an EHCI controller loads a new QTD for processing if the
    QH is not already marked as active. It states:

    =====
    If the field Bytes to Transfer is not zero and the T-bit in the Alternate
    Next qTD Pointer is set to zero, then the host controller uses the
    Alternate Next qTD Pointer. Otherwise, the host controller uses the Next
    qTD Pointer. If Next qTD Pointer’s T-bit is set to a one, then the host
    controller exits this state and uses the horizontal pointer to the next
    schedule data structure.
    =====

    Hence, we must ensure that the alternate next QTD pointer's T-bit
    (TERMINATE) is set, so the EHCI controller knows to use the next QTD
    pointer.

    Signed-off-by: Stephen Warren

    Stephen Warren
     
  • .bmp files contain 32-bit integers aligned at offsets of +2, +6,
    et cetera within the bmp_header structure (see include/bmp_layout.h).

    Support for gzip-compressed .bmp files is present in the cfb_console
    display subsystem by uncompressing them prior to use.

    This patch forces the in-memory header to be aligned properly
    for these compressed images by extracting them to a 2-byte
    offset in the memory returned by malloc. Since malloc will always
    return a 4-byte aligned value, this forces the .bmp header
    fields to be naturally aligned on 4-byte addresses.

    Refer to these files for more details:
    doc/README.displaying-bmps

    Signed-off-by: Eric Nelson

    Eric Nelson
     
  • I have observed timeouts on a cubietruck.

    The increase to 40ms is completely arbitrary and Works For Me(tm). I
    couldn't find a good reference for how long you are supposed to wait,
    although googling around it seems like tens of ms rather than single
    digits is more common. I don't think there is any harm in waiting a bit
    longer.

    Signed-off-by: Ian Campbell

    Ian Campbell
     
  • This allow the platform to register the platform ahci device.

    Signed-off-by: Ian Campbell

    Ian Campbell