Embedded_Projects/u-boot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: board: anbernic: Update rgxx3 to add new boards

Browse Source 
Update the RGxx3 documentation to note that it now supports the
RG-ARC-D, RG-ARC-S, Powkiddy RK2023, and Powkiddy RGB30. Also update
verbiage around panel detection to note that it is no longer hard coded
to the RG503.

Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
Reviewed-by: Kever Yang <kever.yang@rock-chips.com>
This commit is contained in:
Chris Morgan 2024-01-02 09:46:54 -06:00 committed by Kever Yang
parent 0cc6cbe84d
commit 350afb9752
1 changed files with 14 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/board/anbernic/rgxx3.rst
View File

@ -5,6 +5,8 @@ U-Boot for Anbernic RGxx3 Devices
This allows U-Boot to boot the following Anbernic devices:
- Anbernic RG-ARC-D
- Anbernic RG-ARC-S
- Anbernic RG353M
- Anbernic RG353P
- Anbernic RG353PS
@ -12,18 +14,24 @@ This allows U-Boot to boot the following Anbernic devices:
- Anbernic RG353VS
- Anbernic RG503
Additionally, the following very similar non-Anbernic devices are also
supported:
- Powkiddy RGB30
- Powkiddy RK2023
The correct device is detected automatically by comparing ADC values
from ADC channel 1. In the event of an RG353V or RG353P, an attempt
is then made to probe for an eMMC and if it fails the device is assumed
to be an RG353VS or RG353PS. Based on the detected device, the
environment variables "board", "board_name", and "fdtfile" are set to
the correct values corresponding to the board which can be read by a
boot script to boot with the correct device tree. If the board detected
is not of type RG503 (which currently has only 1 panel revision) a
panel detect is then performed by probing a "dummy" display on the DSI
bus and then querying the display ID. The display ID is then compared
to a table to get the known compatible string for use in Linux, and
this string is saved as an environment variable of "panel".
boot script to boot with the correct device tree. If a board is defined
as requiring panel detection, a panel detect is then performed by
probing a "dummy" display on the DSI bus and then querying the display
ID. The display ID is then compared to a table to get the known
compatible string for use in Linux, and this string is saved as an
environment variable of "panel".
FDT fixups are performed in the event of an RG353M to change the device
name, or in the event the panel detected does not match the devicetree.