03 Oct, 2013

1 commit


02 Oct, 2013

6 commits


27 Sep, 2013

7 commits


24 Sep, 2013

24 commits

  • When unbind the gadget driver, need call disconnect first.

    Signed-off-by: Bo Shen

    Bo Shen
     
  • The download gadget code and DFU function lacks of proper declarations
    for the case when a target board wants to use only one of available usb
    functions.

    Moreover the relevant declarations have been moved to consistent
    localization (like ).

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

    Lukasz Majewski
     
  • Only the requires error.h include. Hence, several
    includes of error.h at USB gadget functions are not needed.

    Moreover unnecessary malloc.h includes were also removed.

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

    Lukasz Majewski
     
  • The mass storage composite function is now compiled in only when
    CONFIG_USB_GADGET_MASS_STORAGE is defined.
    Such change provides binary size reduction for boards which use USB
    download gadget (like am335x_evm) with DFU, but don't use UMS.

    For example at am335x_evm board reduction is more than 2KiB for
    text and around 120B for data.

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

    Lukasz Majewski
     
  • Enable DFU for RAM, provide example dfu_alt_info

    Signed-off-by: Afzal Mohammed
    Cc: Heiko Schocher
    Cc: Tom Rini
    Cc: Marek Vasut
    Cc: Lukasz Majewski
    Cc: Pantelis Antoniou
    Reviewed-by: Lukasz Majewski

    Afzal Mohammed
     
  • DFU spec mentions it as a method to upgrade firmware (software stored
    in writable non-volatile memory). It also says other potential uses of
    DFU is beyond scope of the spec.

    Here such a beyond the scope use is being attempted - directly pumping
    binary images from host via USB to RAM. This facility is a developer
    centric one in that it gives advantage over upgrading non-volatile
    memory for testing new images every time during development and/or
    testing.

    Directly putting image onto RAM would speed up upgrade process. This and
    convenience was the initial thoughts that led to doing this, speed
    improvement over MMC was only 1 second though - 6 sec on RAM as opposed
    to 7 sec on MMC in beagle bone, perhaps enabling cache and/or optimizing
    DFU framework to avoid multiple copy for ram (if worth) may help, and
    on other platforms and other boot media like NAND maybe improvement
    would be higher.

    And for a platform that doesn't yet have proper DFU suppport for
    non-volatile media's, DFU to RAM can be used.

    Another minor advantage would be to increase life of mmc/nand as it
    would be less used during development/testing.

    usage: ram
    eg. kernel ram 0x81000000 0x1000000

    Downloading images to RAM using DFU is not something new, this is
    acheived in openmoko also.

    DFU on RAM can be used for extracting RAM contents to host using dfu
    upload. Perhaps this can be extended to io for squeezing out register
    dump through usb, if it is worth.

    Signed-off-by: Afzal Mohammed
    Cc: Heiko Schocher
    Cc: Marek Vasut
    Cc: Lukasz Majewski
    Cc: Pantelis Antoniou
    Cc: Gerhard Sittig
    Acked-by: Marek Vasut
    Acked-by: Lukasz Majewski
    Acked-by: Heiko Schocher

    Afzal Mohammed
     
  • MMC and NAND independently defines same enumerators for read/write.
    Unify them by defining enum in dfu header. RAM support that is being
    added newly also can make use of it.

    Signed-off-by: Afzal Mohammed
    Cc: Heiko Schocher
    Cc: Marek Vasut
    Cc: Lukasz Majewski
    Cc: Pantelis Antoniou
    Acked-by: Lukasz Majewski
    Acked-by: Marek Vasut
    Acked-by: Heiko Schocher

    Afzal Mohammed
     
  • New dfu_init_env_entities() function has been extracted from cmd_dfu.c and
    stored at dfu core.

    This is a dfu centric code, so it shall be processed in the core.

    Change-Id: I756c5de922fa31399d8804eaadc004ee98844ec2
    Signed-off-by: Lukasz Majewski
    Tested-by: Heiko Schocher

    Lukasz Majewski
     
  • Add RNDIS gadget support to test atmel usba udc driver

    Signed-off-by: Bo Shen

    Bo Shen
     
  • Correct the UDPHS name from UDHPS

    Signed-off-by: Bo Shen
    Acked-by: Marek Vasut

    Bo Shen
     
  • Add atmel usba udc driver support, porting from Linux kernel

    The original code in Linux Kernel information is as following

    commit e01ee9f509a927158f670408b41127d4166db1c7
    Author: Jingoo Han
    Date: Tue Jul 30 17:00:51 2013 +0900

    usb: gadget: use dev_get_platdata()

    Use the wrapper function for retrieving the platform data instead of
    accessing dev->platform_data directly.

    Signed-off-by: Bo Shen

    Bo Shen
     
  • As seen with codesourcery compiler 2010q1, the buf pointer in
    usb_request structure is not aligned on 4 bytes boundary causing
    data aborts in eth_setup -> conf_buf -> usb_gadget_config_buf.
    Make it as align access to fix this issue.

    Signed-off-by: Troy Kisky
    [voice.shen@atmel.com: add commit message]
    Signed-off-by: Bo Shen

    Troy Kisky
     
  • Up till now the DFU maximum file size (to be written to e.g. eMMC)
    was different from the DFU data buffer size. It caused errors when
    one buffer was smaller than data to be written.

    Now, the maximum DFU file size is equal to default DFU buffer size.
    In spite of this, user is still able to manually adjust those default
    values.

    Change-Id: Ied75d0f7b59588ebd79dae9a22af801d36622216
    Signed-off-by: Lukasz Majewski

    Lukasz Majewski
     
  • Correct error message if overflow is detected.

    Change-Id: I8a915c7353d49822c046fbc36241237b370e6c98
    Signed-off-by: Lukasz Majewski

    Lukasz Majewski
     
  • As seen on GCC 4.6 Linaro compiler, control_req buffer is not aligned
    on 4 byte boundaray causing data aborts in eth_setup -> conf_buf
    during dhcp boot over usb_ether. Fix the issue my aligning control_req
    buffer using DEFINE_CACHE_ALIGN_BUFFER.

    Tested on am335x_evm platform (beaglebone).
    Applies on 2013.10-rc1 branch.

    Cc: Tom Rini
    Cc: Marek Vasut
    Signed-off-by: Joel Fernandes

    Joel Fernandes
     
  • This patch modifies the MAX98095 audio codec to support
    I2S0 channel in codec slave mode.

    Signed-off-by: Dani Krishna Mohan

    Dani Krishna Mohan
     
  • This patch makes required changes to make use
    of I2S0 channel instead of I2S1 channel on exynos5250.

    Signed-off-by: Dani Krishna Mohan

    Dani Krishna Mohan
     
  • This patch makes the necessary changes for making use of
    I2S0 channel instead of I2S1 channel on smdk board. This
    changes are done to maintain the uniformity to use I2S0 channel.

    Signed-off-by: Dani Krishna Mohan

    Dani Krishna Mohan
     
  • This patch enables default I2S0 channel.And I2S platform
    parameter has been moved to a common file viz exynos5.dtsi.

    Signed-off-by: Dani Krishna Mohan

    Dani Krishna Mohan
     
  • This patch modifies the WM8994 codec to support I2S0 channel
    in codec slave mode

    Signed-off-by: Dani Krishna Mohan

    Dani Krishna Mohan
     
  • When we call do_bootm() with a vmlinuz, this would lead to a NULL
    pointer dereference, and after talking with Wolfgang the right thing to
    do here for now is to make sure that we pass cmdtp to these functions
    rather than NULL.

    Reported-by: Steven A. Falco
    Signed-off-by: Tom Rini

    Tom Rini
     
  • In 5c427e4 we pass BOOTM_STATE_OS_CMDLINE as part of the bootm states to
    run, on all arches. However, this is only valid / useful on PowerPC and
    MIPS, and causes a problem on ARM where we specifically do not use it.
    Rather than make this state fake pass like we do for GO on some arches
    (which need updating to use the GO state), we should just not pass
    CMDLINE except when it may be used, like before.

    Tested-by: Dan Murphy
    Signed-off-by: Tom Rini

    Tom Rini
     
  • Besides the change of this patchset it also updates the
    README to reflect that GOT-generated relocations are no
    longer supported on ARM.

    cc: Albert ARIBAUD
    Signed-off-by: Jeroen Hofstee

    Jeroen Hofstee
     
  • To be more EABI compliant and as a preparation for building
    with clang, use the platform-specific r9 register for gd
    instead of r8.

    note: The FIQ is not updated since it is not used in u-boot,
    and under discussion for the time being.

    The following checkpatch warning is ignored:
    WARNING: Use of volatile is usually wrong: see
    Documentation/volatile-considered-harmful.txt

    Signed-off-by: Jeroen Hofstee
    cc: Albert ARIBAUD

    Jeroen Hofstee
     

23 Sep, 2013

2 commits