PinePhone Pro hardware reference

This is the PinePhone Pro-only hardware entry point. The older combined hardware table remains as a quick cross-board manifest, but new board-specific work should link here or to the per-component pages under PinePhone Pro components.

Board Identity


Board	Pine64 PinePhone Pro
SoC	Rockchip RK3399S
Memory	4 GiB LPDDR4
Boot target	microSD first; SPI flash holds rk2aw + Megi U-Boot
Primary debug	3.5 mm UART at 1500000 baud, privacy switch #6 enabled
Current FreeBSD target	stable/15, arm64/aarch64, built with in-tree clang

Current Support Map

Area	Status	Notes
Boot / storage	● working	SD boot, eMMC access, repeatable local-to-honor build/deploy pipeline
USB management	● working	DWC3 gadget mode, CDC-Ethernet lifeline
Display / touch	● working	VOP -> DW-MIPI-DSI -> HX8394 panel, Goodix GT917S multitouch
GPU	◐ partial	Panfrost-backed Sway is usable; `glxgears` is the light sanity test and `glmark2` is the heavier historical stress benchmark; stress wedges remain under investigation
WiFi	◐ partial	BCM43455 joins WPA2, gets DHCP, uses SDIO IRQ mode, and runs at 50 MHz after discovery; remaining work is long-idle and broader AP/auth coverage
Bluetooth	● working	BCM4345C5 firmware load, SSP, AES-CCM, A2DP path proven
Audio	◐ partial	RT5640 + I2S0 loudspeaker playback is proven; internal DMIC capture/playback is confirmed on kernel `#190` with `div3/edge3/adc32`; earpiece, headset, HP detect, and modem call routing still need receipts
USB-C / charging	● working	FUSB302 PD sink, rk818 charger input-limit handoff, and battery charging work
USB-C host / DisplayPort	◐ partial	DWC3 host attach is bench-proven via `hw.dwc3.force_host=1`. FUSB302 source role enumerates a real downstream USB-C hub. With `hw.rk_typec_phy.usb3_enable=1` + the matching `flip` value, downstream USB-3 devices come up at SuperSpeed 5.0 Gbps; `axge(4)` brings the AX88179 up as `ue0`. Open: dynamic Type-C role-switch bridge that re-roles DWC3 and re-inits the phy from `fusb302(4)` (today `force_host` and `flip` are boot tunables), PD VDM / DP alt-mode, and a `cdn_dp` DRM bridge.
Modem	◐ partial	EG25-G powers up and answers AT; SIM/data/call policy pending
Sensors / input	◐ partial	SARADC buttons and raw sensor sysctls are alive; TSADC readout, soft CPU/GPU thermal caps, and guarded code-domain comparator IRQs work with hardware QSEL; hardware TSHUT and broader sensor UI policy remain open
Cameras / suspend	· not started	Cameras need V4L2/media/IOMMU work; suspend needs power-domain framework integration. The sysctl-only RK3399 power-domain driver exists but is disabled in the phone kernel.

Component Families

SoC foundation: RK3399S, CRU, pinctrl/GPIO, iodomain, SARADC, TSADC, eFuse, watchdog, DMA, IOMMU, VOP, USB2 PHY, TCPHY, DWC3.
Display: DW-MIPI-DSI, HX8394 panel, PWM backlight, VOP-Lit, optional/untested DW-HDMI sibling block.
Power and Type-C: RK818, SYR827/SYR828, FUSB302B, battery/charger path.
Wireless and modem: AP6255 module containing BCM43455 WiFi and BCM4345C5 Bluetooth, plus Quectel EG25-G over internal USB.
Sensors and controls: Goodix GT917S, MPU-6500, STK3311, AF8133J, SARADC volume ladder, GPIO keys, RGB LED, vibration motor.
Audio: RT5640 codec over I2S0 with AW8737/simple-amplifier speaker enable.

Board-Specific References

PinePhone Pro component matrix — status and links for every catalogued chip.
PinePhone Pro schematic support map — board-level grouping by function.
Where we are now — live subsystem snapshot.
What’s next — phone-first roadmap plus the PineTab2 phase boundary.