<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/board/rockchip, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-06-26T13:11:29Z</updated>
<entry>
<title>rockchip: rk3399: Fix enabling boot-on regulators</title>
<updated>2019-06-26T13:11:29Z</updated>
<author>
<name>Mark Kettenis</name>
</author>
<published>2019-06-21T20:57:20Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=7c7ce3600ae97b08f281a6b61aa4abb0b56b0658'/>
<id>urn:sha1:7c7ce3600ae97b08f281a6b61aa4abb0b56b0658</id>
<content type='text'>
The new common rockchip pinctrl driver does not support explicit
requests for a particular pinctrl function.  As a result, the
board_init() function bails out early before enabling the boot-on
regulators.  Fix this by simply removing the request for pwm0, pwm2
and pwm3.  The generic DM code already does the necessary
configuration if necessary.

Reported-by: Levin Du &lt;djw@t-chip.com.cn&gt;
Signed-of-by: Mark Kettenis &lt;kettenis@openbsd.org&gt;
</content>
</entry>
<entry>
<title>rockchip: rk3399: Support common spl_board_init</title>
<updated>2019-06-26T13:11:28Z</updated>
<author>
<name>Jagan Teki</name>
</author>
<published>2019-06-20T18:55:00Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=07586ee4322abca01db52624b925e5218538f259'/>
<id>urn:sha1:07586ee4322abca01db52624b925e5218538f259</id>
<content type='text'>
Support common spl_board_init by moving code from puma
board file into, common rk3399-board-spl.c.

Part of the code has sysreset-gpio, regulators_enable_boot_on
but right now only puma board is using this with relevant
config options rest remains common for all targets.

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>board: rk3399: Drop explicit uart enablement in spl_board_init</title>
<updated>2019-06-26T13:11:27Z</updated>
<author>
<name>Jagan Teki</name>
</author>
<published>2019-06-20T18:54:59Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=9f5a9f9ad3f96bd252b0d011ee4b6e89358ca494'/>
<id>urn:sha1:9f5a9f9ad3f96bd252b0d011ee4b6e89358ca494</id>
<content type='text'>
preloader_console_init is used for printing SPL boot banner that
usually called from spl_board_init.

The current spl_board_init in evb and rock960 is enabling explicit
pinctrl, debug uart prior to calling preloader_console_init which
eventually not required since board_init_f is already enabled
debug uart.

So, drop those explicit enablement calls from  spl_board_init of
evb, rock960.

Tested this by enabling CONFIG_SPL_BOARD_INIT and adding
u-boot,dm-pre-reloc property for uart node.

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>rockchip: rk3328: add rock64-rk3328_defconfig</title>
<updated>2019-06-26T13:11:26Z</updated>
<author>
<name>Matwey V. Kornilov</name>
</author>
<published>2019-06-08T21:27:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=57c4c5d3366b229bfc2228fd8029d06e627972a0'/>
<id>urn:sha1:57c4c5d3366b229bfc2228fd8029d06e627972a0</id>
<content type='text'>
The ROCK64 is a credit card size SBC based on Rockchip RK3328
Quad-Core ARM Cortex A53.

This series allow building u-boot SPL and u-boot.itb for Rock64
board. The proprietary TPL is stil required for deploy:

  ./tools/mkimage -n rk3328 -T rksd \
    -d ./rkbin/bin/rk33/rk3328_ddr_333MHz_v1.16.bin idbloader.img
  cat ./spl/u-boot-spl.bin &gt;&gt; idbloader.img
  dd if=idbloader.img of=/dev/sdcard seek=64 conv=notrunc
  dd if=u-boot.itb of=/dev/sdcard seek=16384 conv=notrunc

Signed-off-by: Matwey V. Kornilov &lt;matwey.kornilov@gmail.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>rockchip: rk3399: Add Rock PI 4 support</title>
<updated>2019-05-30T10:22:35Z</updated>
<author>
<name>Jagan Teki</name>
</author>
<published>2019-05-17T10:29:41Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=540c900dec8d9df50ac3344d26930ce50192497f'/>
<id>urn:sha1:540c900dec8d9df50ac3344d26930ce50192497f</id>
<content type='text'>
Add initial support for Rock PI 4 board.

Specification
- Rockchip RK3399
- LPDDR4
- eMMC
- SD card slot
- RTL8211E 1Gbps
- HDMI In/Out, DP, MIPI DSI/CSI
- PCIe M.2
- USB 2.0, USB-3.0
- USB C Type

Commit details of rk3399-rock-pi-4.dts sync from Linux 5.1-rc2:
"arm64: dts: rockchip: add ROCK Pi 4 DTS support"
(sha1: 1b5715c602fda7b812af0e190eddcce2812e5417)

Signed-off-by: Akash Gajjar &lt;akash@openedev.com&gt;
Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>rockchip: rk3399: Add Rockpro64 board support</title>
<updated>2019-05-30T10:22:35Z</updated>
<author>
<name>Jagan Teki</name>
</author>
<published>2019-05-17T10:29:40Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=001d6745e306ff7c1836ac1c0c8f352d54e2d010'/>
<id>urn:sha1:001d6745e306ff7c1836ac1c0c8f352d54e2d010</id>
<content type='text'>
Add initial support for Rockpro64 board.

Specification
- Rockchip RK3399
- 2/4GB Dual-Channel LPDDR3
- SD card slot
- eMMC socket
- 128Mb SPI Flash
- Gigabit ethernet
- PCIe 4X slot
- WiFI/BT module socket
- HDMI In/Out, DP, MIPI DSI/CSI, eDP
- USB 3.0, 2.0
- USB Type C power and data
- GPIO expansion ports
- DC 12V/2A

Commit details of rk3399-rockpro64.dts sync from Linux 5.1-rc2:
"arm64: dts: rockchip: rockpro64 dts add usb regulator"
(sha1: 6db644c79c8d45d73b56bc389aebd85fc3679beb)

'Akash' has sent an initial patch before, so I keep him as board
maintainer and I'm co-maintainer based on our conversation.

Signed-off-by: Akash Gajjar &lt;akash@openedev.com&gt;
Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>rockchip: rk3399: Add Nanopi NEO4 board support</title>
<updated>2019-05-30T10:22:35Z</updated>
<author>
<name>Jagan Teki</name>
</author>
<published>2019-05-17T10:29:39Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=48b5c25f99d2a45838e67e3b44a0b3eeae5d58a8'/>
<id>urn:sha1:48b5c25f99d2a45838e67e3b44a0b3eeae5d58a8</id>
<content type='text'>
Add initial support for Nanopi NEO4 board.

Specification
- Rockchip RK3399
- 1GB DDR3-1866
- SD card slot
- eMMC Socket
- RTL8211E 1Gbps
- AP6212 WiFI/BT
- HDMI In/Out, DP, MIPI CSI
- USB 3.0, 2.0
- USB Type C power and data
- GPIO expansion ports
- DC 5V/3A

Commit details of rk3399-nanopi-neo4.dts sync from Linux:
"arm64: dts: rockchip: Add Nanopi NEO4 initial support"
(sha1: 092470b537f19788d957aed12d835a179b606014)

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>rockchip: rk3399: Add Nanopc T4 board support</title>
<updated>2019-05-09T10:24:31Z</updated>
<author>
<name>Jagan Teki</name>
</author>
<published>2019-05-08T05:41:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=65cc7dcd77aef48ed20d73d17367e32f5cc4e8dd'/>
<id>urn:sha1:65cc7dcd77aef48ed20d73d17367e32f5cc4e8dd</id>
<content type='text'>
Add initial support for Nanopc T4 board.

Specification
- Rockchip RK3399
- Dual-Channel 4GB LPDDR3-1866
- SD card slot
- 16GB eMMC
- RTL8211E 1Gbps
- AP6356S WiFI/BT
- HDMI In/Out, DP, MIPI DSI/CSI, eDP
- USB 3.0, 2.0
- USB Type C power and data
- GPIO expansion ports
- DC 12V/2A

Commit details of rk3399-nanopc-t4.dts sync from Linux 5.1-rc2:
"arm64: dts: rockchip: Add NanoPC-T4 IR receiver"
(sha1: 95658e21b1707ad7844f873db2fdaa295109a5a3)

Tested-by: Daniel Gröber &lt;dxld@darkboxed.org&gt;
Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>rockchip: rk3399: Add Nanopi M4 board support</title>
<updated>2019-05-09T10:24:31Z</updated>
<author>
<name>Jagan Teki</name>
</author>
<published>2019-05-08T05:41:46Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=b2f5da9dd0689a718bf0c9dbfa48fedfce0bb336'/>
<id>urn:sha1:b2f5da9dd0689a718bf0c9dbfa48fedfce0bb336</id>
<content type='text'>
Add initial support for Nanopi M4 board.

Specification
- Rockchip RK3399
- Dual-Channel 4GB LPDDR3-1866
- SD card slot
- eMMC socket
- RTL8211E 1Gbps
- AP6356S WiFI/BT
- HDMI In/Out, DP, MIPI DSI/CSI
- USB 3.0 x4
- USB Type C power and data
- GPIO1, GPIO2 expansion ports
- DC5V/3A

Commit details of rk3399-nanopi-m4.dts sync from Linux 5.1-rc2:
"arm64: dts: rockchip: Refine nanopi4 differences"
(sha1: c62ffaf5026d0b7633e62b2cea8450b5543c349a)

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
Reviewed-by: Philipp Tomsich &lt;philipp.tomsich@theobroma-systems.com&gt;
</content>
</entry>
<entry>
<title>rockchip: evb-rk3229: add README file for OP-TEE support</title>
<updated>2019-05-08T09:34:12Z</updated>
<author>
<name>Kever Yang</name>
</author>
<published>2019-04-02T12:41:28Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=7c2a7542350ec8807f87417759f404f4865d6cdf'/>
<id>urn:sha1:7c2a7542350ec8807f87417759f404f4865d6cdf</id>
<content type='text'>
Detail of step by step to bring up the board with OP-TEE support.

Signed-off-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
</feed>
