From: Kever Yang <kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
To: Jagan Teki
<jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>,
Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Philipp Tomsich
<philipp.tomsich-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org>
Cc: u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org,
"Matwey V . Kornilov"
<matwey.kornilov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-amarula-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org,
Akash Gajjar <akash-oRp2ZoJdM/RWk0Htik3J/w@public.gmane.org>,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v6 6/6] doc: boards: Add rockchip documentation
Date: Tue, 7 Jan 2020 16:40:35 +0800 [thread overview]
Message-ID: <a2caeaa9-cfcc-539f-3999-b93ea02b9089@rock-chips.com> (raw)
In-Reply-To: <20200104083806.3930-7-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
On 2020/1/4 下午4:38, Jagan Teki wrote:
> Rockchip has documentation file, doc/README.rockchip but
> which is not so readable to add or understand the existing
> contents. Even the format that support is legacy readme
> in U-Boot.
>
> Add rockchip specific documentation file using new rst
> format, which describes the information about Rockchip
> supported boards and it's usage steps.
>
> Added minimal information about rk3288, rk3328, rk3368
> and rk3399 boards and usage. This would indeed updated
> further based on the requirements and updates.
>
> Cc: Kever Yang <kever.yang@rock-chips.com>
> Cc: Matwey V. Kornilov <matwey.kornilov@gmail.com>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
Thanks,
- Kever
> ---
> doc/board/rockchip/index.rst | 10 +++
> doc/board/rockchip/rockchip.rst | 130 ++++++++++++++++++++++++++++++++
> 2 files changed, 140 insertions(+)
> create mode 100644 doc/board/rockchip/index.rst
> create mode 100644 doc/board/rockchip/rockchip.rst
>
> diff --git a/doc/board/rockchip/index.rst b/doc/board/rockchip/index.rst
> new file mode 100644
> index 0000000000..0c377e9bbb
> --- /dev/null
> +++ b/doc/board/rockchip/index.rst
> @@ -0,0 +1,10 @@
> +.. SPDX-License-Identifier: GPL-2.0+
> +.. Copyright (C) 2019 Jagan Teki <jagan@amarulasolutions.com>
> +
> +Rockchip
> +========
> +
> +.. toctree::
> + :maxdepth: 2
> +
> + rockchip
> diff --git a/doc/board/rockchip/rockchip.rst b/doc/board/rockchip/rockchip.rst
> new file mode 100644
> index 0000000000..6c34f1ab99
> --- /dev/null
> +++ b/doc/board/rockchip/rockchip.rst
> @@ -0,0 +1,130 @@
> +.. SPDX-License-Identifier: GPL-2.0+
> +.. Copyright (C) 2019 Jagan Teki <jagan@amarulasolutions.com>
> +
> +ROCKCHIP
> +========
> +
> +About this
> +----------
> +
> +This document describes the information about Rockchip supported boards
> +and it's usage steps.
> +
> +Rockchip boards
> +---------------
> +
> +Rockchip is SoC solutions provider for tablets & PCs, streaming media
> +TV boxes, AI audio & vision, IoT hardware.
> +
> +A wide range of Rockchip SoCs with associated boardsare supported in
> +mainline U-Boot.
> +
> +List of mainline supported rockchip boards:
> +
> +* rk3288
> + - Evb-RK3288
> + - Firefly-RK3288
> + - mqmaker MiQi
> + - Phytec RK3288 PCM-947
> + - PopMetal-RK3288
> + - Radxa Rock 2 Square
> + - Tinker-RK3288
> + - Google Jerry
> + - Google Mickey
> + - Google Minnie
> + - Google Speedy
> + - Amarula Vyasa-RK3288
> +* rk3328
> + - Rockchip RK3328 EVB
> + - Pine64 Rock64
> +* rk3368
> + - GeekBox
> + - PX5 EVB
> + - Rockchip sheep board
> + - Theobroma Systems RK3368-uQ7 SoM
> +* rk3399
> + - 96boards RK3399 Ficus
> + - 96boards Rock960
> + - Firefly-RK3399 Board
> + - Firefly ROC-RK3399-PC Board
> + - FriendlyElec NanoPC-T4
> + - FriendlyElec NanoPi M4
> + - FriendlyARM NanoPi NEO4
> + - Google Bob
> + - Khadas Edge
> + - Khadas Edge-Captain
> + - Khadas Edge-V
> + - Orange Pi RK3399 Board
> + - Pine64 RockPro64
> + - Radxa ROCK Pi 4
> + - Rockchip RK3399 Evaluation Board
> + - Theobroma Systems RK3399-Q7 SoM
> +
> +Building
> +--------
> +
> +TF-A
> +^^^^
> +
> +TF-A would require to build for ARM64 Rockchip SoCs platforms.
> +
> +To build TF-A::
> +
> + git clone https://github.com/ARM-software/arm-trusted-firmware.git
> + cd arm-trusted-firmware
> + make realclean
> + make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399
> +
> +Specify the PLAT= with desired rockchip platform to build TF-A for.
> +
> +U-Boot
> +^^^^^^
> +
> +To build rk3328 boards::
> +
> + export BL31=/path/to/arm-trusted-firmware/to/bl31.elf
> + make evb-rk3328_defconfig
> + make
> +
> +To build rk3288 boards::
> +
> + make evb-rk3288_defconfig
> + make
> +
> +To build rk3368 boards::
> +
> + export BL31=/path/to/arm-trusted-firmware/to/bl31.elf
> + make evb-px5_defconfig
> + make
> +
> +To build rk3399 boards::
> +
> + export BL31=/path/to/arm-trusted-firmware/to/bl31.elf
> + make evb-rk3399_defconfig
> + make
> +
> +Flashing
> +--------
> +
> +SD Card
> +^^^^^^^
> +
> +All rockchip platforms, except rk3128 (which doesn't use SPL) are now
> +supporting single boot image using binman and pad_cat.
> +
> +To write an image that boots from an SD card (assumed to be /dev/sda)::
> +
> + sudo dd if=u-boot-rockchip.bin of=/dev/sda seek=64
> + sync
> +
> +TODO
> +----
> +
> +- Add rockchip idbloader image building
> +- Add rockchip TPL image building
> +- Document SPI flash boot
> +- Describe steps for eMMC flashing
> +- Add missing SoC's with it boards list
> +
> +.. Jagan Teki <jagan@amarulasolutions.com>
> +.. Sat Jan 4 14:00:54 IST 2020
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2020-01-07 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 8:38 [PATCH v6 0/6] rockchip: Add Binman support Jagan Teki
[not found] ` <20200104083806.3930-1-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2020-01-04 8:38 ` [PATCH v6 1/6] Makefile: Add rockchip image type Jagan Teki
2020-01-04 8:38 ` [PATCH v6 2/6] Makefile: rockchip: Suffix platform type with tpl name Jagan Teki
2020-01-04 8:38 ` [PATCH v6 3/6] Makefile: rockchip: Support SPL-alone mkimage Jagan Teki
2020-01-04 8:38 ` [PATCH v6 4/6] arm: dts: rk3036: Add rk3036-u-boot.dtsi Jagan Teki
2020-01-04 8:38 ` [PATCH v6 5/6] rockchip: Add Single boot image (with binman, pad_cat) Jagan Teki
[not found] ` <20200104083806.3930-6-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2020-01-10 9:39 ` Simon Glass
2020-01-10 9:42 ` Matwey V. Kornilov
2020-01-30 2:17 ` Simon Glass
2020-01-04 8:38 ` [PATCH v6 6/6] doc: boards: Add rockchip documentation Jagan Teki
[not found] ` <20200104083806.3930-7-jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2020-01-07 8:40 ` Kever Yang [this message]
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=a2caeaa9-cfcc-539f-3999-b93ea02b9089@rock-chips.com \
--to=kever.yang-tnx95d0mmh7dzftrwevzcw@public.gmane.org \
--cc=akash-oRp2ZoJdM/RWk0Htik3J/w@public.gmane.org \
--cc=jagan-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org \
--cc=linux-amarula-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=matwey.kornilov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=philipp.tomsich-SN7IsUiht6C/RdPyistoZJqQE7yCjDx5@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).