public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alberto Panizzo <alberto@amarulasolutions.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/8] Improve rockusb support in U-Boot
Date: Wed,  4 Jul 2018 20:47:21 +0200	[thread overview]
Message-ID: <1530730069-7448-1-git-send-email-alberto@amarulasolutions.com> (raw)

rockusb protocol has been introduced by Eddie Cai in U-Boot mainline
allowing to write internal eMMC of RK3288 based boards (and potentially
all other Rockchip's CPUs).

On workstation side the open source project rkdeveloptool do implement
the rockusb protocol. You can find it on GitHub here:
https://github.com/rockchip-linux/rkdeveloptool

This patchset increase the supported functionalities on target side
allowing developers to:
- Read flash: rl command of rkdeveloptool
- Read chip version: rci command of rkdeveloptool
- Complete the write cycle implementing block erase
- Improve read/write speed

Changes in v2:
- Reworked patch 1/8 to obtain simpler and more logical code
- Rewrote some patch messages
- Updated documentation in README.rockusb  patch by patch
- Added patch 8/8 to fix debug prints of original code

Alberto Panizzo (8):
  usb: rockchip: fix command failed on host side due to missing data
  usb: rockchip: implement skeleton for K_FW_GET_CHIP_VER command
  rockchip: rk3288: implement reading chip version from bootrom code
  usb: rockchip: implement K_FW_LBA_READ_10 command
  usb: rockchip: implement K_FW_LBA_ERASE_10 command
  usb: rockchip: be quiet on serial port while transferring data
  usb: rockchip: boost up write speed from 4MB/s to 15MB/s
  usb: rockchip: fix printing csw debug info

 arch/arm/include/asm/arch-rockchip/f_rockusb.h |   6 +-
 arch/arm/mach-rockchip/rk3288/Makefile         |   1 +
 arch/arm/mach-rockchip/rk3288/rockusb_rk3288.c |  30 ++++
 doc/README.rockusb                             |  11 +-
 drivers/usb/gadget/f_rockusb.c                 | 217 ++++++++++++++++++++++++-
 5 files changed, 255 insertions(+), 10 deletions(-)
 create mode 100644 arch/arm/mach-rockchip/rk3288/rockusb_rk3288.c

-- 
2.7.4

             reply	other threads:[~2018-07-04 18:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04 18:47 Alberto Panizzo [this message]
2018-07-04 18:47 ` [U-Boot] [PATCH v2 1/8] usb: rockchip: fix command failed on host side due to missing data Alberto Panizzo
2018-07-04 18:47 ` [U-Boot] [PATCH v2 2/8] usb: rockchip: implement skeleton for K_FW_GET_CHIP_VER command Alberto Panizzo
2018-07-04 18:47 ` [U-Boot] [PATCH v2 3/8] rockchip: rk3288: implement reading chip version from bootrom code Alberto Panizzo
2018-07-04 18:47 ` [U-Boot] [PATCH v2 4/8] usb: rockchip: implement K_FW_LBA_READ_10 command Alberto Panizzo
2018-07-05 22:18   ` Lukasz Majewski
2018-07-04 18:47 ` [U-Boot] [PATCH v2 5/8] usb: rockchip: implement K_FW_LBA_ERASE_10 command Alberto Panizzo
2018-07-10 20:49   ` Simon Glass
2018-07-04 18:47 ` [U-Boot] [PATCH v2 6/8] usb: rockchip: be quiet on serial port while transferring data Alberto Panizzo
2018-07-04 18:47 ` [U-Boot] [PATCH v2 7/8] usb: rockchip: boost up write speed from 4MB/s to 15MB/s Alberto Panizzo
2018-07-10 20:49   ` Simon Glass
2018-07-04 18:47 ` [U-Boot] [PATCH v2 8/8] usb: rockchip: fix printing csw debug info Alberto Panizzo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1530730069-7448-1-git-send-email-alberto@amarulasolutions.com \
    --to=alberto@amarulasolutions.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox