From: Eddie Cai <eddie.cai.linux@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V9 0/4] introduce Rockchip rockusb
Date: Mon, 28 Aug 2017 15:45:56 +0800 [thread overview]
Message-ID: <1503906360-13043-1-git-send-email-eddie.cai.linux@gmail.com> (raw)
Changes in v9:
-rebase to the latest mainline
-fix compile error
Changes in v8:
-rebase to v2017.09-rc2
-fix compile error
Changes in v7:
-use imply in the Kconfig to enable rockusb
Changes in v6:
-enable rockusb in defconfig
-move some data to f_rockusb structure
Changes in v5:
-fix build error when build other board
-fix checkpatch error
Changes in v4:
-use enum instead of macro define
-move some structure define and macro to f_rockusb.h
-add some function comment as Simon required
-address other comment from Simon
-fix build error as Lukasz point out
Changes in v3:
-switch back to use g_dnl code
-address comment from Lukasz and Simon
-fix checkpatch error
Changes in v2:
-switch to use usb masstorage framework
-add readme for rockusb
Eddie Cai (4):
usb: rockchip: add the rockusb gadget
usb: rockchip: add rockusb command
rockchip:usb: add a simple readme for rockusb
rockchip: rk3288: enable rockusb support on rk3288 based device
arch/arm/include/asm/arch-rockchip/f_rockusb.h | 132 +++++
arch/arm/mach-rockchip/Kconfig | 2 +
cmd/Kconfig | 9 +
cmd/Makefile | 1 +
cmd/rockusb.c | 74 +++
configs/chromebit_mickey_defconfig | 9 +
configs/chromebook_jerry_defconfig | 9 +
configs/chromebook_minnie_defconfig | 9 +
configs/evb-rk3288_defconfig | 10 +
configs/fennec-rk3288_defconfig | 6 +
configs/firefly-rk3288_defconfig | 6 +
configs/miqi-rk3288_defconfig | 6 +
configs/phycore-rk3288_defconfig | 7 +
configs/popmetal-rk3288_defconfig | 6 +
configs/rock2_defconfig | 10 +
configs/tinker-rk3288_defconfig | 6 +
doc/README.rockusb | 51 ++
drivers/usb/gadget/Kconfig | 8 +
drivers/usb/gadget/Makefile | 1 +
drivers/usb/gadget/f_rockusb.c | 691 +++++++++++++++++++++++++
include/configs/rk3288_common.h | 7 -
21 files changed, 1053 insertions(+), 7 deletions(-)
create mode 100644 arch/arm/include/asm/arch-rockchip/f_rockusb.h
create mode 100644 cmd/rockusb.c
create mode 100644 doc/README.rockusb
create mode 100644 drivers/usb/gadget/f_rockusb.c
--
1.9.1
next reply other threads:[~2017-08-28 7:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 7:45 Eddie Cai [this message]
2017-08-28 7:45 ` [U-Boot] [PATCH V9 1/4] usb: rockchip: add the rockusb gadget Eddie Cai
2017-09-11 20:27 ` [U-Boot] [U-Boot,V9,1/4] " Philipp Tomsich
2017-09-12 8:14 ` Łukasz Majewski
2017-09-12 8:23 ` Dr. Philipp Tomsich
2017-09-12 8:43 ` Łukasz Majewski
2017-10-02 10:40 ` Dr. Philipp Tomsich
2017-10-02 10:41 ` Marek Vasut
2017-10-02 10:51 ` Dr. Philipp Tomsich
2017-11-20 15:54 ` Dr. Philipp Tomsich
2017-11-21 0:30 ` Eddie Cai
2017-11-21 9:34 ` Lukasz Majewski
2017-09-12 8:37 ` Philipp Tomsich
2017-08-28 7:45 ` [U-Boot] [PATCH V9 2/4] usb: rockchip: add rockusb command Eddie Cai
2017-09-11 20:27 ` [U-Boot] [U-Boot,V9,2/4] " Philipp Tomsich
2017-08-28 7:45 ` [U-Boot] [PATCH V9 3/4] rockchip:usb: add a simple readme for rockusb Eddie Cai
2017-09-11 20:27 ` [U-Boot] [U-Boot, V9, " Philipp Tomsich
2017-08-28 7:46 ` [U-Boot] [PATCH V9 4/4] rockchip: rk3288: enable rockusb support on rk3288 based device Eddie Cai
2017-09-11 20:27 ` [U-Boot] [U-Boot, V9, " Philipp Tomsich
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=1503906360-13043-1-git-send-email-eddie.cai.linux@gmail.com \
--to=eddie.cai.linux@gmail.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