u-boot.git/drivers/usb/gadget/f_fastboot.c, branch v2016.05

fastboot: Clean up bulk-out logic

2016-04-25T15:56:30Z

Just use ep->maxpacket to get the maxpacket size and simplify the bulk-out maxpacket alignment. Signed-off-by: Roger Quadros Tested-by: Steve Rae

fastboot: Enable the respective speed endpoints at runtime

2016-04-25T15:56:30Z

In a dual speed configuration we need to check at runtime if we want to enable the Full-Speed or High-Speed endpoint. Signed-off-by: Roger Quadros Acked-by: Lukasz Majewski Tested-by: Steve Rae [Test HW: bcm235xx board]

fastboot: Fix wMaxPacketSize for High-Speed IN endpoint

2016-04-25T15:56:30Z

wMaxPacketSize for IN endpoing in High-Speed must be 512 and not 64. While fixing that we do some clean ups like - use cpu_to_le16(decimal_length) instead of hexadecimal length. - No need to initialize bInterval to 0. Static variables are 0 initialized. - Move descriptor setting from fastboot_add to to fastboot_bind. - check for dual speed configuration before setting the high speed descriptors. Signed-off-by: Roger Quadros Tested-by: Steve Rae Tested-by: Steve Rae [Test HW: bcm235xx board]

fastboot: allow retrieving fastboot variables from env

2016-04-01T21:17:40Z

Some boards need to expose device specific variable through fastboot (to adpat the flashing script depending on hardware revision for example). Provide a way to expose custom fastboot variables. Note that all variables meant to be exposed through fastboot should be be prefixed with 'fastboot.', the variable should not exceed 32 bytes (including the prefix and the trailing '\0') and the variable content should fit in the response buffer (60 bytes excluding the 'OKAY' prefix and the trailing '\0'). Signed-off-by: Rob Herring [Boris Brezillon: add a commit message] Signed-off-by: Boris Brezillon Signed-off-by: Boris Brezillon Acked-by: Steve Rae

fastboot: update error and warning messages

2016-02-24T18:12:33Z

Fix the formatting in error messages, and demote one error message to a warning, as it is only informational. Signed-off-by: Steve Rae

Fix GCC format-security errors and convert sprintfs.

2016-01-15T03:11:34Z

With format-security errors turned on, GCC picks up the use of sprintf with a format parameter not being a string literal. Simple uses of sprintf are also converted to use strcpy. Signed-off-by: Ben Whitten Acked-by: Wolfgang Denk Reviewed-by: Tom Rini

fastboot: Implement NAND backend

2015-11-12T18:18:58Z

So far the fastboot code was only supporting MMC-backed devices for its flashing operations (flash and erase). Add a storage backend for NAND-backed devices. Signed-off-by: Maxime Ripard

fastboot: Implement flashing session counter

2015-11-12T18:17:32Z

The fastboot flash command that writes an image to a partition works in several steps: 1 - Retrieve the maximum size the device can download through the "max-download-size" variable 2 - Retrieve the partition type through the "partition-type:%s" variable, that indicates whether or not the partition needs to be erased (even though the fastboot client has minimal support for that) 3a - If the image is smaller than what the device can handle, send the image and flash it. 3b - If the image is larger than what the device can handle, create a sparse image, and split it in several chunks that would fit. Send the chunk, flash it, repeat until we have no more data to send. However, in the 3b case, the subsequent transfers have no particular identifiers, the protocol just assumes that you would resume the writes where you left it. While doing so works well, it also means that flashing two subsequent images on the same partition (for example because the user made a mistake) would not work withouth flashing another partition or rebooting the board, which is not really intuitive. Since we have always the same pattern, we can however maintain a counter that will be reset every time the client will retrieve max-download-size, and incremented after each buffer will be flashed, that will allow us to tell whether we should simply resume the flashing where we were, or start back at the beginning of the partition. Signed-off-by: Maxime Ripard Reviewed-by: Tom Rini

fastboot: Move fastboot response functions to fastboot core

2015-11-12T18:17:31Z

The functions and a few define to generate a fastboot message to be sent back to the host were so far duplicated among the users. Move them all to a common place. Signed-off-by: Maxime Ripard Reviewed-by: Tom Rini

fastboot: Implement OEM format only when we have MMC support

2015-10-20T20:48:28Z

The current fastboot support assumes that CONFIG_FASTBOOT_FLASH implies that we have an MMC in our system, which might not be the case if we have some other storage device. Change the configuration option protecting that call to FASTBOOT_FLASH_MMC_DEV, that makes much more sense. Signed-off-by: Maxime Ripard Reviewed-by: Tom Rini Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede